EU Product Liability Directive 2024/2853: Evidence Preparation for Cross-Border Sellers

Who should read this: Chinese manufacturers, private-label brands, importers, authorised representatives, fulfilment providers and distributors selling products into the European Union, especially products with software, connectivity or continuing update capability.

Bottom line: The revised product-liability regime is about compensation for damage caused by defective products. It is not a product certificate and it is not a single Amazon delisting rule. A seller’s practical task is to connect product identity, design and testing, instructions and warnings, software changes, supply-chain roles and incident handling, then check the national law that implements the Directive in each target Member State.

1. Start with scope: timing, products and compensable damage

Directive (EU) 2024/2853 repeals and replaces Council Directive 85/374/EEC, while Article 21 preserves a transition for products placed on the market or put into service before the new regime applies. The transposition deadline and the product-level application date are therefore different questions. Keep first-market dates, batches and versions for each SKU so that the applicable rule can be identified if a complaint or claim arrives.

Question	What the Directive says	Evidence to retain
When?	Transposition is due by 9 December 2026. After the corrigendum, the Directive applies to products placed on the market or put into service after 8 December 2026.	First-placement date, batch, version, put-into-service record and Member State sales scope.
What product?	The rules address liability for damage caused by defective products and expressly respond to digital scenarios such as software, AI systems and product-related digital services. Commercial software and free, non-commercial open-source software should not be treated as the same case.	Product definition, software and firmware versions, related digital services, update capability and supplier boundaries.
What damage?	The Directive covers death or personal injury, including medically recognised damage to psychological health; specified property damage; and destruction or corruption of non-professional data. The defective product itself, certain damage to the same product and property used exclusively for professional purposes are excluded.	Complaint facts, damage category, product-to-damage causal record, after-sales and recall files. National law still affects compensation.

2. Defectiveness: software updates matter, but an update is not automatically unlawful

Article 7 asks whether the product failed to provide the safety a person is entitled to expect or that EU or national law requires. The assessment takes account of the product’s presentation, labelling, design, technical features, composition, packaging and instructions, together with reasonably foreseeable use.

For digital products, the analysis can include the effect of continued learning or new features after market placement, foreseeable effects of interconnection with other products, relevant product-safety requirements including safety-relevant cybersecurity, recalls or other safety interventions, the needs of the intended user group, and a failure to perform a damage-prevention purpose. A product is not defective merely because a better product, update or upgrade exists.

3. Map the economic operators instead of treating a platform, FBA and an importer as one category

Article 8 covers the manufacturer of a defective product and the manufacturer of a defective component integrated or interconnected under the product manufacturer’s control. Where the product or component manufacturer is outside the Union, the analysis also reaches the Union importer, the authorised representative and, where there is no importer or authorised representative, the fulfilment service provider. The Directive contains rules for distributors that cannot promptly identify the relevant economic operator. A party that substantially modifies a product and then makes it available or puts it into service may be treated as a manufacturer.

An online platform does not become a manufacturer under the new PLD merely because it hosts a product page. The Commission and the Directive’s recitals point to a role-based analysis: when a platform performs the role of manufacturer, importer, authorised representative, fulfilment service provider or distributor for the defective product, the corresponding liability analysis applies. Amazon FBA contracts, platform policies, market-surveillance law and the Product Liability Directive are separate instruments and should be documented separately.

Role	Questions to answer	Files to retain
Manufacturer / brand	Who designed, made or presented the product under its name or trademark? Who controls changes and updates?	BOM, design inputs and outputs, risk assessment, tests, labels, instructions, version and change approvals.
Importer / authorised representative	Which Union entity is identified? What is the written mandate, product scope and validity?	Contracts, mandate, address and contact details, covered SKUs, change notices and communications.
Fulfilment provider / distributor	Do the facts meet the relevant role definition? Can the business identify the relevant Union economic operator when a complaint arrives?	Warehousing, packaging, dispatch and distribution chain; notice, recall and traceability workflow.
Online platform	Is the platform only displaying or matching the sale, or does it perform a statutory economic-operator role in this transaction?	Platform contract, listing versions, delisting and recall notices, seller-account and dispute records.

4. The real evidentiary change: disclosure and presumptions, not a blanket burden reversal

Article 10 does not say that every complex product, AI product or software product automatically requires the manufacturer to prove that it is defect-free. The basic rule remains that the claimant proves defectiveness, damage and the causal link. The change is that Article 9 allows a claimant who has presented facts and evidence sufficient to support the plausibility of a compensation claim to ask the defendant to disclose relevant evidence in its possession. The court must balance necessity, proportionality, confidentiality and trade secrets.

Article 10 also provides presumptions in defined situations, such as failure to disclose relevant evidence, non-compliance with mandatory product-safety requirements intended to protect against the damage, or an obvious malfunction during reasonably foreseeable use or ordinary circumstances. Where technical or scientific complexity creates excessive difficulty and the claimant shows that defectiveness or causation is likely, a court may make a further presumption. The defendant can rebut the presumptions. This is a conditional statutory mechanism, not a promise of a result.

5. Time limits, defences and six preparation actions

Do not repeat the claim that the new rules universally change the period to five years with a fifteen-year long stop. Article 16 sets a three-year limitation period for proceedings, running from when the injured person knew or should reasonably have known the damage, the defectiveness and the identity of the relevant liable economic operator. Article 17 generally ends the right to compensation after ten years from placement on the market or putting into service. Where a personal injury’s latency prevented proceedings within that period, the special expiry period can extend to twenty-five years. National rules on procedure and the implementing legislation still require separate review.

Article 11 lists facts that may exempt an economic operator, including that it did not place or make the product available, that the defect probably did not exist at the relevant time, that the defect resulted from compliance with legal requirements, or that the objective scientific and technical knowledge at the relevant time could not reveal it. Article 18 permits Member States, subject to conditions, to maintain or introduce different treatment of the development-risk defence. Preserve the standards, rules, risk decisions and approvals that existed at the time; do not announce in advance that “industry practice” guarantees an exemption.

1. Build a role map: for each SKU, map manufacturing, branding, import, authorised-representative, fulfilment and distribution relationships, with the contract and facts supporting each role.
2. Build a version map: link hardware, packaging, instructions, listings, firmware, apps, cloud services and third-party components to one change record.
3. Build a damage map: identify complaints that may involve personal injury, property or non-professional data, and assign responsibility for preserving original evidence.
4. Prepare for disclosure: retain the material that explains design choices, risk controls, test scope and software decisions, while marking trade secrets and a reviewable disclosure version.
5. Track national transposition: before 9 December 2026, follow the implementing law, authority requirements and language or safety duties in every target Member State. Do not treat the EU date as the entire local operating rule.
6. Review external claims: remove “guaranteed approval”, “zero risk”, “no delisting”, “certain compensation” and “platform approved” promises. Product facts, warnings and evidence should point to the same SKU and version.

6. Official sources

• EUR-Lex: Directive (EU) 2024/2853 consolidated text, especially Articles 2, 5–11 and 16–22.
• EUR-Lex: corrigendum of 7 May 2026, for the Article 2(1) application date.
• European Commission: EU adapts product liability rules to digital age and circular economy, for the policy context on software, AI, digital services and Union economic operators.