---
id: JNY-COM-FUL-006
title: Implementation staff load and reconcile Commerce history
feature: FEAT-COM-FUL-05
product_area: commerce
module: fulfillment
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
supersedes: []
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
actor: ACT-COM-009
goal: >-
  Validate historical Commerce imports, apply reviewed impact and reconcile
  source identities.
capabilities:
  - CAP-COM-FUL-020
screens: []
steps:
  - 'n': 1
    surface: submitStoreDataJob (validate)
    action: Submit the first collection for validation while the workspace is loading.
    capability: CAP-COM-FUL-020
    expected: 'A validation job exposes its state, counts and inspection reference.'
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/e2e/data-jobs.e2e.spec.js#accepts
      the validation, answering the job validating, its counts and where to read
      it
  - 'n': 2
    surface: getStoreDataJob
    action: Inspect validation completion.
    capability: CAP-COM-FUL-020
    expected: Impact is available without application writes.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/e2e/data-jobs.e2e.spec.js#reads
      the job back once its batch has run: validated, its impact one create,
      nothing applied
  - 'n': 3
    surface: applyStoreDataJob
    action: Apply the reviewed job using its digest.
    capability: CAP-COM-FUL-020
    expected: Queued batches execute toward completion.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/integration/services/jobs/data-jobs.integration.spec.js#applies
      the validated job echoing its digest: queued, one batch on the queue table
      for the dispatcher
  - 'n': 4
    surface: 'listStoreDataJobResults, listStoreDataJobRejections'
    action: Read result and rejection pages.
    capability: CAP-COM-FUL-020
    expected: Item positions retain outcomes and refusal details.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/e2e/data-jobs.e2e.spec.js#pages
      the job’s results and rejections by position
  - 'n': 5
    surface: readStoresBySourceKey
    action: Reconcile loaded records through original source keys.
    capability: CAP-COM-FUL-020
    expected: Readback returns imported shapes and identifies unmatched keys.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/e2e/data-jobs.e2e.spec.js#answers
      the key missing before the apply, and the store as its load carried it
      once the job is applied and run
  - 'n': 6
    surface: 'submitOrderDataJob, submitInventoryItemDataJob …'
    action: Load the remaining declared collections in dependency order.
    capability: CAP-COM-FUL-020
    expected: >-
      Historical orders retain delivery states and stock opens through
      movements.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/integration/services/operations/order-import.integration.spec.js#creates
      one obligation per item line in its final state: completed and open for
      the fulfilled line, blocked for the other
alternates:
  - from_step: 3
    condition: A referenced record has not been loaded.
    path: Classify the item as waiting on a missing dependency.
    outcome: The cited test proves dependency waiting without an item write.
    provenance: test
    source: >-
      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
failures:
  - from_step: 3
    condition: The application request uses another digest.
    path: Reject the impact mismatch.
    outcome: Application does not proceed under that digest.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/integration/services/jobs/data-jobs.integration.spec.js#refuses
      an apply that echoes a digest other than the validation recorded,
      impact_digest_mismatch
  - from_step: 1
    condition: The workspace is already live.
    path: Reject initial-import submission.
    outcome: No initial import is accepted.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/integration/services/jobs/data-jobs.integration.spec.js#is
      refused for a tenant that is live
rules_in_play:
  - BR-CAP-COM-FUL-020-03
  - BR-CAP-COM-FUL-020-05
  - BR-CAP-COM-FUL-020-07
  - BR-CAP-COM-FUL-020-10
  - BR-CAP-COM-FUL-020-11
assertions:
  - id: AS-JNY-COM-FUL-006-01
    statement: Validation records impact without applying records.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/integration/services/jobs/data-jobs.integration.spec.js#validates
      without writing: the submission validating, its one batch run, the job
      validated with its impact one create
  - id: AS-JNY-COM-FUL-006-02
    statement: Applied records are reconciled using their source-key readback shapes.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/e2e/data-jobs.e2e.spec.js#answers
      the key missing before the apply, and the store as its load carried it
      once the job is applied and run
  - id: AS-JNY-COM-FUL-006-03
    statement: Repeated source identities do not create another imported record.
    provenance: test
    source: >-
      services-commerce:modules/data-operations/tests/integration/services/operations/order-import.integration.spec.js#refuses
      the same key loaded again as that item’s invalid value, writing nothing
e2e_policy: none
e2e_reason: >-
  This backend migration workflow is exercised through job operations and has no
  console journey surface requiring browser proof.
evidence:
  - >-
    services-commerce at c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b: the
    end-to-end and integration suites named in the step and assertion sources.
  - >-
    react-console at baf6dae382d6f41dce976c7f848667ccc37e076f: the console pages
    and adapters named in the steps.
proved_by: []
---

# Implementation staff load and reconcile Commerce history

## Story

Implementation staff validate prepared collections before applying their reviewed impact. They inspect item outcomes and use original source keys to reconcile the result. Related records can remain waiting on dependencies, and the loading lifecycle keeps this work distinct from ordinary live selling.
