Blank sailings explained: what they do to throughput counts

When a carrier cancels a scheduled port call outright, pulls a string from the rotation, or skips a port on a loop, that's a blank sailing. Desks also call it a void sailing or a capacity withdrawal, and all three mean the same thing: a vessel that was supposed to show up on the berth schedule simply doesn't.

Carriers do this to defend freight rates when demand softens, after a holiday slows factory output, or when an alliance restructures a loop. The periodic reshuffles inside 2M's successors, Ocean Alliance, and THE Alliance all produce rounds of them. Golden Week blanks out China-origin strings every year. Chinese New Year does the same, on a bigger scale. None of this is secret. Carriers file blank sailing notices weeks ahead, and the weekly trackers that compile them turn those filings into a tally of cancelled strings per trade lane.

The problem for anyone nowcasting throughput is that the notice tells you a ship isn't coming. It doesn't tell you what that does to the yard.

Why a cancelled string doesn't translate cleanly into box counts

A blanked sailing removes capacity from a lane, but the cargo booked onto it doesn't vanish. Shippers roll bookings to the next available string, consolidate into fewer, fuller vessels, or shift the freight to a different carrier entirely. So a port can post a quieter month of vessel calls while stack density on the ground barely moves, because the boxes that would have spread across three ships get absorbed into two.

The reverse happens too. A round of blank sailings announced for August can get partially reinstated in July once a carrier sees spot rates firm up, and the schedule change shows up in vessel arrivals before anyone updates a tracker. AIS only catches a ship once it's within range of a receiver, which is late if you're trying to read a trend two or three weeks ahead of it landing in customs data. Carrier schedule filings and void notices are directional for capacity. They're not a count of what's actually sitting on the apron.

Reading stacks and anchorage queues instead of a schedule PDF

What moves first, before a blanked sailing or a reinstated one ever shows up in the official numbers, is the yard itself. A terminal absorbing rolled cargo starts stacking higher ahead of the next confirmed call. An anchorage queue thins out when fewer ships make their berth windows, even if the printed schedule still lists them. None of that depends on a carrier's notice being accurate or current, or on anyone updating a spreadsheet of cancelled strings.

That's the gap a daily image pass closes. Trade Flow Index builds a time series from container stack counts, vessel calls, and anchorage queues at named ports, so a desk can see whether throughput at a given terminal is falling off in step with announced blanks, or whether volume is just getting repacked onto fewer hulls while the port runs as busy as ever. It's a read on what's physically there, independent of whether a carrier followed through on a schedule change or quietly walked one back a few weeks later.

For a trade-flow desk, that distinction matters more than the blank sailing count itself. A string of cancellations tells you carriers expect softer volume. A stack count tells you whether that softness has landed at the berth, or whether it's still three weeks out and priced in early.

If you're trying to close the gap between a carrier's blank sailing notice and what's piling up dockside, that's the use case Trade Flow Index is built around.