ESPRRequirement taxonomyEU

EU Ecodesign for Sustainable Products Regulation Ecodesign Requirement Types

Use this page to separate ESPR performance requirements, information requirements, product parameters, and DPP dependencies before a product-specific delegated act applies.

The page stays at framework level: it explains how requirement types are set and evidenced without inventing product-group limits, dates, penalties, or final DPP fields.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

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

ESPR does not create one universal checklist for every product. It creates a framework for product-specific or horizontal ecodesign requirements, set mainly through delegated acts, that can take the form of performance requirements, information requirements, or both. Teams should therefore track the requirement type, the product parameter it uses, the delegated act that makes it operative, the DPP or data-carrier channel used to publish information, and the technical evidence needed to verify compliance.

Section 1

What are the ESPR ecodesign requirement types?

ESPR ecodesign requirements divide into two legal types: performance requirements and information requirements. Both are tied to product aspects and are laid down for covered product groups in delegated acts adopted under Article 4.

A team should not treat the framework regulation alone as a finished product rule. The operative requirement set depends on the relevant delegated act, which must define the covered product group, the applicable ecodesign requirements, verification methods, conformity-assessment module, technical-documentation elements, and transition details.

  • Performance requirements set minimum or maximum levels, or non-quantitative requirements, for relevant product parameters.
  • Information requirements require product information, including DPP and substances-of-concern information unless an exception applies.
  • Product parameters come from Annex I and include durability, repairability, recyclability, resource use, recycled content, carbon footprint, environmental footprint, waste generation, functional performance, and related sustainability parameters.
  • Delegated acts determine which requirements actually apply to a product group and how compliance information must be verified.
  • A DPP requirement is part of the information-requirement architecture, not a standalone substitute for meeting performance requirements.
Recommended next step

Turn ESPR guidance into an evidence workflow

Use this ESPR guide to map delegated-act requirements to product parameters, DPP data dependencies, and technical documentation evidence.

Section 2

How do performance requirements differ from information requirements?

Performance requirements control product characteristics directly. Article 6 says products must comply with performance requirements laid down in the applicable delegated act, and those requirements are based on Annex I product parameters.

Information requirements control what must be made available about the product and how it is supplied. Article 7 includes DPP requirements and substances-of-concern tracking as minimum elements, and it can also require performance information, user and repair information, treatment-facility information, and other information that influences sustainable choices or product handling.

  • Performance evidence should map the product to the threshold, level, test method, calculation method, or non-quantitative condition in the delegated act.
  • Information evidence should map each required statement to its source data, update owner, language or access channel, and publication format.
  • Information requirements may be set for a product parameter even when no performance requirement is set for that same parameter.
  • Substances-of-concern information is not a generic marketing claim; Article 7 specifies tracked data such as substance identity, product location, concentration information, safe-use instructions, and end-of-life information.
  • Where a DPP exists, Article 7 requires the relevant information to be provided in the DPP and, where necessary, through other forms such as the product, packaging, label, manual, website, or application.
Section 3

How do delegated acts control the requirement set?

The delegated act is the hinge between ESPR's framework language and product-level obligations. Article 8 requires delegated acts to specify the covered product group, ecodesign requirements, relevant Annex I parameters for which no requirement is necessary, methods or standards, digital-tool requirements where relevant, information needed for compliance verification, conformity assessment, manufacturer information, transitional period, and review date.

This matters operationally because the same Annex I parameter can drive different outputs. A delegated act might set a performance threshold, require disclosure, require a DPP data element, require a label, or decide that no ecodesign requirement is needed for that parameter for the product group.

  • Track the product group definition and commodity-code scope before assigning obligations.
  • Record each Annex I parameter considered and whether the delegated act sets a performance rule, information rule, both, or no requirement.
  • Separate legal applicability from data readiness: a DPP schema decision does not prove the product meets a performance requirement.
  • Tie each compliance method to the test, measurement, calculation standard, harmonised standard, or common specification named in the delegated act.
  • Avoid publishing dates or product-group requirements until the relevant delegated act or working-plan source supports them.
Section 4

Where do DPPs and data carriers fit?

A DPP is part of the information-requirement system. Article 9 says products can be placed on the market or put into service only if a DPP is available in accordance with the applicable delegated act and DPP requirements, where that requirement applies.

Article 10 connects the DPP through a data carrier to a persistent unique product identifier. The delegated act specifies the data to include, the data carrier or carriers, the layout and positioning of the carrier, whether the passport is at model, batch, or item level, who can access data, who can create or update data, and how long the passport remains available.

  • Do not design a fixed DPP field list for all ESPR products; Annex III lists possible data elements and the delegated act selects what is required for the product group.
  • Keep DPP granularity explicit: model, batch, or item level changes evidence ownership and update logic.
  • Keep data-carrier placement explicit because Article 10 allows the product, packaging, or accompanying documentation as specified by the delegated act.
  • Plan access rights separately for public users, value-chain actors, market surveillance authorities, and customs authorities.
  • Treat data accuracy, completeness, currency, interoperability, security, privacy, and fraud prevention as DPP design controls, not just website-display details.
Section 5

What evidence should support each requirement type?

Evidence should mirror the requirement type. For performance requirements, keep the product data, measurements, calculations, test reports, and comparison against the delegated-act requirement. For information requirements, keep the source data, publication channel, DPP field mapping, substance-tracking data where required, and proof that the information remains accurate and accessible.

Annex IV describes internal production control and technical documentation. It expects documentation that allows conformity assessment against the delegated act, including design and manufacturing information, standards or technical specifications used, design calculations, examinations, measurements against ecodesign requirements, test reports, and a copy of the information provided under Article 7.

  • For performance rules, maintain a trace from Annex I parameter to delegated-act requirement to test or calculation result.
  • For information rules, maintain a trace from required statement to source data, publication channel, language/access decision, and update owner.
  • For DPP rules, maintain a trace from delegated-act field requirement to model, batch, or item identifier, access right, data-carrier placement, and backup or service-provider control.
  • For market-surveillance readiness, keep the technical documentation and declaration-of-conformity package aligned with the delegated act and available for authority requests.
  • For unsupported claims, record the gap instead of turning framework-level ESPR language into product-specific requirements.
Primary sources

References and citations

data.europa.eu
Referenced sections
  • Annex IV describes technical documentation for internal production control and requires evidence such as measurements, test reports, and copies of Article 7 information.
"technical documentation shall specify the applicable requirements"
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 delegated acts watchlist for product and DPP teams
Track ESPR delegated-act priorities without inventing dates: product groups, source status, likely requirement types, DPP impact, evidence owners, and open source gaps.
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 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.