Not every breach has the same legal significance
Regulatory non-compliance can be relevant to product defectiveness, but the exact requirement matters. Article 7 of Directive (EU) 2024/2853 includes relevant product-safety requirements in the overall assessment. Article 10(2)(b) then provides a more specific evidential rule: defectiveness is presumed where the claimant demonstrates non-compliance with mandatory product-safety requirements in Union or national law intended to protect against the risk of the damage suffered.
This is a rebuttable presumption of defectiveness, not an automatic finding of liability. The overall defectiveness framework still distinguishes the product's safety, covered damage and the causal link. A breach of an unrelated administrative obligation does not necessarily meet the presumption's conditions. The analysis should identify the provision, its mandatory character, its application to the product and the risk it protects against.
Establish that the requirement applies
Start with the official legal text and the relevant product category, activity and date. A requirement can apply only to defined products, particular operators or a specified stage of supply. A general summary of a regulation may omit those limits. National rules require verification from authoritative national sources before their content or current application is asserted.
Distinguish a legal requirement from a voluntary standard or an internal quality target. A standard may have a particular legal effect under a relevant regime, but that effect needs its own basis. Failure to follow a preferred test method is not automatically a breach of mandatory product-safety law. The companion explanation of safety requirements and defectiveness describes how legal rules, standards and compliance documents should be separated.
Demonstrate the non-compliance
An allegation needs evidence that the product did not comply with the relevant requirement. Identify the product version and the material facts. A report about another model, an unexplained test result or a missing document may not establish the alleged breach without further context. Record the method used, the sample examined and the relation between the evidence and the operative provision.
A regulator's finding can be important, but read what it actually decides. It may concern one batch, a labelling issue or a particular hazard. Do not extend it to another configuration without explanation. Distinguish a final finding from an investigation, provisional concern or information request. A notice that a regulator is examining a product does not itself establish the result of that examination.
Connect the protected risk with the actual damage
Article 10(2)(b) expressly links the mandatory requirement to protection against the risk of the damage suffered. Explain that relationship. A rule preventing excessive surface temperature may have a clear connection to certain burns. A different requirement may serve traceability or another objective and need more careful analysis. Avoid assuming that any legal breach is enough because an injury occurred somewhere in the product's history.
This risk connection differs from establishing the causal link between defectiveness and the particular damage. The presumption concerns defectiveness. A claimant still needs the other elements, subject to their own applicable proof rules. Article 10(3), for example, separately addresses causation where defectiveness has been established and the damage is of a kind typically consistent with that defect. Its conditions should not be silently treated as already satisfied.
Preserve the defendant's rebuttal position
Article 10(5) gives the defendant the right to rebut the presumptions. That matters to how an educational explanation describes the evidence. A demonstrated qualifying breach can shift the evidential position without making every factual dispute disappear. The defendant may contest the applicability or satisfaction of a condition, or seek to rebut the resulting presumption through relevant evidence.
A review should therefore record contrary evidence and unresolved issues. The purpose is not to weaken a supported concern, but to state its actual legal significance. A report that omits known limits can confuse a regulatory finding with a concluded compensation case. Keeping the categories separate allows readers to understand both the strength of the evidence and the questions still open.
Compliance is not the reverse presumption
The provision does not say that a compliant product is presumed non-defective for every purpose. Article 7 considers all the circumstances and expected safety as well as legally required safety. Compliance with a specific requirement can be relevant evidence without settling an allegation involving another hazard, foreseeable use pattern or product interaction. Identify the scope of the compliance evidence rather than expanding it into universal immunity.
Article 11(1)(d) provides a distinct exemption where the defectiveness is due to compliance with legal requirements. That is a specific condition, not a general defence based on holding certificates. A product following a legal requirement and a product whose defectiveness was caused by compliance with that requirement are different propositions. The evidence must support the one actually relied upon.
Use a transparent evidence chain
A practical record connects the requirement, applicability, non-compliant condition, protected risk and damage category in separate steps. Preserve the official provision, product identifiers, test evidence and any regulatory decision. Mark whether each step is established, alleged or unresolved. This helps prevent an administrative criticism being mistaken for proof of a safety defect with a demonstrated causal mechanism.
The applicable national legislation and procedural rules still require checking in an individual dispute. Article 10 supplies an evidential framework with specific conditions, not a general prediction about who will win. A precise explanation of those conditions is more useful than a statement that breaking any regulation automatically makes a manufacturer liable.
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.
- Incident-time product identity and configuration
- Source documents and dated safety analysis
- Separate defect, damage and causation records
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 7, 10, 11 ↗
- 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.