← ← Back to Supply Chain Review Ports & Infrastructure

Typhoon Saudel shutters Shanghai and Ningbo; ~90 vessels queued as Far East congestion persists

Source: Freightos / WIGO Logistics · 2026-09-25
Summary

Typhoon Saudel closed ports including Shanghai and Ningbo for several days last week, disrupting operations as far north as Busan and threatening Shenzhen later. The succession of storms since mid-July has left as many as 90 ships waiting more than a week for a berth in Shanghai, with carriers skipping calls at backed-up ports and pushing transhipment volumes to other regional hubs. Far East congestion is also feeding into Asia-Europe rate levels.

Supply Chain Action Points

Typhoon Saudel is the latest in a chain of storms that has kept the Far East congested since mid-July, and the operational lesson for importers and exporters is that 'closed for a few days' understates the damage. When Shanghai and Ningbo shut, the backlog does not clear the moment the wind drops - it takes days to absorb the pile-up, and the next storm arrives before the port fully recovers. With as many as 90 vessels waiting over a week for a berth in Shanghai, the constraint is no longer the ship; it is the terminal and the truck.

Understand the mechanism before you plan around it. A typhoon closure is not a clean two-day pause. Ports close, vessels divert or wait at anchor, and once the storm passes the terminal must work through a mountain of delayed boxes while new arrivals keep coming. The succession of storms since mid-July means affected ports have rarely had a clean window to clear backlogs. The reported figure of ~90 ships waiting more than a week for a slot in Shanghai is the symptom; the cause is cumulative, not single-event. Busan was disrupted as far north as the storm track reached, and Shenzhen was threatened later, so this is a regional Far East problem, not a single-port one.

For an exporter, the immediate exposure is the booked sailing that quietly gets skipped. When a port is saturated, carriers omit calls there and shift volume to other regional hubs, which then get congested in turn. Your container can sit in a closed or jammed port while the vessel sails without it. The fix is visibility: get from your forwarder the actual vessel cutoff and the contingency routing if your load port is omitted, and do not treat 'booked' as 'will sail'. For cargo already in transit, expect transhipment at an unexpected hub and add that to your lead-time math. A box that was supposed to go Shanghai direct may land via Busan or Kaohsiung, and each extra leg is days you did not plan for.

Importers feel this as delayed receipts and a mismatch between the arrival date they promised their customer and the one the vessel will actually make. Build the buffer into the purchase order, not the apology. If your supplier's goods are due to leave a Far East port in the storm window, add 7-10 days of contingency to every downstream commitment - production line feeding, e-commerce fulfilment, retail shelf date. A delayed container that misses a launch is far more expensive than a small amount of safety stock held a little earlier. Put the contingency number in writing in the commercial agreement so the late-delivery risk is owned, not argued about later.

There is also a cost layer beyond delay. Congestion feeds into rates: when capacity is trapped in queues, effective supply drops and the Asia-Europe corridor in particular has repriced on every congestion scare this year. Even if your lane is not the one physically closed, the network effect raises the cost of the box you do get. Treat any storm-window quote as provisional and reconfirm it at vessel cutoff.

Finally, paperwork discipline protects you when things go wrong. Keep bills of lading, delay and omission notices clean and timely. A missing or late delay notice is exactly what a carrier or insurer will point to when you file a force-majeure or delay claim. The teams that recover costs after a storm are the ones that documented the disruption on the day it happened, not the ones that reconstructed it from memory a month later.

When the delay is unavoidable, how you communicate it determines whether you keep the account. Notify the customer the moment the omission or delay notice lands, with a revised ETA and the contingency routing, rather than letting them discover it from a late container. Put a delay-SLA clause in the commercial agreement that triggers a pre-agreed remedy - a small credit, a free next shipment, or a rate concession on the recovery leg - so the conversation is about service recovery, not blame. On the inventory side, the cheapest insurance is a small, deliberate safety-stock pre-position: holding a little extra at the destination DC before the storm window costs far less than a missed launch or a ruptured production line. If working capital is tight, negotiate a short transit-based payment term with the supplier so you are not paying for goods sitting in a jammed port. And keep a single source of truth - one shared tracker showing each shipment's actual status, not three email threads with conflicting ETAs. The storm is exogenous; the confusion around it is not, and the confusion is what costs you the relationship. The relationship cost of a missed delivery almost always exceeds the freight saving from a few days of delay, so protect the customer timeline first.

  • Treat 'booked' as 'may be omitted' during storm windows; get the vessel cutoff and contingency routing from your forwarder in writing.
  • Add 7-10 days of contingency to every downstream commitment for cargo leaving a Far East port in the typhoon window.
  • Expect transhipment at unexpected hubs and rebuild lead-time estimates around the new routing, not the planned direct service.
  • Map alternate exit ports (less-affected gateways) now for standard FCL, before the next storm hits, and pre-clear them with your buyer.
  • Keep bills of lading and delay notices clean and timely to defend against force-majeure and delay claims.
  • Reconfirm any storm-window quote at vessel cutoff; treat it as provisional, not fixed, because congestion reprices the box.

— 作者 Leo

Read original article →