iCommerce Scenarios and Examples

Choose tested native workflows, isolated simulations, and qualified storefront or external integrations.

Start from an executable example for your actual interface. A protocol demonstration, isolated native scenario and production external integration have different evidence scopes.

Scenario	Start here	Verify
Local commerce state	Quickstart	Exact amount and second-process persistence
Governed action/retry	Kernel example	No preview effect; same receipt after restart
Full-order physical stock	Stock fulfillment	On-hand and allocated balances, safe repeat
Shipment tracking	Fulfillment	Enforced states and version guards; actual carrier evidence separate
Replenishment/cash policy	Native simulations	Assumptions, paths, exact cash/stock reconciliation and goal status
Storefront checkout	Starter	Launch config and private native journey; settlement qualification separate
Procurement/receiving	Supplier, receiving	Native PO/receipt states and actual stock effect
Customer returns	Returns	Receipt/disposition/completion/refund boundaries
OMS/WMS/TMS integration	System ownership	Actual connector outcomes and physical custody
Response-loss recovery	HTTP receipts	Original key, pending status and verified operator evidence

Source examples

The 1.39 source checkout provides cli/examples/commerce-scenario.json, inventory-plan.json, and experiments for demand spikes, supplier schedules, purchasing constraints, minimum cash, cash reserves, product service goals and review intervals. Run native inputs through stateset-simulate and inspect all result/reconciliation fields. They do not use a live business store or transfer money.

cli/examples/durable-merchant.mjs is a loopback protocol reference with simulated balances; native-merchant.mjs needs an explicit native integration and operator-owned authority. A signed protocol response does not prove a provider settled or an ERP accepted an order.

Keep qualification attached to the exact artifact

Record source/package/binary, backend, policy, assumptions and retained results. Source tests, local execution, published packages, release CI, external acceptance and production operating objectives are separate observations. The source release-evidence matrix still requires scoped independent review, live-provider and durability/soak evidence.