---
id: TST-COM-FUL-005
title: Catalog 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/catalog-import.integration.spec.js
implements:
  - ATS-COM-FUL-020-06
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/catalog-import.integration.spec.js
    test_titles:
      - >-
        creates the categories under the ids their lines name, through the catalog persistence, and
        updates one its key names again
      - >-
        blocks a listing whose product nothing has loaded as dependency_missing, naming the product
        source key, and writes nothing
      - >-
        creates the listing once the product is crosswalked: keyed by the product, published, its
        1.0 id kept, its sale window set aside
      - >-
        reuses the 1.0 stored image in place (the same reference, never copied) and makes the
        gallery’s staging upload permanent
      - >-
        writes the shelves the line names with the positions the tool computed, not the appended
        ones
      - >-
        replaces the listing a second delivery of its key carries: unlisted, off one shelf, its
        gallery gone, its position moved
      - 'writes the crosswalk once per key, the listing’s pointing at its product'
      - >-
        reads a load back by its keys in the shape the tool carried it: the listing with its
        positions, its 1.0 id and its product’s source key
    scenario_anchors:
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/catalog-import.integration.spec.js#blocks
        a listing whose product nothing has loaded as dependency_missing, naming the product source
        key, and writes nothing
---

# Catalog import

## Verification Boundary

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

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## 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.