The 2026 and 2030 Handover Dates: What Happens to the Ecodesign Rules You Already Comply With

The ESPR conversation belongs almost entirely to sectors that have never been regulated for ecodesign before. Textiles. Furniture. Steel. Tyres. For those industries the task is adoption - building a capability from nothing.

There is another cohort, and it is large, and almost nobody is writing for it.

Manufacturers of energy-related products have been complying with ecodesign requirements for over fifteen years. Lighting. Electric motors. Servers and data storage. Washing machines, refrigeration, transformers, external power supplies, air conditioners. They hold conformity documentation, they run test programmes, they have staff who have lived through several rounds of tightening requirements.

For them the question is not how to start. It is what happens to the regulation they already comply with.

Regulation (EU) 2024/1781 repealed Directive 2009/125/EC when it entered into force on 18 July 2024. That headline has caused a genuinely damaging amount of confusion.

Nothing lapsed

Start here, because the misreading is common enough to be worth stating without qualification.

The repeal of the Ecodesign Directive did not repeal the implementing regulations made under it.

ESPR's transitional regime - the provisions around Article 75 - keeps implementing measures adopted under Directive 2009/125/EC in force. Delegated and implementing regulations adopted under the previous Directive remain applicable until they are repealed or replaced by an ESPR delegated act.

If you make a product covered by one of those regulations, your obligations on 19 July 2024 were identical to your obligations on 17 July 2024. They remain so today. Your declarations of conformity did not become invalid. Your technical documentation did not need reissuing. No transitional deadline passed unnoticed.

The framework changed. Your rules did not - yet.

The two dates

Certain provisions of the old Directive were kept alive for limited purposes, and this is where the calendar gets specific. Two dates recur in the commentary.

31 December 2026. The window during which measures still in the pipeline can be adopted under the old Directive rather than waiting for an ESPR delegated act. Commentary generally ties this to the product groups already covered by the former Directive, allowing work already well advanced to be completed under the machinery it was started with, instead of being restarted under ESPR.

31 December 2030. The outer horizon. The point by which the legacy implementing measures are expected to have given way, with the intervening period available for amending measures already in force.

A necessary caveat, offered in the spirit this site tries to maintain: secondary sources are not perfectly consistent on the precise scope each date governs, and the distinction between "measures that may still be adopted" and "measures that may still be amended" is easy to blur in summary. The dates themselves recur reliably. What each one governs is worth checking against the regulation text for your specific product group before you build a plan on it.

What is not in doubt is the direction. There is a defined end to the legacy regime, and it is inside most manufacturers' current product-planning horizon.

Migration is an expansion, not a re-issue

This is the part that matters commercially, and the part most likely to be underestimated by a team that reads "transition" and thinks "paperwork".

The implementing regulations under the old Directive were, with limited exceptions, about energy efficiency in use, with a growing but still modest overlay of resource-efficiency and information requirements in later measures. Ecodesign meant, primarily, watts.

ESPR's delegated acts can require considerably more. When your product group migrates, the replacement act can bring with it:

• A Digital Product Passport. Nothing in the old implementing regulations required anything like it. This is a data and systems programme, not a testing programme.
• Substances of concern disclosure. ESPR's definition reaches well beyond REACH SVHCs, and the tracking obligation runs down through your supply chain to a level of granularity most ErP manufacturers have never had to reach.
• Recycled content and durability requirements, with the evidence to support them.
• Classes of performance, potentially - a ranking rather than a threshold, which is a different competitive proposition entirely.

So the migration is not a like-for-like re-issue of your existing obligations under a new legal base. It is your existing obligations plus a set of data requirements that did not previously exist.

The practical implication: the transition period is not dead time. It is the only time you get to build the data infrastructure before the act that requires it applies.

Reading the Working Plan for your own product

The ESPR Working Plan 2025-2030 is usually discussed for its new priority groups. For this audience the relevant content is the treatment of energy-related products and the review and migration of existing measures.

Three things to extract when you read it for your category:

1. Is your product group listed for review or replacement, and when? An indicative date is not a legal deadline, but it is the best available signal of sequencing, and it tells you roughly how much runway you have.

2. Is your product group also exposed to horizontal requirements? This is the genuinely new risk and it deserves its own section.

3. What does the preparatory study for your category discuss? Preparatory studies are the clearest early view of what a delegated act will contain. If your category's study is exploring reparability scoring or recycled content thresholds, that is what is coming.

The horizontal risk

Under the old Directive, requirements arrived product group by product group. If your implementing regulation had not been revised, nothing changed for you.

ESPR can set requirements horizontally - across product groups - and the Working Plan explicitly contemplates horizontal work on aspects such as reparability and recyclability.

The consequence for ErP manufacturers is a sequencing risk that did not previously exist. A horizontal act could reach your product before your product-group-specific act does. You could find yourself with new obligations while your governing implementing regulation is still the same 2019 measure you have complied with for years.

Anyone whose regulatory monitoring is organised around "watch my implementing regulation for amendments" has a gap. That approach was correct for fifteen years. It is no longer sufficient.

Documentation and conformity continuity

Practical questions, and the honest answers.

Does existing technical documentation carry over? The substance largely does. Test results, performance data and design documentation supporting requirements that persist into the ESPR act remain relevant evidence. What changes is the frame: references to the legal base, the declaration of conformity, and the conformity assessment route your ESPR delegated act specifies. Expect to reissue documents, not to redo the underlying work - for the requirements that carry over.

What about requirements that do not carry over? Where the ESPR act introduces something new - passport data, substances tracking, recycled content evidence - there is no existing evidence to reuse. This is where the real effort sits, and it is not a documentation exercise.

CE marking? Continues. ESPR sits within the same conformity assessment architecture, and we have covered how ESPR conformity assessment works in detail.

Timing? Delegated acts normally carry a transition period after adoption before they apply. That period is for implementation, not for starting to think about implementation. If your first substantive action happens on the adoption date, an 18-month transition to build passport infrastructure and supply-chain substance data is not generous.

What to do now

Four steps. The first is more valuable than it sounds.

1. Build the inventory. For every SKU, record which implementing regulation currently governs it. A surprising number of manufacturers cannot produce this list quickly, particularly after acquisitions or portfolio changes. Everything else depends on it.

2. Check each regulation's status in the Working Plan. Flag which are queued for review or replacement and on what indicative timing. Add a separate flag for horizontal exposure - this is the one your existing monitoring probably misses.

3. Do a gap analysis against a plausible ESPR act, not against your current one. Take your product group's preparatory study and ask what data an ESPR-style act would require that you do not hold. Substance data at the granularity ESPR contemplates is usually the largest gap, and the longest to close, because it runs through suppliers you do not control.

4. Do not build twice. The most expensive mistake available here is standing up a tactical system to satisfy an amended legacy regulation, then rebuilding it two years later for the ESPR act. If you are investing in product data infrastructure during the transition, build it to the ESPR data model - passport-shaped, substance-aware, verifiable - even where your current obligations do not require it.

The short version

Your existing ecodesign implementing regulations remain in force and continue to bind you until an ESPR delegated act replaces them. Two dates bound the handover - commonly cited as 31 December 2026 and 31 December 2030 - and the direction of travel is not in question even where the fine print rewards checking.

When replacement comes, it will bring obligations the old regime never contained. The manufacturers who handle this well will treat the transition period as build time for data infrastructure they can see coming, rather than as a quiet interval before a paperwork exercise.