Define what the map must explain
A product liability supply-chain map should explain how the relevant product was made, supplied, integrated and changed. Its purpose is to connect actors and evidence to the alleged defect and damage. It should not be a list of every organisation associated with the brand. Start with the incident product, relevant configuration and proposed failure mechanism, then expand only where another link could affect the investigation.
The component and supply-chain liability overview supplies the legal framework. Under Directive (EU) 2024/2853, a product's manufacturer, a component manufacturer and other specified economic operators can have different roles and conditions of liability. The mapping process helps identify those conditions for examination. It does not turn a commercial relationship into a finding that the supplier is liable for the incident.
Establish the incident product and relevant dates
Record the product model, serial or batch reference, version and condition at the incident. Separate original assembly from later repairs, software updates and replacements. Keep a record of the sources supporting each fact. If identification relies on a photograph or purchaser recollection rather than a surviving label, state that limitation so later readers do not assume a stronger match.
The corrected Directive scope concerns products placed on the market or put into service after 8 December 2026. Record those events separately from manufacturing, delivery, purchase and accident dates. A recent incident does not itself establish the applicable framework. Applying the timeline to a particular product requires review of the relevant national law, especially where components and finished products entered the chain at different times.
Identify the component and its function
Describe the allegedly relevant component in functional terms: what it senses, calculates, supports, contains or controls. Identify its revision, supplier and actual installed state. A bill of materials can provide a starting point, but verify that it describes the affected product. A current design record may omit an earlier substitution or later service replacement.
For software, distinguish project names, supplied distributions, modified forks and the artefact actually used. For materials, identify batch transformations rather than expecting an individual serial number. The guide to component traceability explains these identity links. Mark each link as verified, inferred or unresolved. This makes the map useful even where the evidence cannot yet establish a complete chain.
Record actors by conduct as well as label
Identify the legal entities that developed, manufactured, branded, imported, represented, distributed or supplied the relevant product. A business called a supplier may perform several functions, while a familiar brand may represent different entities in different transactions. Article 4's definitions and Article 8's conditions should be applied to the actual conduct rather than inferred from invoice terminology.
Where the product or component manufacturer is outside the Union, record the importer, authorised representative and any relevant fulfilment role. Article 8 contains specific conditions governing these actors and conditional distributor or platform routes. Do not summarise these rules as automatic liability for every intermediary. The map should show which actor condition is supported and which identity or relationship still requires evidence.
Connect integration and control to actual records
Identify who selected the component, specified its interface and authorised its integration or interconnection. Preserve drawings, technical instructions, approval correspondence and update arrangements. Article 4's manufacturer control definition includes specified actions, authorisation or consent and software update capabilities. Ownership of the component at the time of the incident is not a complete substitute for that inquiry.
Separate approved changes from unauthorised additions. A manufacturer may approve one version but have no involvement in a later modification. Where the component manufacturer invokes finished-product design or instructions, identify the records relevant to Article 11(1)(f)'s exemption. The map should connect that argument to an actual technical explanation, not simply repeat a contractual statement that one party was responsible for design.
Show the alleged path from defect to damage
Describe the component behaviour, the finished-product safety consequence and the resulting harm. Identify relevant safeguards and whether they operated. Article 7 requires consideration of all relevant circumstances, including foreseeable use and interaction. Article 10 retains proof requirements subject to specified rebuttable presumptions. A complex map does not itself satisfy either assessment.
Classify the damage separately under Article 6. Damage to the defective product, specified component-caused damage to the product containing it, professional property and qualifying injury or other losses can raise different outcomes. Avoid combining replacement costs, business downtime and injury under a single loss label. The map should make clear which claimed losses are connected to the proposed mechanism and which legal categories remain unresolved.
Identify evidence gaps and the next relevant record
For each disputed link, identify the record or examination that could resolve it. A supplier test report may address material strength; a release log may identify the installed software; an approval email may clarify control. A focused evidence gap is more useful than a general instruction to obtain all supplier files. Preserve contrary evidence and alternative explanations alongside the preferred hypothesis.
Article 9 provides conditional disclosure under court control with proportionality and confidentiality safeguards. Shared liability and recourse also require separate analysis under Articles 12 and 14. Finish with an account that distinguishes identities, verified events, causal hypotheses, damage categories and unresolved legal conditions. This produces a practical investigation map without implying that supply-chain membership alone establishes a right to compensation.
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.
- Product and component identity crosswalk
- Actor, control and integration evidence map
- Causal hypotheses, damage categories and evidence gaps
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, 9, 10, 11, 12, 14 ↗
- 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.