What Is the EU DPP Registry?

The EU DPP Registry: What It Is and Why It Matters

The EU DPP Registry is the centralised digital infrastructure that will index every Digital Product Passport for products placed on the European Union market under the Ecodesign for Sustainable Products Regulation (ESPR). Rather than storing the full passport data itself, the registry functions as a directory. It records the existence of each DPP, holds the key identification metadata, and resolves to the location where the manufacturer or its hosting provider holds the actual passport contents.

The registry exists because of a practical problem. The EU expects hundreds of millions of Digital Product Passports to come into existence across thousands of economic operators and dozens of product categories between 2026 and 2030. Without a single discovery layer, market surveillance authorities, customs officers, and downstream buyers would have no reliable way to find a specific product's passport among a fully distributed hosting landscape. The registry provides that single window.

This guide sets out exactly what the registry is, when it goes live, who will use it, how DPP registration will work in practice, and what businesses need to do now to be ready.

EU DPP Registry at a Glance

Aspect	Detail
Established by	EU Regulation 2024/1781 (ESPR), Article 13
Operated by	European Commission, via implementing acts
Architecture	Federated index, DPP data remains hosted by economic operators
Expected launch	By 19 July 2026 under the ESPR timetable
First mandatory use	Batteries from 18 February 2027 under the EU Battery Regulation
Primary purpose	Discovery, verification, and access management for DPPs
Identification standard	Expected to use GS1 Digital Link or equivalent unique product identifier
Access tiers	Public, authority, operator, with role-based controls

Timeline: From Regulation to Live Registry

The registry is being built in defined steps rather than as a single launch event. Knowing the sequence helps businesses plan registration readiness against the right dates.

• July 2024: ESPR enters into force as Regulation 2024/1781. Article 13 mandates the establishment of the EU DPP Registry.
• 2024 to 2025: Commission consultations and technical workshops on registry architecture, identification standards, and access rules.
• 2025: Implementing acts drafted to define the technical protocols for DPP registration, data carriers, and authentication.
• By 19 July 2026: EU DPP Registry expected to be operational, providing the federated discovery infrastructure required by the ESPR.
• 18 February 2027: Battery DPPs become mandatory under the EU Battery Regulation 2023/1542, making batteries the first product category to use the registry at scale.
• 2027 to 2028: First ESPR sector delegated acts come into force, beginning with iron, steel, textiles, and tyres. Registration becomes mandatory for these categories.
• 2028 to 2030: Further sector delegated acts extend mandatory registration to furniture, mattresses, electronics, chemicals, and other categories on the published ESPR working plan.

The phased rollout means that the registry's full data load builds up over four years rather than arriving all at once. The Commission can use the early sector launches to test scale, performance, and authority workflows before higher-volume categories such as textiles and electronics come online.

Core Functions of the Registry

The registry is designed to perform five distinct functions, each supported by specific technical capabilities.

Indexing

The registry maintains a comprehensive catalogue of all Digital Product Passports for products placed on the EU market, linked to unique product identifiers. Each entry records the identifier, the responsible economic operator, the product category, the applicable delegated act, and the URL or endpoint where the full passport data is hosted.

Search and Discovery

Authorised users can query the registry by product identifier, manufacturer, product category, place of origin, or other metadata fields. This is what allows a market surveillance officer to find any DPP from any economic operator without prior knowledge of which hosting provider the operator uses.

Verification

The registry can confirm that a given DPP exists, is registered to the claimed economic operator, and is current. This is critical for customs at borders, for anti-counterfeiting checks, and for downstream buyers verifying the authenticity of supplier-provided passport links.

Access Management

DPP data has multiple audiences with different access rights. Public consumer-facing fields differ from confidential commercial information, which differs again from regulator-only data. The registry enforces these access tiers through role-based authentication, ensuring that each query returns only the fields the requesting party is entitled to see.

Statistics and Analytics

The registry aggregates anonymised data on registration volumes, sector coverage, compliance indicators, and access patterns. The Commission can use these aggregates to evaluate ESPR implementation progress, identify enforcement gaps, and inform future delegated-acts policy.

The Federated Architecture Explained

The registry does not centrally store every Digital Product Passport. That would create a single point of failure, place an unsustainable hosting burden on the Commission, and force economic operators to surrender direct control over their own product data.

Instead, the registry adopts a federated architecture. Each economic operator hosts its own DPP data, either on its own infrastructure or via a DPP-as-a-service platform. The registry records where each passport can be found and provides the resolution layer that takes a unique product identifier and returns the correct hosting endpoint. When an authorised party queries a DPP, the registry hands off to the hosting provider, which returns the data subject to the registry-enforced access controls.

The federated model is similar in principle to how DNS works for web addresses. The Commission operates the index, the economic operators operate the hosting, and the registry sits between them as the lookup layer.

Who Will Use the Registry

Market Surveillance Authorities

National market surveillance authorities, the bodies responsible for enforcing product regulations in each member state, are the primary registry users. They will use it during routine inspections, in response to consumer complaints, and as part of proactive market-monitoring campaigns. The registry gives them visibility across the entire EU market rather than only the products they happen to encounter in their own jurisdiction.

Customs Authorities

Customs officials at EU borders will query the registry to verify that imported products carry valid DPPs. A scan of the product's data carrier returns the unique identifier, which the customs system looks up in the registry. If no DPP is registered, the product can be held or refused entry depending on the applicable delegated act.

Downstream Businesses

Distributors, retailers, contractors, and converters will use the registry to verify that supplier-provided DPP links resolve to genuine, registered passports. This protects them from carrying non-compliant products and supports the supply-chain audit trails increasingly demanded under CSRD and similar frameworks. The construction sector and the automotive sector in particular will rely on registry verification when reading metal, electronic, and battery DPPs into their own product passports.

Repair Networks and Recyclers

Repair professionals can use the registry to access technical documentation, spare-parts data, and disassembly guidance. Recyclers can pull end-of-life data and substance information to plan material recovery. Both use cases are central to the ESPR's circular-economy objectives.

Consumers

Consumers will have access to a public layer of the registry, typically through scanning a product's QR code. The data returned at this tier is limited to consumer-facing information such as material composition, repairability score, and end-of-life guidance, with commercial and regulatory data restricted to authorised parties.

How DPP Registration Will Work

When an economic operator creates a Digital Product Passport for a product, registration with the EU DPP Registry will be a mandatory step before placing the product on the market. The registration process will involve submitting a defined set of metadata to the registry.

Required Registration Metadata

• Unique product identifier, expected to be based on GS1 Digital Link or equivalent
• Economic operator identification, including the EORI number for customs interoperability
• Product category and applicable ESPR delegated act reference
• Place of manufacture and key supply-chain locations
• URL or API endpoint where the full DPP data is hosted
• Key compliance indicators relevant to the sector delegated act
• Effective date of placement on the EU market

Automated Registration via Hosting Platforms

The implementing acts are expected to support machine-to-machine registration, so that DPP hosting platforms can register passports directly with the EU registry through standardised APIs as part of the DPP creation workflow. This removes the need for economic operators to manually register each product, which would be operationally impossible at the volumes involved.

Platforms such as MyProductPassport are being built with EU DPP Registry integration in mind. As the registry's technical specifications are finalised through implementing acts, the platform will support automated registration directly from the DPP authoring flow.

What Happens After Registration

Once a DPP is registered, the registry validates the metadata and assigns the passport its registry-level identifier. The DPP is then discoverable by any authorised query against the registry. The economic operator remains responsible for maintaining the underlying data, including updates, corrections, and end-of-life data. The registry is notified of material updates via the same API used for initial registration.

Technical Standards Likely to Apply

The implementing acts will define the formal standards, but several technical choices are already strongly signalled by Commission consultations and the wider EU digital infrastructure direction.

GS1 Digital Link

GS1 Digital Link is the leading candidate for the DPP identification standard. It encodes structured product identification keys, including GTINs, batch numbers, and serial numbers, into web-resolvable URIs that can be embedded in QR codes, RFID tags, or NFC chips. The format is already widely deployed in retail and is well suited to registry indexing.

Decentralised Identifiers and Verifiable Credentials

The W3C standards for Decentralised Identifiers (DIDs) and Verifiable Credentials (VCs) are being explored for DPP authentication and verification. They allow economic operators to cryptographically sign their DPP data so that any party can verify both the source and the integrity of the data without relying on a central trust authority.

Existing EU Digital Building Blocks

The Commission has signalled that the registry will reuse existing EU digital building blocks where possible, including the EU Single Window Environment for Customs and the Information and Communication System for Market Surveillance (ICSMS). This reduces duplication and supports cross-system authentication for authorities working across registry, customs, and surveillance contexts.

Data Persistence and Long-Term Obligations

DPPs are not single-point disclosures. The ESPR expects passport data to remain accessible throughout the product's lifecycle and for a defined period beyond, potentially 10 years or more after the last unit of a product model is placed on the market. The registry must support this persistence even when economic operators cease trading or change hosting providers.

Possible mechanisms include mandatory data-escrow arrangements with DPP hosting providers, registry-level caching or archival of essential passport data, or deposit-with-trusted-third-party regimes. The Commission has not finalised the rules, but businesses should design their data management programmes with long-horizon persistence in mind. For businesses using third-party DPP platforms, it is essential to understand the provider's persistence commitments and what happens to passport data if the business changes provider or the provider ceases operations.

Integration with Other EU Digital Infrastructure

The DPP Registry is one node in a broader EU product-data ecosystem. Several adjacent systems will exchange data with the registry to support unified compliance and enforcement workflows.

• EU Single Window for Customs: Allows customs systems to verify DPP existence and key compliance indicators during import processing.
• ICSMS: The Information and Communication System for Market Surveillance, which supports cross-border enforcement cooperation between national authorities and will integrate with registry data.
• SCIP database: The European Chemicals Agency database for substances of concern in articles. Where DPP data overlaps with SCIP requirements, integration reduces duplication.
• CBAM reporting system: The Carbon Border Adjustment Mechanism reporting infrastructure, especially relevant for metals and cement where carbon-intensity data appears in both DPPs and CBAM reports.
• Member state product registers: Some member states already operate national product registers (for example for batteries or waste packaging) that will need to interoperate with the EU DPP Registry.

What Businesses Need to Prepare

While the registry's full technical specifications are still being defined through implementing acts, the preparation programme is already clear enough to begin.

1. Assign unique product identifiers. Ensure every SKU that may eventually require a DPP has a globally unique identifier, ideally based on GS1 standards. This is the foundation that registry registration is built on.
2. Select a DPP hosting model. Decide whether you will host DPP data internally, use a third-party platform, or adopt a hybrid model. Each choice has implications for registry integration, data persistence, and ongoing operational cost.
3. Inventory data sources. Map which internal systems and which suppliers will need to feed which DPP data fields. The longer the supplier chain, the longer the lead time to clean data.
4. Plan for automated registration. Ensure that whatever DPP hosting solution you adopt can register passports directly with the EU registry via the implementing-act APIs.
5. Document persistence arrangements. Establish how DPP data will remain accessible for the required period if your business structure or technology providers change.
6. Monitor Commission publications. Implementing acts, FAQs, and technical specifications will be published over 2025 to 2026. A workflow that gets these into the hands of the responsible compliance owner reduces last-minute scrambles.

Frequently Asked Questions

When does the EU DPP Registry go live?

The EU DPP Registry is expected to be operational by 19 July 2026, the date by which the ESPR requires the central infrastructure to be in place to support the first sector delegated acts.

Where is the registry hosted and who runs it?

The registry is established by the ESPR and operated by the European Commission, with technical implementation defined through implementing acts. The exact hosting arrangements will be set by those implementing acts.

Does the registry store the full DPP data?

No. The registry is a federated index. It stores key identification metadata and the location of the full DPP, but the passport contents themselves remain hosted by the economic operator or its DPP hosting provider.

Who must register DPPs with the registry?

Every economic operator placing a product on the EU market in a category covered by an ESPR delegated act must register the relevant DPP with the registry before or at the time of market placement.

Which is the first product category to require registry use?

Batteries from 18 February 2027 under the EU Battery Regulation, followed by iron, steel, textiles, and tyres under the first ESPR delegated acts.

Will consumers be able to access the registry?

Consumers will have access to a public tier, typically by scanning a product's QR code. The data returned at this tier is limited to consumer-facing fields. Commercial and regulator-only fields require higher access levels.

What identification standard does the registry use?

The implementing acts will confirm the formal standard. The leading candidate is GS1 Digital Link, which encodes structured product identifiers into web-resolvable URIs.

What happens to DPP data if a manufacturer goes out of business?

The ESPR requires DPP data to remain accessible for a defined period beyond the product's market life. The Commission is still finalising the rules, but mechanisms under consideration include mandatory data-escrow arrangements, registry-level caching, and deposit-with-trusted-third-party regimes.

Do non-EU manufacturers need to register?

Yes. Any product placed on the EU market in a covered category requires a registered DPP, regardless of where the manufacturer is based. Non-EU manufacturers typically register through an EU-established authorised representative.

Can a DPP be hosted on the manufacturer's own website?

Yes, provided the hosting meets the technical requirements set by the implementing acts, including API support for registry interaction, role-based access controls, persistence guarantees, and data integrity.

Key Takeaways

The EU DPP Registry is the centralised federated index that will catalogue every Digital Product Passport for products placed on the EU market. It serves as the discovery layer that allows market surveillance authorities, customs officers, downstream businesses, repairers, recyclers, and consumers to find, verify, and access any DPP from any economic operator across any category.

The registry adopts a federated model, where DPP data remains hosted by economic operators and the registry holds only the index and metadata. It is expected to be live by 19 July 2026 in line with the ESPR