The DPP Registry Is Live; Product Duties Still Need Their Own Act
Verify an ESPR Digital Product Passport claim through the regulation, product-specific act and live EU Registry instead of treating one portal as proof of every duty.
Signals to watch
- A forwarded message says the EU DPP database is live but gives no European Commission link or Registry record
- A product team treats Registry availability as proof that its product group already has mandatory passport fields
- A vendor demo uses a private passport platform while the economic operator, applicable legal act and EU registration receipt remain unstated
The EU Digital Product Passport Registry is operational, but that fact does not make every product subject to a passport or prove that a private platform is the EU Registry. Verify three different objects: the legal basis, the product-specific requirement and the actual Registry transaction or record. A claim is ready for business review only when all three are connected to a named economic operator and product.
Definition: the DPP Registry is the EU database supporting the Digital Product Passport system. The European Commission says it stores unique product identifiers and mandatory registration data. The complete product information remains with the responsible economic operator or a DPP service provider, while a data carrier such as a quick response (QR) code links the physical product to its passport.
A true launch date can still support the wrong product claim
A product-data consultancy business-development lead may follow authorised Telegram groups used by manufacturers, importers, enterprise-resource-planning teams, traceability vendors and sustainability specialists. On 21 July, a forwarded thread might say:
“EU DPP database is open now.”
“Need all product passports connected this quarter—platform already has a registry connector.”
This is an illustrative composite, not a customer message or implementation result. The first sentence can be traced to a real official event. The second omits product group, delegated act, separate sector law, economic operator, required data, data carrier, access rights, Registry environment and market date. Combining the two turns a verified launch into an unsupported universal deadline.
Seeing the thread late can still cost the consultancy a useful discovery window: the manufacturer may choose an implementation scope before anybody checks what must actually be registered. Seeing it early is valuable only if the lead restores the missing source layers.
Level 1: ESPR creates the framework, not one universal product file
Regulation (EU) 2024/1781, the Ecodesign for Sustainable Products Regulation (ESPR), was published on 28 June 2024. It establishes the framework for ecodesign requirements and Digital Product Passports. The framework defines the system and the types of elements later acts can require; it does not assign identical passport fields and dates to every product group.
This is the first source level because it answers “What EU framework authorises this system?” It does not answer “Which fields must this exact textile, tyre, steel product or appliance publish today?”
Separate legislation can also create passport duties. The Commission’s DPP portal lists the Batteries Regulation as an example. That is why a battery passport should not be presented as proof that an ESPR delegated act already applies to another product group.
Level 2: the product-specific act defines the duty
The second source is the legal act that names the product group, required data, timing, data carrier, access rules and responsible economic operator. Under ESPR, that may be a product-specific delegated act. For batteries or another sector, it may be a separate regulation.
Capture at least:
- exact act and article;
- product group and scope definition;
- adoption, entry-into-force and application dates;
- transition period and market event;
- mandatory data and registration metadata;
- data-carrier and identifier requirements;
- access classes and responsible economic operator.
If the delegated act is planned but not yet adopted, record that status. A Commission timeline can support planning, but an indicative future entry is not the same as an adopted legal duty. The Commission portal itself labels parts of the wider timeline as indicative and subject to publication requirements.
Level 3: the Registry proves a registration event, not complete compliance
The European Commission records 20 July 2026 as the date the DPP Registry became operational. Its launch notice and current Registry service page are the official sources for that system event.
The Commission describes a practical sequence: the economic operator gathers data required by applicable law, creates and registers the passport, the Registry generates a unique registration identifier, and users receive information according to their access role. For imported products, the identifier can support a customs check. The complete information is not described as living entirely inside the Registry.
A registration receipt can therefore support claims such as “this identifier was registered in this environment at this time.” It cannot alone prove that every required product datum is accurate, that the economic operator has the stated role, that confidential access rules are correct or that the product meets every ecodesign requirement.
The three-level receipt exposes private-platform substitutions
Use a receipt with one row for each source level:
| Source level | Evidence to preserve | Valid conclusion | Unresolved question |
|---|---|---|---|
| Regulation | official URL, version, article and retrieval date | the framework exists and defines the legal route | which product act applies |
| Product act | adopted text, product scope, fields, dates and access rules | the named product group has the stated duty | whether the actual product and operator are in scope |
| Registry | environment, operator account, identifier, timestamp and response | the named registration event occurred | whether the hosted information is complete and accurate |
A private provider may create passports, host complete product information or connect to the EU service. That can be a legitimate implementation component. It does not make the provider’s dashboard the EU Registry. Ask for the EU service environment and transaction receipt rather than accepting a logo, screenshot or phrase such as “registry-ready.”
For early implementation demand, the DPP pilot article separates a real task from generic interest. For batteries, the battery-passport owner handoff follows that sector’s separate law. When the original URL is missing, use the official-source ladder before evaluating the commercial claim.
Monitoring can surface the mismatch; people must verify the account and act
TOP Prospect can preserve fragments from Telegram groups the user deliberately connects and is authorised to access, with source, time and original wording for human review. The current production matching-target interface saves configuration but does not automatically create new candidates.
It cannot access a company’s Registry account, prove an economic-operator role, read restricted product information, validate identifiers, determine legal scope or contact the author. A consultancy lead must open the official sources, obtain authorised account evidence and ask qualified product and legal owners to confirm applicability. The public product workflow describes that boundary.
Key facts
- ESPR, Regulation (EU) 2024/1781, was published on 28 June 2024.
- The Commission records 20 July 2026 as the date the DPP Registry became operational.
- Product requirements arise through ESPR delegated acts or separate EU legislation.
- The Registry stores unique identifiers and mandatory registration data; complete product information remains with the economic operator or a DPP service provider.
- A data carrier links the physical product to the passport, and access depends on user roles under applicable law.
- A live Registry does not create one universal DPP deadline for every product.
FAQ
Is the EU Digital Product Passport Registry operational?
Yes. The European Commission records 20 July 2026 as the date the DPP Registry became operational and published a launch notice and supporting materials.
Does the live Registry make DPP mandatory for every product?
No. Product-specific requirements arise through delegated acts under ESPR or through separate EU legislation such as the Batteries Regulation. Registry availability is not the same as product applicability.
What does the DPP Registry store?
The Commission describes it as storing unique product identifiers and mandatory registration data. Complete product information remains with the economic operator or a DPP service provider.
Can a private DPP platform be treated as the EU Registry?
No. A private service may host product information or support implementation, but the claim must still identify the applicable legal act, EU Registry transaction or record, economic operator and access rules.
Reviewed by TOP Prospect Editorial Team on 19 August 2026 against ESPR and European Commission DPP sources updated through 20 July 2026. Product applicability, delegated-act status, access rights, operator responsibility and Registry account evidence require review of the current official acts and authorised records.
Frequently asked questions
Is the EU Digital Product Passport Registry operational?
Yes. The European Commission records 20 July 2026 as the date the DPP Registry became operational and published a launch notice and supporting materials.
Does the live Registry make DPP mandatory for every product?
No. Product-specific requirements arise through delegated acts under ESPR or through separate EU legislation such as the Batteries Regulation. Registry availability is not the same as product applicability.
What does the DPP Registry store?
The Commission describes it as storing unique product identifiers and mandatory registration data. Complete product information remains with the economic operator or a DPP service provider.
Can a private DPP platform be treated as the EU Registry?
No. A private service may host product information or support implementation, but the claim must still identify the applicable legal act, EU Registry transaction or record, economic operator and access rules.
Sources and further reading
- Regulation (EU) 2024/1781 establishing a framework for ecodesign requirements for sustainable products, published 28 June 2024
- European Commission, Digital Product Passport portal, updated 20 July 2026
- European Commission, DPP Registry, current official service page accessed 19 August 2026
- European Commission, The Digital Product Passport Registry is now live, 20 July 2026
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
