Continuity and change
Directive (EU) 2024/2853 replaces Directive 85/374/EEC for products within its new scope. Both frameworks use a no-fault approach to damage caused by defective products. The revision responds to digital products, changing supply chains and evidential difficulties. It should therefore be read as a substantial update to definitions and mechanisms, not as a switch from a purely negligence-based system to strict liability for the first time.
The new EU Product Liability Directive explains the current provisions in their own terms. A comparison is useful only if the two regimes remain distinct. Do not import a new disclosure mechanism or damage category into an older-product investigation merely because it improves the apparent result. Start by establishing which framework and national implementing law apply.
Product dates govern the transition
The corrected Article 2(1) covers products placed on the market or put into service after 8 December 2026. Article 21 preserves the previous Directive for products placed on the market or put into service before 9 December 2026. The 9 December national transposition deadline in Article 22 is a related but separate rule. An accident occurring after that date does not automatically choose the new framework.
Identify the actual product, not just the model's commercial launch. Supply and first-use records may be needed to establish the relevant date. Later changes can introduce additional questions about software, control or substantial modification, but do not justify assuming every older product has become a new product. The temporal conclusion needs its own legal and factual explanation.
Digital products receive explicit treatment
The new definition expressly includes software and digital manufacturing files, alongside electricity and raw materials. It also defines components and related services in a way that can address digital integration. Recital 13 explains software regardless of its delivery or use method, including network and cloud models. This reduces uncertainty that can arise when traditional physical-product terminology is applied to modern systems.
The update does not turn every service, information file or piece of published code into a product. Definitions, commercial context and exclusions remain important. Software integrated into a commercial product can require a different analysis from free and open-source development outside commercial activity. Read the actual new boundaries rather than describing digital scope as unlimited.
Harm and evidential access change
The new Directive expressly addresses medically recognised psychological harm and destruction or corruption of data not used for professional purposes. Property exclusions and the treatment of the defective item still require care. It is inaccurate to summarise the revision as compensation for every digital loss. Pure economic loss and professional data can raise other legal questions without falling within this damage category.
Articles 9 and 10 establish disclosure and rebuttable-presumption mechanisms with defined conditions. The claimant's starting burden remains damage, defectiveness and causation. These mechanisms respond to information imbalance, especially for technically complex products, but are not a general presumption that every manufacturer is liable. The main changes explained separates the particular proof routes from the broader policy objective.
Supply chains and post-supply control
The new framework addresses a wider set of possible responsibility routes, including authorised representatives, fulfilment service providers and certain platforms under the stated conditions. It also addresses substantial modification and manufacturer control of digital elements. A supplier's role should be mapped against the relevant provision rather than inferred from its position on a purchase order or logistics diagram.
Continuing control matters to defectiveness timing and to particular exemptions. The ability to supply updates, authorisation of integration and consent to changes can all require evidence. The analysis is more specific than saying the manufacturer is always liable after sale or never liable once ownership changes. Preserve the actual release, approval and service relationships.
Compare issues, not slogans
Keep the earlier national implementing law in the research record when an older product is involved. A new internal policy cannot retrospectively change that product's governing legal framework.
A useful comparison record has a separate entry for product scope, damage, actor, proof, exemptions and time rules. For each issue, identify the governing text and national law. This approach prevents an attractive new rule from being combined with a favourable older rule to create a framework that neither Directive actually establishes. Marketing summaries about stronger protection are not a substitute for the operative provisions.
National implementation and procedure remain necessary research tasks. This page does not assert the status of any Member State or determine an individual's rights under the older or newer regime. Its purpose is to explain the transition and the main categories of change while keeping the product date, legal basis and evidential limits visible.
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 market or first-use date
- Applicable version of the EU and national framework
- Issue-by-issue comparison rather than a merged rule summary
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, 21, 22 ↗
- 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.