Name the systems of record
We list the storefront, payment gateways, tax services, ERP, WMS, and marketplace channels you actually use. Each row states which system owns order identity, stock quantity, and customer profile fields.
Integration Map
A practical walkthrough of how we chart commerce connectors before any remediation begins.
The map is the shared artifact between commerce leads and engineers. It names systems, data ownership, failure modes, and who must approve a change before it reaches production.
Trace one happy path and one failure path
A paid order that reaches the warehouse is drawn beside a payment retry, a partial shipment, and a cancelled line. Those sketches expose where webhooks fan out and where humans still patch data by hand.
Score connectors by blast radius
Severity ranks combine order volume affected, recoverability, and whether customers already see the problem. High-blast items move to the top of the remediation backlog without pretending every issue is equal.
Agree the next buildable slice
The readout ends with a slice your developers can ship in one release cycle: an idempotency guard, a reservation window, or a feed mapping table — not a multi-year platform rewrite.