Problem
An ecommerce business runs a storefront, an ERP, and a messaging channel — and treats them as separate worlds. Orders are re-typed, stock drifts, and status lives in a chat thread.
Root Cause
The systems were connected at the field level (sync product names, sync prices) instead of at the process level. Field sync keeps copies in agreement; process sync keeps the operation moving.
Architecture
Everything orients around the order lifecycle: checkout → record → payment → reserve stock → confirm → fulfill → dispatch. Each transition in one system triggers the next in another, with the order as the shared identifier.
Solution
An integration pipeline listens for order events, creates the ERP record, reserves inventory, and triggers customer communication from live state. The website, the ERP and the messaging channel all read from the same order story.
Implementation
We build the storefront-to-ERP sync first and validate it with test orders. Inventory sync follows, then the communication layer. Each stage is observable before the next one is added.
Trade-offs
Event-driven pipelines add moving parts: retries, idempotency, failure queues. The cost is justified because it removes the manual hand-offs that the team was already paying for in time and errors.
Verification
The integration is healthy when an order can move from checkout to dispatch without a human touching any of the three systems, and when a failure produces an alert instead of a silent drift.
Lessons
Do not ask 'which systems must sync'. Ask 'what happens to an order at every step'. The order is the unit of truth — build around it and the manual steps disappear.
Galaxy DigiLabs · Engineering Notes
All Notes →