A correction to one temporal provision
The Official Journal corrigendum of 7 May 2026 corrected Article 2(1) of Directive (EU) 2024/2853. The corrected provision covers products placed on the market or put into service after 8 December 2026. This is the rule to use when describing the new Directive's temporal product scope. The correction does not move the separate 9 December 2026 deadline for national transposition in Article 22.
The EU Product Liability Directive explanation uses the corrected boundary. The importance of the corrigendum is practical: an otherwise careful analysis can select the wrong temporal scope if it relies on an outdated downloaded copy or summary. Check the provision itself and the official correction rather than assuming that every document carrying the Directive number contains identical wording.
Why a one-day difference is material
The product-date rule helps decide which EU framework must be investigated for a particular product. A mistaken boundary can therefore affect which definitions, evidence mechanisms and responsibility provisions a reader considers. The correction should not be dismissed as harmless typography merely because most product histories are months away from the boundary. An accurate site must also work for products close to the transition.
For a product first placed on the market on 9 December 2026, the corrected after-8-December rule is directly relevant. That does not by itself establish defectiveness, damage, causation or national implementation. It establishes a temporal point that belongs at the beginning of the legal analysis. The remainder of the framework still needs to be applied on its own terms.
What the correction did not change
The corrigendum identifies Article 2(1). It does not rewrite the entire Directive or establish a new national compensation procedure. It does not turn an accident date into the product market date, and it does not state that every later update makes an older physical product newly placed on the market. Those questions require separate definitions, provisions and facts.
It also does not verify any Member State's implementing legislation. Article 22 remains the EU-level transposition provision, while national law requires examination of official adopted measures and commencement. The Directive timeline separates these institutional and product-related dates. Keeping them apart avoids a correction to one provision becoming an unsupported claim about several others.
Consolidated records and authentic texts
EUR-Lex provides the Directive, consolidated documentation and the official corrigendum. A consolidated text helps readers follow the current wording, but the authentic acts are those published in the Official Journal. Preserve the correction's identifier or precise link with any internal source note. This lets another researcher trace the change even if an old briefing or printed copy remains in circulation.
A displayed document date should not be treated as conclusive evidence that a correction is absent. Consolidation and document metadata can be confusing to a reader looking only at the heading. Compare Article 2(1), identify the corrigendum and record the version checked. This is more reliable than choosing whichever search result happens to appear most recently published.
Updating an existing research system
Keep a short change note linking the revised statement to the official correction, so later editors can distinguish a deliberate legal correction from an unexplained copy edit.
Search internal guidance, article copy, date calculators, checklists and structured data for outdated temporal language. Review the context of every match. A reference to the 9 December transposition deadline can be correct and should not be globally replaced. The objective is to correct the product scope while preserving other dates that serve different legal functions.
Where a previous conclusion depended on a product close to the boundary, re-examine the source facts and legal analysis. Record what was corrected and why. Do not silently overwrite the historical product date or change an incident date to make an earlier conclusion fit. The source history should show that the legal wording changed in the research record while the underlying factual evidence remained distinguishable.
Using the corrected boundary responsibly
Start with evidence of placing on the market or putting into service under the Directive's definitions. A customer's invoice, a model announcement and a deployment record may answer different temporal questions. Identify which record supports the relevant event and note any uncertainty. If the facts are not sufficient, the responsible conclusion is that temporal scope needs further research, not that the newer regime automatically applies.
The corrected rule is one part of the framework. Article 21's transition, national implementation, product definitions and later modifications can also matter. This page provides an educational explanation of the correction and the records needed to use it accurately. It does not determine the applicable national law, the success of a compensation claim or an individual's filing deadline.
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.
- Official Journal corrigendum dated 7 May 2026
- Version and retrieval date of any downloaded Directive copy
- Corrections to internal summaries, date rules and product-scope 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 2, 21, 22 ↗
- 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.