Connect the component defect to the product defect
A defective component does not establish every element of a finished-product liability claim. Article 8(1)(b) of Directive (EU) 2024/2853 links component manufacturer responsibility to integration or interconnection within manufacturer control and to the component causing the product to be defective. A useful analysis therefore explains two relationships: what was wrong with the component and why that made the complete product unsafe.
The component and supply-chain liability framework provides the wider legal context. Here, the focus is the integration boundary. An electronic controller can receive an incorrect signal yet prevent an unsafe action through a safeguard. Conversely, a component operating as specified can become unsafe in an unsuitable assembly. Neither the component's presence nor a laboratory fault report alone settles the finished-product question.
Identify the relevant product configuration
Record which component version was incorporated, where it was fitted and how it interacted with the rest of the product. For hardware, this may include tolerances, materials and assembly settings. For software, it can include interfaces, configuration and dependencies. The affected product's actual state matters more than a generic diagram showing how the current model is normally built.
Compare design records with production and service history. A drawing can describe an intended configuration without proving that a particular unit matched it. A later replacement may introduce a different component despite retaining the same model name. Where records conflict, preserve both versions and state which observation supports the incident-time configuration. That avoids building the causal explanation around a convenient but unverified specification.
Explain the transition from faulty behaviour to unsafe behaviour
Describe the component's function and the alleged departure from safe performance. Then explain how the product responded. A temperature sensor may provide an incorrect value, but the product's control logic, independent cut-out and user warning can affect whether that value creates danger. The safety analysis should examine the complete path rather than stopping at the first abnormal measurement.
Article 7 includes presentation, characteristics, instructions, foreseeable use and foreseeable effects of other products expected to be used together. These circumstances help assess whether the integrated product provided the required safety. A component supplier's stated operating range is relevant evidence, but it is not conclusive. The product's intended users, environment and reasonably foreseeable operation also matter when evaluating the alleged safety shortfall.
Distinguish component faults from interface mismatches
An interface mismatch can arise even when both businesses believe they supplied a compliant item. One may assume a signal is expressed in degrees while the other interprets it as a scaled integer. A mechanically compatible connector may permit an electrically unsuitable pairing. Investigators should identify the specific assumption that failed and whether it was documented, communicated and verified.
Retain specifications from both sides of the interface, including revisions and correspondence resolving ambiguities. Review what integration tests actually covered. A successful basic function test may not test emergency operation or an out-of-range input. The distinction between component and final-product responsibility is developed in the comparison of component and finished-product manufacturers, including the conditional component exemption where design or instructions explain the defectiveness.
Establish manufacturer control without relying on ownership
Article 4 defines manufacturer control through specified conduct, authorisation or consent and software update capabilities. The product manufacturer may control integration performed by a contractor. It may also authorise supply or interconnection by a third party after initial sale. A direct purchase order is useful evidence but is not the sole way to establish the relevant relationship.
Record who approved the component, its permitted configurations and later changes. Separate an authorised service replacement from an unauthorised modification. Where control is disputed, explain which records show consent and which merely show technical compatibility. This prevents the analysis from treating every interoperable component as authorised or assuming that anything installed after sale necessarily falls outside the manufacturer's control.
Analyse the component exemption and timing evidence
Article 11(1)(f) permits a component manufacturer to prove that the product's defectiveness is attributable to the finished product's design or instructions from its manufacturer. A supplier's assertion that it followed instructions needs comparison with the actual part, requirements and failure mechanism. If a component itself departed from those instructions, that factual difference can matter to the claimed explanation.
Other timing questions also remain relevant. Article 11 addresses exemptions and exceptions concerning when defectiveness arose, including specified matters within manufacturer control. Preserve release, integration and update dates rather than assuming the initial assembly date answers every question. The corrected Directive scope concerns products placed on the market or put into service after 8 December 2026; the relevant national law must also be checked.
Separate the causal mechanism from covered damage
Article 6 excludes specified losses, including damage to a product caused by a defective component integrated by its manufacturer or within its control. A convincing account of how a part destroyed the assembled product does not automatically make that product loss recoverable under this Directive. Injury or damage to other qualifying property requires its own classification and causal account.
A mature integration report states the verified configuration, proposed fault, unsafe product response, control evidence, competing explanations and resulting damage. It distinguishes direct observations from technical reconstruction. Where testing is incomplete, it explains what could confirm or weaken the hypothesis. That produces a usable account of integration responsibility without treating a failed component as a substitute for the statutory conditions.
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.
- Incident-time component and product configuration
- Interface specifications and integration approvals
- Fault propagation and safeguard test records
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 2, 4, 6, 7, 8, 11 ↗
- 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.