EU Digital Product Passport DPP registry FAQ

The registry is the official ESPR register for DPP identifier data. Article 13 requires the Commission to set up a secure digital registry that stores at least unique identifiers; for products intended for release for free circulation, it also stores the commodity code.

The registry should not be treated as the public product passport page or as a complete product-data repository. ESPR keeps the DPP architecture decentralised: the economic operator or a DPP service provider stores the passport, while the registry records identifier data needed for authentication, customs, and authority access.

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.

That registry response is operational proof of a successful upload, not proof of compliance. Teams should keep the registry identifier linked to the product passport record, customs workflow, and authority-support files so the same product can be traced through its DPP, registry, and import checks.

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.

This means the registry exists to support border controls and traceability, not to replace the product passport. Customs may retrieve and use registry and passport data for their duties, but a successful customs release is still not proof that the product complies with ESPR or other Union law.

Do not assume the registry is a public passport page, a compliance certificate, or a complete product-data store. ESPR makes the registry a secure identifier record, while the passport itself remains distributed across economic operators and service providers.

Do not assume the registry will expose every passport field. The regulation requires a secure registry for at least unique identifiers and, in customs cases, commodity codes, while any additional stored data must come from the delegated acts and the criteria set in Article 13.