Supply chains rarely fail all at once. A supplier misses a production slot, a vessel loses its place in a port queue, or a warehouse system goes offline. By the time customers see empty shelves, the useful decision window may already have closed. The 2021 Suez Canal blockage, the 2022 U.S. infant formula shortage, and the 2017 NotPetya attack on Maersk each began at a different kind of weak point. All exposed dependencies that were hard to replace quickly.

Business continuity is therefore less about predicting the next shock than knowing what can stop the business, how long it can absorb the loss, and who is authorized to act. The strongest plans connect supplier data, inventory, transport, quality, IT, and customer communication before any of them becomes an emergency.

Navigating Supply Chain Disruptions Business Continuity Case Studies

1) What breaks first: failure modes, signals, and time-to-recover

The first sign is often an exception rather than a shutdown: a supplier repeatedly revises its promised date, lead times spread beyond their normal range, or a carrier misses several cutoffs. Those signals matter because average lead time can still look acceptable while the worst deliveries exhaust safety stock.

A McKinsey analysis published in 2020 estimated that supply interruptions lasting a month or longer occurred every 3.7 years on average across the industries it studied. That is a planning estimate, not a forecast for any one company. A more useful question for an operations team is which specific outage its network cannot outlast.

Two measures make that question concrete. Time-to-recover, or TTR, is the time a disrupted site or supplier needs to restore usable output. Time-to-survive, or TTS, is how long downstream operations can meet demand without that output. If a sole-source component takes eight weeks to restore and available stock lasts three, the business has a five-week gap to close through an approved substitute, another production site, or a change in customer allocation.

Calculate those measures for physical sites and shared services. A second supplier is little protection if both plants depend on the same specialist ingredient, power substation, or transport corridor. An enterprise resource planning system can be a single point of failure, too: goods may exist, but teams may be unable to see stock or release orders.

2) Case-based lessons: ports, plants, and platforms under stress

A blocked canal turns transit time into an inventory problem

When the Ever Given blocked the Suez Canal in March 2021, a UN maritime logistics case study recorded 367 vessels held up by the end of the rescue phase. A shipper could not simply decide to use the Cape of Good Hope and expect an immediate fix. Rerouting meant checking vessel position, customer delivery dates, available capacity, and the cost of a longer voyage.

That is the practical lesson: an alternate route is useful only if someone has worked out when to use it. For a high-priority shipment, an early diversion or change of carrier may protect a delivery date. For lower-priority goods, accepting a delay may cost less. The plan should give the team authority to make that distinction.

The disruption did not end with Suez. During the Red Sea attacks, IMF data showed Suez Canal trade volume fell 50% year over year in the first two months of 2024; diversion around the Cape added 10 days or more to delivery times on average. In 2026, disruption in the Strait of Hormuz showed how a chokepoint can also affect inputs far beyond ocean freight: UN Trade and Development identified risks to energy and fertilizer flows. Teams responsible for imported materials need to watch fuel, packaging, and upstream production costs as well as the position of their own containers. Trade policy and its effects on local economies add another layer to those sourcing decisions.

A plant closure exposes the limits of substitution

The U.S. infant formula shortage shows why a backup source must be more than a name on a supplier list. On February 17, 2022, Abbott Nutrition recalled certain products and stopped production at its Sturgis, Michigan, facility. The FDA’s evaluation of its response found that the recall and shutdown placed further strain on an already stressed supply chain, including supply of specialty formulas.

A manufacturer facing this kind of failure cannot treat an untested recipe or an unapproved site as an instant substitute. Food safety, product suitability, production capacity, and distribution all have to be resolved. The FDA’s long-term infant formula strategy addresses both contamination prevention and greater diversity of supply. A July 2026 FDA call for stronger ingredient-supplier oversight reinforced the point: continuity cannot come at the expense of product safety.

Deep-tier suppliers and utilities can stop a factory

After the 2011 earthquake and tsunami in Japan, Toyota found damage extending well beyond its direct suppliers. Its account of the response identified 659 damaged supplier sites, including secondary and deeper-tier sites. Toyota later reported mapping suppliers through the fourth tier and working to spread sources for vulnerable parts and use more standardized designs. Recovery depended on finding exactly which parts were affected, how much inventory remained, and whether production could move—not merely knowing that a supplier had a disaster plan.

Utilities deserve the same attention. During Taiwan’s 2021 drought, TSMC arranged alternative water sources and controls for water delivered by truck. For a chipmaker, water quality is part of the production specification. A backup source that cannot meet that specification is not a backup. The case illustrates a broader rule for critical inputs: test both availability and usability.

A cyberattack can immobilize freight without touching a vessel

Maersk’s June 2017 NotPetya attack disrupted its transport and logistics businesses. The company reported losses of roughly $250 million to $300 million, including lost revenue, restoration costs, and extraordinary operating costs. Its incident account describes systems being shut down and operations gradually returning; vessels remained under control.

The distinction matters. A cyber continuity plan must identify which commercial tasks can be done manually—accepting bookings, confirming cargo, contacting terminals—and how those records will be reconciled when systems return. A shipper’s own plan should also consider the loss of a carrier or third-party logistics provider’s systems. The growth of integrated networks makes that dependency worth examining alongside the benefits described in Amazon’s logistics transformation.

3) Building resilience that earns its cost

Continuity spending should protect a defined service commitment, not buy redundancy everywhere. Start with the products whose loss would cause the greatest harm or commercial damage. For each, compare the cost of a shutdown with the cost of a few more days of inventory, a qualified second source, spare tooling, or reserved freight capacity. The cheapest buffer depends on how quickly each option can actually be used.

Supplier diversification helps only when the risks are independent. Two contract manufacturers may share a specialty resin producer; two shipping options may depend on the same strait. The Black Sea Grain Initiative made corridor dependence visible: the UN reported that its designated route carried nearly 33 million metric tons of grain and other foodstuffs before the arrangement ended in July 2023. A sourcing map should show the route and underlying inputs, not just the supplier’s headquarters.

A workable program has five parts:

  • Map critical products through at least the second supplier tier where feasible, recording production sites, unique processes, utilities, and transport routes.
  • Estimate TTR and TTS, then assign a decision trigger before TTS is exhausted.
  • Qualify alternatives in advance. Engineering, quality, regulatory, and customer approvals can take longer than finding a supplier willing to quote.
  • Put surge capacity, tooling access, and data-sharing expectations into agreements where they matter. Test the capacity behind the promise.
  • Protect order and inventory data. The CISA ransomware guide recommends offline, encrypted backups and regular restoration tests.

That work should produce a short response playbook: who checks the facts, who can authorize extra spending or a substitute, and when customers receive a revised delivery date. If every exception must wait for a meeting, the trigger was set too late.

4) Measuring readiness: KPIs, trade-offs, and governance

On-time-in-full delivery shows the customer outcome, but it does not show whether the network is one outage away from missing it. Pair service measures with indicators such as the share of critical parts with a qualified alternate, days of usable stock at exposed nodes, supplier recovery time, and the time required to restore essential ordering systems. Count alternates that have passed the necessary tests, not those merely listed in a database.

Failure mode What the case reveals Readiness test
Canal or corridor disruption A longer route changes delivery dates and inventory needs Can the team price and approve a reroute before the stock buffer runs out?
Single-plant shutdown Available capacity elsewhere may not produce an approved substitute Has the alternate site or product cleared quality and other required reviews?
Deep-tier supplier or utility loss Direct suppliers may share an unseen dependency Can planners identify affected products and usable stock within hours?
Logistics-system outage Freight can stall while physical assets remain intact Can teams transact manually and reconcile records afterward?

A tabletop exercise should test those questions with real decision-makers, not just the continuity team. Give the group a supplier outage and a port delay on the same day. Ask it to identify affected orders, authorize a response, contact partners, and tell customers what is known. Then run a separate technology drill: a tabletop discussion cannot prove that backups restore or that a manual booking process works. CISA’s continuity guidance distinguishes tabletop reviews from partial- and full-function recovery exercises for that reason.

Finance should review the trade-offs after each drill and real incident. If extra inventory prevented one missed sale but expired on the shelf, its location or quantity may be wrong. If a second source exists but cannot take an order for six weeks, the company has purchased less protection than its dashboard suggests. Assign owners to close those gaps, with dates, rather than filing the exercise as complete.

Customer communication belongs in the same playbook. Give a credible delivery window, explain when the next update will come, and offer a suitable substitute where one exists. Start the continuity review with one important product family and one exposed route. Once the team can show that its alternatives work under test, extend the method to the rest of the network.