Digital product passports do not exist in a vacuum: the EU is establishing a central register — the DPP Registry — that links product passports together and lets authorities, customs and market participants carry out checks. Let us look at what it is for, and what it means for the manufacturer.
What is the DPP Registry?
The DPP Registry is a central system operated by the European Commission that records the identifiers and core data of digital product passports. It does not necessarily store the full DPP content (that is often provided by the economic operator); rather, it holds the connection point: where a given product's passport can be reached, who the issuer is, and whether it is valid.
What is it for?
- Official checks: market surveillance can quickly locate a product's passport.
- Customs: at import, it can be verified whether a valid DPP exists.
- Searchability: a single entry point into the product-data ecosystem.
- Integrity: registration supports the DPP not disappearing (persistence).
How does it fit into the process?
Manufacturer/importer → produce DPP (data + signature)
→ publish DPP (QR / GS1 Digital Link / resolver)
→ register in the DPP Registry (identifier + connection point)
→ authority / customs / consumer access itSo the platform must not only produce the DPP, but also prepare for the requirements of Registry registration and verification.
What does this mean for the manufacturer?
1. A unique, stable identifier is needed for every product (GS1 Digital Link + serial number). 2. Reliable availability: the resolver and URL must work over the long term (persistence — see prEN 18221). 3. Updatability: if the product's state changes (re-issue, second life), the link must be refreshed. 4. Data quality: the core data provided to the Registry must be accurate and authentic.
The question of persistence
A DPP must remain accessible for years — even decades (think of a battery's second life). This is a serious architecture question: where to store it, how to guarantee long-term availability, and what happens if the supplier ceases to exist. A future-proof solution handles this by design (see on-premise plus a persistence strategy).
Frequently asked questions
Is the DPP Registry already live?
The framework is being built; the details emerge from the implementing acts. Preparing in advance — identifier and persistence — is already advisable.
Does the Registry store the full DPP?
Typically the connection point and core data; the full content is provided by the economic operator.
What if my DPP provider ceases to exist?
That is why a persistence strategy and data portability matter — ask your supplier about them.
The DPP is not a one-off file but a living service. ReadyPass prepares you for the Registry era with GS1 Digital Link identifiers, resolver logic and a persistence-aware architecture.
Sources: ESPR (EU) 2024/1781; Battery Regulation (EU) 2023/1542; prEN 18221 (persistence). Registry details depend on the implementing acts.
