Weather risk is procurement risk: a sourcing contingency playbook

This month it is Hurricane Isaias. FreightWaves reported on October 7 that the storm was forecast to reach Category 2 or 3 and make landfall between Houston and the Florida Panhandle, with up to six Gulf refineries in its path, tender rejections of 17% to 19% in New Orleans, Mobile and Montgomery, and delays possible at the ports of Mobile and New Orleans. Every hurricane season brings a similar story. Procurement teams read it as a logistics problem. It is not. It is a sourcing problem that happens to surface at the port.

The distinction matters. If weather is a logistics problem, the fix is a faster carrier, an air freight upgrade, a demurrage line item. If weather is a sourcing problem, the fix is upstream: dual origin, buffer stock positioned on the right side of the chokepoint, contract clauses that do not collapse the first time a factory loses power for 72 hours. Only the second approach actually protects a launch date.

The real cost of a weather event is never the freight bill

A major storm hitting the US Gulf Coast can push up diesel prices and truckload spot rates on affected lanes for a few weeks, and tender rejections rise as shippers rush freight out ahead of landfall. Those costs are real, but for most B2B sourcing programmes they are small against the landed cost of goods.

The expensive line is elsewhere. It is the retail promotion that goes live without stock. It is the trade show booth that opens on Tuesday with empty shelves. It is the influencer drop whose unboxing window closes before the pallet clears customs. None of those costs appear on a freight invoice, which is exactly why they rarely get modelled before the event.

Weather does not create new risk in a supply chain. It exposes the single points of failure that were already there.

Four weather exposures a sourcing team should actually track

Not every climate headline is actionable. These four are, because each one maps to a specific decision a buyer makes months before the event:

• Atlantic hurricane season (June to November): affects Gulf refineries, Houston, Savannah, Charleston, and the inland trucking network that feeds Southeast DCs.
• Western Pacific typhoon season (May to October): affects Yantian, Ningbo, Shanghai, Kaohsiung, and the Vietnam coastal corridor from Haiphong down to Ho Chi Minh.
• South Asian monsoon (June to September): affects Mumbai, Mundra, and the ground transport windows between inland factories and the coast.
• Heat and drought on inland waterways: low water on the Rhine and Yangtze and draft restrictions at the Panama Canal have repeatedly cut capacity in recent years.

A buyer sourcing promotional goods from Guangdong for a European Christmas window can face the first three exposures in sequence between production and arrival. That is the sort of stacked risk a contingency playbook needs to make visible.

What a contingency playbook actually contains

A playbook is not a document that lives in a shared drive and gets opened once a year. It is a set of pre-decided actions, each tied to a trigger and an owner. The minimum useful version has five layers:

1. Origin diversification mapped to seasonality

If 100 percent of a SKU ships from Shenzhen in September, that is a typhoon bet, not a sourcing strategy. The fix is not to abandon the primary supplier. It is to qualify a secondary origin in a different weather basin (Vietnam, Turkey, India, or Italy depending on category) and route a meaningful share of volume through it during the exposed months. The premium is real, and so is the insurance.

2. Buffer stock on the right side of the chokepoint

Three weeks of safety stock sitting in a Chinese 3PL does nothing if the typhoon closes Yantian. The same three weeks sitting in a bonded warehouse in Jebel Ali, Rotterdam, or an East Coast FTZ changes the outcome entirely. The question is not only how much buffer, but where.

3. Pre-negotiated force majeure language

Most standard supplier contracts treat weather as an automatic get-out clause for the factory. A better contract defines what the supplier owes when a named storm hits: prompt notification, a documented impact assessment within a few days, and a replan with a committed recovery date. Without that structure, the buyer absorbs 100 percent of the schedule risk by default.

4. A pre-approved air freight budget per SKU

Air is the recovery tool, not the plan. But if nobody has pre-approved the delta between sea and air for the critical SKUs, the decision will be made under pressure in a Friday afternoon email thread, and it will be made badly. Approve the ceiling in advance; use it only when triggered.

5. A monitoring layer beyond the news

Hurricane coverage on general news is a trailing indicator. By the time a storm has a name on the front page, the forwarders are already booked out. The useful signals come earlier: official forecast models several days out, port congestion data, and direct updates from the supplier on its operating status.

Build it into the RFQ

Most of these decisions are cheapest to make before an order is placed. When you send an RFQ, ask each factory for its location and weather exposure, its fallback plan, and lead times for both sea and air. This is the kind of check Opifix builds into every RFQ, alongside quotes that include freight and duty.

The procurement team owns this, not logistics

The uncomfortable organisational conclusion is that weather risk belongs in the procurement team's remit, not the freight team's. Logistics can execute the recovery, but only sourcing can design the structural resilience: the dual origin, the buffer location, the contract language, the air budget. Any company that keeps punting these decisions to its forwarder will keep paying for them in missed launches.

The next named storm will arrive on schedule. The question is whether it finds a procurement function that has already made its decisions, or one that is about to make them under duress.