The EU DPP Registry Goes Live July 19 — What Manufacturers Need to Know
Key Takeaways
- The EU DPP Registry opens July 19, 2026 — not as an enforcement date, but as a submission window that gives manufacturers six months to test data pipelines before the February 2027 battery deadline.
- The registry stores product identifier references and validates data structure; manufacturers host their own DPP data and submit a validated reference link, not the full dataset.
- The registry's sandbox environment is available now — organisations that have not engaged with it are missing the most practical pre-launch preparation step.
- ESPR obligations attach to the product being placed on the EU market, not to the seller's location — UK manufacturers distributing through EU partners must comply regardless of Brexit.
Four weeks from now, the European Commission's official Digital Product Passport Registry will go live. Most manufacturers are broadly aware that digital product passports are coming. Far fewer know that the central submission infrastructure — the database where every DPP must ultimately be registered — opens its doors on July 19, 2026.
This is not a drill date or a consultation milestone. It is the launch of the operational portal. If your organisation sells physical products in the EU, the clock is no longer measured in years. It is measured in weeks.
What the DPP Registry Actually Is
The DPP Registry is the centralised EU database operated under the Ecodesign for Sustainable Products Regulation (ESPR) (Regulation EU 2024/1781, Article 12). Think of it as the single source of truth for product sustainability data across the European single market. Every Digital Product Passport — regardless of product category or manufacturer — must ultimately be linked to an entry in this registry.
The registry does two things. First, it stores product identifiers and the canonical location of each product's DPP data. Second, it provides the verification layer that lets customs authorities, market surveillance bodies, and consumers confirm that a product's passport is authentic and complete.
What the registry does not do is store the full DPP data itself. Manufacturers host their own DPP data (or use a platform to do so) and submit a validated reference to the registry. The registry resolves that reference, confirms the data structure is compliant, and issues a registry ID that must appear on the product or its packaging.
How the Registry Fits Into the Broader ESPR Framework
The ESPR framework is built around three layers:
- Product-level data — materials, components, carbon footprint, repairability, end-of-life instructions
- Digital carrier — a QR code, NFC tag, or data matrix that links to the DPP
- The registry — the EU-operated backbone that validates and indexes every issued passport
The registry going live on July 19 completes layer three. Layers one and two require manufacturer action. The infrastructure will exist; using it correctly is now the manufacturers' responsibility.
Which Products Are Affected and When
The registry infrastructure is category-agnostic — it is built to handle all product types. But the compliance deadlines are staggered by category. Here is the current timeline:
| Date | Milestone |
|---|---|
| July 19, 2026 | DPP Registry portal goes live — submission accepted for all categories |
| February 18, 2027 | Industrial and EV batteries — DPP mandatory for market access |
| 2027–2028 | Textiles and apparel — DPP requirements enter force |
| 2028–2029 | Electronics and ICT equipment — DPP mandatory |
| 2029–2030 | Furniture, construction products, chemicals — phased rollout |
| 2030+ | Remaining product categories under ESPR scope |
The battery mandate is the first hard enforcement deadline. If your organisation manufactures, imports, or distributes industrial or EV batteries into the EU, February 2027 is your drop-dead date — and July 2026 is when you can begin submitting to test and validate your data pipeline.
What Data Must Be Submitted
The specific data fields vary by product category, but the core data model required by the ESPR registry covers five domains:
Product Identification
- Unique product identifier (conforming to ISO/IEC 15459 or GS1 standards)
- Product model and variant codes
- Manufacturer legal entity and EU authorised representative
- Country of manufacture and batch/serial traceability data
Materials and Composition
- Bill of materials including substances of concern under REACH
- Recycled content percentage by material type
- Presence of hazardous substances and safe disassembly instructions
- Supply chain origin for critical raw materials
Carbon and Environmental Footprint
- Product carbon footprint across lifecycle stages (cradle to gate minimum for phase one)
- Energy consumption in use (where applicable)
- Water usage during manufacture (category-dependent)
Repairability and Durability
- Repairability score and spare parts availability
- Minimum guaranteed software support period (for connected products)
- Durability test results and expected product lifespan
End-of-Life Instructions
- Disassembly instructions for consumers and professional recyclers
- Material sorting codes
- Deposit scheme or take-back programme details
Not every field is mandatory on day one for every category. The European Commission is publishing implementing regulations on a category-by-category basis that specify exactly which fields are required and at what level of detail. Manufacturers should be monitoring the Official Journal of the EU and the ESPR delegated acts as they are published.
What "Registry Live" Actually Means for You
The portal opening on July 19 does not automatically trigger compliance obligations for most manufacturers. What it does create is a submission window — a period during which you can register products, test your data pipeline, and resolve errors before enforcement deadlines arrive.
This distinction matters. Organisations that wait until February 2027 to begin battery DPP submissions will be debugging their data integration under enforcement pressure. Organisations that begin in August 2026 will have six months to identify gaps in their materials data, fix integration issues with their ERP systems, and build the operational workflows that DPP compliance requires on an ongoing basis.
The registry also publishes a sandbox environment that precedes the live portal. Manufacturers can use the sandbox to validate data structure and field completeness without creating live registry entries (European Commission ESPR Digital Infrastructure Guidance, 2025). If you have not engaged with the sandbox, that is the first practical step to take before July 19.
Platforms and Tools in the Market
Several platforms have emerged to help manufacturers build and manage DPP data. The market is still forming, but a few players have established meaningful track records:
Circularise is a Netherlands-based platform with deep expertise in plastics and chemicals supply chains. Their approach uses zero-knowledge proofs to let manufacturers share DPP data selectively — useful for protecting commercially sensitive formulations while still meeting disclosure requirements.
SAP Digital Product Passport integrates directly into SAP's existing ERP and PLM ecosystem. For manufacturers already running SAP, this route minimises integration complexity and leverages existing master data. The trade-off is that it inherits SAP's implementation timelines and licensing structure.
Protokol focuses on the NFC and physical carrier layer, with pre-built connectors to common data sources. Their strength is rapid deployment of the physical DPP infrastructure — the tags and QR systems — which is often the component organisations underestimate.
Each platform has genuine strengths and makes different trade-offs between flexibility, integration depth, and deployment speed. The right choice depends heavily on your existing technology stack, your product category, and how much of your supply chain data is already structured and accessible.
BrandedMark connects product identity data — QR codes, NFC tags, customer-facing product pages — with the compliance and registry layer, giving manufacturers a single point of truth for both consumer experience and regulatory submission.
What to Do Between Now and July 19
Four weeks is enough time to be meaningfully better prepared. Here is the priority order:
This week: Audit your data readiness. Pull the bill of materials for your five most complex products. Map each field in the ESPR data model against what you can actually provide today. The gap analysis will tell you whether your problem is data collection, data structure, or data accessibility — and those require different responses.
Next week: Engage your supply chain. Carbon footprint and materials data for most products cannot be assembled from internal systems alone. Tier 1 and Tier 2 suppliers need to be in scope now. If supplier data sharing agreements are not already in place, they need to be drafted.
Week three: Evaluate your platform options. A spreadsheet is not a DPP platform. The registry requires structured, machine-readable data submitted via API. Identify whether you will build, buy, or partner — and if buying or partnering, begin vendor evaluation this week.
Week four: Register for registry access. The European Commission will publish registration procedures for manufacturer accounts ahead of the July 19 launch. Ensure your EU authorised representative details are current and that you have identified the person in your organisation who will hold registry credentials.
For a comprehensive look at the broader compliance landscape, see our DPP compliance timeline from 2026 to 2030 and our DPP readiness checklist for 2026.
Frequently Asked Questions
Does the registry opening on July 19 mean we are legally required to submit immediately?
No. The registry opening creates the infrastructure and the submission capability, but enforcement obligations are tied to the per-category implementing regulations. For batteries, the mandatory submission deadline is February 18, 2027. For textiles, electronics, and other categories, deadlines follow later. However, using the submission window before your deadline is strongly advisable — six months of lead time to resolve data and integration issues is a significant operational advantage.
What happens if a product is submitted to the registry and the data is later found to be incomplete or incorrect?
The registry supports data updates and version control. Manufacturers can revise submitted data and the registry maintains an audit trail of changes. Market surveillance authorities will have access to the revision history. The expectation is that data quality will improve iteratively, but submissions containing materially false information — particularly on hazardous substances or recycled content claims — carry regulatory risk independent of the registry correction process.
We sell through distributors, not directly to EU customers. Does DPP still apply to us?
Yes. The ESPR obligation attaches to the product being placed on the EU market, not to who sells it. If your products — manufactured anywhere in the world — are sold by distributors into the EU, the DPP requirement applies to you as the manufacturer. Your EU authorised representative (if you are based outside the EU) carries legal responsibility for registry compliance. Distributors are not exempt, but the primary obligation sits with the manufacturer or importer who first places the product on the EU market.
The registry opening is not the end of the DPP story — it is the beginning of the operational phase. The policy debate is largely settled. What remains is execution: building the data infrastructure, integrating the supply chain, and establishing the workflows that will make DPP submission a repeatable operational process rather than a one-time compliance scramble.
If you are starting from scratch, our introduction to EU Digital Product Passports covers the regulatory foundation. For manufacturers who already understand the framework and need to move from understanding to action, the DPP readiness checklist is the practical next step.
July 19 is four weeks away. The portal will be open. The question is whether your data will be ready when it is.