What Must Be Proven in a Product Liability Claim?

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

Start with the three core elements

Article 10(1) of Directive (EU) 2024/2853 requires the claimant to prove damage, defectiveness of the product and the causal link between them. These are separate issues. Proof that a person was injured does not by itself prove that the product was defective, and proof of a defect does not by itself show that it caused the particular injury. The framework does not add manufacturer negligence to these three core elements.

Other threshold questions remain important. The relevant product and dates must fall within the applicable law, the damage must be of a covered kind and the defendant must meet the responsibility conditions. The product liability fundamentals place those questions around the proof rule. A useful investigation records what supports each proposition and what remains uncertain instead of relying on an undifferentiated statement that the product caused a problem.

Prove damage of the relevant kind

Article 6 identifies the Directive's damage categories and exclusions. Records should establish what was harmed, who suffered the harm and the nature of the resulting loss. Personal injury, property damage and data destruction or corruption require different evidence. Do not infer that a company's business interruption is within this Directive merely because software was involved. Nor should damage to the defective item itself be confused with damage to other property.

The data and property exclusions are not identical. Data used for professional purposes are excluded from the data category, while the property exclusion concerns property used exclusively for professional purposes. Medical, ownership, usage and restoration records may help clarify the facts, but their legal significance still depends on the governing framework. The national rules concerning compensation calculations and non-material losses also need examination.

Prove an unsafe defect

Defectiveness under Article 7 concerns expected or legally required safety, assessed in all the circumstances. Identify the alleged unsafe condition, the product version and the situation in which it could produce harm. A useful technical report states its test conditions, assumptions and limits. It distinguishes an observed malfunction from a conclusion that the product did not provide the safety the legal test required.

Relevant materials may include design and manufacturing records, instructions, safety requirements, recall notices and incident-time configuration. None should be treated as conclusive merely because it looks official or technical. A conformity report for one revision may not cover another, and a later recall may concern a different mechanism. The evidence must be connected to the product and allegation actually under review.

Prove the causal connection

Causation asks whether the defect produced the damage. An investigation should describe the mechanism, not merely the order of events. If damage followed an update, examine what changed, whether the affected release was deployed and how the change could produce that kind of harm. Preserve evidence of competing explanations such as power conditions, installation faults or unauthorised modifications.

Separate the product's involvement from its causal role. A device may be present at an incident without initiating it. A failure discovered during inspection might have been caused by the accident rather than caused the accident. Chronology, physical examination and digital records should be compared, with uncertainty recorded rather than concealed by a confident narrative.

Disclosure is conditional and court-controlled

Article 9 provides for disclosure of relevant evidence held by a defendant when the claimant presents sufficient facts and evidence to support the plausibility of the compensation claim. It also addresses disclosure by claimants in the specified circumstances. Courts must consider necessity, proportionality, legitimate interests and protection of confidential information, including trade secrets. The provision is not an unrestricted right to obtain every internal document.

Describe missing evidence by the question it could answer. A request for deployment records tied to a specific product and incident is different from a demand for every company email. The investigation checklist can help organise those questions. Access, preservation and disclosure must follow the applicable procedure; practical relevance alone does not authorise entering somebody else's system or collecting personal data without a lawful basis.

Presumptions do not remove every issue

Article 10 provides rebuttable presumptions for defined situations. These include certain failures to disclose, specified safety non-compliance and obvious malfunction during reasonably foreseeable use or ordinary circumstances. A further route concerns a typical connection between an established defect and damage. Technical or scientific complexity can support assistance where the paragraph's excessive-difficulty and likelihood conditions are satisfied. Identify the actual provision and what it allows to be presumed.

The defendant may rebut these presumptions under Article 10(5), and exemptions remain a separate question. National implementation and procedure also require review. The corrected product-date scope is after 8 December 2026. A disciplined evidence matrix therefore records the ordinary element, the supporting facts, any claimed assistance and the remaining gaps, without presenting an allegation or presumption as a final judicial finding.

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.

Evidence matrix separating defect, damage and causation
Source and limitations for each technical or factual record
Grounds and missing conditions for any proposed presumption

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.