The question is safety
A product is defective under Article 7 of Directive (EU) 2024/2853 when it falls short of the safety people are entitled to expect or safety required by Union or national law. The assessment concerns safety rather than ordinary disappointment with performance. A scratched surface, a short battery life or a missing convenience feature does not automatically establish the kind of defect relevant to compensation for harm. Conversely, a product can carry out its advertised function while exposing people to an unacceptable danger.
This guide explains that EU framework. The applicable national legislation, product dates and other scope conditions must be checked before applying it to a particular dispute. Establishing a defect also differs from establishing liability. Article 10 starts with three separate matters: defectiveness, damage and the causal connection between them. Identifying an unsafe condition does not itself identify compensable harm or prove how an incident occurred.
All the circumstances, rather than one decisive label
Article 7 requires consideration of all circumstances. Its examples include the product's presentation, labelling, design, technical features, composition and packaging, together with instructions for assembly, installation, use and maintenance. What was actually supplied matters. A current manual may differ from the version accompanying the affected product, and a model name may cover several hardware or software revisions.
The assessment also includes reasonably foreseeable use; the effects of learning or acquiring new features; and foreseeable effects from products expected to be used together, including through interconnection. Relevant timing includes placing on the market or putting into service and, where a manufacturer retains control afterwards, the time that control ends. Relevant safety requirements, including safety-related cybersecurity requirements, are another circumstance. These considerations make the inquiry wider than a factory inspection or an isolated specification sheet.
Article 7 further identifies recalls and other relevant safety interventions by competent authorities or economic operators; the particular needs of the intended user group; and failure to fulfil a product's very purpose of preventing damage. The last consideration is particularly relevant to protective products such as alarms. The list is inclusive, rather than a closed checklist that excludes other relevant evidence. A reasoned assessment explains why the circumstances matter to the alleged risk.
Design, production and information
A design allegation concerns the safety of the product concept or specification. A production allegation concerns how the particular product was made or assembled. An information allegation concerns presentation, warnings or instructions. These categories help organise evidence, but the Directive does not replace its overall safety test with three independent statutory claim routes bearing those names.
The distinction matters during investigation. If every unit follows a specification that permits hazardous operation, proving that the affected unit matched that specification does not resolve the safety issue. If an isolated soldering fault caused an electrical hazard, a sound design document does not resolve the condition of the actual unit. Read the explanation of design defects alongside the product's manufacturing and testing history to identify the allegation precisely.
Warnings can influence legitimate expectations, especially where risks cannot be eliminated, but the existence of a warning does not automatically make a dangerous design safe. Consider whether information was understandable, available when needed and consistent with the product's presentation. The warning and instruction analysis distinguishes missing safety information from a missing marketing detail. A warning defect still requires a connection to the harm alleged, rather than a general criticism of the manual.
Intended use does not exhaust foreseeable use
A manufacturer's intended purpose is important but does not necessarily describe every foreseeable situation. Realistic handling, installation, cleaning, maintenance and interaction with other products may influence expected safety. Recital 46 explains reasonably foreseeable use by reference to intended use, ordinary use indicated by construction and lawful, readily predictable human behaviour. A label alone therefore does not answer whether a use pattern was reasonably foreseeable.
This does not mean that every imaginable misuse must be treated as an expected use. Describe the actual behaviour, the environment and the product's safeguards before choosing a label. An overloaded machine, a predictable momentary mistake and deliberate interference with a safety device raise different questions. The discussion of reasonably foreseeable use explains why an evidence-based description is more useful than simply declaring that somebody used the product incorrectly.
Connected products and changing conditions
A connected device may depend on another product, embedded software, an update or a related digital service. Article 7 expressly recognises foreseeable interconnection and later learning. Identify the actual combination at the time of the incident: component revision, installed software, permitted accessories, configuration and service state. The latest supported configuration may not describe the relevant historical state.
The legal inquiry must still identify the applicable responsibility conditions. A compatible accessory does not automatically transfer all liability to its supplier, and a software update does not automatically create a new liability finding. Records of authorisation, control and the effect of the change help separate the condition of the product from the roles of businesses involved. Interoperability and product safety considers how an interaction can create a risk absent when each item is examined separately.
Safety rules and recall evidence
Compliance documents and product-safety requirements can be valuable evidence. They are not interchangeable. Identify whether a document is a binding legal requirement, a technical standard, a test report, a declaration or a regulator's finding. Then identify the risk and product configuration it addresses. A passing result on one test is evidence about that test, rather than a universal conclusion about every hazard.
Article 10(2)(b) provides a rebuttable presumption of defectiveness where the claimant demonstrates non-compliance with mandatory Union or national product-safety requirements intended to protect against the risk of the damage suffered. It does not say that every administrative breach proves defectiveness. Nor does that presumption automatically establish damage and causation. Other Article 10 presumptions have their own conditions, including the obvious-malfunction route and the separate causal-link provision.
Article 7 also makes recall and other relevant safety intervention part of the circumstances. A notice may identify a hazard, a component or a production range, but it must be matched to the relevant product and event. Absence of a recall is not proof of safety. The recall evidence guide explains how to read the scope and reasons without treating preventive action as a compensation award.
Newer products and useful evidence
Article 7(3) prevents defectiveness being inferred solely from the existence of a better product, update or upgrade, whether already available or introduced later. Product development alone therefore does not prove an earlier product unsafe. Equally, that rule does not exclude independent evidence that the earlier product fell below the required safety level. The inquiry remains focused on the relevant product and circumstances.
A useful file preserves product identity, dated instructions, photographs, use conditions, maintenance history, relevant safety requirements and the alleged failure mechanism. Keep original observations separate from later expert explanations. Record gaps and competing causes rather than silently filling them. Evidence should allow another reader to distinguish what was observed, what was inferred and what still needs technical examination.
Does an incident establish the defect?
An incident can provide important evidence, particularly when its circumstances support a statutory presumption. It is still necessary to describe what happened and to identify the applicable proof rule. A product breaking, a user being injured and a manufacturer issuing a notice are different facts. A mature assessment connects them through evidence instead of substituting one for the others.
The practical objective is an intelligible safety analysis. State the expected level of protection, the alleged shortfall and its relevance to the incident. Then address damage, causation, responsible actors and potential exemptions separately. This preserves the difference between a credible safety concern and a concluded legal entitlement.
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
A newer model or a recall notice does not, standing alone, decide defectiveness in an individual case.
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 ↗
- 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.