A late automatic assembly machine can stall a launch. When we ship terminal-making lines from Wenzhou, vague liability clauses for delivery delays cost both sides money. Clear drafting fixes that.
Liability clauses for delivery delays in an automatic assembly machine contract should define delivery milestones, set liquidated damages as a percentage of the delayed equipment price per week with a grace period and cap, list force majeure events, separate delay from acceptance failure, and add a long-stop termination right.
That is the short version. The rest of this article shows how each piece works. I will use our own custom automation projects as examples, and I will point out where buyers and suppliers usually disagree.
Last year a terminal crimping line of ours was ready in Wenzhou on schedule, but the buyer's compressed air supply was not. The contract said nothing about that.
A delivery delay liability clause should include defined milestones such as FAT, shipment, site arrival, installation, and SAT; the applicable Incoterm; a baseline schedule; buyer dependencies; separate remedies for delay and acceptance failure; a rectification period; the damages formula; and the conditions for termination.
A custom assembly machine passes through many hands before it makes a good part. If the contract names one "delivery date," nobody knows which step it means. Does it mean the day the crate leaves our dock? The day it lands at the buyer's plant? The day it runs at full cycle time? Our contracts list project milestones instead. Each one has a date, and each one can be checked.
| Milestone | What it proves | Who usually controls it | Typical remedy if late |
|---|---|---|---|
| Drawing approval | Specifications are frozen | Buyer | Schedule extension for supplier |
| Virtual commissioning review | PLC logic and cycle time proven in a digital twin | Supplier | Delay damages 1 on this milestone |
| Factory Acceptance Test (FAT) | Machine runs to spec before shipment | Supplier | Delay damages; retest at supplier cost |
| Shipment under agreed Incoterm | Handover to the carrier | Supplier | Delay damages |
| Site arrival | Physical receipt, not acceptance | Carrier / Buyer | Transit claims |
| Installation complete | Machine powered and connected | Both | Delay damages or extension |
| Site Acceptance Test (SAT) | Machine runs to spec on buyer's parts | Both | Rectification period, then performance remedies |
| Production ramp-up | Throughput and yield sustained | Both | Performance warranty |
Some ranking advice says to define "delivery" as successful completion of the Factory Acceptance Test 2 (FAT), not the arrival date. That works well as the trigger for shipment and payment. However, I still keep the Site Acceptance Test (SAT) as a separate milestone. Receipt at the site should never equal acceptance. One published machinery condition says exactly that: acceptance happens only after a successful SAT.
The clause should also say what kind of date each milestone is. A fixed deadline, an estimate, a target subject to extension, and a milestone that becomes binding only after prerequisites are met are four different promises. If time is meant to be critical, say so in plain words and explain the consequence.
This is the single change I ask buyers to make most often. Put delivery delay and acceptance failure in two different clauses. Give each its own trigger, its own remedy, and its own exit. A late machine and a non-conforming machine are different problems. Each clause should state the rectification period, how damages are calculated, and the conditions for termination for default.
Do not just write "the supplier shall deliver on time" or "the equipment must meet the requirements." When a dispute comes, that wording gives no standard for responsibility and no standard for compensation. I have seen that sentence create months of argument over who owed what.
Equipment lead time on our side depends on inputs from the buyer. The contract should list them, with dates:
Three newer tools are worth adding. A Buyer-Furnished Equipment trigger lets the buyer supply long-lead parts like a specific PLC or sensor when our vendor is the bottleneck. Step-in rights let the buyer send its own technical team to our shop if a critical milestone is missed. And a digital handshake readiness milestone ties liability to delivery of API documentation needed for MES or ERP integration. Each one makes the clause operational, not just legal.
Every quote we send for a custom terminal assembly line forces one choice: a higher weekly rate with a low cap, or a lower rate with a high cap.
Calculate penalty fees as liquidated damages: a fixed percentage, commonly 0.5% to 1.0%, of the delayed equipment price for each full week of delay, after a 7 to 14 day grace period, capped at 5% to 10%, and payable without excusing continued performance or the buyer's termination rights.
Buyers often ask for a percentage of the full contract price. I understand why. A missed launch hurts. But picture a line with a main assembly cell and two vibratory bowl feeder stations on separate stands. If one feeder stand ships ten days late and the cell is already running, damages on the whole line are out of proportion. The fairer base is the delayed equipment, module, or affected line. The contract must then say when the whole line counts as delayed, for example when the missing part stops installation or commissioning.
A clean formula reads: "Liquidated damages equal to [x]% of the price of the delayed equipment for each full week of delay, capped at [y]% of that price." Also state how delay is measured. Calendar days or business days. Full weeks or part weeks. Measured from the original date or a properly revised date.
| Source type | Rate | Grace period | Cap |
|---|---|---|---|
| Industrial machinery condition | 3% per week or part week | None stated | 20% of order value |
| Crane equipment terms | 0.2% per complete week | None stated | 5% of delayed equipment |
| Machinery and installation terms | 0.5% per week | Two weeks | 5% |
| Industrial procurement standard | 0.5% per calendar day | None stated | 15%, further remedies after 30 days |
| Industrial delivery standard | 0.2% per week | Two weeks | 2% of delayed machine or unit |
These are market illustrations, not legal benchmarks. The right figure depends on how critical the machine is, how fast it can be replaced, and the governing law.
The clause should say that paying damages does not excuse continued performance. It should also say whether damages keep accruing through a failed FAT until a successful retest.
Liquidated damages do not help when a machine arrives too late to serve a plant opening. The contract should give the buyer a unilateral termination right once delay passes a threshold, often 60 or 90 days, or once accumulated damages hit the cap. One published sample treats delay beyond 60 days from the shipment date as a material breach while still requiring payment of liquidated damages. That combination works well. The termination clause should cover notice, whether the whole contract or only the delayed portion ends, refund of advance payments, return of buyer tooling and data, and the cost of substitute equipment.
A procurement manager in Germany once asked me a fair question: if a PLC vendor runs out of stock, is that my problem or his?
Define force majeure narrowly: list specific events such as natural disasters, war, epidemics, export controls, sanctions, port closures, and strikes; require that the event be beyond reasonable control, unavoidable, and the actual cause of delay; mandate written notice within days; and exclude ordinary supply chain and planning failures.
My answer to that German buyer was simple. If I knew the PLC had a long equipment lead time when we signed, that is my planning problem. If a government blocked its export after signing, that is an excusable delay. A broad force majeure clause that says "any cause beyond the supplier's control" blurs that line and invites disputes.
| Event | Excusable? | Reason |
|---|---|---|
| Port closure ordered by government | Yes | Beyond control and not avoidable |
| Pandemic lockdown of the supplier's plant | Yes | External restriction on performance |
| New export control or sanction on a component | Yes | Legal barrier that did not exist at signing |
| Standard servo on a long lead time known at signing | No | Foreseeable; should be in the schedule |
| Subcontractor misses its date | No, unless a listed event hit the subcontractor | Supplier is responsible for its vendors |
| General labor shortage | Usually no | Ordinary business risk |
| Buyer late approving drawings | Separate buyer-delay clause | Not force majeure; handled as an extension |
One published automation condition lists fire, natural disasters 3, epidemics, weather, war, strikes, labor and energy shortages, raw material shortages, permit delays, transport delays, and government measures. That is a long list. I still recommend a shorter, firmer one. The more a list reads like a supplier escape hatch, the less a buyer trusts the rest of the contract.
Listing an event is not enough. The supplier should show that the event:
Immediate written notice matters most. Our contracts require the notice to name the event, the affected milestone, the expected delay, the evidence, and a recovery plan. The extension should equal the actual delay, plus a short remobilization period if the parties agree.
Buyer-caused delay deserves its own clause. Late approvals, missing samples, an unready site, or late payment all push our schedule. One published arbitration summary describes a contract that expressly treated the buyer's failure to open a letter of credit on time as an exception to delivery-delay fines. That is sensible. Without funds, we cannot buy motors, vision systems, or safety components.
The supplier should give notice before claiming an extension, and the notice should identify the buyer action, the milestone hit, the days lost, and any extra cost. Change orders should adjust both price and schedule, but only when the change actually touches the critical path.
Our hardest lesson in export contracts 4 came from one that never named a governing law. The penalty clause looked strong on paper and was useless in practice.
To make the liability clause enforceable under international trade law, choose a governing law and arbitration seat, state whether the CISG applies, keep liquidated damages a pre-estimate of loss rather than a penalty, define consequential damages, align the clause with the limitation of liability, and have local counsel review it.
If the contract is an international sale of machinery 5, the United Nations Convention on Contracts for the International Sale of Goods may apply by default. Most markets we ship to, including the United States, Germany, Japan, and France, are CISG contracting states, while India is not. The contract should either select the CISG, exclude it, or explain how it interacts with the remedies you wrote. Pay attention to its rules on notice of breach, proof of loss, mitigation, and foreseeability of damages. Silence here is what sank the contract I mentioned above.
The label "penalty fee" is common in buyer requests, but I avoid it in the written clause. Under many legal systems, a court or tribunal can reduce or strike an amount that looks punitive. Chinese courts, for example, can adjust excessive liquidated damages on request. Common-law systems apply their own penalty tests. The safe approach is a rate and cap that reflect a reasonable estimate of the buyer's likely loss, written as liquidated damages, with the reasoning kept in the project file.
Here is the objection I hear most. Suppliers want wording that says liquidated damages are the buyer's sole and exclusive remedy for delay, with consequential damages 6 excluded. Buyers reply that a late line can trigger customer penalties, idle labor, expedited freight, and temporary manual assembly, none of which the agreed amount covers.
My suggested compromise:
Define "consequential damages" in the contract. Do not rely on the label. Whether lost production is consequential or a direct, foreseeable result of delay is argued differently in different jurisdictions.
The delay clause must fit the general limitation of liability. State whether delay damages count toward the overall cap or sit outside it. Then pick an arbitration seat whose awards are enforceable in both countries, and make sure the Incoterm, risk transfer, payment, warranty, and acceptance clauses do not contradict the delay clause.
| Question | Why it matters |
|---|---|
| Is every delivery and acceptance milestone defined and dated? | Removes argument over which event counts as delivery |
| Which Incoterm and named place apply? | Fixes transport cost and risk, separate from acceptance |
| Are dates binding or indicative? | Determines whether delay triggers any remedy at all |
| Is a baseline schedule attached with buyer dependencies? | Lets both sides show cause and effect on the critical path |
| Is the damages base the delayed equipment or the full price? | Controls proportionality and enforceability |
| What are the grace period, unit of calculation, and cap? | Makes the arithmetic certain |
| Are delay and acceptance failure in separate clauses? | Gives each its own rectification period and exit |
| Is the force majeure clause specific, with notice and mitigation duties? | Prevents supply chain excuses |
| How does late payment or a late letter of credit affect the schedule? | Avoids an impossible delivery promise |
| Are consequential damages defined, not just named? | Reduces disputes over lost production |
| Does the delay cap sit inside or outside the general liability cap? | Avoids contradiction between clauses |
| Is there a long-stop termination right with refund and handover terms? | Protects the buyer when the project loses value |
| Is the CISG selected, excluded, or clarified? | Stops default rules from overriding your remedies |
| Is the arbitration seat enforceable in both countries? | An unenforceable award is worthless |
| Has local counsel reviewed the final text? | Catches mandatory rules you cannot contract around |
Vague delivery promises create disputes. Clear milestones, proportional liquidated damages, a narrow force majeure clause, and enforceable termination rights protect both parties. Have local counsel review the final wording.
Interested in sourcing the products mentioned in this article? See details and request a quote here:
1. Legal definition of damages in contract law from an authoritative educational source. ↩︎
2. Standard industry definition for the FAT process in manufacturing and equipment delivery. ↩︎
3. Authoritative UN definition of disasters used in force majeure clauses for industrial contracts. ↩︎
4. Official US government resource for managing international trade and export agreements. ↩︎
5. Official UNCITRAL page for the CISG, which governs international machinery sales contracts. ↩︎
6. Authoritative legal explanation of consequential damages in commercial contract disputes. ↩︎
