---
id: TST-COM-FUL-008
title: Merchandise import
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - >-
    modules/data-operations/tests/integration/services/operations/merchandise-import.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: >-
      modules/data-operations/tests/integration/services/operations/merchandise-import.integration.spec.js
    test_titles:
      - >-
        creates the option sets under the ids their lines name, a modifier set with its priced
        option
      - >-
        blocks an extension whose product nothing has loaded as dependency_missing, and writes
        nothing
      - >-
        creates the extension once the product is crosswalked: keyed by the product, its SKUs
        selecting the size set, the second’s image written as text
      - >-
        replaces the extension a second delivery of its key carries: the kept SKU keeps its id, the
        dropped one goes, the new one comes
      - >-
        refuses a variant selecting a value the set does not hold as that item’s invalid value,
        leaving the extension as it was
      - >-
        reads a load back by its keys in the shape the tool carried it: the extension with its 1.0
        id and its product’s source key
    scenario_anchors: []
---

# Merchandise import

## Verification Boundary

This suite checks merchandise import against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## What This Suite Proves

The suite’s source cases exercise the registered boundary, but this back-fill does not map them to a complete capability or feature scenario. The executable record remains useful without an invented scenario binding.

## What It Does Not Prove

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.