A later improvement is not enough by itself
No. Article 7(3) of Directive (EU) 2024/2853 prevents a product being considered defective solely because a better product, including an update or upgrade, has already been or is later placed on the market or put into service. Product improvement is therefore not, by itself, proof that an earlier version failed the legal safety test. The word solely matters: the provision does not exclude independent evidence about the earlier product's safety.
The overall defectiveness assessment still examines expected or legally required safety in all the circumstances. A later model can be safer in a particular respect without establishing that its predecessor was defective. Equally, a manufacturer cannot answer every supported allegation merely by describing the change as progress. Identify the actual safety allegation and evidence rather than letting either characterisation decide the inquiry.
Establish what changed
Compare the relevant revisions. A newer product may improve convenience, efficiency, durability, accessibility or safety, and several changes may occur together. Preserve specifications, release notes, component identifiers and dates. A marketing statement that the new model is better does not explain the engineering difference. Determine whether the change addresses the same mechanism alleged in the incident or an unrelated product attribute.
For software, distinguish a version made available from one installed on the affected product. An update description may combine safety corrections and new features. Record the incident-time release and the actual effect of the change. Do not assume that every update fixes a legally defective condition or that every unsupported version was necessarily unsafe in the way relevant to the claimed damage.
Compare circumstances as well as designs
Article 7 includes product presentation, foreseeable use, learning, interconnection, relevant timing, safety requirements, safety interventions, intended-user needs and damage-prevention purpose. Those circumstances can differ between versions. A newer product designed for another environment or user group may not be a meaningful direct comparator. Explain why a comparison helps assess the earlier product rather than merely placing two specifications side by side.
The assessment of design defects concerns the safety of the intended configuration. A later alternative can illuminate technical possibilities, but the Directive does not make the existence of any safer alternative the sole statutory test. Avoid importing a particular jurisdiction's alternative-design formula and presenting it as Article 7. The legal question remains the expected or required safety of the product being assessed.
Independent evidence remains important
Examples of independent evidence can include examination of the affected product, tests addressing the relevant risk, contemporaneous safety analysis, applicable mandatory requirements and a well-supported incident mechanism. A later change may help interpret those records, but the explanation should identify the work each item performs. Do not treat the improvement itself as proof of all the underlying propositions.
A change introduced after a safety intervention may have particular factual significance, but its scope and reasons need examination. Preserve the notice, affected versions and stated hazard. A preventive action can respond to uncertainty or risk without deciding compensation. Conversely, calling an action precautionary does not make its factual findings irrelevant. The reader should be able to distinguish the action's stated basis from conclusions drawn later.
Timing and continued manufacturer control
Article 7 includes the time of placing on the market or putting into service and, where the manufacturer retains control afterwards, the time the product left that control. Software and connected products can therefore require more than a comparison between original and replacement models. Identify the relevant change history and who could supply or authorise safety-relevant changes.
Article 11 contains specific rules concerning later defectiveness and manufacturer control, including software and necessary safety updates. Those rules should not be reduced to a general statement that every later update creates retrospective liability. Nor should Article 7(3) be read as eliminating all questions about failures to maintain safety. The relationship between the actual defect, control and applicable provision requires separate analysis.
Causation does not follow from a correction
Even where evidence supports an earlier safety shortfall, the claim needs covered damage and a causal link. A later design that prevents one failure path does not prove that this path caused the incident. Physical evidence, operating conditions, logs and other possible causes still matter. Avoid reasoning backwards from the chosen correction to an unproven account of what happened.
Article 10 provides specific rebuttable presumptions under defined conditions. A newer product is not an independent automatic presumption listed in Article 10(2). If another route is relied on, such as qualifying mandatory safety non-compliance or obvious malfunction, identify its conditions directly. The defendant's right to rebut also remains relevant. A comparison between generations cannot replace that statutory analysis.
A useful comparison states its limits
Document the older configuration, the later change, the reason given and the evidence linking either to the alleged hazard. Separate statements made at the time from later interpretations. Explain whether the comparison shows technical feasibility, supports a particular mechanism or merely demonstrates that product development occurred. Where the reason for a change is unknown, state that limitation rather than assuming a safety admission.
The applicable national implementation and other scope questions still need checking for a particular dispute. Article 7(3) supplies a clear boundary against improvement alone establishing defectiveness. A mature assessment respects that boundary while examining independent evidence of the earlier product's safety, the harm alleged and the causal connection required by the relevant law.
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.