FAQDPP registryEU ESPR

EU Digital Product Passport DPP registry FAQ

The Commission launched the DPP Registry on 20 July 2026. It is a secure central record of identifiers and registration metadata, not a substitute for the product passport itself.

Use it to separate legal registry duties from product data hosting, resolver design, access-right handling, and service-provider contracts.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Overview

The Commission launched the and its testing environment on 20 July 2026. The Registry records DPP identifiers and required metadata; the complete product information remains decentralised with the responsible economic operator or a DPP service provider.

Search this module

Find a question or answer quickly

5 of 5 questions
Question 1

What does the EU Digital Product Passport registry do?

The Registry is the central EU register for DPP identifier data and associated mandatory metadata. Article 13 requires it to store at least unique identifiers; for products intended for release for free circulation, it also stores the commodity code. Applicable legal acts can require additional registration data.

The Registry is not the public product passport page or a complete product-data repository. The economic operator or a DPP service provider stores the complete passport, while the Registry supports registration, authentication, authority access, and future automated customs checks.

  • Store at least the unique identifiers required for the DPP system.
  • Store commodity codes for products intended for customs release for free circulation.
  • Return a unique registration identifier after the economic operator uploads the required registry data.
  • Give the Commission, competent national authorities, and customs authorities access for their legal duties.
  • Avoid presenting registry acknowledgement as proof that the product complies with ESPR or other EU law.
Recommended next step

Turn DPP registry duties into a maintained identifier workflow

Use Sorena to map ESPR registry fields, product identifiers, service-provider duties, resolver paths, and access-right evidence before DPP rollout.

Question 2

Who uploads registry data and what gets a registration identifier?

The economic operator placing the product on the market or putting it into service uploads the data required for the registry. Once that data is uploaded, the registry automatically communicates a unique registration identifier associated with the unique identifiers uploaded for that product.

The Commission also says an economic operator can request proof of registration as a secure electronic document. That document evidences registration; ESPR separately says the Registry's identifier communication is not proof of compliance with ESPR or other Union law.

  • Treat the economic operator as the registry uploader unless the applicable legal process says otherwise.
  • Keep the returned unique registration identifier tied to the product's unique identifiers and commodity code where relevant.
  • Do not use the registry response as a general compliance certificate.
  • Preserve upload and correction history so changes to registry data remain auditable.
Question 3

How do customs checks use the registry?

For products intended to be placed under the customs procedure for release for free circulation, customs authorities verify at minimum that the unique registration identifier and the commodity code correspond to the registry data. The verification is electronic and automatic once the registry-to-customs interconnection is operational.

The Registry is live, but the EU CSW-CERTEX interconnection has its own timetable: ESPR requires it to become operational within four years after the Registry implementing act enters into force. Until the interconnection is operational, do not describe automatic DPP customs matching as live. A later successful customs release will still not prove compliance with ESPR or other Union law.

  • Prepare the unique registration identifier before customs release workflows start.
  • Map the commodity code to the product record before registry upload.
  • Test the customs handoff electronically once the interconnection is operational.
  • Keep customs release records separate from general product-compliance evidence.
Question 4

What are the Registry's limits?

The Registry is a secure identifier and metadata record. It is neither the public passport page nor a complete product-data store, and its identifier communication does not prove compliance. The passport itself remains distributed across economic operators and service providers.

The Registry does not expose every passport field. It stores at least unique identifiers and, in customs cases, commodity codes. Delegated acts can specify additional stored data under the criteria in Article 13.

  • Registry acknowledgement is not proof of compliance.
  • The Registry and the public web portal are separate systems.
  • Additional registry fields depend on delegated acts, not on page-level convenience.
  • Passport storage can remain decentralised even when registry data is centralised.
Question 5

Questions and answers

What is the EU for?

It is the live Commission-managed register for DPP identifiers and mandatory registration metadata. Under ESPR, it stores at least unique identifiers and, for products intended for release for free circulation, the commodity code. The complete passport data remains decentralised.

Who uploads the registry data?

The economic operator placing the product on the market or putting it into service uploads the required data, and the registry then communicates a unique registration identifier for that product.

Does a registry hit prove compliance?

No. ESPR says the registry communication is not proof of compliance with the regulation or other Union law.

What do customs check?

Once the EU CSW-CERTEX interconnection is operational, customs will verify at minimum that the unique registration identifier and commodity code match the Registry data for release for free circulation. The Registry itself is live, but that automated interconnection has a separate timetable.

Primary sources

References and citations

eur-lex.europa.eu5 citations
Referenced sections
  • Primary legal source for DPP registry duties, unique registration identifiers, customs checks, and the relationship between the registry and the passport.
  • ESPR Articles 13 and 15 define the DPP registry, required stored data, registration identifier, authority access, and customs checks.
  • Article 13 assigns registry upload duties to the economic operator placing the product on the market or putting it into service and states that the registry response is not proof of compliance.
Show 2 more
  • Article 15 sets the customs verification rule and the link to the registry and EU CSW-CERTEX interconnection.
  • Articles 13 to 15 distinguish the secure registry, the web portal, customs checks, and the limits on what registry communication proves.
"By 19 July 2026, the Commission shall set up a digital registry"
More quoted passages
"the registry shall automatically communicate to that economic operator a unique registration identifier"
"shall not be deemed to be proof of compliance"
"the unique registration identifier referred to in Article 13(5) and the commodity code"
"That communication by the registry shall not be deemed to be proof of compliance"
single-market-economy.ec.europa.eu3 citations
Referenced sections
  • Current Commission source for the 20 July 2026 launch, testing environment, registration channels, proof-of-registration document, and decentralised product-data model.
  • Confirms the Registry launch, testing environment, registration through a user interface or API, and decentralised storage of complete product data.
  • Confirms that economic operators can request proof of registration as a secure electronic document.
cencenelec.eu
Referenced sections
  • CEN-CENELEC describes DPP design work covering data carriers, information portal contents, and information exchanges.
"data carrier, information portal contents, and information exchanges"
etsi.org
Referenced sections
  • Technical source support for DPP access, persistence, identifier-linked data, data quality, and the distinction between product operators and third-party DPP service providers.
"structured collection of product-specific data conveyed through a unique identifier"
gs1.org
Referenced sections
  • Industry standard source for DPP identification and data-carrier preparation in the ESPR context.
"accessible via electronic means through the scan of an internationally standardized data carrier"
Show all related guides (37)

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

An intake workflow for EU Digital Product Passport data models: product scope, legal status, field owner, evidence, access class, identifiers, carrier, registry mapping, 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

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

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.