The product. The evidence. The responsibility.Independent product liability resource
ProductLiability.helpProducts · Defects · Evidence
Home / Topic library / Component and Supply-Chain Product Liability

Components and supply-chain liability

Component and Supply-Chain Product Liability

Component liability requires a reliable link between the supplied item, its integration, product defect and damage. Map physical and digital components, manufacturer control, supplier evidence and responsibility without treating every supplier as automatically liable.

Start with the component and the finished product

Component and supply-chain product liability concerns how a defective part, material, software item or related service can contribute to an unsafe product and who may be responsible for the resulting harm. A product's supply chain can include designers, factories, software developers, importers and service providers. Their involvement does not make them all liable. Each role and causal contribution needs examination under the applicable rules.

Directive (EU) 2024/2853 expressly addresses components alongside finished products. Article 4's component definition includes tangible and intangible items, raw materials and related services integrated into or interconnected with a product. The existing explanation of whether components count as products addresses basic classification. For a liability investigation, the next task is to establish the actual component, its supplied and installed state, the integration relationship and the alleged safety defect.

Map the actual supply relationship

Start with the product involved in the incident rather than a generic model description. Identify its version, serial or batch reference and known modifications. Then connect the relevant component to that product. A supplier invoice may identify a commercial transaction without showing which finished units received the part. A bill of materials may describe the intended assembly without proving the configuration present at the incident.

Record the entities involved and what each did. A supplier can be a manufacturer, distributor or another actor, and a business can perform several functions. Branding, outsourced manufacture and group-company arrangements can complicate identification. Distinguish the legal entity that supplied a component from the upstream project or factory named in its records. The objective is a defensible map of conduct and evidence, not a list of familiar names.

Separate component behaviour from product defectiveness

A component can fail without causing the finished product to fall below the required safety standard. An independent safeguard may prevent a hazardous consequence. Conversely, a component that meets its own specification can become unsafe when selected or integrated improperly. Explain both the alleged component problem and the complete product's response. This avoids mistaking the location of visible damage for the origin of the failure.

Article 7 assesses the safety a person is entitled to expect or that law requires, considering all relevant circumstances. These include characteristics, instructions, foreseeable use and foreseeable interaction with other products. A supplier certificate is relevant evidence, but it cannot replace that assessment. Identify the operating assumptions, interface conditions and safeguards that connect the component's behaviour to the alleged defectiveness of the finished product.

Assess component and finished-product manufacturers separately

Article 8(1)(b) addresses the manufacturer of a defective component where the component was integrated or interconnected within the product manufacturer's control and caused the product to be defective. It preserves the finished-product manufacturer's potential liability. Article 8 also addresses the latter manufacturer's liability for damage caused by a defective component integrated or interconnected within its control. Outsourcing does not automatically remove the finished-product manufacturer from the inquiry.

The detailed comparison of component and final-product manufacturers explains how these conditions fit together. Identify the alleged component defect, approved integration and causal contribution before allocating responsibility. Where a product or component manufacturer is outside the Union, Article 8 also provides specified routes involving importers, authorised representatives and, under relevant conditions, fulfilment service providers. Distributor and platform provisions have their own conditions rather than automatic chain-wide liability.

Manufacturer control includes approval and continuing capabilities

Article 4 defines manufacturer control through specified actions, authorisation or consent concerning third-party integration, interconnection, supply and modification, together with software update capabilities. Control is therefore not simply physical ownership at the time of an accident. An approved supplier can integrate or update a component on the product manufacturer's behalf. A later unauthorised addition presents a different factual relationship.

Preserve integration approvals, technical instructions, update arrangements and change histories. Determine what was authorised and whether the installed configuration matched that authority. Compatibility alone does not prove consent, while work performed after sale does not automatically fall outside control. A reliable timeline separates initial manufacture, market placement, service replacements and later software changes so each event can be assessed on its own evidence.

Physical and digital components require different records

Physical component inquiries may depend on material batches, tolerances, manufacturing processes and the condition of recovered parts. A fractured fastener can be a cause or a consequence of an incident. Compare the supplied state, assembly process and operating environment. Preserve examination records and explain where destructive testing or incident damage limits further investigation. A specification mismatch must still be connected to the alleged safety problem.

The explanation of intangible components as products distinguishes software and related-service classification. The software supplier liability guide addresses the corresponding developer and supplier roles. Software inquiries require identification of the actual artefact, configuration and supply route. Public project names, commercial distributions and modified forks can represent different product states and actors. Software can also be supplied or changed independently of the main hardware release. The guide to open-source components in commercial products examines the handoff between upstream projects, commercial suppliers and the manufacturer's integration without assigning automatic responsibility to every contributor.

Supplier evidence must be linked and interpreted

Specifications, delivery documents, certificates, test reports and correspondence answer different questions. Identify each record's author, revision and relationship to the affected component. A current datasheet may not describe an earlier supply, and a production-family certificate may not cover the relevant batch. Explain the evidential link rather than allowing a document title to imply more than its contents establish.

The guide to supplier testing records examines sample identity, methods, conditions and acceptance criteria. A component can pass one test while failing under another relevant operating condition. Failed tests and retests also matter, especially where the method or component changed between them. Article 9 provides conditional disclosure under court control, with necessity, proportionality and safeguards for confidential information and trade secrets. It does not guarantee unrestricted access to every supplier file.

Examine design instructions and the component exemption

Article 11(1)(f) permits a component manufacturer to prove an exemption where the finished product's defectiveness is attributable to that product's design or instructions from its manufacturer. This makes design schedules, interface requirements and change correspondence important. The inquiry is causal: what explains the unsafe product? The existence of a contractual clause assigning design responsibility does not by itself prove the exemption.

Compare the instructions with the actual supplied component and the observed mechanism. Determine whether the supplier followed them and whether another component characteristic contributed. The guide to supplier contracts as evidence distinguishes technical instructions, commercial allocation and injured-person rights. A contract can be highly relevant without conclusively determining statutory responsibility or removing the need to establish defect, covered damage and causation.

Distinguish compensation from commercial recourse

Article 6 defines covered damage and exclusions. In particular, it excludes specified damage to a product caused by a defective component integrated or interconnected by its manufacturer or within its control. Replacement of a defective part, destruction of its containing product, personal injury and damage to other property therefore need separate classification. A strong technical account does not make every associated commercial loss recoverable under this Directive.

Where multiple operators are liable for the same damage, Article 12 provides for joint and several liability under its conditions. Article 14 addresses remedies pursued after compensation, in accordance with national law. The guide to recourse between economic operators covers component supplier recovery and the conditional small-software exception. Article 12(2) requires both qualifying enterprise status and an agreed contractual waiver; small size alone is not general immunity. Article 15 separately protects the injured person's position against contractual exclusion or limitation.

Use the correct timeline and mark remaining uncertainty

The corrected scope covers products placed on the market or put into service after 8 December 2026. The Member States' transposition deadline is 9 December 2026. These are different legal functions. Record component supply, finished-product placement and subsequent intervention dates separately, and examine the relevant national law before applying the framework to a particular product. An accident after the date does not alone establish the applicable regime.

The supply-chain mapping checklist turns these questions into a practical sequence. A mature supply-chain investigation connects product identity, component state, actor conduct, integration control, safety defect, damage and the evidence supporting each link. Mark verified facts, inferences and gaps clearly. That structure preserves useful supplier information while preventing shortcuts such as treating every broken part as defective, every supplier as liable or every contractual allocation as binding on the injured person.

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.

  • Component identity, revision and supplier-to-product links
  • Specifications, integration approvals and change history
  • Supplier tests, design instructions and applicable contracts
  • Incident-time configuration, failure evidence and classified damage

Every component supplier is not automatically liable merely because its part appears in the affected product.

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.

Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.

Continue the research