← Back to Supply Chain Review Ports & Infrastructure

Ningbo reopens 13 July after Bavi; backlog lingers at Shanghai

Source: Everstream Analytics · 2026-07-13 · 6 min read
中文

Supply Chain Action Points

Read this first — the conclusion, and the moves to make:

  1. By 16 July 2026, pull every Transpacific booking with a vessel cut-off between 10 and 24 July and rank them by whether they were rolled, using your own container events rather than waiting for a carrier notice.
  2. Before 20 July, secure a second allocation on a different string for the top 20 percent of volume by value, and set a written premium ceiling tied to one week of lost margin.
  3. Set the internal recovery trigger at gate-in throughput returning to the pre-closure level for three consecutive days, not at the reopening announcement.
  4. By 31 July 2026, ask each carrier on the affected strings for a dated recovery schedule and amend the port-closure clause to require that schedule within 48 hours of reopening.
  5. Hold three extra days of cover for the last week of July only, and put a named owner and a 1 August release date on it.
Skip to the detailed analysis ↓
Summary

Everstream and Hapag-Lloyd indicate the Port of Ningbo reopened on 13 July after the 10–13 July Typhoon Bavi closure, but lingering vessel backlogs and high yard utilization will take days to clear. Shanghai continues to recover from prolonged terminal closures, with rollover risk on Transpacific cargo persisting into the following week.

The Analysis

Two dates stand at the front of this story and only one of them made the headline. The closure ran from 10 July and the port reopened on 13 July. Everstream and Hapag-Lloyd both point at the 13th, because the 13th is the day the gate lifted and the notice changed. The other date is the one nobody can print yet, because nobody knows it: the day the last box that was sitting offshore on the 13th finally clears the yard.

A port reopening and a port recovering are two different events, and the gap between them is where the money gets decided. Ningbo is open, with vessel backlogs and high yard utilisation that will take days to work down. Shanghai is still climbing out of a longer closure. Transpacific cargo faces rollover risk into the following week. Read as three sentences, that is a status update. Read as one system, it is a queue that has not finished moving.

A gate lifting is an administrative act. A yard draining is a physical one. The terminal can declare itself open on the 13th and be entirely correct while the boxes that arrived during the closure sit in the same stack they occupied on the 12th. Nothing about the reopening changes the number of boxes on the ground. It only changes the rate at which they can leave, and that rate was set long before the typhoon by cranes, trucks, barges and the people who drive them.

The size of a backlog is not proportional to the length of the closure, which is the first thing people get wrong when they build a recovery estimate. A four-day interruption does not produce four days of delay. It produces a queue whose length depends on how much was arriving each day, and whose drain time depends on how much spare capacity the terminal has once it is also handling today's arrivals. A terminal running at its practical ceiling has no spare capacity. That is what high yard utilisation means in plain language: the terminal is already using the room it needs in order to catch up.

Shanghai and Ningbo are being reported as two stories and they are one. They pull from the same hinterland. The barges, the trucks, the rail slots and the feeder vessels that evacuate Ningbo are the same pool Shanghai has been drawing on through its own, longer closure. Shanghai has been in that pool first and has not finished. So Ningbo's recovery does not begin from a clean sheet on the 13th. It begins by competing for a corridor that is already loaded. Two recovery curves that look separate on a chart are, underneath, one curve.

This is the part I would underline, because it changes what you do next. The published reopening date is the least useful number in the story. The useful fact is the ordering: Shanghai first, Ningbo second, same corridor. That means the binding constraint on how fast your cargo moves is not Ningbo's berths. It is the shared evacuation capacity of the delta, and no press release can make that capacity larger. It also means the rollover risk on Transpacific cargo is not really a berth story at all. Rollover happens at the booking layer. The boxes that missed their vessel are now hunting allocation on ships that were sold out before the typhoon arrived, which is exactly why the risk is described as running into the following week. Physical recovery and commercial recovery are on two different clocks, and the second one is the one your customer calls about.

Who hurts first is the shipper holding a Transpacific booking whose cut-off fell inside the closure window. Not necessarily the largest account, but the one with the least room to move on the sailing it was counting on. Who feels almost nothing is the importer whose cargo was already at sea before 10 July, and the shipper moving on a premium service with a guaranteed slot. The middle of the market, the ordinary weekly booking that assumes the vessel it was quoted is the vessel it will get, is where rollovers concentrate.

Timing is where intuition usually fails. The physical clearing starts on the 13th and is visible within days. The commercial consequence lands later, roughly one to two weeks out, when the rolled boxes come back into the market for space and meet an allocation that has already been consumed. The week of the reopening is quiet. The last week of July is loud. That is the opposite of how it feels on the day the notice changes.

Ten years out, this is a pulse. The delta's port hierarchy, the depth of the channel, the position of Ningbo and Shanghai in the transpacific string, none of that is being renegotiated by one typhoon. What accumulates is a habit. Every closure of this kind teaches carriers to price the tail of the distribution a little more carefully, and teaches shippers to stop treating a reopening notice as a recovery signal. That habit is what remains after the water goes down, and it is the only part of this that is structural.

Run the drain arithmetic with numbers I am choosing, because the update publishes no throughput. Assume a terminal holding three days of accumulated arrivals on the ground at reopening. If it can work at 1.5 times the normal daily arrival rate, a 50 percent headroom, the net drain is half a day of arrivals per day and the backlog clears in about six days. If it can only manage 1.25 times, the drain is a quarter of a day per day and the clearing takes twelve. The second number matters more than the first, because on the sixth or seventh day the next vessel arrives. A terminal that needs twelve days does not clear; it meets the next wave and the queue changes shape rather than shrinking. That is the difference between a backlog and a regime.

The trap is reading 13 July as an all-clear and releasing your own contingency on the 14th. The second trap is assuming the carrier's recovery plan and your recovery plan are the same document. They are not. The carrier's plan restores a rotation. Your plan has to protect a delivery date, and the two overlap only for as long as the rotation holds.

↑ Back to the key points

— By Tomás Ferreira