FAQDPPEU ESPR

EU Digital Product Passport questions answered

Concise answers on how the EU works under the Ecodesign for Sustainable Products Regulation.

Covers who creates and updates passports, which product groups are first in scope, what goes into the registry, how customs access works, and how public and restricted data should be separated.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
5 sections8 primary sources7 FAQ modules
Overview

The EU is the ESPR mechanism for making product sustainability, circularity, traceability, and compliance information available electronically. The exact passport content, access rights, , and product level are set in product-specific delegated acts, so implementation starts with the applicable product group rule rather than a one-size-fits-all passport template.

Browse sub-FAQs

Choose the question set you need

These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.

Browse all FAQ items31
Focused FAQ modules
7
Showing 7 of 7
FAQ module

DPP QR code vs NFC data carrier choices under EU ESPR

How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier.

4 items
FAQ module

EU DPP customs access: registry, portal, and restricted data

FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data.

4 items
FAQ module

EU DPP unique identifier requirements: product, operator and facility IDs

FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence.

5 items
FAQ module

Public vs restricted EU Digital Product Passport data

How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules.

5 items
FAQ module

What is the EU Digital Product Passport registry?

FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming.

5 items
FAQ module

Which products come first for the EU Digital Product Passport?

FAQ on EU Digital Product Passport product priority: batteries have a separate passport rule, while ESPR product groups depend on the working plan and delegated acts.

4 items
FAQ module

Who must create an EU Digital Product Passport?

DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together.

4 items
Question 1

Who creates EU Digital Product Passports and when are they required?

Under ESPR, a product covered by a can be placed on the EU market or put into service only if a is available as required by that delegated act. The passport data must be accurate, complete, and up to date.

The for the product group specifies which actors create the passport, which actors may update which data, whether the passport is at model, batch, or item level, how long it remains available, and how customers can access it before purchase. Manufacturers must ensure the passport is available for covered products; the economic operator placing the product on the market must also provide access support to dealers and online marketplaces and make a back-up copy available through a DPP service provider.

  • Start by identifying whether a product-specific ESPR covers the product.
  • Use that to assign the passport creator, data updater, passport level, access method, and availability period.
  • Do not assume every passport is item-level; ESPR allows the to choose model, batch, or item level.
  • Do not treat the registry response as proof of product compliance; ESPR says the unique registration identifier communication is not proof of compliance.
Question 2

Which product groups come first under ESPR?

ESPR is framework legislation: concrete DPP duties arrive through product-specific or horizontal delegated acts. The adopted 2025-2030 working plan prioritises new work on textiles and apparel, furniture, tyres, mattresses, iron and steel, aluminium, repairability, and recycled content and recyclability of electrical and electronic equipment. It also carries forward work on specified energy-related products.

The working plan is narrower than the list in ESPR Article 18. Detergents, paints, lubricants, and chemicals were not included as product groups in the adopted plan; footwear is subject to a separate study. A working-plan date is an indicative date for adopting a measure, not the date every product in that group must carry a passport.

  • Indicative adoption sequence for the new product work: iron and steel in 2026; textiles and apparel, tyres, aluminium, and repairability in 2027; furniture in 2028; mattresses and recycled-content and recyclability rules for electrical and electronic equipment in 2029.
  • ICT products are covered through the horizontal measures and some energy-related product work rather than one generic ICT in the working-plan table.
  • Separate working-plan monitoring from active delegated-act compliance. The sets the covered products, DPP fields, access rights, carrier, product level, transition period, and application date.
Question 3

What data is public, restricted, or available to customs?

ESPR does not make every DPP field public. It requires free and easy access for customers, manufacturers, importers, distributors, dealers, repairers, refurbishers, remanufacturers, recyclers, market surveillance authorities, customs authorities, civil society organisations, trade unions, and other relevant actors based on the access rights set in the applicable .

The went live on 20 July 2026 and stores the identifiers and metadata required by the applicable legal act. Under ESPR, it stores at least unique identifiers and, for products intended for release for free circulation, the commodity code. The separate automatic customs verification applies only when the EU CSW-CERTEX interconnection is operational.

  • Public-facing DPP views should expose only the fields the makes accessible to customers and other public stakeholders.
  • Restricted views should protect fields whose access is limited to authorities, supply-chain actors, or other named roles.
  • Customs workflows need the unique registration identifier and commodity code path, not only a consumer-facing QR landing page.
  • The Commission web portal is for search and comparison of DPP data according to each stakeholder's access rights.
Recommended next step

Prepare the Digital Product Passport evidence model

Use the applicable delegated act to map passport fields, access rights, registry data, identifiers, data carriers, owners, and update controls before publishing a DPP endpoint.

Question 4

How should teams handle identifiers, QR codes, NFC, and governance?

The DPP must be connected through a to a persistent . The data carrier must be physically present on the product, packaging, or accompanying documentation as specified by the , and the data must be open-standard, interoperable, machine-readable where appropriate, structured, searchable, and transferable without vendor lock-in.

ESPR does not hard-code QR or NFC as the universal answer in the main regulation. The product specifies the and layout. QR codes are a common candidate for electronic access, while NFC or RFID may be relevant where the selected standard and product rule allow them; the governance control is that identifiers, data carriers, access rights, update rights, back-up copies, security, privacy, and service-provider arrangements remain traceable and documented.

Since 15 July 2026, six cited harmonised standards cover DPP data exchange, unique identifiers, data carriers, storage and persistence, lifecycle APIs, and system interoperability. Conformity with a cited standard gives a presumption of conformity for the ESPR Articles 10 and 11 requirements it covers. It does not decide whether a product needs a DPP or which fields and access rights apply.

  • Maintain a , relevant operator identifiers, facility identifiers where required, commodity code, compliance documentation links, instructions, importer details, and DPP service-provider reference where the requires them.
  • Keep customer personal data out of the DPP unless there is explicit consent under EU data-protection rules.
  • Restrict who can introduce, modify, or update DPP data according to delegated-act access rights.
  • Use open, interoperable formats and avoid vendor lock-in in the passport data exchange layer.
  • For NFC or RFID implementations, check the product and the selected identification standard before treating a tag as an accepted DPP .
Question 5

Questions and answers

Who creates an EU ?

The product-specific decides which actors create the passport or update its data. Manufacturers must ensure a passport is available for covered products. Article 10(4) separately requires the economic operator placing the product on the market to make a back-up copy available through a DPP service provider.

Which product groups are first in scope?

Covered LMT batteries, industrial batteries above 2 kWh, and electric vehicle batteries have the first fixed passport date: 18 February 2027 under the separate Batteries Regulation. Under ESPR, the 2025-2030 working plan schedules iron and steel first for indicative measure adoption in 2026, followed by textiles and apparel, tyres, aluminium, and other measures. None of those working-plan dates is a universal DPP go-live date; the applicable sets the requirement and transition.

What does customs check in the DPP system?

Once the EU CSW-CERTEX interconnection is operational, customs will verify at least the unique registration identifier and commodity code against the Registry data for products intended for release for free circulation. The customs check will not prove that the product complies with ESPR or other Union law.

Is every DPP field public?

No. Access depends on the rights set in the applicable . The public portal lets stakeholders search and compare data according to their access rights, while restricted data can remain limited to authorities or other named roles.

Do the harmonised DPP standards decide which products need a passport?

No. Commission Implementing Decision (EU) 2026/1736 cites six EN 182xx:2026 standards for DPP data exchange, identifiers, carriers, persistence, APIs, and interoperability. Conformity with a cited standard gives a presumption of conformity only for the ESPR Articles 10 and 11 technical requirements it covers. A product-specific or separate Union legislation still decides product scope, mandatory passport content, access rights, passport level, transition, and application date.

How often must a operator repeat identity verification?

From 6 August 2026, a verified economic operator keeps Registry verification only until its electronic identification means expire and never for more than three years. After the earlier of those events, it cannot register a new DPP or modify Registry data until it successfully repeats the verification process. The operator should record the expiry date and complete renewal before a planned product registration or correction.

Primary sources

References and citations

eur-lex.europa.eu5 citations
Referenced sections
  • Primary legal source for DPP requirements, product-group delegated acts, identifiers, registry, customs checks, access rights, web portal, and governance.
  • Supports the DPP requirement for products covered by delegated acts, the requirement for accurate and current data, and the allocation of creation, update, access, and availability details through product-group delegated acts.
  • Article 9 makes the DPP obligation and its operational details depend on the applicable delegated act.
Show 2 more
  • Supports role-based DPP access, registry contents, customs verification of unique registration identifiers and commodity codes, and the public web portal for search and comparison.
  • Supports DPP identifier, data carrier, interoperability, personal-data, update-rights, security, privacy, back-up, and service-provider governance requirements.
"DIGITAL PRODUCT PASSPORT"
More quoted passages
"the data in the digital product passport shall be accurate, complete and up to date"
"based on their respective access rights"
"connected through a data carrier to a persistent unique product identifier"
single-market-economy.ec.europa.eu2 citations
Referenced sections
  • Commission source on DPP system governance topics, including data storage, management by service providers, certification questions, and stakeholder access.
  • Confirms that the DPP is intended for consumers, businesses, and relevant public authorities and that future DPP rules cover data storage, management, and service-provider governance.
"how data should be stored and managed by service providers"
More quoted passages
"available to consumers, businesses and relevant public authorities"
data.europa.eu2 citations
Referenced sections
  • Current binding source for the six cited harmonised DPP standards and their limited presumption-of-conformity effect.
  • Current binding source for the six cited EN 182xx:2026 standards and their presumption-of-conformity effect for covered ESPR Articles 10 and 11 requirements.
eur-lex.europa.eu2 citations
Referenced sections
  • Current Commission working plan for product priorities, excluded Article 18 categories, and indicative adoption dates.
  • Commission working plan identifying the adopted product priorities, indicative adoption years, horizontal measures, carried-over energy-related products, and exclusions from the Article 18 list.
single-market-economy.ec.europa.eu2 citations
Referenced sections
  • Current Commission source for the Registry launch, testing environment, registration channels, and decentralised product-data model.
  • Confirms the 20 July 2026 Registry launch, decentralised product-data model, registration channels, and current testing environment.
commission.europa.eu2 citations
Referenced sections
  • Commission overview describing the DPP purpose and its role in sustainability, circularity, legal compliance, and customs checks.
  • Explains the DPP as an electronic identity card for products, components, and materials that supports sustainability, circularity, and legal compliance.
"making it easier for consumers, manufacturers, and authorities"
More quoted passages
"a digital identity card for products, components, and materials"
ref.gs1.org2 citations
Referenced sections
  • Technical standards source support for data-carrier terminology and implementation options including barcodes, RFID, and NFC.
  • Provides source support for data-carrier implementation options such as barcodes, RFID, and NFC within GS1 identification and data-capture standards.
"AIDC data carrier"
More quoted passages
"barcode, RFID tag or NFC tag"
Show all related guides (30)

DPP Governance, Verification and Audit Controls

Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.

DPP registry and web portal integration under EU ESPR

EU Digital Product Passport Registry and web portal integration guide based on official sources: identifiers, carriers, access rights, providers, and lookup design.

DPP vs Battery Passport: ESPR and Battery Regulation Comparison

Compare the ESPR Digital Product Passport framework with the EU Batteries Regulation battery passport by scope, timing, data, access rights, identifiers, registry, governance, and evidence.

DPP vs EPREL Comparison

Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits.

DPP vs GS1 Digital Link: Duties vs Standard

Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences.

EU Digital Product Passport access: public, restricted, and customs views

How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal.

EU Digital Product Passport API and resolver architecture

DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates.

EU Digital Product Passport Applicability Test

Check whether an ESPR delegated act or battery passport rule may require a Digital Product Passport, which operator owns it, and what evidence to keep.

EU Digital Product Passport architecture and integration

Guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance.

EU Digital Product Passport checklist

A concrete EU Digital Product Passport readiness checklist covering product-group scope, passport fields, identifiers, data carriers, access rights, supplier evidence, registry preparation, and publication controls.

EU Digital Product Passport compliance: ESPR requirements

EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence.

EU Digital Product Passport Data Carriers, Access Control, and UX

How to choose DPP data carriers, identifiers, access rights, and scanning UX under ESPR Articles 9-14, with QR, NFC, RFID, registry, and customs constraints.

EU Digital Product Passport data requirements and fields

How to plan Digital Product Passport data fields under ESPR: delegated-act scope, Annex III data categories, access rights, customs data, and supplier validation.

EU Digital Product Passport deadlines and compliance calendar

EU Digital Product Passport calendar covering the live DPP Registry, ESPR product-rule milestones, and fixed battery passport dates.

EU Digital Product Passport identifier and data carrier design

How to design Digital Product Passport identifiers, QR or other data carriers, resolver links, registry records, access paths, and evidence without overclaiming the EU rules.

EU Digital Product Passport penalties and enforcement

How EU Digital Product Passport breaches can lead to national penalties, corrective action, market restrictions, and customs holds under ESPR or battery law.

EU Digital Product Passport Product Group Readiness

Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs.

EU Digital Product Passport requirements under ESPR

Overview of EU Digital Product Passport requirements under ESPR: product-specific delegated acts, data fields, identifiers, carriers, registry, access rights, supplier data validation, and open points.

EU Digital Product Passport supplier data validation controls

Build a supplier data validation file for EU Digital Product Passports: source owner, product link, access class, data model fit, evidence quality, approval record, and release gate.

EU DPP implementation playbook and vendor selection

Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence.

EU DPP Product-Group Readiness Checklist

A checklist for preparing a product group for an EU Digital Product Passport delegated act, covering data fields, suppliers, identifiers, carriers, access rights, and registry readiness.

EU DPP QR Code and Data Carrier Implementation Guide

Guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence.

EU DPP supplier data validation workflow

A workflow for checking supplier data before it is used in an EU Digital Product Passport, covering product linkage, evidence, owners, access class, and approval records.

What is a Digital Product Passport under ESPR?

A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts.