Use this page to separate ESPR framework duties from product-group obligations that only become concrete through delegated acts.
The page focuses on the legal architecture: ecodesign performance and information requirements, Digital Product Passports, unsold goods, technical documentation, market surveillance, standards, and source limits.
Structured answer sets in this page tree.
Cited legal and guidance references.
ESPR is not a single finished checklist for every product. Regulation (EU) 2024/1781 creates a framework for setting product-group ecodesign requirements through delegated acts. A defensible requirements file should therefore track the framework duties that already matter, the product groups and working-plan signals to monitor, and the future delegated acts that will define specific performance, information, DPP, conformity, and evidence obligations.
The core ESPR requirement is structural: products may be placed on the market or put into service only when they comply with ecodesign requirements applicable to those products in delegated acts adopted under Article 4. Until a delegated act applies to a product group, teams should avoid treating ESPR as if it already imposes final product-specific limits, fields, labels, or test methods for that group.
The useful operating record is a delegated-act dependency register. It should identify the product group, relevant commodity codes or descriptions when available, the applicable or expected delegated act, the date of application in that act, the conformity module, the test or calculation method, the required information channel, and the evidence owner.
ESPR delegated acts can set performance requirements, information requirements, or both. Performance requirements are tied to product aspects and parameters such as durability, reliability, reusability, upgradability, repairability, energy and water efficiency, resource efficiency, recycled content, recyclability, environmental impacts, carbon footprint, and expected waste generation.
Information requirements can require product performance information, customer and value-chain instructions, end-of-life information for treatment facilities, substance-of-concern tracking, labels, website or manual disclosures, and Digital Product Passport data. The final scope, wording, method, language, access channel, and transition timing must come from the applicable delegated act.
DPP requirements are part of ESPR information requirements, but the data set, data carrier, access rights, model-batch-item level, update roles, and availability period are delegated-act decisions. Article 9 requires the passport data to be accurate, complete, and up to date when the applicable delegated act requires a DPP.
Teams should build a DPP readiness register, not a final field list. The register should distinguish Article 10 and 11 essential design requirements from product-group data that Annex III says a delegated act can include, such as unique product identifiers, commodity codes, compliance documentation, technical documentation, declarations of conformity, instructions, manufacturer and importer information, unique operator or facility identifiers, and service-provider references.
ESPR contains unsold consumer product obligations that are not the same as product-group ecodesign performance limits. Economic operators that discard unsold consumer products must disclose annual information on number and weight, reasons for discarding, treatment routes, and prevention measures, subject to the enterprise-size rules and application dates in Article 24.
The destruction prohibition is also product-list dependent. Article 25 prohibits destruction of unsold consumer products listed in Annex VII and gives the Commission power to amend that annex and set derogations. A requirements file should therefore record the Annex VII category, enterprise-size status, disclosure evidence, derogation evidence, and whether later delegated acts add products or exceptions.
ESPR requirements need a verification path. Article 39 requires compliance and verification methods to use harmonised standards or other reliable, accurate, and reproducible methods that reflect the generally recognised state of the art and meet delegated-act method requirements.
Article 41 gives a presumption of conformity when products, methods, or DPPs conform to harmonised standards whose references have been published in the Official Journal of the European Union, to the extent those standards cover the requirement. Article 42 allows common specifications only in defined circumstances, such as where requested harmonised standards are not accepted, not delivered, not compliant, or not expected within a reasonable period.
Use this ESPR requirements page to separate binding framework duties from product-group delegated-act dependencies before teams publish claims, build DPP fields, or change conformity evidence.
Use Regulation (EU) 2024/1781 as the binding baseline for ESPR framework duties. Use Commission pages for policy context, working-plan context, consultation status, and explanatory DPP context only when they do not replace the legal text.
Do not use research reports, standards drafts, project deliverables, consultation pages, or roadmap material to invent final obligations, final dates, product-specific limits, penalties, DPP field lists, or access-right models. Those materials can support readiness analysis only when clearly labelled as non-binding or preparatory.
"public consultation on the future Digital Product Passport"
"Ecodesign for Sustainable Products Regulation"
"setting ecodesign requirements"