ESPRWatchlistEU

EU Ecodesign for Sustainable Products Regulation Delegated Acts Watchlist

A source-status watchlist for product groups likely to need ESPR delegated-act monitoring and DPP readiness work.

Use it to separate adopted framework rules, Commission working-plan signals, CIRPASS roadmap candidates, and gaps that still need official delegated-act text.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
4

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

ESPR is framework legislation: product obligations become concrete through later delegated acts or horizontal measures. This watchlist helps product, sustainability, regulatory, data, and supplier teams track likely exposure without assigning invented effective dates, penalties, or final DPP fields before the product-specific acts are available.

Section 1

Watchlist status model

Classify every product group by source status before assigning work. The strongest status is an adopted delegated or implementing act. The next level is a Commission working-plan or implementation page signal. A CIRPASS roadmap or JRC preparatory study is useful for readiness, but it is not a final legal obligation by itself.

For each watchlist row, keep an evidence owner who can prove the product boundary, maintain the cited source, and flag when a draft or adopted act changes the data model.

  • Adopted ESPR framework: Regulation (EU) 2024/1781 sets the delegated-act mechanism, ecodesign parameters, DPP architecture requirements, conformity evidence, and working-plan process.
  • Commission implementation signal: the Commission states that the first ESPR and Energy Labelling Working Plan was adopted in April 2025 and that product rules will be developed through impact assessment and stakeholder consultation.
  • Roadmap candidate: CIRPASS lists aluminium, furniture including mattresses, tyres, detergents, paints, lubricants, chemicals, energy-related products, and ICT products and other electronics as candidate groups for later mandatory DPPs, while warning that the order is not a priority ranking and may change.
  • Open gap: do not assign product-group application dates, exact DPP fields, penalties, or compliance deadlines unless the grounded source includes an adopted act or official Commission text for that specific group.
Sources for this answer
Regulation (EU) 2024/1781 (ESPR)
Adopted framework source for the delegated-act mechanism, product parameters, DPP provisions, working-plan process, conformity evidence, and market-surveillance context.
European Commission ESPR overview
Commission implementation page stating that ESPR product rules follow a working-plan and consultation process, and that DPP content depends on the specific product.
CIRPASS project results
Project-results hub for CIRPASS DPP roadmaps used only as non-binding roadmap support for candidate product groups and DPP implementation dependencies.
Recommended next step

Turn the ESPR watchlist into a maintained evidence register

Map product groups, source status, DPP dependencies, and owner gaps before product-specific delegated acts turn roadmap signals into implementation work.

Research workflow
Open Research Copilot

Monitor ESPR delegated-act and DPP source changes with cited evidence.

Explore next step
Talk to Sorena
Discuss ESPR implementation

Review product-group exposure, source status, and DPP readiness gaps with Sorena.

Explore next step
Section 2

Concrete product-group watchlist

Use the watchlist as a monitoring register, not as a launch calendar. The row owner should hold product taxonomy, supplier data coverage, and current source status for each group.

Textiles and footwear need separate attention because the ESPR framework and Commission page also discuss destruction of unsold textiles and footwear, while delegated-act/DPP product requirements still need the relevant adopted product-specific text before final data fields can be asserted.

  • Textiles and footwear: source status is high for ESPR framework relevance and unsold-product destruction measures; expected requirement families include durability, repairability, recyclability, substances of concern, recycled content, environmental footprint, information requirements, and DPP dependencies; evidence owner: apparel or product-compliance lead plus sustainability data owner; open gap: final product-specific delegated-act fields and application dates are not supplied by the grounding.
  • Iron and steel: source status is preparatory and methodology-backed in JRC material, with CIRPASS roadmap context for DPP readiness; expected requirement families include material efficiency, recycled content, environmental footprint, information requirements, and traceability; evidence owner: materials engineering or procurement compliance owner; open gap: no grounded adopted ESPR delegated act for final obligations or dates.
  • Aluminium: source status is CIRPASS roadmap candidate and preliminary product-priority material; expected requirement families include recycled content, resource efficiency, environmental footprint, information requirements, and supply-chain traceability; evidence owner: materials procurement owner; open gap: no grounded adopted ESPR delegated act for exact DPP content or enforcement timing.
  • Furniture including mattresses: source status is CIRPASS roadmap candidate and preliminary product-priority material; expected requirement families include durability, reparability, reusability, recyclability, recycled content, substances of concern, and information requirements; evidence owner: product engineering owner with supplier-quality support; open gap: no final product boundary, delegated-act date, or DPP field list in the grounded sources.
  • Tyres, detergents, paints, lubricants, chemicals, energy-related products, and ICT products and other electronics: source status is roadmap candidate only for this artifact; expected requirement families should be treated as broad ESPR families until product-specific text exists; evidence owner: regulatory intelligence owner with category-specific product leads; open gap: grounded sources do not provide final obligations, penalties, application dates, or complete DPP fields for these groups.
Sources for this answer
Regulation (EU) 2024/1781 (ESPR)
Adopted framework source for the categories of ecodesign parameters that later product-specific delegated acts may address.
European Commission ESPR overview
Commission page supporting the framework nature of ESPR, DPP dependency on the specific product, working-plan process, and special unsold textiles and footwear measures.
CIRPASS project results
Roadmap support for DPP candidate groups only; use it to prepare systems, not to claim adopted legal obligations.
JRC ESPR method report
JRC methodology support for preparatory studies and design-option ranking, including testing through steel and textiles preparatory work.
Section 3

Expected requirement and DPP impact fields

Do not build a DPP schema from a generic ESPR wish list. Build a draft register that separates product facts you can collect now from legal fields that must wait for the delegated act.

Each row should show whether the likely impact is a performance requirement, an information requirement, a DPP access or identifier requirement, a conformity-assessment evidence item, or a supplier-data dependency.

  • Product group and product boundary: owner is product regulatory; evidence is SKU taxonomy, CN or product-family mapping, and source status.
  • Likely performance requirement types: owner is engineering or product sustainability; evidence is durability, repairability, recyclability, recycled-content, energy or resource-efficiency, substances, and footprint data only where relevant to the product.
  • Likely information and DPP impacts: owner is data governance or PLM; evidence is data-carrier strategy, product identifiers, access-control assumptions, source system ownership, and fields marked draft until an adopted act confirms them.
  • Supplier evidence: owner is procurement or supplier quality; evidence is material origin, substances-of-concern declarations, repair or spare-parts data, recyclability data, and environmental-footprint inputs where needed.
  • Open-source gap: owner is regulatory intelligence; evidence is a dated note explaining which claim is unsupported, which source is being monitored, and what internal work is paused until official text appears.
Sources for this answer
Regulation (EU) 2024/1781 (ESPR)
Adopted framework source for performance parameters, information requirements, DPP requirements, conformity assessment, and documentation retention concepts.
European Commission ESPR overview
Commission page explaining that the DPP stores sustainability, circularity, and compliance information and can include technical performance, materials, repair, recycling, and lifecycle-impact information depending on product rules.
CIRPASS project results
Technical roadmap support for DPP readiness topics such as identifiers, data carriers, system components, dataspace integration, prototyping, and deployment.
Section 4

Blocked facts to leave out until stronger sources exist

A useful watchlist is explicit about what is not yet grounded. That prevents internal teams from converting a roadmap signal into a shipment blocker or public legal claim.

Keep these fields blank or marked pending unless a grounded official source supplies the exact product-specific answer.

  • Do not state product-group application dates for textiles, footwear, steel, aluminium, furniture, tyres, detergents, paints, lubricants, chemicals, energy-related products, ICT products, or electronics unless an official product-specific act in the source pack supports the date.
  • Do not state final DPP data fields, access rules, data-carrier choices, or unique identifier rules for a product group until the delegated act or implementing act confirms them.
  • Do not assign ESPR penalties or fine amounts on this page; the grounding used here supports framework monitoring and product-readiness work, not penalty quantification.
  • Do not treat CIRPASS or JRC roadmap language as binding law; label it as roadmap, project, or preparatory support.
  • Do not claim that a candidate list is ranked by priority when the CIRPASS roadmap warns that the listed order is not a ranking and may change.
Sources for this answer
European Commission ESPR overview
Commission implementation page supporting the cautious status distinction: product rules follow the working-plan, impact-assessment, and consultation process.
CIRPASS project results
Project-results source used to identify roadmap support and to avoid presenting CIRPASS roadmap candidates as adopted legal obligations.
JRC ESPR method report
Methodology source used to describe preparatory-study and design-option work without turning methodology into final product obligations.
Primary sources

References and citations

CIRPASS project results
cirpassproject.eu
Referenced sections
  • Project-results source used to identify roadmap support and to avoid presenting CIRPASS roadmap candidates as adopted legal obligations.
"sector-specific DPP roadmaps"
European Commission ESPR overview
commission.europa.eu
Referenced sections
  • Commission implementation page supporting the cautious status distinction: product rules follow the working-plan, impact-assessment, and consultation process.
"inclusive planning, detailed impact assessments"
JRC ESPR method report
data.europa.eu
Referenced sections
  • Methodology source used to describe preparatory-study and design-option work without turning methodology into final product obligations.
"design options"
Regulation (EU) 2024/1781 (ESPR)
eur-lex.europa.eu
Referenced sections
  • Adopted framework source for performance parameters, information requirements, DPP requirements, conformity assessment, and documentation retention concepts.
"Digital product passports"
Related guides

Explore more topics

ESPR and DPP connection: delegated acts, identifiers, and access
How ESPR connects ecodesign information requirements to Digital Product Passports, including delegated acts, data carriers, identifiers, access rights, registry, and architecture choices.
ESPR Applicability Test for Products and DPP Readiness
A source-linked ESPR applicability test for physical product scope, exclusions, delegated-act dependency, economic operator triage, DPP readiness, unsold goods, and evidence.
ESPR compliance checklist for delegated acts and DPP readiness
A source-linked ESPR checklist for monitoring delegated acts, mapping product requirements, preparing technical documentation, and building DPP and unsold-goods evidence.
ESPR compliance program operating model
Build an ESPR operating model for product-group intake, delegated-act monitoring, supplier evidence, DPP governance, release gates, and authority response.
ESPR compliance: delegated acts, DPP and evidence
Practical ESPR compliance guidance for mapping product delegated acts, Digital Product Passport dependencies, unsold goods duties, technical documentation, standards, and market-surveillance evidence.
ESPR deadlines and compliance calendar
Source-linked ESPR calendar for framework dates, delegated-act dependency, working-plan monitoring, unsold-goods disclosure, and DPP readiness limits.
ESPR delegated act intake by product group
A grounded intake checklist for tracking ESPR delegated acts by product group, covering product identification, DPP data, ecodesign requirements, conformity evidence, and source limits.
ESPR delegated act intake workflow
A source-grounded intake workflow for ESPR delegated acts: trigger checks, product-group scope, requirement extraction, DPP impacts, release gates, owners, and evidence outputs.
ESPR delegated acts FAQ: product rules, DPP impact, and monitoring
Standalone FAQ on ESPR delegated acts, why product-group duties depend on them, what teams should monitor, and how they shape Digital Product Passport information.
ESPR destruction ban and unsold goods FAQ
What ESPR says about preventing destruction of unsold consumer products, annual disclosure, the Annex VII apparel and footwear ban, and grounded derogation evidence.
ESPR destruction of unsold goods: disclosure, ban scope, and records
Source-linked ESPR guide to unsold consumer product disclosure, destruction-ban scope, records, derogations, and national enforcement limits.
ESPR DPP information mapping workflow
Map ESPR delegated-act information requirements into DPP data elements, source systems, access levels, identifiers, carriers, validation evidence, and unresolved design decisions.
ESPR durability, repairability, and recyclability evidence
Build ESPR evidence for durability, repairability, and recyclability without inventing product-group tests before the applicable delegated act is known.
ESPR Ecodesign Evidence Checklist
Checklist for collecting ESPR ecodesign evidence from delegated acts, technical documentation, supplier substantiation, DPP mapping, standards, and market surveillance records.
ESPR ecodesign requirement types: performance, information, and DPP links
Source-grounded guide to ESPR ecodesign requirement types, product parameters, delegated-act dependency, DPP links, and evidence implications.
ESPR FAQ: scope, delegated acts, DPP, unsold goods
Standalone ESPR FAQ answers on product scope, delegated acts, Digital Product Passports, unsold goods, product priorities, standards, surveillance, and source limits.
ESPR harmonised standards and common specifications
How ESPR uses harmonised standards, common specifications, delegated acts, and DPP standards evidence without inventing product-specific requirements.
ESPR Information Requirements to DPP Mapping
Map ESPR information requirements into Digital Product Passport data classes, source systems, access rules, carrier choices, validation checks, and evidence records.
ESPR Information Requirements, Labels, and Disclosure
Grounded ESPR guide to delegated-act information requirements, product labels, digital product passport access, data carriers, and unsold-goods disclosure.
ESPR market surveillance FAQ: evidence, DPP data, and authority requests
Standalone FAQ on ESPR market surveillance: technical documentation, conformity evidence, DPP data, authority response, delegated-act limits, and national penalties.
ESPR market surveillance technical documentation checklist
Source-grounded ESPR checklist for technical documentation, conformity evidence, DPP records, and responses to market surveillance authority requests.
ESPR penalties and fines: Member State rules and evidence
A conservative ESPR penalties guide explaining Article 74, why fine amounts depend on Member State law, and which conformity and market-surveillance evidence matters.
ESPR Product Priorities and Delegated Acts Tracker
Track ESPR priority product groups, source status, delegated-act progress, expected DPP impact, owners, evidence, and source gaps without treating preliminary studies as binding obligations.
ESPR product priorities FAQ: working plan and delegated acts
Standalone FAQ on ESPR product priorities, the Commission working plan, delegated-act dependency, monitoring points, and limits of preliminary source material.
ESPR requirements: delegated acts, ecodesign, DPP, and evidence
ESPR requirements explained as a framework for delegated acts, ecodesign performance and information rules, Digital Product Passports, unsold goods, technical documentation, and market surveillance.
ESPR unsold goods disclosure FAQ
Standalone FAQ on the ESPR Article 24 duty to disclose discarded unsold consumer products, its relationship to the destruction ban, records, and source limits.
ESPR unsold goods disclosure tracker
Track ESPR unsold consumer product disclosure fields, website publication evidence, destruction-ban status, owners, and unresolved source gaps.
ESPR vs Batteries Regulation Comparison
Compare ESPR delegated-act planning with the Batteries Regulation product-specific regime, including DPP overlap, battery passport evidence, timing limits, and source boundaries.
ESPR vs Ecodesign Directive
Compare ESPR with the earlier Ecodesign Directive across scope, legal form, delegated acts, DPP requirements, unsold goods, transition rules, and evidence.
ESPR vs GPSR: Sustainability vs Product Safety
A source-limited comparison of ESPR sustainability and product-information requirements against GPSR product-safety context, with evidence and DPP reuse limits.
ESPR vs PPWR Comparison
Compare ESPR product ecodesign and Digital Product Passport work with the separate PPWR packaging regime, using only source-linked ESPR and packaging-boundary claims.
ESPR vs REACH and RoHS Comparison
Compare ESPR ecodesign, sustainability, information, and digital product passport requirements with source-limited REACH and RoHS substance-control context.
EU ESPR DPP obligations FAQ
Standalone FAQ on Digital Product Passport obligations under ESPR, covering delegated acts, identifiers, carriers, access rights, data governance, and supplier evidence limits.
Timeline for ESPR: practical implementation guide
Practical ESPR guidance for Timeline, with source-linked decisions, owners, evidence records, and implementation steps.
What ESPR is and why it matters
A grounded explainer of the EU Ecodesign for Sustainable Products Regulation, including scope, delegated acts, DPPs, unsold goods, and enforcement limits.
Which products are in scope of the EU ESPR?
Standalone FAQ on ESPR product scope, excluded products, delegated-act dependency, working-plan monitoring, and the digital product passport link.