Force Majeure Clauses in Vendor Contracts: What They Cover in a Supply Disruption

A force majeure clause excuses a party from performing its contract obligations when a genuinely unforeseeable event, outside either party’s control, makes performance impossible or impracticable. For a medical-supply or lab-equipment buyer, the clause matters most in exactly one moment: a vendor invokes it and stops shipping, and you need to know fast whether that invocation actually holds up, or whether the vendor is using the words “force majeure” to cover an ordinary business problem that was theirs to solve.

This is educational background, not legal advice. Force majeure language is negotiated clause-by-clause, interacts with the governing state’s law, and courts read it narrowly and literally. Have institutional counsel review the actual clause in your contract, and the specific facts of any invocation, before you accept or contest one — this guide exists to help you ask the right questions going into that review, not to replace it.

The Three Things a Force Majeure Event Actually Has to Be

Courts and well-drafted clauses converge on the same three requirements. An event has to be all three, not just one, for force majeure to genuinely apply:

• Unforeseeable. The event could not reasonably have been anticipated when the contract was signed. A clause negotiated in 2026 that lists “pandemic” as a covered event has, by definition, foreseen that risk — which is exactly why post-2020 vendor contracts routinely name it explicitly rather than leaving it to be argued after the fact.
• Outside either party’s control. The event has to be external to both the vendor and the buyer — not a decision either party made, and not a risk either party priced in or should have managed. A vendor’s own hiring shortfall, cash-flow problem, or failure to diversify its supplier base is not external to the vendor.
• Unavoidable despite reasonable efforts. The invoking party generally has to show it tried to mitigate — sourcing an alternate carrier, drawing down safety stock, seeking a substitute input — not just that the event happened. Most clauses require this expressly; even where a clause is silent, many governing-law regimes read a mitigation duty in anyway.

All three matter because courts interpret force majeure clauses narrowly, generally only to the events actually listed or clearly implied by the clause’s language — a party invoking force majeure carries the burden of showing the event qualifies, not the other way around.

What Typically Qualifies

The event categories that reliably meet all three tests, and that most vendor contracts list explicitly:

• Natural disasters — hurricanes, earthquakes, floods, wildfires that physically disable a facility, port, or transport route.
• War, civil unrest, and terrorism — events that disrupt manufacturing regions or shipping lanes.
• Government action — export controls, import bans, mandated facility shutdowns, embargoes, or a sudden regulatory change that makes performance illegal, not just harder.
• Public health emergencies — a government-declared pandemic or epidemic that triggers travel restrictions, facility closures, or workforce quarantine mandates, as opposed to ordinary seasonal illness.
• Extended labor actions the invoking party didn’t cause — a strike at a raw-material supplier or a port, for example, though some clauses carve labor disputes back out if they involve the invoking party’s own workforce.

What Doesn’t Qualify — Even Though It’s Genuinely Painful

This is the half of the picture that gets skipped, and it’s the half that matters most in practice, because most real disputes involve a vendor citing force majeure for something that doesn’t actually meet the three-part test above:

• Ordinary supply-chain tightness. A raw-material price spike, a longer-than-usual lead time, or a general market shortage that a reasonably diligent vendor should have anticipated and planned around isn’t automatically force majeure just because it’s inconvenient or costly — foreseeable market volatility is a business risk the vendor priced into the contract, not an excuse from it.
• A vendor’s own operational failure. Understaffing, a missed reorder point, a production-line breakdown from deferred maintenance, or a vendor’s own single-sourcing decision that leaves it exposed — none of these are external, uncontrollable events. They’re the vendor’s operational risk, and a well-drafted clause says so explicitly.
• A vendor’s own upstream supplier problem, if reasonably avoidable. If the vendor could have qualified a second supplier, held more safety stock, or sourced a substitute component and chose not to, many courts and most well-drafted clauses won’t excuse performance on that basis — the vendor’s failure to diversify is treated as within its control, even if the immediate trigger (its own supplier’s shutdown) technically wasn’t.
• Increased cost of performance, standing alone. Performance becoming more expensive is not the same as performance becoming impossible or illegal. Many clauses state this outright: force majeure does not excuse a party merely because the contract became a worse deal for them.
• Anything the clause doesn’t actually list or reasonably imply. Because courts read these clauses narrowly, a generic catch-all phrase like “any other cause beyond a party’s control” gets interpreted in light of the specific, listed examples around it — it is not a blank check.

Force Majeure vs. Commercial Impracticability

If a contract has no force majeure clause at all — or the clause doesn’t cover the event in question — U.S. buyers sometimes hear a vendor invoke a related but distinct doctrine instead: commercial impracticability under UCC §2-615, which applies to contracts for the sale of goods. It’s a narrower fallback, not a broader one: it requires the vendor to show performance has become impracticable because of a contingency whose non-occurrence was a basic assumption of the contract, and it’s a default gap-filler that a written force majeure clause typically displaces or narrows by its own terms. In practice, a specific, well-drafted force majeure clause controls; the statutory doctrine matters mainly when the contract is silent.

What a Force Majeure Clause Should Actually Specify

For a lab-equipment or medical-supply purchase, the clause language itself determines how much protection — or exposure — you actually have. Before signing, check whether the clause specifies:

• An enumerated event list, not just a vague reference to “circumstances beyond a party’s control.” Specific, named categories (see above) are enforced more predictably than open-ended language.
• Notice requirements — how quickly the invoking party must notify the other side, and what documentation or proof it must provide. A clause with no notice deadline lets a vendor invoke force majeure retroactively, after the fact, which is far harder for you to verify or contest.
• An express mitigation duty — language requiring the invoking party to use commercially reasonable efforts to work around the event, not just declare it and stop.
• An allocation provision, if the vendor sells the same scarce item to multiple customers. This became a real, recurring issue in 2020–2021: vendors invoking force majeure on a genuinely qualifying event (a government-mandated shutdown, a pandemic-driven demand spike on raw materials) then rationed remaining supply across customers under whatever allocation method the contract specified — or, if the contract was silent, whatever the vendor decided unilaterally. Ask what allocation method applies before you need to find out the hard way.
• A suspension-vs-termination threshold — most clauses suspend obligations for the duration of the event, but let either party terminate if it drags on past a defined period (30, 60, or 90 days is common). Confirm what happens to open purchase orders and any deposits if that threshold is reached.
• Whether payment obligations are excused too, or only delivery obligations — these are sometimes treated differently within the same clause.

Why a Force Majeure Clause Isn’t a Continuity Plan

Even a well-drafted force majeure clause only tells you what happens after a qualifying event occurs and is invoked — it doesn’t prevent the disruption, and, as the allocation point above shows, it doesn’t guarantee your institution actually receives product during a genuine shortage. A vendor can invoke force majeure entirely correctly and you still don’t get your order on time. That gap is exactly why continuity planning has to sit outside the contract itself, not rely on it: qualifying and maintaining a real second source for critical consumables and equipment is the structural protection that a force majeure clause, by design, cannot provide. See Backup Supplier Strategy: Second-Sourcing Critical Medical Consumables for how to build that redundancy deliberately, rather than discovering the gap during the next disruption.

A Quick Gut-Check

When a vendor cites force majeure, these questions separate a genuine invocation from an excuse of convenience:

• Is the cited event actually named in the clause, or reasonably implied by what is named?
• Could the vendor have reasonably foreseen and planned around this at the time the contract was signed?
• Is the cause genuinely external to the vendor — or is it the vendor’s own staffing, planning, or single-sourcing decision showing up under a different name?
• Did the vendor give notice and documentation within whatever window the clause requires?
• Is the vendor claiming performance is impossible, or just that it became more expensive or less convenient?

If the answer to the third or fifth question points toward the vendor’s own operational choices rather than a genuinely external event, that’s worth raising with institutional counsel before accepting the invocation — and it’s a useful data point for your vendor scorecard regardless of how the immediate dispute resolves.

Frequently Asked Questions

Is a pandemic automatically force majeure?

Only if the clause names pandemics or public health emergencies, or the language is broad enough to reasonably cover one, and the specific impact meets the unforeseeable/uncontrollable/unavoidable test. A pandemic that started years before a given contract was signed is harder to call “unforeseeable” for that specific agreement — which is exactly why current vendor contracts increasingly name it explicitly rather than relying on that argument.

Can a vendor use force majeure just to raise prices?

Generally no. Increased cost of performance, standing alone, is not the same as performance becoming impossible or illegal, and most clauses (and courts) treat a pure price increase as ordinary commercial risk rather than a force majeure event.

What’s the difference between a force majeure clause and a warranty or SLA remedy?

A force majeure clause excuses non-performance entirely for the duration of a qualifying event; a warranty or service level agreement instead defines a performance standard and a remedy (credit, replacement, escalation) when the vendor falls short for ordinary, non-excused reasons. They apply to different situations and shouldn’t be confused.

Does invoking force majeure end the contract?

Not automatically. Most clauses suspend the affected obligations first, and only allow either party to terminate if the disruption continues past a specified threshold. Check the clause’s actual suspension-vs-termination language, and see wind-down provisions for what an eventual termination should address.

Should force majeure risk affect how we single-source critical equipment?

Yes — it’s one of the concrete reasons continuity planning shouldn’t rely on contract language alone. A qualifying force majeure event can legitimately excuse your sole vendor from delivering at exactly the moment you need supply most; a qualified second source is the structural mitigation for that gap. See backup supplier strategy and second-sourcing.