Summary

The EU's Digital Product Passport Registry went live on 20 July 2026. It's the central registration layer for the ESPR, though it can't register passports yet, because the first product catalogues are still being defined. When that work is done, we'll prepare your registrations and take you through submitting them in your name.
The Registry is an index, not a database. It holds each passport's identifier, registration data and a proof of registration, not your product information. The passport and everything in it stays with the business or its service provider.
The business placing a product on the market stays accountable for its passport data. For in-scope products the regulation also requires a back-up copy held by an independent DPP service provider. The Commission's rules for that role are still being written.
A live Registry doesn't make a passport mandatory today. That still depends on your category, batteries first, from 18 February 2027, then the other ESPR priority groups out to 2030.

The infrastructure is real now. On 20 July 2026 the European Commission switched on the Digital Product Passport Registry, the central service that ties the ESPR framework together. For two years the passport has been a regulation with one firm deadline and a lot of unfinished plumbing behind it. The plumbing is now built and running. You can’t register a passport on it just yet, though, because the Commission is still defining the first product catalogues. Batteries lead the way, and their registrations become mandatory on 18 February 2027.

We’ve been working towards this for a while, so it’s worth marking. There’s a lot of hype about what the Registry does, and most of it is overblown. Here’s what actually changed.

What actually went live

The Registry is an index, not a database. It doesn’t hold your product information and it never will. It holds the unique identifier for each passport, the registration data and the metadata, and it issues a proof of registration in return. The passport itself, and everything inside it, stays with the business or its chosen service provider. So “the Registry has gone live” means the enrolment and registration layer is open. It does not mean a central product database has appeared. Think of it as a ledger of proofs sitting on top of a decentralised system. The design is deliberate, and it keeps the data close to the people responsible for it.

That responsibility matters more than any of the technology. The business placing a product on the market is accountable for the accuracy and upkeep of its passport data. The Registry doesn’t take that on, and no platform can lift it off you. What the regulation does require, for in-scope products, is that a backup copy of the passport is available through a DPP service provider, so the record survives even if a brand’s own systems don’t. The ESPR defines that role, though the detailed rules for it are still to come.

Where TalkPod fits

This is what we’ve been building for. TalkPod is built to be your DPP service provider. When the Registry starts accepting passports, we’ll prepare your registrations and take you through submitting them under your own account. We read product data from the systems a brand already runs. Spreadsheets work today, Shopify is in testing, and we build other connections, such as Akeneo or NetSuite, as part of getting you live. We publish a passport at a stable URL that stays put. Every field change is logged by timestamp, author and previous value. The passport resolves in both human-readable and GS1 Digital Link formats from the same record, the QR code comes from the same place.

We won’t write your regulatory strategy or certify your compliance. If your category needs central registration, uploading the identifiers is your job as the economic operator, even where we host the passport. The Registry verifies the businesses that enrol, but it doesn’t accredit anyone’s software, so a vendor claiming to be “approved by the Registry” is making that up. We build the passport, host it, and act as your service provider. The legal responsibility sits with you, where the rules put it.

What this means if you’re in scope

The Registry going live doesn’t make a passport mandatory for you today. That still depends on your product category. The sector-specific delegated acts under the ESPR set both the required data and the date. Batteries come first, with the battery passport required from 18 February 2027, and textiles, furniture, iron and steel and the rest of the priority groups follow on the published schedule out to 2030. Watch the delegated act for your own category, and check its detail before you treat any requirement as settled.

What has changed is that the target has stopped moving. The standards carry legal weight, the Registry is live, and the buy-or-build question is a real decision now rather than a forecast. The longer job was always the data, not the technology: the composition of a garment, the state of health of a battery, the maintenance and end-of-life guidance for a machine, most of it scattered across PIMs, supplier emails and spreadsheets rather than sitting ready in one place. That work doesn’t get shorter by waiting, and the infrastructure it feeds into is now in place.

The same data that satisfies a regulator is the most accurate description of your products you will ever hold. Most brands will publish the passport and let it sit behind a QR code a customer scans once. It can do a lot more than that, and turning compliance data into something a customer actually uses is the real prize. But it starts with getting the data right, and a live Registry is a good reason to start.

If you want to talk through what passport readiness looks like for your category, get in touch.

This article reflects the status of DPP implementation as publicly available in August 2026. Verify the sector-specific delegated acts for your category before treating any implementation detail as mandatory.