EU Central DPP Registry — What Manufacturers Need to Know

The EU Central DPP Registry — Purpose, Architecture, and What It Means for You

Article 12 of the Ecodesign for Sustainable Products Regulation (ESPR), Regulation (EU) 2024/1781, establishes a central EU registry for Digital Product Passports. This registry will become a critical piece of infrastructure for every manufacturer placing products on the EU market. Understanding what it is, how it works, and how to prepare for it is not optional — it is a requirement for continued market access.

This guide explains the registry’s purpose, legal basis, technical expectations, and the practical steps you should take now.

What Is the Central DPP Registry

The central DPP registry is a single EU-wide database that stores the unique identifiers of all Digital Product Passports. It is not a database of passport data itself. It is an index — a directory that links each unique product identifier to the location where the full passport data is hosted.

Think of it as a phone book for product passports. The registry tells you which passport exists for which product and where to find it. The actual passport data — material composition, carbon footprint, performance parameters, end-of-life instructions — lives on the platform chosen by the economic operator, not in the registry.

This architecture is deliberate. Centralising the index while distributing the data avoids creating a single point of failure and respects the commercial reality that manufacturers use different platforms and systems to manage their product data.

Legal Basis

The central registry is established by Article 12 of the ESPR (Regulation (EU) 2024/1781). Article 12(1) mandates the European Commission to set up and maintain the registry. Article 12(2) specifies that the Commission shall adopt implementing acts defining the technical design, development, and operation of the registry.

The registry is not discretionary. It is a binding obligation on the Commission to create, and on economic operators to use once it is operational. The legal framework leaves no ambiguity: if your product requires a DPP under any ESPR delegated act, its unique identifier must be registered in the central registry.

The implementing acts defining the registry’s technical specifications have not yet been finalised as of early 2026, but the Commission has published preparatory documents and conducted stakeholder consultations. The registry must be operational before the first ESPR delegated acts imposing DPP requirements take effect.

What Data Goes Into the Registry

The registry stores a limited, defined set of data for each product. It does not duplicate the full Digital Product Passport. The data fields expected in the registry include:

• The unique product identifier (as encoded in the data carrier on the product)
• The Global Trade Item Number (GTIN) or equivalent standardised product identifier
• The product type and product category
• A list of applicable ESPR delegated acts under which the product falls
• The identity of the economic operator who placed the product on the EU market
• The URL or endpoint where the full DPP data can be accessed
• The date of registration

This is intentionally minimal. The registry’s purpose is identification and routing, not data storage. When a market surveillance authority needs to inspect a product’s DPP, they use the registry to locate the passport, then access the full data from the hosting platform. When customs authorities check an incoming shipment, they query the registry to verify that a valid DPP exists for the products in the consignment.

Who Must Register

The registration obligation falls on the economic operator responsible for placing the product on the EU market. In most cases, this is the manufacturer. For imported products, it is the importer or the authorised representative established in the EU.

Every product unit that carries a DPP must have its unique identifier registered in the central registry before the product is placed on the market. This means the registration must happen as part of the product release process — not retroactively, not optionally, and not as an afterthought.

For manufacturers with high production volumes, this implies automated registration. Manually registering each product identifier in a web portal is not feasible at scale. The registry’s API-based design (discussed below) is intended to support automated, system-to-system registration as part of manufacturing and logistics workflows.

Registry vs. Product Passport — Understanding the Distinction

The distinction between the central registry and the product passport is fundamental and frequently misunderstood.

The product passport is the complete dataset about a product: its materials, its carbon footprint, its performance characteristics, its end-of-life handling instructions. The passport is created and maintained by the economic operator, hosted on a platform of their choosing, and accessible through the QR code on the product.

The central registry is the EU-managed index that records the existence of each passport and the location where it can be found. The registry does not store material composition data, carbon footprint values, or performance parameters. It stores identifiers and links.

This means that the registry cannot replace your DPP platform. You still need a system to create, host, and serve passport data. The registry adds a layer of visibility and verification on top of that system. It enables the EU and its Member States to see, at a glance, which products have passports and where to find them.

Economic operators are responsible for ensuring that the link between the registry entry and the actual passport data remains active and accurate for the entire lifetime of the product. If you change DPP platforms or restructure your data architecture, you must update the registry entry accordingly.

Timeline

The ESPR entered into force on 18 July 2024. Article 12 requires the Commission to adopt implementing acts defining the registry’s technical specifications. The registry must be operational before the first product-specific delegated acts imposing DPP requirements come into force.

The Commission’s work programme indicates that the first delegated acts — likely covering sectors such as textiles, iron and steel, and batteries (where not already covered by the Battery Regulation) — are expected to begin applying from 2027 onwards. The registry must therefore be operational by that date.

The implementing acts defining the registry specifications are expected in 2026. Manufacturers should monitor the Official Journal and the European Commission’s DPP web pages for publication. However, waiting for the implementing acts before taking any preparatory action is ill-advised. The registry’s core function — indexing unique identifiers linked to passport data — is already clear from Article 12. You can and should be preparing now.

Relationship to the Battery Regulation

The Battery Regulation (Regulation (EU) 2023/1542) predates the ESPR and establishes its own electronic exchange system for battery passports under Article 78. This system serves a similar indexing function for batteries specifically.

The ESPR acknowledges existing sector-specific regulations. Recital 26 of the ESPR states that where specific Union legislation already sets requirements for product passports, the ESPR framework should be applied in a complementary manner. The Commission has indicated that the central DPP registry under Article 12 of the ESPR and the battery passport electronic exchange system under Article 78 of the Battery Regulation will be designed to interoperate or integrate.

For battery manufacturers, this means you may need to register in both systems, or the systems may merge. In either case, the underlying requirement is the same: every battery passport’s unique identifier must be registered in a central system accessible to market surveillance and customs authorities. Preparing your data architecture to support automated registration is the correct step regardless of which system ultimately applies.

Expected Technical Architecture

While the implementing acts have not yet been published, the Commission’s preparatory work and stakeholder consultations provide a clear picture of the expected technical architecture.

API-Based Registration

The registry will provide an API (Application Programming Interface) that economic operators and their DPP platforms can use to register product identifiers programmatically. Manual registration through a web portal may be available for low-volume operators, but the primary design assumption is machine-to-machine communication. This is essential for manufacturers producing thousands or millions of units per year.

Machine-Readable Identifiers

All identifiers in the registry will be machine-readable and conform to internationally recognised standards. GS1 Digital Link URIs, encoding GTINs and serial numbers, are the expected format. The registry will parse these identifiers and store the structured components (GTIN, serial number, product type) in a queryable database.

Interoperability with National Systems

The registry must interoperate with the market surveillance systems of all 27 EU Member States. When a national authority inspects a product, they must be able to query the central registry and retrieve the location of the product’s DPP in real time. This requires standardised query protocols, consistent response formats, and high-availability infrastructure.

Authentication and Access Control

Access to the registry will be tiered. Economic operators will have write access to register and update their own product identifiers. Market surveillance authorities and customs authorities will have read access across all entries. Public access may be provided for basic lookups — confirming that a DPP exists for a given product — but detailed registry data will likely be restricted to authorised users.

Customs Integration

One of the registry’s most significant functions is enabling customs enforcement at EU borders. Today, customs authorities have limited tools to verify that imported products comply with sustainability and ecodesign requirements. The central registry changes this.

When a shipment arrives at an EU border, customs authorities will be able to scan the data carrier on the product (or query the product identifier from shipping documents), check the central registry to confirm that a valid DPP exists, and access the passport data to verify compliance with applicable delegated acts. Products without a registered DPP can be flagged, held, or refused entry.

Article 12(4) of the ESPR explicitly provides for the registry to be accessible to customs authorities. The Commission’s preparatory work references integration with the EU Single Window Environment for Customs, the digital platform through which all customs procedures will be managed.

For manufacturers, this means that non-compliance is not just a market surveillance risk — it is a border control risk. Products without properly registered DPPs may be stopped at customs, delaying shipments and potentially incurring storage costs, fines, or forced return.

Impact on Manufacturers

The central registry creates several operational requirements that manufacturers must build into their processes.

Register Every Unique Identifier

Every product unit placed on the EU market with a DPP requirement must have its unique identifier registered. For a battery manufacturer producing 100,000 units per year, that is 100,000 registration events per year. This must be automated and integrated into production workflows.

Maintain Links Between Registry and Passport

The registry entry includes a URL pointing to the passport data. That URL must remain valid for the entire lifetime of the product. If you migrate platforms, change domain names, or restructure your data hosting, you must update every affected registry entry. Broken links mean products with inaccessible passports, which is equivalent to having no passport at all.

Update When Products Change

If a product is recalled, withdrawn, or modified in a way that changes its DPP status, the registry entry must be updated accordingly. The registry is not a one-time filing. It is a living record that must reflect the current status of every product throughout its lifecycle.

Respond to Authority Queries

When market surveillance or customs authorities query the registry and follow the link to your passport data, the data must be immediately available and complete. Downtime, incomplete records, or access errors during an authority inspection create enforcement exposure. Your DPP hosting platform must deliver the uptime and data integrity that regulatory inspection demands.

How to Prepare Now

The implementing acts defining the registry’s technical specifications are forthcoming, but the strategic preparation can and should happen now.

Choose a DPP Platform With Registry Integration Capability

Your DPP platform must be able to communicate with the central registry via API when it becomes operational. This means the platform must support standardised unique identifiers (GS1 Digital Link format), automated registration workflows, and the ability to update registry entries programmatically. If your current platform cannot do this, you will face a costly integration or migration when the registry launches.

Start Generating Unique Identifiers in the Standard Format

Begin assigning GS1 Digital Link-compliant unique identifiers to your products now, even before the registry is operational. This establishes your serialisation processes, validates your data architecture, and ensures that when registration becomes mandatory, you are ready to register immediately rather than scrambling to retrofit identifiers onto products already in production.

Build Registry Registration Into Your Manufacturing Workflow

Treat registry registration as a step in your production process, just like quality inspection or packaging. Design the workflow now: at what point in production is the unique identifier generated? When is the passport created? When is the identifier registered? How is registration confirmed before the product ships? These are process questions that require planning and testing, not just technical implementation.

Plan for Long-Term Data Hosting

The registry links to your passport data, and that link must remain valid for the product’s lifetime. For durable goods, that could be 10, 15, or 20 years. Your data hosting strategy must account for this. Choose a platform with a credible long-term commitment, contractual uptime guarantees, and a data portability plan in case you need to move providers.

Traceable and the Central Registry

Traceable is built to integrate with the EU Central DPP Registry from the moment the implementing acts are published and the registry becomes operational. The platform already generates GS1 Digital Link-compliant unique identifiers, hosts passport data at stable, long-lived URLs, and supports the API-based communication patterns that the registry will require. When the registry opens for registration, Traceable customers will be able to register their product identifiers automatically as part of the passport creation workflow — no additional integration work required.

Regulatory Status and Updates

This guide reflects the regulatory position as of March 2026 and is based on Regulation (EU) 2024/1781 (ESPR) as published in the Official Journal of the European Union. The implementing acts defining the central registry’s technical specifications are pending adoption by the European Commission. Subscribe to Regulatory Radar on traceable.digital for updates as implementing acts are published and the registry becomes operational.