One product, ten markets, one passport — and a few things that do vary.
You sell the same product in Germany, France, the Netherlands, Poland and Spain. Does that mean five passports? No — and building five is one of the more expensive mistakes available to you. The Digital Product Passport is a single-market instrument: one product, one identifier, one record. What varies between member states is not the passport itself but the environment it is read in: the language, the authority, the enforcement and the national schemes around it.
Last updated:
In one line: selling into ten member states does not mean ten passports — it means one passport that has to render for ten sets of readers, sit under ten national enforcement regimes, and coexist with the take-back and producer-responsibility schemes each country already runs.
What stays the same everywhere
The passport is EU legislation, and its whole point is that a product carries one truthful record across the single market. Four things do not change when you cross a border:
One passport per product — the same data record, whichever member state the item is sold in.
One identifier — the unique identifier behind the QR or Data Matrix code, typically carried as a GS1 Digital Link, resolves to the same passport everywhere.
One registry entry — the EU DPP registry is an EU-level system, which opened for registration on 19 July 2026. It is not a per-country filing, and what must be registered for each product group follows that group’s delegated act.
One set of declared values — composition, carbon figures and durability claims are properties of the product, not of the market. If they genuinely differ per market, you are selling different products.
What actually varies by member state
Language expectations — EU product law generally expects consumer- and authority-facing information in the language of the market where the product is placed, and member states set that for their own territory. The passport-specific detail is expected to be fixed per product group through delegated acts.
Which authority reads it — market surveillance is organised nationally. Five markets means five sets of authorities who might inspect, each working in their own language and with their own inspection habits.
Enforcement and penalties — member states set penalties, which must be effective, proportionate and dissuasive. Customs can detain non-compliant goods and authorities can order withdrawal from the market. The commercial exposure is usually the detained stock, not the fine.
Take-back, producer-responsibility and national schemes — EPR registrations, packaging and electrical-waste obligations, deposit systems. These are national, they pre-date the passport, and the passport does not replace them. It may reference them; it does not discharge them.
Why a passport per market is the wrong instinct
The natural reflex — “we localise everything else, so we will localise the passport” — creates three problems at once.
It breaks the identifier. The design assumes one code resolves to one record. Market-specific passports mean either multiple identifiers on identical products, or one identifier with a branching resolution nobody downstream expects. Both make item-level traceability and cross-border resale unreliable — and products do move between markets after first sale.
It multiplies maintenance. Passports must stay current for the product’s regulated lifetime. Every correction, supplier change and recalculated figure now has to be applied N times, and the day one copy drifts you are making inconsistent declarations about the same product inside the same union.
It solves the wrong problem. The reason people reach for per-market passports is usually language — and language is a rendering problem, not a data problem. One record rendered in the reader’s language gives you the local experience without any of the duplication.
A workable approach for 5–10 markets
Keep one master record per product, with the identifier and registry entry attached to it. Resist any architecture in which a market gets its own copy.
Render, do not duplicate. The field structure should display in the reader’s language automatically; the declared values stay exactly as you filed them.
Isolate the genuinely market-facing text — safety and care instructions, warnings, disposal guidance — and hold those as multi-language fields inside the one record. That is a small, finite translation job.
Map your markets once. For each country: the market-surveillance authority, the producer-responsibility and take-back registrations you already hold, and the language you expect to be asked for. A one-page table answers most audit questions before they are asked.
Track deadlines by product group, not by country. Timing follows the delegated act for your product group across the whole EU, so the question is never “when does Poland start?” but “when does our group’s act apply?”
Frequently asked questions
Do we need a separate Digital Product Passport for each EU country we sell in?
No. The passport is a single-market instrument: one product, one identifier, one record, read across all member states. What differs by country is the language the reader expects, the authority that may inspect, the national penalties and the take-back schemes you already have to register with.
Does the passport replace our national EPR or take-back registrations?
No. Producer-responsibility registrations, packaging and electrical-waste obligations and deposit schemes are national regimes that exist independently of the passport. The passport can carry information that references them, but it does not discharge them, and none of them disappear when a passport goes live.
Which country’s authority will actually check us?
Any market-surveillance authority in a member state where the product is placed on the market, plus customs at the point of entry. That is why the passport has to be readable by an official who is not working in your language — and why gaps tend to surface wherever your goods happen to land first.
Do we register the passport in every market?
The EU DPP registry is an EU-level system rather than a per-country filing — it opened for registration on 19 July 2026 — and what has to be registered for each product group is set by that group’s delegated act. Plan for one registration path, not one per market.