On 20 July the European Commission launched the Digital Product Passport Registry — together with a public testing environment, user guidelines, a dedicated helpdesk, and a new Implementing Regulation setting out how registration actually works. This is the biggest piece of DPP infrastructure to go live so far, and it arrived before a single product group is legally required to use it.
What the Registry is — and isn’t
The Registry does not store your product data. Passports stay decentralised — hosted by you or your DPP provider. What the Registry does is index: economic operators register each passport’s unique identifier and associated metadata, and the Registry links that identifier to the responsible operator and attests that the passport exists. Think land registry, not filing cabinet.
Three practical features stand out:
Two registration routes. A secure user interface for low-volume use, and an API so registration can be wired into your existing systems. For any brand with more than a handful of SKUs, the API route is the only one that scales — batch-level granularity in the textile spec means passport counts multiply fast.
Proof of registration. Operators can request a secure electronic document proving a passport is registered — explicitly designed for B2B use. Expect this to show up in wholesale and retailer onboarding checklists well before any legal deadline, the same way DPP-readiness questions already appear in RFPs.
A free semantic repository. Machine-readable data models, definitions and vocabulary per product group, served over documented APIs. When the textile delegated act lands, this is where its data model will live in machine-readable form.
The timeline, without the panic
First mandatory use is 18 February 2027, for certain large batteries. Textiles are explicitly named among the product groups the Registry supports, but the textile delegated act is still expected around 2027, with compliance realistically 2028. Nothing you sell needs registering this year.
That is precisely what makes this quarter useful. The testing environment is open now, unmetered by any deadline pressure. The brands that had someone spend two days in it in 2026 will scope their real integration in 2027 from evidence. Everyone else will scope it from vendor slide decks.
Operator takeaway: put one hour in someone’s diary to create access to the testing environment and walk the registration flow end to end. Then ask your IT lead one question: if we had to register 10,000 passports via this API, what would we need? The answer — even a rough one — is the start of your integration requirement, written two years early and at zero cost.