Product Liability Explained: Defective Products, Damage, Evidence and Responsibility

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

What product liability means

Product liability is the legal responsibility that may arise when a defective product causes harm. Its central question is whether the applicable law requires a particular business to compensate a person for that harm. Product quality, customer dissatisfaction and product safety can all matter, but they are not interchangeable with an established compensation claim. The product, the relevant defect, the damage and the connection between them must be identified separately.

There is no single worldwide product liability code. This guide uses Directive (EU) 2024/2853 to explain a modern framework while distinguishing it from national law and other legal routes. The Directive establishes rules for natural persons harmed by defective products. It does not make every manufacturer responsible for every disappointing outcome involving something it supplied. Begin with scope and evidence, then consider the responsibility rules and available exemptions.

Establish the product and applicable dates

Identify what was supplied, by whom and in which market. For a physical item, record its model, batch and serial number. For software, record the release, deployment and relevant configuration. A connected device may combine hardware, software and a digital service, each with a separate supplier. Calling the whole arrangement a platform or a service does not settle the legal classification. Article 4 provides definitions for products, components, related services and manufacturer control.

The corrected Article 2(1) covers products placed on the market or put into service after 8 December 2026. This is distinct from the 9 December 2026 national transposition deadline in Article 22. Article 21 preserves the old Directive for products placed on the market or put into service before 9 December 2026. Record the relevant product dates rather than assuming the accident date chooses the framework. National implementing legislation and its commencement still need examination.

Identify a safety defect

A defect for this purpose concerns the safety a person is entitled to expect or that applicable Union or national law requires. Article 7 calls for an assessment of all relevant circumstances, including presentation, instructions, foreseeable use, learning behaviour, interoperability, relevant safety requirements and manufacturer control. A product may perform its advertised function while presenting an unacceptable safety risk. Conversely, a failed product does not necessarily expose anyone to the kind of harm addressed by product liability.

Keep the alleged mechanism specific. An allegation that a battery separator failed is different from saying a device was bad. Identify the failure location, operating conditions and evidence supporting the explanation. Preserve alternative hypotheses, including installation problems, external damage and later unauthorised changes. A recall or regulatory finding may be relevant, but the individual damage and causal connection still require analysis. The distinction between product liability and product safety helps keep prevention and compensation questions clear.

Separate damage from the defective item

Article 6 includes death or personal injury, including medically recognised damage to psychological health. It also addresses damage to property subject to important exclusions, and destruction or corruption of data not used for professional purposes. Damage to the defective product itself is excluded. There is also an exclusion for a product damaged by a defective component integrated or interconnected by its manufacturer or within that manufacturer's control. Property used exclusively for professional purposes is excluded.

These boundaries differ. Mixed-use property and mixed-use data cannot automatically be treated alike: the professional-use exclusion for data is broader. Material losses resulting from covered damage and national-law treatment of non-material loss require separate attention. A refund, repair bill, lost subscription fee or missed business opportunity does not become recoverable under this Directive merely because defective software was involved. Other legal regimes may address losses outside this compensation framework.

Connect the defect to the harm

An investigation must explain how the alleged unsafe condition produced the particular damage. Timing can support an inquiry, but an incident after an update does not by itself show that the update caused it. Compare the product state, the sequence of events and plausible competing causes. Preserve original records, identify their source and distinguish direct observations from assumptions. Technical testing should document its conditions and limitations so another reviewer can understand what it establishes.

Under Article 10(1), the claimant must prove damage, defectiveness and their causal link. Later paragraphs create conditional, rebuttable presumptions. Article 9 provides for court-controlled evidence disclosure subject to plausibility, relevance, proportionality and confidentiality protections. These mechanisms help address evidential imbalance, but they are not a universal transfer of every issue to the defendant. The detailed explanation of what must be proven separates the starting burden from the specific routes for assistance.

Map responsibility by legal role

Start with the manufacturer of the allegedly defective product and any relevant component manufacturer. The economic operator map explains the legal roles and their conditions. Article 8 also establishes routes involving importers, authorised representatives, fulfilment service providers, distributors and certain online platforms, each with conditions. A seller is not automatically liable in every case, and an invoice is not a complete operator map. Own-brand supply, substantial modification and the location of the manufacturer can change the investigation.

Contracts can help identify who developed, integrated, approved or supplied a component, but contractual labels do not replace statutory definitions. Multiple operators may be liable for the same damage under the Directive, with joint and several liability addressed in Article 12 and recourse addressed separately. Record actual conduct as well as company names. A development agency, software publisher and device manufacturer may play different roles even when a customer sees only one brand.

Distinguish fault, contract and consumer remedies

The Directive provides a no-fault framework: the claimant's core elements do not include proving careless conduct. This is different from proving a product defect and is not a guarantee of compensation. Article 11 contains exemptions, and scope, proof and time limits still apply. The comparison of product liability and negligence explains why evidence about a manufacturer's conduct can be useful without making negligence an additional universal requirement.

Warranty promises and statutory consumer guarantees ask different questions about conformity and contractual remedies. They may support repair, replacement or other remedies when no qualifying injury has occurred. Product safety rules concern preventing or responding to unsafe products. One incident can therefore require several parallel analyses. Keep each legal route, its defendant, its remedy and its evidence requirements in a separate part of the research record.

Organise an investigation without prejudging it

Create a chronology that distinguishes manufacture, first market placement, installation, software changes, the incident and discovery of the alleged defect. Record uncertainties explicitly. Preserve the product and contemporaneous digital evidence safely; do not run destructive tests or overwrite an incident-time installation merely to reproduce a symptom. Identify who holds missing records and the lawful route for obtaining them. Evidence preservation is useful even when the initial allegation is later disproved.

Use a product liability investigation checklist to connect each record with a question rather than collecting documents without a purpose. National rules determine important aspects of procedure, compensation and time limits. Articles 16 and 17 address limitation and expiry, but a generic article cannot calculate a deadline for an individual dispute. A mature investigation ends with a supported account of what is known, what remains uncertain and which legal questions require jurisdiction-specific assessment.

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 model, batch, serial number and incident-time software version
Sourced chronology of supply, changes, incident and discovery
Separate defect, harm, causal-mechanism and actor records
Applicable jurisdiction, market date and national-law research

A complaint is not a judicial finding. This resource explains questions and sources; it cannot determine the outcome of an individual dispute.

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.