Digital Product Passport
Multilingual DPPs: Which Languages Do You Need?
Which languages must a Digital Product Passport be available in? Member State rules, coded fields and a data model approach that cuts translation cost.
The EU has 24 official languages, and consumer-facing information must be provided in the language of the Member State where the product is sold. This is one of the most underestimated cost lines in a Digital Product Passport — and most of it disappears with the right data model.
Which languages are required?
ESPR and product legislation generally require consumer-facing information in the language determined by the Member State where the product is placed on the market. In practice:
- Selling into Germany, France and Italy: German, French, Italian.
- Distributing EU-wide: your language list grows with your distribution network.
- English is not universally accepted; many Member States require their own language.
The real fix: reduce free text
A passport has two kinds of field:
| Type | Example | Translation burden |
|---|---|---|
| Coded | Country code, material code, care symbol, certificate type | Zero |
| Free text | Product description, repair instruction, usage note | High |
Coded fields render in the requested language at the presentation layer. Entering a new market grows the interface dictionary, not the content. See the DPP data model guide.
Where code lists apply
- Country and region: ISO 3166.
- Materials: sector code lists (fibre names are legally defined in textiles).
- Care instructions: international care symbols.
- Hazardous substances: CAS numbers and REACH references.
- Certificates: issuing body + document type + number.
When free text is unavoidable
Some fields, like repair instructions, need prose. Three practical rules:
- Write short and structured — step lists are cheaper and more consistent to translate.
- Tie versioning to language: when the source text changes, mark every translation stale.
- Do not hide a missing translation: falling back to the source language beats showing an empty field.
Interface versus data
One common mistake: the interface strings of a passport page (headings, labels) and the data content must be managed separately. The interface dictionary is translated once and works for every product; data content is managed per product. Projects that skip this distinction multiply translation cost by SKU count.
For field design see the DPP data model guide, for the consumer-side language experience what consumers should see, and for the cost impact DPP cost breakdown.
Frequently asked questions
Isn't English enough?
Usually not. Member States can require their own language for consumer-facing information. In restricted B2B tiers, English is often acceptable.
Can I use machine translation?
It is risky for compliance fields — a wrong care or safety instruction creates liability. Coded fields remove most of that risk.
Should the user choose the language?
Default to the browser language, but include a visible language switcher: an auditor or recycler may arrive in a different language.
