ESPR vs Ecodesign Directive What actually changed

ESPR extends the ecodesign approach to almost all physical goods placed on the EU market or put into service, with specific exclusions and product-specific tailoring through later acts.

The Ecodesign Directive focused on energy-related products. Existing implementing measures under that framework remain important for covered product groups until they are repealed, replaced, or declared obsolete.

Do not treat an existing Ecodesign Directive product conclusion as enough for ESPR. Check whether the product is energy-related and already covered by an implementing measure, then separately check whether an ESPR product group or horizontal requirement is being developed.

ESPR is a regulation, chosen to replace the directive model with uniform application across the Union for the new framework and for horizontal elements such as unsold-goods transparency, circumvention, and market surveillance.

The Ecodesign Directive was a directive framework that relied on implementing measures for covered energy-related products.

For new ESPR work, track delegated and implementing acts under Regulation (EU) 2024/1781. For legacy product rules, keep a separate inventory of applicable Ecodesign Directive implementing measures and the ESPR transition rule that keeps them relevant.

ESPR gives the Commission power to set product-specific or horizontal ecodesign requirements through delegated acts. Those acts determine the actual requirements for a product group.

The Ecodesign Directive used implementing measures adopted for specific energy-related product groups. Those measures can still control products during the ESPR transition.

The practical trigger is not the ESPR title alone. A product team needs the current product-group act, the requirement parameter, and any transition provision before changing design, labelling, conformity, or evidence processes.

ESPR explicitly covers performance requirements and information requirements. The Commission overview lists durability, reusability, upgradability, reparability, maintenance, refurbishment, energy and resource efficiency, substances inhibiting circularity, recycled content, remanufacturing, recycling, footprint, waste, and sustainability information as possible areas.

The Ecodesign Directive was centred on energy-related products, although earlier implementing measures also included some circularity aspects such as durability, repairability, and recyclability.

Map each product requirement to its legal source and parameter. Do not infer a recycled-content, DPP, repair, or disclosure obligation for a product unless the relevant delegated or implementing act actually sets it.

ESPR strengthens market-surveillance planning and corrective-action mechanics. For products covered by ESPR delegated acts, authorities can evaluate compliance, require corrective action, restrict or withdraw products, and rely on technical documentation and declaration-of-conformity evidence.

The Ecodesign Directive also used conformity assessment, technical documentation, declarations, and safeguard mechanisms for products covered by its implementing measures.

Keep evidence at product-model level: applicable act, harmonised standards or common specifications used, measurement results, information provided under information requirements, declaration of conformity, and retained technical documentation. Transition products may need both the old implementing-measure record and ESPR market-surveillance response readiness.

ESPR introduces the Digital Product Passport as a way to make product information electronically available across the value chain and to authorities. Delegated acts specify which DPP data elements are required or allowed for the relevant product group.

The Ecodesign Directive did not create the ESPR DPP architecture. It did include information obligations through implementing measures, but not the ESPR passport system with unique identifiers, registry, data carrier, and web portal architecture.

Treat DPP readiness as an ESPR workstream. Legacy Ecodesign Directive technical files may feed the passport, but the DPP data model, access rights, identifiers, and update responsibilities must be checked against ESPR and the applicable delegated act.

ESPR adds rules addressing destruction of unsold consumer products, including a ban for unsold textiles and footwear and disclosure duties for large and later medium-sized companies, as described by the Commission overview.

The Ecodesign Directive comparison side does not provide an equivalent general unsold-goods destruction and disclosure regime.

Do not park unsold-goods controls inside an old Ecodesign Directive file. They need separate ESPR ownership for product classification, discarded-product metrics, reasons for discard, website disclosure, and any applicable ban or derogation.

ESPR repeals Directive 2009/125/EC from 18 July 2024, but Article 79 preserves specified Directive provisions for certain transitional cases and keeps existing implementing measures relevant until repeal or obsolescence where the article says so.

The Ecodesign Directive side remains relevant mainly through product-specific implementing measures and transitional provisions, not as a source for new ESPR-only obligations such as the DPP system or unsold-goods regime.

When briefing a product team, cite the exact current source: ESPR framework article, ESPR delegated act, legacy Directive implementing measure, or transition clause. Leave dates, penalties, and product obligations blank unless the grounded source states them for that product group.

If a product is already covered by a valid Directive 2009/125/EC implementing measure, use that measure for the legacy requirements that still apply during the transition.

If an ESPR delegated act covers the same product group or requirement, use the ESPR act for the new framework requirements and keep the transition crosswalk in view.

First identify the current legal act, then check Article 79 transition rules before retiring old evidence or replacing a product-specific implementing measure with an ESPR workflow.