Case study
When commerce systems do not share a record
Orders, customers, catalog, fulfillment and payments were all “integrated.” Operators still rebuilt the truth by hand.
Before
A media and entertainment operation running orders through OMS, CRM, PIM, fulfillment, payments and internal tools. Each system had an owner. None of them had the whole order.
Friction
Flows between those systems lacked traceability, retries, idempotency and a log someone would actually read. When something failed, teams reprocessed by hand and argued about which record was current.
Result
Connected flows with traceability and a shared way to see a failure. Less manual rework between areas, and technical decisions that could be tied back to the operation instead of to a local backlog.
The company did not lack integrations. It lacked a contract for what an integration was allowed to do when it failed. Messages moved. Confidence did not.
The design work was unglamorous and specific: identify the critical flows, give each one a trace, make retries safe, and log in a way an operator can use at 7 p.m. without calling the person who wrote the connector.
That is the pattern I still look for in commerce and operations stacks. A diagram of arrows is not a system. A system can explain a failed order without a meeting.