FAQESPREU

ESPR market surveillance What evidence should teams prepare for authority checks

Prepare product conformity evidence, , Digital Product Passport (DPP) records, and a response path for competent authority requests.

This FAQ helps separate binding ESPR duties from product-specific delegated-act details and national penalty rules that must be checked in the relevant source.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

Under Regulation (EU) 2024/1781, ESPR is not a voluntary audit checklist. Member States plan checks for ESPR and delegated acts, authorities may evaluate products and require corrective action, and economic operators need records that show conformity, DPP availability, traceability, and response readiness. Timings on this page are tied to cited sources; verify current legal source language before implementation decisions.

Search this module

Find a question or answer quickly

6 of 6 questions
Question 1

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 record 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 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 , , 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.
Question 2

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 , draw up an 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 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.
Recommended next step

Build an ESPR evidence file before authority requests arrive

Connect delegated-act applicability, conformity evidence, DPP data, and response ownership so market-surveillance requests can be answered from maintained records.

Question 3

How should teams respond to authority requests?

For an authority request, identify the product and delegated act, collect the requested conformity evidence, provide it in the required form and language, record what was sent, and track corrective action to 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, including , in a language easily understood by that authority. They must respond in paper or electronic form as soon as possible and in any event within 15 days of receipt. Economic operators must also be able to provide supply-chain traceability information to 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 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, , 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.
Question 4

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 , 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; 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.
Question 5

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.

Member States set penalty amounts and national enforcement details. Article 74 requires penalties to be effective, proportionate and dissuasive. Its factors include the nature, gravity and duration of the infringement, intent or negligence where appropriate, the responsible person's financial situation, determinable economic benefit, environmental damage, mitigation or remediation, whether the infringement is repeated, and other aggravating or mitigating circumstances. Check the relevant national law for amounts and 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 supported by cited sources, mark it as unresolved in the product evidence file instead of filling the gap with assumptions.
Question 6

Questions and answers

What is the main ESPR task for product teams?

Build a product-level evidence file that links the applicable delegated act, each requirement and supporting test or calculation, , the , marking, DPP records, supply-chain traceability, and a named response owner. Keep it current before placing the covered product on the market or putting it into service.

How long should supply-chain traceability information be kept ready?

Economic operators must keep the relevant supply-chain traceability information available for 10 years after receiving or supplying the products. They must provide it to a authority in paper or electronic form within 15 days of a request.

Can teams publish product-specific surveillance rules before the delegated act is known?

No. Use the applicable delegated act for the product requirements, conformity route, evidence, and any product-specific surveillance support measures. Use the relevant Member State law or authority source for national procedures and penalty amounts; the ESPR framework does not supply those details for every case.

When must the conformity file be reassessed?

Reassess conformity when a production process, product design, product characteristic, harmonised standard, common specification, or other technical specification changes and the change may affect compliance. Update the supporting , declaration, marking, instructions, and DPP data that the change affects.

What happens when an authority finds ESPR non-compliance?

The authority evaluates the product and can require the economic operator to correct the non-compliance. If the operator does not correct it, authorities can restrict or prohibit market availability or require withdrawal or recall. The responsible operator should record the authority finding, affected identifiers and markets, correction, customer or authority notifications, and closure evidence.

Primary sources

References and citations

eur-lex.europa.eu6 citations
Referenced sections
  • Primary legal source for ESPR market surveillance, safeguards, penalties, conformity assessment, technical documentation, DPP duties, and delegated-act limits.
  • Grounds the market-surveillance planning, risk evaluation, corrective-action, withdrawal, recall, conformity, DPP, and penalty framework.
  • Supports the conformity-assessment, technical-documentation, EU declaration, marking, and retention duties in Articles 27 and 44 and Annex IV.
Show 3 more
  • Grounds authority request handling, 15-day traceability responses, corrective action, and formal non-compliance categories.
  • Supports DPP availability, accuracy, access rights, data carrier, unique identifier, and Annex III data-element guidance.
  • Grounds the delegated-act dependency for product requirements and the Article 74 limits on national penalty detail available from ESPR itself.
"Planned market surveillance activities"
More quoted passages
"technical documentation"
"within 15 days"
"accurate, complete and up to date"
"effective, proportionate and dissuasive"
etsi.org2 citations
Referenced sections
  • Technical source for DPP information-model concepts, access rights, interoperability, verifiability, traceability, and the boundary between generic DPP standards and product-specific requirements.
  • Provides technical source support for DPP information models, access rights, interoperability, verifiability, traceability, and the limits of generic DPP standards compared with product-specific legal requirements.
"structured collection of product-specific data"
single-market-economy.ec.europa.eu2 citations
Referenced sections
  • Commission source for DPP data sharing with consumers, businesses, public authorities, and possible inclusion of instructions or conformity documents.
  • 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.
"available to consumers, businesses and relevant public authorities"
commission.europa.eu2 citations
Referenced sections
  • Commission overview source support for ESPR objectives and the DPP's role in sustainability information, circularity, and legal compliance.
  • Explains that ESPR requirements are set through the framework and that the DPP supports sustainability information, circularity, and legal compliance.
"strengthen legal compliance"
Show all related guides (36)

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 cited 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 cited 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

Cited 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 product-group intake checklist for ESPR delegated acts, covering product identification, DPP data, ecodesign requirements, conformity evidence, transition dates, and source limits.

ESPR delegated act intake workflow

A source-based intake workflow for ESPR delegated acts: trigger checks, product-group scope, requirement extraction, DPP impacts, release gates, owners, and evidence outputs.

ESPR delegated acts watchlist for product and DPP teams

Track the adopted ESPR 2025-2030 working plan, indicative delegated-act years, product scope, DPP dependencies, evidence owners, and unresolved legal details.

ESPR destruction of unsold goods: disclosure, ban scope, and records

Cited 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-cited 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, and the six DPP standards cited in Decision (EU) 2026/1736.

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

Source-cited ESPR guide to delegated-act information requirements, product labels, digital product passport access, data carriers, and unsold-goods disclosure.

ESPR market surveillance technical documentation checklist

Source-cited 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

ESPR penalties guide explaining Article 74, why fine amounts depend on Member State law, and which conformity and market-surveillance records matter.

ESPR Product Priorities and Delegated Acts Tracker

Track the ESPR 2025-2030 product priorities, indicative adoption years, delegated-act status, DPP dependencies, owners, and evidence.

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 Timeline: Fixed Dates and Delegated-Act Phasing

A cited ESPR timeline separating fixed framework milestones from product-specific application dates, DPP readiness, unsold-goods duties, surveillance, and evaluation.

ESPR unsold goods disclosure tracker

Track ESPR unsold-product disclosures under Regulation (EU) 2026/2 and destruction-ban derogations under Regulation (EU) 2026/296.

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 scope-bounded 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 duties with PPWR packaging design, labelling, conformity, producer-responsibility, and waste obligations.

ESPR vs REACH and RoHS Comparison

Compare ESPR ecodesign, sustainability, information, and digital product passport requirements with separately sourced REACH and RoHS substance-control context.

What ESPR is and why it matters

A source-cited explainer of the EU Ecodesign for Sustainable Products Regulation, including scope, delegated acts, DPPs, unsold goods, and enforcement limits.