What Changed Under the New EU Product Liability Directive?

EU Directive-level explanationUpdated 16 October 2026By ProductLiability.help editorial desk

The revision changes several connected questions

Directive (EU) 2024/2853 modernises how EU product liability addresses digital products, harm, supply-chain roles and evidence. The core remains compensation for damage caused by a defective product under a no-fault framework. The revision does not create a universal remedy for every customer complaint or every loss involving technology. Its changes need to be applied together with scope, exemptions and national implementation.

The Directive overview explains the framework as a whole. For change assessment, begin with the products and relationships a business actually has. A manufacturer of connected appliances may face different questions from a raw-material supplier or software publisher. A useful review identifies the relevant provision, the factual relationship and the records needed to assess it.

Products now expressly include software

Article 4 expressly includes software, digital manufacturing files and raw materials. Components can be tangible or intangible, and related services have a defined relationship to product functions. This gives investigators a clearer basis for examining software separately or as part of a larger product. A physical enclosure is not the sole boundary of the relevant technical system.

Delivery labels are not decisive. Software supplied through a network, the cloud or a SaaS arrangement can still require product analysis. At the same time, ordinary information, a general service and non-commercial free and open-source software should not be treated as identical categories. Inventory the actual functionality and commercial supply instead of classifying an entire business by one marketing term.

Expected safety includes digital relationships

Article 7 addresses circumstances including learning behaviour, foreseeable interconnection and relevant safety requirements, including cybersecurity. Manufacturer control can continue after initial supply. Article 11(2) limits particular post-supply exemptions for software, related services, necessary safety updates and substantial modifications within that control. Product liability research therefore needs a history of changes, rather than only a snapshot from the day of sale.

This is not a blanket duty to support every product forever. The relevant law, safety expectations, control and facts must be examined. An update that introduces an unsafe behaviour, a missing safety update and an unauthorised third-party modification are different scenarios. Record who could supply or approve changes and whether the affected release actually reached the product involved in an incident.

Damage coverage is broader but bounded

Article 6 expressly recognises medically recognised psychological harm within personal injury and includes destruction or corruption of data not used for professional purposes. The property and data categories have different professional-use wording. Property used exclusively professionally is excluded, while professional use of data is enough to exclude that data category. Mixed-use situations therefore need careful factual records.

The defective product itself and certain component-related damage to the integrated product are excluded. Pure economic loss, privacy infringement or discrimination does not by itself trigger liability under this Directive. Other legal routes can remain relevant. A change summary should therefore identify the new category and its limits, rather than suggesting every digital loss is now compensable.

Responsibility reflects modern supply chains

Article 8 provides responsibility routes beyond the final product manufacturer, including relevant component manufacturers and specified EU actors where the manufacturer is outside the Union. Distributors and certain online platforms have conditional treatment. Substantial modifiers can also be treated as manufacturers in the stated circumstances. These are separate tests, not a rule making everybody in the supply chain automatically liable.

Article 12 addresses multiple operators liable for the same damage, while recourse is a separate issue. Contracts, supplier records and the practical distribution route become useful evidence of roles. A label such as technology partner or logistics provider is less helpful than a record of who manufactured, imported, integrated, approved or supplied the relevant part of the arrangement.

Evidence mechanisms address information imbalance

For implementation planning, connect each change to a practical question: which products depend on software, which operators hold evidence and which teams can reconstruct the incident-time state? The answer should be supported by records rather than a generic declaration of readiness.

Article 9 provides court-controlled evidence disclosure subject to plausibility and safeguards. Article 10 provides defined rebuttable presumptions, including routes involving particular non-disclosure, safety non-compliance, obvious malfunction and technical complexity. The ordinary starting burden remains defectiveness, damage and causation. Assistance on one issue should not be described as proof of all the others.

The comparison with the previous Directive explains why product dates must be checked before using these provisions. The corrected new scope is products placed on the market or put into service after 8 December 2026. Readiness means maintaining a supported product, actor, control and evidence map, then checking relevant national law. It does not mean a business has received a certification or a guarantee about future claims.

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.

Affected product and component inventory
Role and control map for digital elements
Evidence retrieval and preservation responsibilities

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.

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