What a booking roll does to your cargo's ETA
A booking roll is when the carrier confirms your container has space on a vessel, then pulls it off that sailing before it loads and puts it on a later one. The booking still exists. The vessel it was supposed to sail on doesn't have your box anymore.
This is different from the container just sitting in the yard a day or two longer than planned. A roll means you missed the entire sailing. On a weekly string that's roughly seven days added to your transit, assuming space actually opens up on the next voyage. If the lane is running tight, your container can get rolled twice in a row.
Why carriers roll bookings in the first place
Carriers overbook on purpose. Every string has a no-show rate, cargo that gets canceled, delayed at origin, or rerouted, and carriers sell space against that assumption the same way airlines oversell seats. Most of the time it works out. When a lane is busier than forecast, or a blank sailing cancels a voyage mid-string, there isn't enough room for everyone who booked, and something has to come off.
What comes off first is usually freight-all-kinds cargo booked through a forwarder on standard terms. Reefer, named-account volume, and anything with contractual priority tends to stay on. If you're shipping FAK on spot or short-term rates, you're closer to the front of the line for a roll, not the back of it.
A vessel omit makes this worse at a specific port. When a carrier skips a scheduled port call entirely, usually to recover schedule after delays upstream, every booking tied to that call gets rolled at once, not just the marginal ones. If your port of loading gets omitted, you're not competing for the last few open slots. You're competing with the entire sailing's worth of cargo for space on whatever comes next.
How you find out
There's rarely a clean notification that says "your booking has been rolled." More often it shows up as a vessel name change on the booking confirmation, a cargo cutoff that quietly moved, or your container failing to show as loaded on the vessel schedule you were tracking. Forwarders sometimes catch it before you do because they're pulling carrier EDI feeds directly. If you're relying on the booking confirmation PDF from two weeks ago, you can be a week behind the actual status.
By the time most planners confirm a roll happened, the slip has already eaten into the buffer they built into the PO date. The real cost is that the added transit days show up as a surprise instead of a number you'd planned around.
What moves the needle on ETA
The lanes that roll bookings aren't random. A string running near full utilization, a terminal with chronic berth delays, or a port working through a yard backlog all produce more rolls than a lane with slack in the schedule. The signals are usually visible before the roll happens, vessel queues stacking up outside the terminal, yard dwell climbing on inbound boxes, berth windows slipping voyage over voyage. The booking roll is often just the downstream symptom of congestion that's been building on that specific lane for a week or two.
That's the piece most schedule tools don't give you. A generic "port congestion is elevated" alert doesn't tell you whether your specific lane, the one with your actual inbound volume on it, is running three days behind or three weeks behind. Lead Time Risk turns that congestion into a day count for the lanes you've registered, so instead of guessing how much buffer a roll-prone lane needs, you have a number to plan against.
If you're tired of finding out about a roll after it's already cost you a sailing, it's worth checking what your registered lanes are running behind by, in days.