Name the stock system of record first

The owner must define states, movements, locations, availability, corrections, traceability, integrations, reconciliation, cutover, and acceptance evidence before choosing an implementation.

Short answer

No packaged inventory or WMS module was established in the reviewed default product evidence

Catalog, sales shipments, carrier adapters, integrations, data sync, workflows and app-local module conventions can surround an external or custom stock system. Reviewed evidence does not show on-hand truth, availability, movements, warehouse work, traceability, or valuation. A downstream app, provider, external official module, private extension or later release may supply them; this review did not cover that code.

Reviewed
2026-07-14
Revision
01911d00e28f44cf484d0b1d04860dcfef5370bf (v0.6.5-1202-g01911d00e)
Latest tag and npm core
v0.6.5 · 0.6.5

The feat/wms changelog reference covers CI branch matching only. It proves no shipped WMS behavior or roadmap commitments.

Capability and evidence boundary

available

Product identity

Catalog products, variants, SKUs and human-readable keys

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Catalog products, variants, SKUs and human-readable keys
Release/current
released/current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Product master remains separate from stock truth
Owner
Product-data steward
Limitation
Not a balance, movement, lot, serial or location
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

configurable

Units and conversions

Catalog unit records and conversion controls

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Catalog unit records and conversion controls
Release/current
released/current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Define warehouse units and rounding explicitly
Owner
Product and stock owner
Limitation
Does not prove physical quantity
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

available

Order demand

Sales order-line quantity

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Sales order-line quantity
Release/current
released
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Demand record only
Owner
Sales owner
Limitation
Not on-hand or available-to-promise
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

custom

Reserved quantity field

Order-line reservedQuantity initialized or preserved

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Order-line reservedQuantity initialized or preserved
Release/current
current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
A stock system must own holds, expiry and release
Owner
Stock owner
Limitation
No general reservation engine established
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

available

Fulfilled quantity

Recomputed from sales shipment items

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Recomputed from sales shipment items
Release/current
current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Order-scoped fulfillment record
Owner
Sales owner
Limitation
Not warehouse confirmation or stock deduction
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

configurable

Sales shipment record

Multiple order-scoped shipment records and items

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Multiple order-scoped shipment records and items
Release/current
released/current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Reference external warehouse evidence
Owner
Sales owner
Limitation
No physical movement follows automatically
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

configurable

Shipment status

Configurable labels including picking, packed and shipped

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Configurable labels including picking, packed and shipped
Release/current
released
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Confirm the work behind each label
Owner
Operations owner
Limitation
A status does not perform work
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

integration-required

Carrier rates

Provider adapter rate contract

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Provider adapter rate contract
Release/current
released/current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Configured provider required
Owner
Carrier owner
Limitation
Not stock availability
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

integration-required

Label and tracking

Carrier create, label, track, cancel and verified webhook seams

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Carrier create, label, track, cancel and verified webhook seams
Release/current
released/current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Provider acknowledgement and reconciliation required
Owner
Carrier owner
Limitation
Not WMS or packing-station execution
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

custom

Low-stock subscriber

Notification type and subscriber for catalog.product.stock_low

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Notification type and subscriber for catalog.product.stock_low
Release/current
current seam
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
No runtime producer or threshold source found
Owner
Application owner
Limitation
Operational detection not established in reviewed evidence
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

integration-required

External integration and data sync

Manifests, credentials, mappings, runs, workers and logs

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Manifests, credentials, mappings, runs, workers and logs
Release/current
released/current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Provider-specific objects and contract required
Owner
Integration owner
Limitation
No ready WMS mapping established
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

configurable

Workflow orchestration

State, tasks, timers, signals and activities

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
State, tasks, timers, signals and activities
Release/current
released/current
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Orchestrate only around a stock authority
Owner
Process owner
Limitation
Does not create a stock ledger
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

custom

Custom app module

Official tutorial proves app-local module conventions

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
Official tutorial proves app-local module conventions
Release/current
released tutorial/current framework
Evidence conclusion
bounded surface established
Prerequisite and system-of-record implication
Application owns ACL, data, APIs, migrations, tests and operations
Owner
Application owner
Limitation
Tutorial CRUD is not production inventory
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

custom

Stock ledger

No packaged reviewed inventory module

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
No packaged reviewed inventory module
Release/current
not established
Evidence conclusion
not established in reviewed evidence
Prerequisite and system-of-record implication
Design movements, balances, atomicity and correction
Owner
Stock owner
Limitation
Not established in reviewed default package evidence
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

integration-required

Physical warehouse execution

No packaged reviewed WMS module

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
No packaged reviewed WMS module
Release/current
not established
Evidence conclusion
not established in reviewed evidence
Prerequisite and system-of-record implication
Retain specialist system or build bounded controls
Owner
Warehouse owner
Limitation
No bins, waves, counts or scanner work established
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

integration-required

Inventory valuation

No reviewed costing ledger

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
No reviewed costing ledger
Release/current
not established
Evidence conclusion
not established in reviewed evidence
Prerequisite and system-of-record implication
Finance system and valuation authority required
Owner
Finance owner
Limitation
No valuation outcome established
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

integration-required

Procurement dependency

No reviewed procurement stock flow

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
No reviewed procurement stock flow
Release/current
not established
Evidence conclusion
not established in reviewed evidence
Prerequisite and system-of-record implication
Contract with purchasing authority
Owner
Procurement owner
Limitation
Supplier records or events are insufficient
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

integration-required

Manufacturing dependency

No reviewed production consumption flow

Manager question
What record, action and external evidence does this layer actually own?
Evidence surface
No reviewed production consumption flow
Release/current
not established
Evidence conclusion
not established in reviewed evidence
Prerequisite and system-of-record implication
Contract with manufacturing authority
Owner
Manufacturing owner
Limitation
No BOM or consumption outcome established
Confidence, source and date
high · source at 01911d00e28f44cf484d0b1d04860dcfef5370bf · 2026-07-14

Each record has a distinct purpose

Product master, order demand, reserved quantity, available-to-promise, on-hand stock, stock movement, sales shipment, carrier execution, financial valuation and external acknowledgement require different authorities and evidence. Catalog products, variants, units, dimensions, availability dates, shipping flags, prices, and offers serve as commercial records. They do not hold warehouse balances, movements, reservations, lots, serials, or locations.

The catalog form has draft values for manageInventory, allowBackorder and hasInventoryKit. Their reviewed controls are disabled and say Inventory tracking controls are not available yet. Reviewed evidence contains no persisted configuration for them. A low-stock notification type and subscriber exist. Operational detection still lacks a reviewed runtime producer and threshold source. sales reservedQuantity does not provide a reservation engine. fulfilledQuantity is recomputed from shipment items and proves order fulfillment tracking. It does not prove stock deduction.

Stock system-of-record decisions

  • physical operations
  • system of record
  • sites, zones and bins
  • item and unit identity
  • reservation and availability
  • lots and serials
  • expiry
  • valuation
  • procurement
  • manufacturing
  • scanner or offline work
  • volume and concurrency
  • existing WMS
  • regulatory traceability
  • integration latency
  • recovery
  • accountable operators

Outcome 1

Retain and integrate an external ERP or WMS

Choose when an existing specialist system owns physical operations, locations, traceability, allocation or valuation. Require stable keys, direction, latency, idempotency, ordering, acknowledgement, outage behavior and reconciliation.

Outcome 2

Build a bounded app-local inventory module

Choose only for a deliberately constrained movement set with explicit ownership, atomic invariants, ACL, tests, migrations, backup, recovery and expansion stops.

Outcome 3

Use a deliberately simple quantity register

Choose only after a control review proves that no warehouse, reservation, traceability, valuation or high-concurrency outcome is required. A mutable quantity still needs correction and audit rules.

Outcome 4

Stop or defer

Stop when specialist WMS depth is required, stock authority is undefined, controls are unowned, integration evidence is missing or cutover cannot be reconciled safely.

Tutorial versus production control ledger

SKU and name

Production decision: Stable business identity, alias, merge, lifecycle and downstream reference policy.

One mutable integer quantity

Production decision: Immutable movement identity, atomic balance invariant, correction or reversal and duplicate protection.

Free-text location

Production decision: Governed site, zone, bin hierarchy, stable keys and transfer semantics.

CRUD API

Production decision: Commands, authorization, idempotency, concurrency, audit, recovery and reconciliation.

Simple form

Production decision: Role-specific work, validation, approvals, scan/offline needs and exception handling.

App-local module

Production decision: Ownership of ACL, scope, migrations, workers, integrations, operations, upgrades and retirement.

The official tutorial creates an app-local inventory module with SKU, name, one mutable quantity, free-text location, CRUD and forms. It proves module conventions only. Directly editing one quantity does not provide a generally safe perpetual-stock design. Require a movement or transaction model, derived balances or a justified alternative, atomic invariants, duplicate protection and accountable correction.

Warehouse control map

1. item identity

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

2. units and conversions

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

3. locations, zones and bins

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

4. stock states

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

5. movement types

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

6. receipts

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

7. issues

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

8. transfers

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

9. adjustments

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

10. reservations

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

11. allocation

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

12. availability

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

13. negative-stock policy

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

14. picks

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

15. packs

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

16. shipments

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

17. returns

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

18. counts

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

19. replenishment

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

20. lots

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

21. serials

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

22. expiry

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

23. quarantine

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

24. damaged stock

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

25. valuation boundary

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

26. suppliers and purchasing

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

27. manufacturing consumption

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

28. scanners and offline work

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

29. permissions

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

30. concurrency

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

31. integration

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

32. reconciliation

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

33. audit evidence

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

34. observability

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

35. recovery

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

36. operating ownership

Define the business rule and expected evidence; identify the current Open Mercato contribution, custom or integration work, system owner, failure risk, acceptance test and stop condition. Mark not applicable explicitly when justified.

Responsibility, integrity, cutover and operation

Named responsibilities

  • product-data steward
  • stock controller
  • warehouse operator
  • warehouse supervisor
  • sales owner
  • integration owner
  • application owner
  • security owner
  • finance or valuation owner
  • external-system owner
  • adjustment or emergency approver

Movement integrity

  • immutable movement identity
  • source and destination
  • quantity and unit
  • reason
  • effective and recorded time
  • actor or service identity
  • correlation and idempotency keys
  • reference document
  • lot or serial when applicable
  • balance impact
  • reversal or correction linkage
  • audit evidence

Concurrency and failure challenges

  • duplicate receipt
  • duplicate order event
  • simultaneous allocation
  • overship attempt
  • stale balance
  • negative-stock race
  • partial transfer
  • lost acknowledgement
  • out-of-order update
  • worker outage
  • provider timeout
  • replay
  • manual correction
  • failed reconciliation

Migration and cutover

  • source inventory
  • item and location identity mapping
  • unit normalization
  • opening balances
  • open orders and reservations
  • in-transit stock
  • lots and serials
  • history window
  • trial loads
  • count freeze
  • parallel run
  • reconciliation tolerances
  • go or no-go authority
  • rollback
  • post-cutover physical verification

After launch

  • exception queues
  • backlog and lag
  • reconciliation schedule
  • count variance
  • negative availability
  • unprocessed movements
  • provider health
  • alert thresholds
  • correction authority
  • runbook
  • recovery drill
  • evidence retention
  • owner and backup owner

Three synthetic operating examples

Hypothetical only

Hypothetical external-WMS distributor

The worksheet exposes Open Mercato contribution, external or custom stock truth, identity, operational control, failure and recovery, reconciliation evidence, owners and a stop.

Hypothetical only

Hypothetical bounded custom stock ledger

The worksheet exposes Open Mercato contribution, external or custom stock truth, identity, operational control, failure and recovery, reconciliation evidence, owners and a stop.

Hypothetical only

Hypothetical specialist WMS required

The worksheet exposes Open Mercato contribution, external or custom stock truth, identity, operational control, failure and recovery, reconciliation evidence, owners and a stop.

Local planning tool

Stock system-of-record worksheet

Field completeness shows planning progress. It does not confirm WMS selection, readiness, compliance, or fit.

Do not enter real data: Do not enter real item, SKU, stock, lot, serial, warehouse, bin, supplier, customer, order, employee, endpoint, credential, cost, valuation, capacity, SLA, incident or regulated traceability data. Use abstract labels only.

Privacy: The page does not send worksheet content, put it in the URL, or store it in cookies.

Required-field progress: Not started (0/24). This count tracks field completion. It does not score fit or determine readiness.
Planning row 1

Manager acceptance pack

1. normal receipt

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

2. allocation

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

3. pick

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

4. shipment

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

5. return

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

6. transfer

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

7. adjustment

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

8. count

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

9. duplicate

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

10. concurrency

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

11. wrong organization

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

12. unauthorized adjustment

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

13. invalid unit

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

14. missing item

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

15. stale product reference

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

16. lost provider acknowledgement

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

17. delayed sync

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

18. out-of-order event

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

19. external outage

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

20. partial cutover

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

21. reconciliation mismatch

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

22. negative-stock policy

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

23. lot or serial mismatch

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

24. manual recovery

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

25. post-cutover physical verification

Use synthetic identities, authorized and denied actors, expected movement and balance, duplicate and failure behavior, external acknowledgement, reconciliation evidence, cleanup and a recovery owner.

Stop conditions

  • high-complexity warehouse execution.
  • automated material handling.
  • regulated traceability without validated controls.
  • advanced wave or labor planning.
  • offline scanning without architecture.
  • real-time allocation without consistency guarantees.
  • undefined valuation.
  • no reconciliation owner.
  • no safe cutover path.
  • no accountable stock system owner.

Method and limitations

Evidence was refreshed at the exact revision across default and documented module inventories, package version, catalog UI and persistence, low-stock runtime search, sales quantities and shipment commands, carrier adapters, integration and data-sync seams, workflows, and the app-local tutorial. External WMS contracts, provider packages, concurrency, valuation, traceability, procurement, manufacturing, scanners, performance, legal controls, cost, timing, support and roadmap remain deployment-specific or not established.