A shipment control design that joined bookings, milestones, documents and carrier updates while leaving source systems in place.
Shipment status was scattered across a booking application, carrier portals, clearing records, driver messages and document folders. Customer service staff spent much of each day asking for updates, then translating those updates into a status that customers could understand. Different teams used the same milestone words for different events, so a dashboard could look current while the underlying evidence was stale.
The work centred on a canonical shipment timeline. It did not try to turn every partner into a real-time API provider. Each source entered through the mechanism it could reliably support: webhook, scheduled pull, file exchange or operator confirmation. The platform recorded the source and observation time of every milestone, which allowed operators to distinguish a recent confirmed event from an old inferred status.