ESPR delegated acts FAQ: product rules, DPP impact, and monitoring
What do delegated acts do under the ESPR?
Delegated acts are how the Commission supplements the ESPR with binding product-group rules. Article 4 empowers the Commission to set ecodesign requirements by delegated act, and Article 8 lists the minimum content those acts must specify.
For a covered product group, a delegated act can define the product group, set performance or information requirements, identify test or calculation methods, specify conformity assessment, set manufacturer information obligations, and include transitional and review dates. The delegated act is therefore the place to check the exact product rule, not only the framework Regulation.
Use the ESPR text to understand the framework and powers.
Use the applicable delegated act to identify product-group requirements.
Do not assume a generic ESPR requirement applies to a product unless the framework or the applicable delegated act supports that conclusion.
Track delegated-act review dates because ESPR requirements are designed to adapt to technical progress and market developments.
Article 4 and Article 8 ground the claim that delegated acts set product-group ecodesign requirements and must specify covered products, requirements, methods, conformity assessment, transition, and review elements.
ESPR delegated acts FAQ: product rules, DPP impact, and monitoring
Why do product-group obligations depend on delegated acts?
The ESPR does not make every possible ecodesign duty immediately specific for every product. Article 5 says ecodesign requirements are set for a specific product group and may be differentiated within that group. Article 18 requires a working plan that prioritises product groups and horizontal measures.
This means the practical obligation analysis starts with the product group and the working-plan or delegated-act status. A team can identify that ESPR may be relevant to a product category, but it should not invent a deadline, threshold, conformity module, label content, or product-specific data field unless the applicable delegated act or another grounded source states it.
Map the product to the ESPR product group definition in the delegated act when one exists.
Check whether the obligation is product-specific or horizontal across multiple product groups.
Separate prioritisation signals from binding product requirements.
Record unsupported facts as pending rather than filling gaps with assumed dates or thresholds.
Commission implementation text grounds the public sequence: prioritisation, first ESPR and Energy Labelling Working Plan, then product-rule development through impact assessment and consultation.
ESPR delegated acts FAQ: product rules, DPP impact, and monitoring
What should teams monitor before a delegated act applies?
Monitor four layers: the ESPR working plan, Ecodesign Forum and consultation activity, adopted delegated acts, and any related standards or common specifications needed for testing, measurement, calculation, or DPP operation.
The monitoring output should be a product-group watch record, not a generic compliance memo. For each product group, record the source URL, publication status, affected products, requirement type, application timing if stated, open consultations, and internal owners for product design, sustainability data, conformity assessment, labels, DPP, procurement, and market access.
Working plan: product groups, horizontal measures, and estimated timelines.
Delegated act: product definitions, performance requirements, information requirements, conformity route, transitional period, and review date.
DPP and labels: data carrier, access, label content, and distance-selling access requirements where specified.
Evidence limits: facts not stated in the source remain unresolved and should not be published as commitments.
Commission overview links this working plan as the public planning source for product priorities; use it as a monitoring source, not as a substitute for final delegated acts.
ESPR delegated acts FAQ: product rules, DPP impact, and monitoring
How do delegated acts affect Digital Product Passport work?
The DPP impact is product-specific. ESPR 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 acts and the DPP rules. The same article says those delegated acts specify the data, data carrier, layout and positioning, model-batch-item level, pre-contract access, access rights, update responsibilities, update arrangements, and availability period.
Annex III lists possible DPP elements, but it does not by itself finalize every product group's passport. Teams can prepare their DPP architecture around stable ESPR concepts such as unique identifiers, open and interoperable data, access rights, back-up copies, and no customer personal data without consent. They should wait for the applicable delegated act before freezing product-specific mandatory fields.
Prepare data governance for model, batch, or item-level passports, but confirm the required level in the delegated act.
Prepare access controls for customers, economic operators, repairers, recyclers, market surveillance, customs, and other actors where applicable.
Treat Annex III as the menu of possible passport data, then check the delegated act for what is required for the product group.
Do not publish product-specific DPP field lists unless the field is grounded in Annex III, Article 9, Article 10, Article 11, or the applicable delegated act.
Article 9, Article 10, Article 11, and Annex III ground the DPP availability rule, delegated-act specifications, technical requirements, access concepts, and possible DPP data elements.
Commission DPP overview grounds the plain-language explanation that the passport stores sustainability, circularity, and legal-compliance information and supports consumers, manufacturers, authorities, and customs.
ESPR delegated acts FAQ: product rules, DPP impact, and monitoring
Where do the public sources stop short?
The current public grounding supports the ESPR framework, the delegated-act mechanism, the working-plan approach, the first priority product groups listed in the Regulation, DPP architecture concepts, and example categories of DPP information. It does not justify inventing product-specific application dates, penalties, conformity modules, passport field lists, or measurement thresholds for every product group.
When a business question needs those details, the answer should identify the missing source and the monitoring channel. If no applicable delegated act has been adopted for the product group, the most accurate answer is that the product-specific obligation is not yet fully determined from the available sources.
Does ESPR create a destruction ban for all unsold goods?
No. ESPR sets a general prevention principle for unsold consumer products, a disclosure duty for economic operators that discard unsold consumer products, and a specific prohibition for the consumer products listed in Annex VII.
Article 23 says economic operators must take reasonably expected measures to prevent the need to destroy unsold consumer products. Article 24 is a disclosure rule. Article 25 is the prohibition rule, and it applies first to the Annex VII list: apparel and clothing accessories, plus footwear.
Treat prevention as the baseline control for all unsold consumer product decisions.
Treat disclosure separately: it covers discarded unsold consumer products and asks for annual quantities, reasons, treatment routes, and prevention measures.
Treat the ban separately: Article 25 prohibits destruction of Annex VII products from 19 July 2026, subject to the enterprise-size carve-outs and derogation framework in the ESPR text.
Do not describe ESPR as banning destruction of every unsold product category unless a later grounded delegated act has added that category.
What must be disclosed about discarded unsold consumer products?
Article 24 requires economic operators that discard unsold consumer products directly, or have them discarded on their behalf, to publish annual information in a clear and visible manner at least on an easily accessible website page.
The disclosure is not only a count. ESPR asks for the number and weight by product type or category, reasons for discarding, relevant derogations where applicable, the proportion sent to preparing for reuse, recycling, other recovery, or disposal, and measures taken or planned to prevent destruction.
Keep annual number and weight records by product type or category.
Record the reason for discarding and, where relevant, the Article 25(5) derogation basis.
Track where discarded products went: preparing for reuse, recycling, other recovery including energy recovery, or disposal.
Publish prevention measures taken and planned, not only disposal outcomes.
Retain delivery, reception, and derogation documentation because the Commission or a competent national authority can request it.
Which products are named in the ESPR destruction ban?
The grounded product list is Annex VII. It names apparel and clothing accessories, including leather or composition-leather apparel and accessories, knitted or crocheted apparel and accessories, non-knitted or non-crocheted apparel and accessories, and specified headgear. It also names footwear under commodity codes 6401 to 6405.
The Commission can amend Annex VII to add products, but Article 25 requires evidence work before doing so: prevalence and environmental impacts must be assessed, Article 24 disclosure information must be considered, and an impact assessment must be based on best available evidence and analyses.
Grounded current Annex VII groups: apparel and clothing accessories; footwear.
Grounded apparel/accessory commodity-code references include 4203, 61, 62, 6504, and 6505.
Grounded footwear commodity-code references include 6401, 6402, 6403, 6404, and 6405.
Other product groups should be treated as watch-list candidates unless a grounded delegated act or source confirms their inclusion.
Which enterprise-size limits and derogations are grounded?
Article 24 says the disclosure paragraph does not apply to micro and small enterprises and applies to medium-sized enterprises from 19 July 2030. Article 25 uses the same micro, small, and medium-sized enterprise timing for the Annex VII prohibition.
Article 25(5) gives the grounded derogation reasons the Commission must set out in delegated acts: health, hygiene and safety; damage that cannot be repaired cost-effectively; unfitness for intended purpose; non-acceptance of products offered for donation; unsuitability for preparing for reuse or remanufacturing; unsaleability due to intellectual property infringement, including counterfeit products; and destruction being the option with the least negative environmental impacts.
Do not invent company-size thresholds in the FAQ; use only the ESPR labels micro, small, and medium-sized enterprises unless another grounded source gives threshold definitions for the specific use.
Do not treat Article 25(5) as a self-executing blank cheque. It is a delegated-act framework, so the evidence file should point to the applicable derogation instrument before approving destruction.
Record product condition evidence, repair-cost evidence, donation refusal, reuse or remanufacturing assessment, IP/counterfeit evidence, or environmental-impact comparison only where that reason is actually relied on.
Watch for anti-circumvention: ESPR says operators outside the prohibition must not destroy covered products supplied to them for the purpose of circumventing the ban.
Commission overview states that implementing and delegated acts on destruction of unsold consumer products were adopted on 9 February 2026, but this FAQ does not rely on ungrounded details from those acts.
What evidence should teams keep before discarding or destroying unsold goods?
Keep evidence that proves which ESPR track applied: prevention only, disclosure, Annex VII prohibition, or a specific derogation path. The record should be usable by sustainability reporting, product, legal, logistics, and marketplace teams without relying on local knowledge.
Because Article 24 allows authorities to request information and documentation demonstrating delivery and reception of discarded products, evidence should follow the product flow from internal decision through the third party or waste-treatment destination.
Product classification record against Annex VII commodity-code descriptions.
Enterprise-size applicability note using only the grounded ESPR micro, small, or medium-sized enterprise categories.
Prevention actions considered before destruction, such as resale, donation, repair, refurbishment, remanufacturing, or preparing for reuse where applicable.
Annual disclosure dataset for number, weight, product category, reason, treatment route, and prevention measures.
Delivery and reception records from any third party handling discarded products.
Derogation evidence tied to the exact Article 25(5) reason and the applicable delegated act or source.
ESPR market surveillance FAQ: evidence, DPP data, and authority requests
What should teams do about ESPR market surveillance?
Prepare a product-level evidence file before a product covered by an ESPR delegated act is placed on the EU market or put into service. The file should show which delegated act applies, which ecodesign and information requirements were assessed, how conformity was demonstrated, and where the Digital Product Passport and supporting source data are maintained.
ESPR Article 66 requires Member States to include planned ESPR market surveillance activities in their national market surveillance strategies. Those activities can include document checks and, where appropriate, physical and laboratory checks. Article 69 then gives the authority response path when a product covered by a delegated act presents a risk: evaluation, required corrective action, and possible restriction, withdrawal, or recall if non-compliance is not corrected.
Map each covered product to the applicable ESPR delegated act rather than assuming one generic ESPR test.
Keep technical documentation, EU declaration of conformity, CE or other required conformity marking evidence, product identifiers, and DPP records together.
Assign a response owner who can supply documentation, coordinate corrective action, and update the DPP or public product information when evidence changes.
Do not invent product-specific check frequencies, authority names, or national enforcement steps; use the applicable delegated act and Member State source when those details matter.
ESPR market surveillance FAQ: evidence, DPP data, and authority requests
Which technical documentation and conformity evidence should be ready?
For products covered by a delegated act, the manufacturer must carry out the specified conformity assessment procedure, draw up technical documentation, draw up an EU declaration of conformity where compliance is demonstrated, and affix the required marking. The default ESPR retention rule for manufacturers is 10 years after the covered product is placed on the market or put into service, unless the relevant delegated act sets a different period.
Annex IV describes the internal production control file: product description and intended use, design and manufacturing drawings, explanations needed to understand the design and operation, standards or specifications used, design calculations, measurement results against ecodesign requirements, test reports, and a copy of information supplied under ESPR information requirements.
Evidence should connect each requirement to the test, measurement, calculation, standard, common specification, or design control used to show conformity.
The EU declaration of conformity should identify the product model and reference the applicable delegated act and other Union legal acts when a single declaration covers more than one regime.
Series-production controls should show how process, design, product-characteristic, standard, or specification changes trigger reassessment when conformity may be affected.
Keep the DPP back-up and the most recent DPP version aligned with the conformity file so authority checks do not reveal conflicting data.
ESPR market surveillance FAQ: evidence, DPP data, and authority requests
How should teams respond to authority requests?
The response process should be practical and documented: identify the product and delegated act, collect the requested conformity evidence, provide it in the requested form and language where ESPR requires that, record what was sent, and track any corrective action until closure.
ESPR gives specific response hooks. Manufacturers must provide all information and documentation necessary to demonstrate conformity after a reasoned request from a competent national authority. Economic operators must also be able to provide supply-chain traceability information to market surveillance authorities for 10 years after receiving or supplying the relevant products, and that information must be provided in paper or electronic form within 15 days of the request.
Keep a request log with requester, product identifier, delegated act, documents provided, response date, and unresolved items.
Escalate suspected non-conformity to the product owner immediately because manufacturers and distributors have duties to take corrective action and inform market surveillance authorities in the Member States where the product was made available.
When an authority raises formal non-compliance, check for the listed ESPR issues: CE marking, declaration of conformity, technical documentation, manufacturer or importer information, and other Article 27 or Article 29 administrative requirements.
Do not promise a single EU-wide response deadline for every document; use the specific ESPR provision or national request wording that applies.
ESPR market surveillance FAQ: evidence, DPP data, and authority requests
What DPP and source data should be prepared for surveillance?
The DPP should be treated as inspected product evidence, not only a customer-facing page. ESPR requires DPP data to be accurate, complete, and up to date, connected through a data carrier to a persistent unique product identifier, and structured so access rights can differ by actor and product group. Delegated acts decide the exact data set, carrier, layout, position, granularity, access rights, update rights, and availability period for the product group.
Annex III shows the kinds of DPP data delegated acts may require, including the unique product identifier, commodity codes, compliance documentation such as declarations of conformity and technical documentation, user manuals or warnings, manufacturer and importer information, responsible Union economic operator information, facility and operator identifiers, and the DPP service provider hosting the back-up copy.
Keep source data behind DPP values: laboratory results, calculation files, supplier inputs, standards applied, conformity documents, manuals, and update approvals.
Verify that the data carrier resolves to the right product model, batch, or item level and that the same identifier appears in the evidence file.
Apply access controls that reflect the delegated act; market surveillance and customs authorities are among the actors ESPR expects to access DPP data according to their rights.
Track DPP changes with date, field changed, source evidence, approver, and reason so an authority can see why the current value is trustworthy.
Confirms the Commission's framing of the DPP as a way to store and share product sustainability, durability, environmental, instruction, and conformity information with consumers, businesses, and public authorities.
Provides technical grounding for DPP information models, access rights, interoperability, verifiability, traceability, and the limits of generic DPP standards compared with product-specific legal requirements.
ESPR market surveillance FAQ: evidence, DPP data, and authority requests
What depends on delegated acts and national penalty rules?
The ESPR framework does not itself give every product-specific requirement. Product groups, performance requirements, information requirements, conformity modules, DPP fields, DPP access rights, and any market-surveillance support measures that are necessary for a product group come through delegated acts adopted under ESPR. A team should therefore keep a delegated-act watch list for every product family it sells or imports.
Penalty amounts and many national enforcement details are also source-limited. ESPR Article 74 requires Member States to set penalties that are effective, proportionate, and dissuasive, and to consider factors such as the nature, gravity, duration, intent or negligence, financial situation, economic benefit, environmental damage, prior infringements, cooperation, affected population, and any mitigating or aggravating factors. The grounded ESPR source does not provide national penalty amounts or name national procedures.
Do not publish product-specific ESPR requirements until the applicable delegated act supports them.
Do not infer national penalty amounts from the ESPR framework; use the relevant Member State law or authority source.
Use Article 67 reporting and benchmarking as EU-level context only; it reports checks, non-compliance levels, penalties imposed, benchmarks, and priorities, but it does not supersede national penalty rules.
When a fact is not grounded, mark it as unresolved in the product evidence file instead of filling the gap with assumptions.
ESPR product priorities FAQ: working plan and delegated acts
How are ESPR product priorities identified?
ESPR Article 18 directs the Commission to prioritise products by looking at their potential contribution to EU climate, environmental, and energy-efficiency objectives. The criteria include improvement potential without disproportionate costs, gaps or insufficiency in existing Union law, market-performance disparities, sales and trade volumes in the Union, value-chain impacts, energy and resource use, waste generation, and the need to adapt rules as technology and markets change.
The regulation also requires the Commission to adopt and publish a working plan. That plan lists product groups prioritised for ecodesign requirements, estimated timelines for setting them, and product aspects or groups considered for horizontal requirements. Product-priority status is therefore a signal that a product group is in the Commission pipeline, not a substitute for a product-specific legal act.
Treat the working plan as the authoritative public planning document for ESPR priorities.
Treat JRC preparatory studies as evidence inputs, especially where they explain screening criteria, environmental relevance, policy gaps, and improvement potential.
Treat the adopted delegated act, not a priority list alone, as the source of binding product-specific requirements.
Commission overview confirming that the first ESPR and Energy Labelling Working Plan was adopted after a prioritisation exercise and that product rules follow through further process.
ESPR product priorities FAQ: working plan and delegated acts
Which product groups should businesses monitor first?
Article 18 names the product groups the Commission must prioritise in the first working plan: iron and steel; aluminium; textiles, in particular garments and footwear; furniture, including mattresses; tyres; detergents; paints; lubricants; chemicals; relevant energy-related products; and information and communication technology products and other electronics. The Commission must justify any departure from that list in the first working plan.
For businesses, the practical action is to map products, components, materials, and sales channels against those priority groups and then track the Commission working plan, preparatory-study launches, Ecodesign Forum consultations, draft delegated acts, and final delegated acts. Do not assign application dates, DPP data fields, performance thresholds, conformity modules, or penalties from the priority list alone.
Monitor whether a product group is in the working plan and whether a preparatory study has started.
Monitor whether the rulemaking is product-specific or horizontal across multiple product groups.
Monitor draft and final delegated acts for the actual requirements, transition periods, conformity assessment, information channels, and DPP details.
Record assumptions as preliminary until the delegated act for the relevant product group is adopted.
ESPR product priorities FAQ: working plan and delegated acts
When do product priorities become legal obligations?
Product priorities become operationally binding only when the relevant delegated act sets ecodesign requirements for the product group. ESPR Article 8 says delegated acts must define the product group, the requirements, the relevant parameters, verification methods, information needed for compliance checks, conformity assessment, transitional period, and review timing.
The same dependency applies to Digital Product Passport obligations. ESPR says DPP information requirements apply in accordance with the applicable delegated act, and that act specifies the data to be included, data carrier, access rules, level of identification, update responsibilities, and availability period. A priority product group may therefore be a strong readiness signal, but it does not by itself fix the DPP fields for a business system.
Use Article 18 to identify monitoring priority.
Use Article 8 and the final delegated act to identify binding product requirements.
Use Articles 7 to 11 and the final delegated act to identify DPP content, access, identifier, and update rules.
Use the delegated act transition period for application timing instead of reusing dates from consultations, studies, or roadmap material.
CIRPASS material is useful for understanding DPP implementation concepts and system questions, but it is project guidance rather than an adopted ESPR delegated act.
ESPR product priorities FAQ: working plan and delegated acts
How should preliminary JRC and CIRPASS material be used?
Use JRC material to understand the evidence base behind prioritisation and methodology. The preliminary JRC study describes screening of end-use and intermediate product groups, environmental relevance, policy gaps, improvement potential, and horizontal measures; it also states that its results are preliminary and do not bind the Commission.
Use CIRPASS material for DPP-readiness questions such as data governance, interoperability, system architecture, value-chain access, and implementation barriers. Do not convert CIRPASS recommendations or roadmaps into legal requirements unless the same point appears in ESPR or in an adopted delegated or implementing act.
Label JRC priority-study conclusions as evidence inputs, not final regulatory choices.
Label CIRPASS recommendations as implementation and standards-readiness material, not binding legal content.
Avoid publishing product-group obligations, penalties, DPP data fields, or application dates unless the source is ESPR itself or an adopted act for that product group.
Keep a source log that separates regulation text, working-plan text, preparatory-study evidence, consultation material, and project guidance.
Article 24 applies to economic operators that discard unsold consumer products directly or have those products discarded on their behalf. The disclosed information must cover the number and weight of discarded unsold consumer products per year, differentiated by product type or category.
The disclosure must also explain the reasons for discarding, identify any relevant Article 25(5) derogation where applicable, show the proportion delivered to preparing for reuse, refurbishment, remanufacturing, recycling, other recovery including energy recovery, or disposal, and describe measures taken or planned to prevent destruction.
Publish the Article 24 information annually for the preceding financial year.
Make the information clear, visible, and available at least on an easily accessible page of the operator's website.
Treat the first disclosure as covering discarded unsold consumer products from the first full financial year during which ESPR is in force.
Do not apply the Article 24 paragraph to micro and small enterprises; medium-sized enterprises are covered from 19 July 2030.
Grounds the Article 24 disclosure trigger, data fields, website-publication duty, annual timing, and micro, small, and medium-sized enterprise caveats.
Commission overview confirming that large and eventually medium-sized companies must disclose annual website information such as number, weight, and reasons for discarded unsold consumer products.