The end-to-end flow, milestones, and the event model that reports it.
3 questions in Logistics & Supply Chain.
It depends entirely on where it stopped, because silence is normal on a long line haul and alarming between two hand-offs that should be minutes apart. The design that answers it is an expected next event with a deadline per milestone, rather than a threshold on time since the last scan.
Model the journey as milestone events, each carrying both the time it happened and the time you recorded it, and derive current status by projecting that set in a fixed milestone order rather than storing a mutable column, because events arrive late, twice and in the wrong sequence.
The split forces order, shipment and parcel apart as separate entities with their own promises, money and tracking, so a single order status stops being expressible. Model the promise per line, capture funds per despatch, and give the customer a page that reads as one order made of several deliveries.