National DPP Registries: How to Prepare for Each Member State's Portal
As EU countries begin defining their national Digital Product Passport registries, fashion brands must understand where and how to upload compliance data — and whether they'll need multiple integrations.
- The ESPR mandates national registries, but each Member State can define its own technical specifications and portal interfaces.
- Early movers like France and Germany are already publishing draft requirements; others will follow through 2025–2026.
- Brands selling across borders may face multiple upload workflows, authentication systems, and data format variations.
- A centralised EU data exchange layer is planned but not guaranteed to eliminate national fragmentation.
- Preparing now means auditing your data architecture and building API-ready infrastructure.
The EU's Ecodesign for Sustainable Products Regulation (ESPR) doesn't just require Digital Product Passports — it requires somewhere to store them. Under the regulation, each Member State must establish a national registry to receive, validate, and make DPP data accessible to market surveillance authorities (European Commission, 2024). For fashion brands operating across multiple EU markets, this raises an uncomfortable question: will you need to integrate with 27 different systems?
The registry landscape taking shape#
The ESPR framework envisions a decentralised architecture. While the European Commission will maintain a central registry of registries — essentially a directory pointing to each national system — the actual data repositories sit at Member State level (ESPR Article 12, 2024).
Some countries are moving faster than others. France, building on its existing anti-waste legislation (AGEC law), has signalled that its registry will extend to cover ESPR requirements. Germany's Federal Environment Agency (UBA) has begun stakeholder consultations on technical specifications. The Netherlands and Sweden have published initial position papers.
What we know about technical requirements#
The Commission has published guidance establishing minimum data standards for DPP content, but portal interfaces remain national competence. Based on early documentation and stakeholder consultations, expect variation in:
| Aspect | Likely variations |
|---|---|
| Authentication | National eID systems, EU Login, or registry-specific credentials |
| Data format | JSON-LD baseline, but schema extensions per country |
| Upload method | Web portal, API, or both — with differing API specifications |
| Validation rules | Stricter checks in some jurisdictions; auto-rejection vs. manual review |
| Language requirements | Some fields may require translation into national language |
The Commission's implementing acts will harmonise core data elements, but the "how" of submission remains fragmented (European Commission ESPR Delegated Acts, 2024).
The interoperability question#
A central EU data exchange layer — sometimes called the "DPP backbone" — is under development to enable cross-border data sharing between national registries. In theory, this could allow brands to submit once and have data propagate across jurisdictions.
In practice, expect a phased reality. The backbone will likely handle read operations first (letting authorities query across borders) before enabling write operations (letting brands submit centrally). The Commission's technical working group estimates centralised submission capabilities no earlier than 2028 (EU DPP Technical Stakeholder Forum, 2024).
Until then, brands with significant multi-market presence should plan for direct integration with at least two to four priority registries.
Practical preparation steps#
1. Audit your current data architecture. Can your PLM or ERP system export product data in structured formats? Do you have unique identifiers at the item level, or only SKU-level?
2. Map your market footprint. Identify which Member States represent 80% of your EU revenue. These are your priority registries.
3. Build API-ready infrastructure. Even if you start with manual portal uploads, architect your systems to support automated API submissions. Retrofitting is expensive.
4. Monitor national consultations. France's ADEME, Germany's UBA, and Italy's MASE are publishing updates. Assign someone to track them.
5. Engage with industry groups. Euratex, FESI, and national textile federations are providing collective input to registry design. Your voice matters.
Frequently asked questions
Will I need to register separately in every EU country where I sell?
Not necessarily. If you sell through distributors who take legal ownership, they may bear registry obligations in their markets. But if you sell direct-to-consumer or maintain legal presence in multiple states, you'll likely need multiple registrations. Clarify your legal structure first.
Can I use the same DPP data for all registries?
The core data elements will be harmonised by Commission implementing acts. However, some Member States may require additional fields — for example, France may extend requirements based on existing AGEC provisions. Build a superset of data that covers the strictest jurisdiction.
What happens if a registry rejects my submission?
Rejection workflows vary. Some registries will provide automated validation feedback; others require manual review. Products cannot legally be placed on that market until registry acceptance. Build buffer time into your launch calendars.
The fragmented registry landscape isn't ideal, but it's the reality brands must navigate. Those who treat DPP compliance as a data infrastructure project — not a one-time filing exercise — will adapt more easily as national systems evolve.
Trama is designed for exactly this complexity: a single platform where you structure your product data once, then export to whichever national registries require it, in whatever format they specify. As new registry APIs come online, we add them — so you don't have to rebuild your integration every time a Member State publishes new specs.
Generate your collection's passports
From product sheet to compliant, hosted, print-ready QR codes.
Get started