This is our Shopify↔ERP sync design as a live simulation: the store and ERP are simulated, the algorithms are real. Break things with the buttons. Duplicate webhooks, ERP outages and malformed events never oversell; a corrupted store count can, until the nightly reconciliation finds it — which is why it runs.
ERP UPLoading simulation…
0oversold orders
0events applied
0duplicates ignored
0queue depth / age
0store API calls
0dead-lettered
Stock: ERP truth vs what the store shows
SKU
ERP
Store
State
Last reconciliation
not run yet — it's the nightly safety net, not the mechanism
Event journey (receipt is not processing)
Tick
Event
SKU
Status
What this is: a Veldway reference design running as a deterministic simulation — the store and ERP are
simulated; the idempotency, available-to-sell targets, batching, outage-queueing, validation and reconciliation logic is
real and unit-tested (a property test checks every sale against an independent stock ledger, not against the engine's
own counter, and the ERP is allowed to go below zero so an oversell can't be hidden). Not a client project.
Design write-up: veldway.com/work/shopify-erp-inventory-sync ·
Source: github.com/veldway/live-demos ·
veldway.com