# Draft and independently activate a shop mapping

Bind a saved SKU table version, status effects and independently expected StoresFlow quantities.

Source: https://help.smartfact.ai/manuals/configsheets/shop-mappings

Review edition: 25 October 2026

Roles: author, reviewer

Shop mappings define how WooCommerce identities and statuses become retained stock terms. Saving a SKU table is not activation of that mapping. An Author prepares an exact release and an independent Reviewer checks and activates it.

## Prepare the exact mapping

Open Shop connections and Draft a mapping release. Choose Saved SKU table version and the intended order-status effects. Check exact shop SKU, target item and conversion meaning. Preserve original text and units instead of treating similar-looking codes as interchangeable.

Enter Expected examples and expected StoresFlow quantity independently of candidate calculations. Cover ordinary deductions, non-deducting statuses, conversions and relevant refusals. A passing example copied from actual output cannot establish the intended mapping.

Choose Save mapping draft. Give the Reviewer the source basis, exact version, expected quantities and intended effect on existing orders. A later edit to the reference table does not silently update this retained release.

## Review every relevant page

The Reviewer prepares the release preview and inspects SKU changes, unmapped SKUs, changed orders, order-line comparisons and retained mappings. Use the paged controls for the complete review scope. Check both old and proposed conversions and why an existing line retains its original terms.

Inspect contributor independence and the expected-example results. If the source or cases need correction, return to the Author's drafting workflow. Do not adjust expectations merely to agree with the candidate.

## Activate and inspect the effect

Complete the review acknowledgement and reason, then Activate reviewed mapping with the required current authority and recent second-factor check. Read the accepted release state. Activation and an individual order's delivery remain separate events.

Ask Operators and Supervisors to inspect orders needing mapping or attention under the current release. Historical accepted line terms and their originating events remain traceable. Use [Review shop orders and delivery](/manuals/configsheets/shop-orders) for the operational follow-through, including receiver outcomes and original-event recovery when an answer is uncertain.