The booking was confirmed on 12 September for a Ningbo sailing. The cargo ready date came and went. The purchase order in your ERP flipped to shipped, customer service gave a delivery week, and the container sat in the yard while two vessels sailed without it. Nobody misled you. The box was rolled, and the systems you watch do not publish anything until a container is loaded on board. By the time tracking woke up, you had lost eleven days and the promise you made was already wrong.
Why the origin leg is biting right now
Consecutive typhoons across the western Pacific have pushed berthing delays at Shanghai and Ningbo to as much as ten days, with vessel bunching and omitted calls spreading to Shenzhen and Hong Kong. Carriers have met softer demand by blanking between 18 and 25 percent of capacity on transpacific and Asia to Europe lanes, and Linerlytica has estimated that congestion is holding up 3.92 million TEU of vessel capacity.
Then there is the booking behaviour around Golden Week. Carriers overbook deliberately to protect themselves against last minute cancellations, and when factories finish on schedule the lower-yielding spot cargo is the cargo that gets rolled. That single decision adds seven to fourteen days of origin dwell that nobody planned for, and it repeats every cycle, which is why it is worth knowing how to plan around a factory shutdown at origin before the gates close. A blank sailing or an omitted port call at least arrives as a notice. A rollover usually does not.
The gap between "shipped" and "sailed"
Most supply chain records carry a status that flips at handover. The supplier confirms the goods left the factory, the forwarder acknowledges receipt, and the order moves to shipped. From that moment your planners, your customer service team, and your inventory projections all behave as though the goods are moving.
They are not moving. They are sitting in a container yard, and they will keep sitting there until a carrier decides to load them. Carrier tracking, meanwhile, generally starts publishing at loaded on board or at actual departure. So the exact window where the risk lives, between handover and departure, is the window with no events in it.
That gap is not a carrier failure. It is a data ownership problem: the party that knows the commercial status of the booking is not the party that publishes the physical milestones. Closing it means holding both sides on one record, which is what a command center like Orkestra is built to do. It normalizes booking and milestone data from carriers and forwarders into a single shipment record, so the origin leg carries events instead of a hole. The same discipline that makes carrier and forwarder tracking agree with each other is what makes the pre-departure window visible at all.
The milestones that already exist before departure
You do not need new telemetry to see the origin leg. You need to capture events that are already being generated and that most teams never bring into one place:
- Booking confirmation, with vessel and voyage. The baseline. Every later change is measured against this record.
- Cargo ready date. When the supplier says the goods are available. The clock on origin dwell starts here, not at departure.
- Gate-in at the container yard. The box is physically at the terminal. Strong evidence the delay is now commercial, not a factory problem.
- VGM submission. Verified gross mass filed. A booking without it will not load, so a missing VGM close to cut-off is an early warning you can act on.
- Export customs release. A hold at origin stops a container as effectively as a full vessel.
- Loaded on board, then actual departure. The two events most tracking treats as the start of the journey.
Captured together, those six events turn a blank stretch of the timeline into a sequence you can reason about. Gate-in three days before cut-off with no load confirmation after the vessel sails is not ambiguous. That is a rollover, and you can see it without anyone telling you.
What a rollover looks like in the data
Rollovers announce themselves quietly, in field changes rather than notifications. The vessel name or voyage number on a confirmed booking changes. The estimated departure slips by exactly one service frequency, usually seven days. A booking amendment appears with no covering explanation. The container shows gate-in, and the vessel it was booked on departs without a corresponding load event.
Any one of those is a signal. The problem is that they are field-level changes buried inside portals and email threads, which is a large part of why 62 percent of supply chain exceptions are detected only after they have already reached the customer. Nothing about a rollover is technically hidden. It is just that no one is watching the right field at the right hour, on a few thousand bookings at once.
This is where detection has to stop being a person's job. When a vessel change on a confirmed booking automatically opens a case, attaches the affected purchase orders, and assigns it to the planner who owns them with a clock attached, the discovery happens on the day it occurs rather than the week the goods fail to arrive. OIA Global cut exception resolution time by 60 percent in a single quarter by working exceptions that way, as cases with owners rather than alerts that pile up in an inbox.
Make origin dwell a number you actually track
Teams measure transit time obsessively and origin dwell almost never. Define it simply: the days between cargo ready date and actual departure. Then track it three ways.
By lane, so you know that Ningbo to Los Angeles is currently running eight days of origin dwell while Busan runs three, and your promise dates can reflect that. By forwarder, because roll rates and how early you hear about them vary enormously between partners. By supplier, because a consistently optimistic cargo ready date is its own problem and worth separating from carrier behaviour.
Once you hold that number, several arguments get easier. Your ETA accuracy across carriers improves immediately, because a large share of arrival error was never a transit problem at all, it was time the cargo spent not moving before the journey started. Quarterly reviews with forwarders get specific. And the case for booking earlier, or for paying for guaranteed loading on genuinely critical cargo, stops being a hunch and becomes a cost you can put next to the premium.
What to do when the box is rolled
Detection only matters if the response is already decided. Agree the sequence before you need it.
Confirm the new vessel and voyage, and get the revised departure in writing rather than as a verbal reassurance. Identify which purchase orders and SKUs are inside the container, since the commercial impact is never evenly spread across a box. Tell customer service before the customer asks, with a revised date rather than an apology. Decide whether any part of the shipment justifies expediting, and make that call against the value of what is late rather than the size of the delay. Finally, check whether the same lane has other bookings exposed to the same cut-off, because rollovers rarely arrive one at a time. When several land at once, rank them by the cost of waiting instead of working the list in the order it appeared.
Where to start this week
Pick one high-volume origin. Pull every booking confirmation for the last sixty days, add the gate-in and departure events, and calculate origin dwell for each. You will almost certainly find that the average is higher than the number in your planning assumptions, and that a small group of shipments carries most of the damage.
That exercise is worth doing by hand once. It is not worth doing by hand every week, and it does not survive a bad month at the origin, which is precisely when you need it. The value of an operational layer over your existing systems is that the origin leg stops being something you reconstruct after the fact and becomes something you watch, on the same record that carries the shipment after it arrives at the destination port. The journey has two ends, and only one of them is usually instrumented.
If your record still goes quiet between handover and departure, that is the next gap worth closing. Get full visibility across the whole shipment, not just the part that happens at sea.
