DPPRequirementsEU ESPR

EU Digital Product Passport Requirements

Understand what ESPR already fixes for Digital Product Passports and what each product-specific delegated act still has to define.

Use this overview to scope passport data, identifiers, carriers, access rights, registry uploads, customs checks, and supplier evidence without treating unfinished technical rules as final.

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

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

The EU Digital Product Passport is not a single universal data sheet for all products. Under Regulation (EU) 2024/1781, ESPR creates the horizontal passport framework, while product-specific delegated acts decide when a product group needs a passport and which data, carrier, access rights, and passport level apply. Teams should design DPP readiness around those two layers: stable ESPR architecture first, then product-group rules as they are adopted.

Section 1

What ESPR already requires for a Digital Product Passport

ESPR links Digital Product Passport obligations to information requirements in delegated acts. A covered product can be placed on the EU market or put into service only if the required passport is available under the applicable delegated act and the ESPR passport rules. The passport data must be accurate, complete, and up to date.

The delegated act for the product group is the controlling document for operational scope. It must specify the passport data, the data carrier, carrier layout and positioning, whether the passport is at model, batch, or item level, pre-contract access including distance selling, who can access which data, who can create or update data, how updates are made, and how long the passport remains available.

  • Start with the product group and commodity-code coverage in the delegated act, not with a generic DPP template.
  • Separate ESPR horizontal requirements from product-specific requirements, because the product act decides the final data set and passport level.
  • Treat passport availability, data accuracy, access rights, and retention as compliance requirements, not just IT publishing tasks.
  • Plan for DPP information to support value-chain access, competent-authority verification, market surveillance, and traceability.
Section 2

Data fields, identifiers, and carriers to design around

Annex III gives the menu of passport elements that product-specific delegated acts can require. That menu includes the unique product identifier, GTIN or equivalent product identifiers, commodity codes, compliance documentation, user instructions, manufacturer and importer information, unique operator identifiers, unique facility identifiers, and the DPP service provider reference for the back-up copy.

ESPR also defines the carrier and identifier architecture. The passport must be connected through a data carrier to a persistent unique product identifier. The carrier must be physically present on the product, packaging, or accompanying documentation as the delegated act specifies. Until harmonised standards are published in the Official Journal, ESPR points to ISO/IEC 15459 standards or equivalent European or international standards for relevant identifiers and carriers.

  • Model the passport around product, operator, facility, importer, EU responsible person, compliance-document, and back-up-provider fields.
  • Keep a clear link between the visible carrier and the persistent unique product identifier that resolves to the passport.
  • Do not assume QR code is always the final carrier for every ESPR product group; the delegated act specifies the carrier or carriers.
  • Preserve version history for data introduced or updated by different actors, because ESPR restricts update rights by access rights.
Section 3

Registry, web portal, customs, and access rights

ESPR creates a Commission-managed DPP registry that stores at least unique identifiers, and for products released for free circulation it also stores the commodity code. The economic operator placing the product on the market or putting it into service uploads the required registry data, and the registry returns a unique registration identifier. That identifier is not proof of product compliance.

The Commission must also set up a public web portal for searching and comparing passport data, consistent with access rights. For imports, customs controls are tied to the registry: customs may release a covered product for free circulation only after checking that the unique registration identifier and commodity code correspond to registry data once the relevant systems are operational.

Access is not all-public. ESPR names broad actor categories, including customers, economic operators, repairers, refurbishers, remanufacturers, recyclers, market surveillance authorities, customs authorities, civil society organisations, trade unions, and other relevant actors, but the applicable delegated act determines who can access which product-group data and who can introduce or update it.

  • Build a registry upload record for unique identifiers, commodity codes where relevant, and any extra registry fields later specified for the product group.
  • Do not represent the registry response as a compliance approval; it is an identifier returned after upload.
  • Design access-control matrices by actor category and data field, then revise them when the product-specific delegated act sets final access rights.
  • Coordinate customs master data with DPP identifiers and commodity codes before products are placed under release for free circulation.
Section 4

Supplier data validation and evidence controls

DPP teams need supplier evidence because many passport fields depend on upstream material, component, facility, process, durability, repairability, recycled-content, or substance data. ESPR allows delegated acts to require supply chain actors to provide relevant information free of charge to manufacturers, notified bodies, and competent national authorities.

Where supplier information is missing, ESPR can require supply chain actors to allow manufacturers to assess supplied products or services and access relevant documents or facilities. It can also require supply chain actors to enable notified bodies and competent national authorities to verify the accuracy of information related to their activities.

  • Add supplier fields for the claim, source system, measurement or calculation method, facility or actor identifier, date received, and approver.
  • Validate supplier values before passport publication when they affect compliance documentation, sustainability claims, substances of concern, recycled content, or repair and recycling instructions.
  • Keep evidence that explains whether a value came from a supplier declaration, test report, calculation, bill of materials, facility record, or authority-verifiable document.
  • Escalate missing supplier evidence before market placement for products whose delegated act requires the field in the passport.
Recommended next step

Turn DPP requirements into a controlled data model

Use this overview to separate fixed ESPR passport architecture from product-specific delegated-act details before you publish passport data or commit supplier workflows.

Section 5

Battery passports show how product-specific rules become concrete

The Batteries Regulation is the clearest example of a product-specific passport already written into EU law. From 18 February 2027, it requires a battery passport for each LMT battery, each industrial battery with a capacity greater than 2 kWh, and each electric vehicle battery placed on the market or put into service.

The battery passport illustrates why DPP implementation cannot stop at the ESPR horizontal framework. Annex XIII of the Batteries Regulation splits battery passport information into public battery-model data, data for persons with a legitimate interest and the Commission, data for notified bodies, market surveillance authorities and the Commission, and individual-battery data for persons with a legitimate interest.

  • Public battery-model data includes material composition, carbon footprint information, responsible sourcing, recycled content, renewable content, capacity, voltage, power capability, expected lifetime, energy efficiency, markings, declaration of conformity, and waste-battery information.
  • Restricted battery-model data includes detailed composition, replacement-spare source details, dismantling information, and safety measures.
  • Authority-only data includes test-report results proving compliance with the Batteries Regulation and its delegated or implementing acts.
  • Individual-battery restricted data includes performance and durability values, state of health, battery status, use data, charge/discharge cycles, negative events, operating conditions, and state of charge.
Section 6

What is not final yet

For most ESPR product groups, the decisive details are not final until the relevant delegated act is adopted. Teams should not publish fixed field lists, carrier choices, access tiers, or passport-level assumptions for a product group unless they can tie them to the applicable delegated act or another binding EU act such as the Batteries Regulation.

Several technical and governance pieces also depend on future or product-specific acts. ESPR empowers the Commission to set DPP service-provider requirements and, where appropriate, a certification scheme; to set procedures for digital credentials for actors with access rights; to establish life-cycle rules for unique identifiers and data carriers; and to specify registry implementation arrangements.

Commission consultation material confirms that service-provider data storage, management, and possible certification were still being shaped through public consultation. Treat those topics as implementation watch items until final rules are adopted.

  • Do not claim that one common DPP field list applies to all ESPR products.
  • Do not lock the carrier, placement, access rights, update permissions, or retention period before the product-specific delegated act defines them.
  • Do not treat DPP service-provider certification, digital-credential procedures, identifier life-cycle rules, or registry implementation details as settled unless a final EU act supports the claim.
  • Use battery passport rules as a concrete example, not as a universal template for every ESPR product group.
Primary sources

References and citations

single-market-economy.ec.europa.eu
Referenced sections
  • Commission consultation page supports treating DPP service-provider data storage, management, and possible certification as still subject to rule development rather than final operating detail.
"data should be stored and managed by service providers"
eur-lex.europa.eu
Referenced sections
  • Article 77, Article 78, and Annex XIII provide the battery passport scope, QR-code and unique-identifier connection, accuracy duty, access tiers, interoperability rules, and concrete battery passport data fields.
"shall have an electronic record ("battery passport")"
eur-lex.europa.eu
Referenced sections
  • Articles 9 to 13 reserve product-group passport details, service-provider requirements, digital credentials, identifier life-cycle rules, and registry implementation arrangements for delegated or implementing acts.
"as specified in the applicable delegated act adopted pursuant to Article 4"
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 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.
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 FAQ
Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance.
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 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 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.
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.
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.
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.
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.
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.
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.
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.