Force Majeure and Delay Liability: Clauses That Protect Both Sides

The Problem: The Delay Is Nobody's Fault and Somebody's Cost

A firing goes wrong in a way that requires a re-run; a typhoon closes a port for a week; a customs regime changes its documentation requirement in the middle of a season. Nobody behaved badly, and yet the buyer's promotion window has moved, or their shelf has a gap, or a chain has issued a chargeback. This is the situation commercial clauses exist for, and it is also the situation in which badly written clauses do the most damage — because a vague force majeure provision invites a dispute, and an aggressive penalty clause pressures the factory into promises it cannot keep. The professional objective is not to win the argument after a delay. It is to have agreed, in calm conditions, what counts as an excusable event, what happens when it occurs, and how foreseeable delay risk is priced and allocated.

Products in this guide: Elegant Newlywed Ceramic Dinnerware Set · Traditional Chinese Blue & White Dinnerware Set

What Force Majeure Actually Covers

Force majeure is a contractual mechanism that excuses performance when an event makes it impossible — not merely inconvenient or unprofitable. Its elements are consistent across legal systems even where the wording differs: the event must be unforeseeable, beyond the party's control, and unavoidable despite reasonable efforts. Typical instances include natural disasters, war and civil disruption, government action that halts activity, and certain epidemics or transport blockades. Two features decide whether the clause works. First, the notice and mitigation duty: the affected party must inform the other promptly and must take reasonable steps to limit the damage — a party that stays silent for weeks and then invokes the clause will struggle. Second, the drafting breadth: a narrow clause covering only listed events gives both sides a clear but limited shield, while a broad "any circumstance beyond our control" formula reads generously and is enforced narrowly. The point worth internalising: ordinary commercial difficulty — a supplier changing its price, a booking shortage, a port that is merely slow — is not force majeure, and treating it as such in the wording sets up an argument rather than preventing one.

Delay Liability in Practice

Where force majeure excuses, delay liability allocates the cost of delay that is not excused. The common mechanism is a liquidated damages provision: the parties agree in advance what a delay is worth, expressed as an amount per period or a percentage of order value, usually with a cap on total exposure and often a cure period before the remedy starts. The virtue of agreeing a figure in advance is that it replaces a speculative dispute with a predictable number — which is why such clauses are typically drafted to be a genuine estimate of loss rather than a punishment, since penalties that bear no relation to actual loss are the ones courts decline to enforce. Three drafting decisions carry most of the weight: what triggers the clock — readiness for shipment, delivery at port, arrival at destination, or availability for a stated window; what is excluded, such as buyer-caused delay in approvals or artwork; and the cap, which should be sized so the remedy can actually be performed. A clause that imposes an exposure larger than the order's margin does not secure delivery; it converts a delay into a likely default.

The Link to the Production Plan

A delay clause is only as good as the schedule it governs. If the specified lead time is already optimistic, adding a penalty does not create capacity — it converts an ordinary slippage into a breach, and it gives the factory a reason to be conservative about what it accepts. The productive pairing is a realistic lead time with an honest buffer, both tied to the ordering calendar that governs the program. The replenishment calendar guide maps the ordering windows for the whole year. Written that way, the clause functions as a shared expectation rather than a trap, and it protects the relationship that has to deliver the re-run.

Documentation Is the Clause's Other Half

When an event occurs, the party seeking protection must be able to show what happened and when. That means a notice sent on time through the agreed channel, and a factual record: production reports, dispatch evidence, carrier notices, and photographs where relevant. The shipment file guide explains how to read inspection reports and transport documents. The pattern to avoid is the one that defeats most claims — everything done correctly but nothing written down, leaving the parties to reconstruct a month of events from memory during the dispute the clause was supposed to prevent.

Where This Fits in the Sourcing Chain

Delay and excuse clauses are the risk layer of the commercial agreement, sitting alongside the quality clause The quality clause guide explains how defect liability and remedies are written down. and the terms that govern pricing and validity. The quote validity guide explains how to hold prices on long programs. They also intersect the arrival-cost mechanisms that punish lateness at the destination. The demurrage and customs delay guide explains how arrival costs stay predictable. The full chain follows the standard sourcing map. See the full ceramic sourcing process map.

The Habit That Ties It Together

The habit is to settle three questions before the first order rather than during the first problem: what counts as an excusable event, what a non-excused delay costs, and how notice is given and evidenced. Programs that answer them in writing handle the bad season as a logistical event. Programs that leave them implicit discover that the most expensive part of a delay is not the delay — it is discovering, in the middle of it, that nobody agreed what it would cost.