The DPP Registry vs. a DPP Service Provider: What's the Difference, and Why You Need Both 

The EU's Digital Product Passport Registry is a discovery tool run by the Commission. It is not where your product data lives. Here's the distinction and why getting it wrong is a compliance risk.

Under the Ecodesign for Sustainable Products Regulation (ESPR), the European Commission must set up a central EU Digital Product Passport Registry by 19 July 2026 (ESPR Article 13, as set out in the JRC methodology report). With that date now behind us, a lot of manufacturers assume the registry is "the DPP system." 

It isn't, and the gap between what the registry does and what a DPP service provider does is where compliance planning actually happens.

What the Registry is

The registry is a Commission-run index with the Commission as its legal controller. Its job is discovery and verification, not data hosting. It stores, at minimum, the unique identifiers of registered passports and for goods entering under "release for free circulation", the commodity code.

So, for example, the registry lets a market surveillance authority confirm that a pair of headphones has a valid passport and find where it lives. 

Crucially, three obligations sit on the manufacturer (or other responsible operator):

• Register each DPP in the EU registry

• Maintain a verifiable link between the registry entry and the data carrier on the product

• Keep the data accurate and accessible for the retention period set in the relevant delegated act 

The registry does none of that for you; it records that you did.

What a DPP Service Provider is

The ESPR defines a "digital product passport service provider" as an independent third party, authorised by the operator placing the product on the market, that processes DPP data to make it available to those entitled to access it. 

This is the platform layer, the infrastructure that actually:

• Pulls product and supply-chain data together

• Structures it against the requirements set per product group

• Generates the passport

• Keeps it current through repairs, resale and end-of-life

• Registers it with the EU registry and keeps it in sync

Importantly, the ESPR lets each operator choose to do this in-house or via a third-party service provider - a genuine decision, not a default.

How They Connect

The link between the two is technical and standardised. 

The draft standard prEN 18222:2025 specifies the exact registration method where an operator's platform submits a payload (operator, backup operator and product header) and receives a unique registry identifier back. 

The fuller product data is served separately, by custodians of DPPs or archiving services via the Life Cycle API. In other words the platform builds and holds the passport; the registry holds the pointer.

What this means for Electronic Hardware Brands

• Registry access alone gives you nothing to point to:  Without a platform (in-house or third-party), there's no valid passport to register in the first place.

• A platform without registry integration is invisible:  A passport nobody outside your systems can verify doesn't satisfy the Article 13 duty.

• The build-or-buy decision is yours to make deliberately: The ESPR explicitly permits both. For smaller or boutique audio brands, a service provider may be the realistic route.

• Ongoing maintenance needs an owner: "Keep it accurate for the retention period" is a lifecycle duty, not a launch task.

Watch Items

• When audio-visual/electronics is actually in scope - no product-group delegated act yet binds it.

• Retention periods and access rights, both set per product group in delegated acts, are still to come.

• Standard finalisation - prEN 18222 remains a draft (prEN); method names and payloads may change.
  
  

TAZAAR's AssetID platform is built as the service-provider layer - consolidating data, generating the passport and maintaining it across the product lifecycle, with registry interoperability built in as standard. 

You can learn more about the platform and contact us here.

Editor's note: general information, not legal advice. Refers to a draft standard and to delegated acts that do not yet exist for audio products; review against current legal texts before relying on specifics.