---
id: TST-COM-FUL-007
title: Inventory 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/inventory-import.integration.spec.js
implements:
  - ATS-COM-FUL-016-08
  - ATS-COM-FUL-017-12
  - ATS-COM-FUL-020-09
  - ATS-COM-FUL-020-10
  - FAS-COM-FUL-05-02
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/inventory-import.integration.spec.js
    test_titles:
      - >-
        creates the warehouse and its locations under the ids their lines name, through the
        inventory persistence
      - >-
        opens the mug’s item through the ledger: a count correction of twelve and a damage of two,
        so the trigger holds ten available
      - >-
        opens the cap’s item under the product’s own SKU at the default location, with no movement
        for a count of nought
      - 'refuses the same key loaded again as that item’s invalid value, moving nothing'
      - >-
        refuses an item at an inactive location as that item’s refusal, as the implicit creation
        would
      - >-
        reads a load back by its keys with what each item opened with, its 1.0 id and its product’s
        source key
    scenario_anchors:
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/inventory-import.integration.spec.js#opens
        the mug’s item through the ledger: a count correction of twelve and a damage of two, so the
        trigger holds ten available
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/inventory-import.integration.spec.js#opens
        the cap’s item under the product’s own SKU at the default location, with no movement for a
        count of nought
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/inventory-import.integration.spec.js#refuses
        the same key loaded again as that item’s invalid value, moving nothing
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/inventory-import.integration.spec.js#refuses
        an item at an inactive location as that item’s refusal, as the implicit creation would
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/inventory-import.integration.spec.js
---

# Inventory import

## Verification Boundary

This suite checks inventory 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. Time-sensitive cases use a controlled clock where the source fixture supplies one.

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