Two chokepoints are squeezing at once. The Panama Canal cut allowable drafts to 49.0 feet on July 24, with a further reduction to 48.5 feet scheduled for August 15, and Suez transit surcharges rose roughly 12% this month — while Drewry's World Container Index sat at $4,530 per 40ft container in early July and peak-season surcharges started on eastbound transpacific services (as reported by Kisun Shipping's July outlook and Transport Intelligence's July risk monitor).
If you move ocean freight on affected lanes, none of this stays abstract. Draft restrictions mean lighter loads or re-routed vessels; re-routed vessels mean schedule changes, transshipments, and rolled cargo (the same mechanics behind blank sailings and port omissions); and every one of those becomes an exception with your company's name on it: a purchase order that will land late, a customer promise that needs re-setting, a booking that needs to move.
What the next six weeks look like operationally
Based on how previous canal restrictions have played out, expect four waves:
1. ETA drift before anyone announces anything. Carriers re-plan quietly. The first sign is usually not a notice — it's ETAs on in-transit shipments slipping in ways the schedule doesn't explain. If nobody is watching ETA changes systematically, you learn about the problem from your customer.
2. A re-booking wave. Some share of planned sailings won't work — too deep, too delayed, or rolled. Those bookings need to move to other services or modes, quickly, while everyone else's freight team is trying to do the same thing. The teams that move in the first days get space; the teams that find out in week two pay for it.
3. Detention and demurrage exposure. Queues and transshipment congestion mean containers waiting — and waiting containers accrue charges. (If the difference between the two charge types is fuzzy, we wrote a plain-language explainer: demurrage vs. detention.)
4. The cost reconciliation. Surcharges, re-bookings, premium space, and charge disputes all land on the freight bill weeks later. Finance will ask what happened; the teams that tracked decisions as they were made will have an answer.
The playbook: run it as a case wave, not an inbox wave
The difference between operations that absorb a chokepoint event and operations that get absorbed by it is not information — everyone reads the same advisories. It's ownership. The playbook:
Triage by business impact, not by lateness. A shipment that's five days late but feeds a well-stocked DC is noise. A shipment that's two days late and feeds a production line or a retail promotion is the priority. That ranking requires connecting shipments to the orders and inventory behind them — which is exactly what a supply chain control tower is for.
Give every affected shipment an owner and a decision. Re-book, re-route, expedite the critical subset, or accept the delay and re-promise. Each is a legitimate decision; what's not legitimate is the un-decision that lives in a reply-all thread. One owner, one recorded decision per exception.
Communicate downstream before the customer notices. A re-promise delivered proactively costs goodwill; a broken promise discovered by the customer costs the relationship. The teams that do this well have the customer-facing impact list generated from the same system that tracks the exceptions.
Log the costs as they happen. Every surcharge and expedite tied to the event, tagged at decision time — so the post-event review is a report, not an archaeology project. Our cost-reduction guide covers why this discipline pays for itself.
Where Orkestra fits
This playbook is manual torture over email and portals, and routine on an orchestration layer: Orkestra watches ETA changes across your carriers, ranks affected shipments by the orders behind them, assigns owners, and tracks every decision and cost — on top of the ERP, TMS, and WMS you already run. One customer, a multi-client 4PL, cut exception resolution time by 60% running exactly this motion. If the August draft cut is about to become your team's problem, a 30-minute call this week beats a war room next month.
