FAQDPPEU ESPR

EU Digital Product Passport questions answered

Concise answers on how the EU Digital Product Passport 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
May 9, 2026
FAQ modules
7

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

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

The EU Digital Product Passport is the ESPR mechanism for making product sustainability, circularity, traceability, and compliance information available electronically. The exact passport content, access rights, data carrier, 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 items29
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.

4 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.

4 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 delegated act can be placed on the EU market or put into service only if a Digital Product Passport is available as required by that delegated act. The passport data must be accurate, complete, and up to date.

The delegated act 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 delegated act covers the product.
  • Use that delegated act 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 delegated act 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. For the first ESPR working plan, the regulation tells the Commission to prioritise iron and steel, aluminium, textiles including garments and footwear, furniture including mattresses, tyres, detergents, paints, lubricants, chemicals, certain energy-related products, and information and communication technology products and other electronics.

A priority product group is not the same as an immediately enforceable passport obligation for every SKU. Teams should monitor the working plan and the delegated act for their product group, then implement the exact data, access, data carrier, and level requirements set there.

  • Priority list: iron and steel; aluminium; textiles, garments, and footwear; furniture and mattresses; tyres; detergents; paints; lubricants; chemicals; selected energy-related products; ICT products and other electronics.
  • The Commission may justify excluding a listed group from the first working plan or adding another group.
  • For search and compliance triage, separate product-priority monitoring from active delegated-act compliance.
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 delegated act.

The Commission registry stores at least unique identifiers and, for products released for free circulation, the commodity code. Customs authorities may release covered imported products only after electronically verifying at least that the unique registration identifier and commodity code correspond to registry data once the registry and customs interconnection are operational.

  • Public-facing DPP views should expose only the fields the delegated act 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 just 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 data carrier to a persistent unique product identifier. The data carrier must be physically present on the product, packaging, or accompanying documentation as specified by the delegated act, 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 delegated act specifies the data carrier 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.

  • Maintain a unique product identifier, relevant operator identifiers, facility identifiers where required, commodity code, compliance documentation links, instructions, importer details, and DPP service-provider reference where the delegated act 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 delegated act and the selected identification standard before treating a tag as an accepted DPP data carrier.
Primary sources

References and citations

single-market-economy.ec.europa.eu
Referenced sections
  • 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.
"available to consumers, businesses and relevant public authorities"
commission.europa.eu
Referenced sections
  • Explains the DPP as an electronic identity card for products, components, and materials that supports sustainability, circularity, and legal compliance.
"a digital identity card for products, components, and materials"
ref.gs1.org
Referenced sections
  • Provides grounding for data-carrier implementation options such as barcodes, RFID, and NFC within GS1 identification and data-capture standards.
"barcode, RFID tag or NFC tag"
eur-lex.europa.eu
Referenced sections
  • Supports DPP identifier, data carrier, interoperability, personal-data, update-rights, security, privacy, back-up, and service-provider governance requirements.
"connected through a data carrier to a persistent unique product identifier"
Related guides

Explore more topics

Annex III Data Model Planning for EU Digital Product Passports
Plan EU Digital Product Passport data fields, identifiers, access rights, update owners, registry inputs, and evidence records against ESPR Annex III and product-specific delegated acts.
Digital Product Passport vs Digital Twin
Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits.
Digital Product Passport vs Paper Product Passports
Compare EU regulated digital product passports with paper, PDF, web, and internal product passports across access, identifiers, data carriers, restricted data, customs checks, registry, and interoperability.
DPP customs access review workflow for ESPR products
Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence.
DPP Data Governance RACI Template for EU Digital Product Passports
Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence.
DPP data-model intake workflow for EU Digital Product Passports
A grounded intake workflow for EU Digital Product Passport data models: product group, delegated-act status, source owner, supplier data, access class, identifiers, carrier, checks, and publication readiness.
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
Grounded guide to EU Digital Product Passport registry and web portal integration under ESPR, covering identifiers, data carriers, access rights, service 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
Grounded 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
Grounded 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
Grounded 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
Grounded EU Digital Product Passport calendar for ESPR and battery passport milestones, with product-group dates flagged as dependent on delegated acts.
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
What ESPR says about Digital Product Passport penalties, Member State fine rules, market surveillance, customs checks, and unresolved product-specific delegated acts.
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
source-linked 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 source-grounded 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
Grounded 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 grounded 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.