A contract can explain responsibilities without deciding the claim
Supplier contracts can help reconstruct who specified, developed, tested, supplied or approved a component. They may contain technical schedules, change-control provisions, warranties, indemnities and limits on commercial remedies. In a product liability investigation, these terms provide evidence and raise legal questions. They do not automatically establish that the component was safe or that one party alone must answer an injured person's claim.
The component and supply-chain liability framework separates statutory responsibility from contractual allocation. Directive (EU) 2024/2853 contains rules about manufacturer roles, defective components, exemptions, multiple liable operators and recourse. A contract may be relevant to each inquiry in different ways. Begin by identifying the purpose for which a particular term is being used rather than treating the agreement as a complete liability verdict.
Identify the agreement that applied to the supplied component
A supply relationship can involve a framework agreement, purchase order, technical specification and later amendment. Determine which documents applied to the affected revision and supply event. A current contract may contain obligations added after the relevant product was released. A draft indemnity or proposed quality agreement should not be described as an accepted term without evidence of its contractual status.
Check the parties' legal identities and the component covered. Group companies can use a common brand while contracting through different entities. A reseller's purchase terms may differ from the manufacturer's development agreement. Preserve the document hierarchy and any clauses resolving inconsistency. Even where contractual interpretation needs national legal analysis, the factual account should identify which agreement and technical schedule the investigation is relying on.
Use technical schedules to understand design and integration
Contracts can specify operating limits, interfaces, materials, intended environments and acceptance tests. Compare these requirements with the component actually supplied and the finished product's actual use. A term assigning the final design to the customer can help identify relevant instructions, but it does not prove those instructions caused the safety defect. The technical mechanism still needs examination.
Article 11(1)(f) provides a component manufacturer's exemption where the finished product's defectiveness is attributable to its design or instructions from its manufacturer. Contract schedules and change correspondence may support or weaken that explanation. Determine whether the supplier followed the instructions and whether its own component had another relevant problem. A broadly worded responsibility clause cannot substitute for evidence of what made the product defective.
Distinguish commercial acceptance from safety approval
A clause deeming goods accepted after a set period may regulate the businesses' contractual remedies. It does not automatically establish compliance with the safety standard in Article 7. Similarly, a customer's signature on a delivery note may confirm receipt without approving every technical characteristic. Explain what the act of acceptance actually covered and what evidence accompanies it.
Warranty language also needs context. A promise that a component meets specification can be relevant to a contractual claim, while a statutory product liability claim concerns defectiveness, covered damage and causation under the applicable framework. Those issues can overlap, but neither a warranty expiry nor a contractual disclaimer should be presented as automatically ending every possible injured-person claim. The legal route and relevant parties must remain clear.
Examine integration control through the actual relationship
Article 4 defines manufacturer control through specified actions, authorisation or consent and software update capabilities. A contract may authorise a supplier to provide updates or replace components, subject to conditions. Record the scope of the authority and compare it with actual conduct. An agreement granting permission to supply one approved revision does not necessarily authorise all later technical changes.
The guide to supplier changes examines revision and approval evidence in more detail. For contracts, preserve the notices and correspondence showing how the agreed process operated. A written change clause can describe the intended process while the parties' records reveal that another process was followed. Distinguishing agreement from performance avoids treating contractual language as proof of events that were never verified.
Keep indemnities and recourse separate from injured-person rights
Article 15 prevents an economic operator's liability under the Directive from being limited or excluded in relation to the injured person by contractual provision or national law. A business-to-business indemnity therefore should not be presented as automatically forcing the injured person to claim only against the named indemnifier. The statutory conditions determine which operators may be liable.
Article 14 addresses remedies against other liable operators after compensation, in accordance with national law. Article 12(2) contains a specific exception concerning an integrating manufacturer's recourse against a defective software component manufacturer. It requires both qualifying microenterprise or small-enterprise status, assessed with relevant partner and linked enterprises, and an agreed contractual waiver. The exception is conditional and does not create general immunity for small software suppliers or remove injured-person rights.
Treat confidentiality as a procedural issue
A confidentiality clause does not by itself establish that relevant evidence can never be disclosed in proceedings. Article 9 provides court-controlled disclosure subject to conditions, necessity, proportionality and safeguards for confidential information and trade secrets. The relevant court and national procedure govern how a particular request is handled. Avoid promising unrestricted access or assuming every commercial term will become public.
A sound contractual evidence account identifies the applicable documents, technical instructions, approval powers, actual performance and any recourse terms. It distinguishes factual interpretation from unresolved legal enforceability questions. That allows the contract to inform component responsibility without replacing the analysis of product safety, causal contribution, damage and the rights protected by the applicable liability regime.
Records that help the review
Use the following as a practical starting point. Select and preserve records appropriate to the product, incident and applicable procedure.
- Applicable supply agreement and technical schedules
- Amendments, change notices and actual approvals
- Indemnity, recourse and software waiver terms
Independent educational information at EU Directive level. National implementing law and procedure require separate review.
Primary sources and legal scope
This page explains the EU Directive framework. Check national implementing law, the corrected temporal scope and relevant procedure before applying it to a case.
- Directive (EU) 2024/2853, consolidated text: Articles 4, 7, 8, 9, 11, 12, 14, 15 ↗
- Official Journal corrigendum, 7 May 2026: Article 2(1) ↗
Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.