A rollover means your container did not sail on the vessel it was booked on — the carrier left it behind at origin or at a transshipment hub, almost always without telling you first. It is discovered, not announced: the box shows a discharge event at the hub, the booked onward vessel departs, and no load event ever appears. On weekly service loops a missed sailing typically costs 7–10 days. The response that protects the relationship: catch the mismatch, re-baseline the ETA, and tell your customer with the new plan attached — before they book a trucker against the old one.
Why doesn’t anyone warn you?
Because rolling is a vessel-planning decision, not a customer-service one. Overbooked allocations, weight and stability cut-offs, missed connections at the hub — the container that loses that arithmetic simply stays on the quay, and no advance notice is the norm. During the 2020–21 capacity crunch, rollover rates at major transshipment hubs ran 28.5–39% (Ocean Insights data — crisis-era history, not today’s baseline, but proof of how routine the practice becomes when ships are full). If you are waiting for the carrier to tell you, you will hear it from your customer first.
How is a rollover actually detected?
From the event trail. A transshipped box should show a matched pair: discharged from the first vessel, loaded onto the booked second one. When the discharge event lands and the booked vessel then sails without a load event for your container, that’s a rollover — announced or not. This is exactly what the desk watches for across carrier sources, continuously: it catches the discharge/load mismatch, classifies the exception as a roll, and starts the re-plan while the old ETA is still the one everyone downstream is working to. The full detection flow is on how it works.
What does a missed sailing cost?
Most deep-sea services run weekly loops, so the next vessel is about seven days out — add re-planning and space at the hub and 7–10 days per missed sailing is the working number. The clock damage is only the start: your customer’s trucker is booked against the dead ETA, their warehouse slot is reserved for a box that is still on a quay in the transshipment port, and their own customer is holding a production plan built on your date. Put your shipment volumes against the one-in-three delay reality in the calculator and the exposure gets concrete quickly.
What should the customer note say?
- What happened, plainly: “your container was rolled at the transshipment hub” — the real exception class, not a generic “delay”.
- The new plan: the vessel it will now sail on and the re-baselined ETA, stated as the new working date.
- What changes for them: rebook the trucker, move the delivery window — spelled out so nobody has to derive it.
- What you’re watching: the load event on the new vessel, confirmed the moment it happens.
That note, sent before the question, is the difference between a forwarder with a problem and a forwarder in control of one. The desk drafts it with the event history attached and your team approves it before it leaves the building. The full exception taxonomy — rolls, blanks, holds and the rest — is in the complete guide.
Put the watch on your boxes.
Everything on this page runs live in a working tracking desk. Bring ten shipments on the water and watch the updates land before the questions do.
Book the working session