The European standards for the Digital Product Passport: EN 18216 ff. at a glance

Why the product passport needs standards at all

The Digital Product Passport is not a document but an infrastructure. A QR code on a sofa sold in 2026 must still lead to readable data in 2041 - by then possibly scanned by a recycling operation in Poland, using software that does not yet exist today.

For that to work, it is not enough for every company to build “some sort of” product passport. Common answers are needed to four technical questions:

• How is a product uniquely identified, so that two systems can be sure they are talking about the same item?
• Which data carrier transports that identifier on the product - QR code, Data Matrix, NFC tag?
• Via which protocol does third-party software query the data, without the two systems knowing each other beforehand?
• Where and for how long does the data remain available, even once the manufacturer has long ceased to exist?

These are precisely the questions answered by the European standards series EN 18216 ff. It was developed by the joint technical committee CEN-CLC/JTC 24 of the European standardisation organisations CEN and CENELEC, under a standardisation request from the European Commission. What the product passport fundamentally is and what it is needed for is explained in our DPP guide.

The eight standards of the EN 18216 ff. series

On 27 May 2026 six of the eight standards were published as final European Standards. Two further ones had not yet appeared at the editorial deadline for this article.

Of all things, the two outstanding standards concern the points that prompt the most follow-up questions in conversations with companies: who may see which data - and how you demonstrate that a passport’s content has not been manipulated. If you are basing an architecture decision on this, check the status again directly with CEN-CENELEC before deciding; it may have changed since the editorial deadline.

What the listing in the Official Journal means

On 15 July 2026 the six published standards were cited in the Official Journal of the European Union. Legally this happened through Implementing Decision (EU) 2026/1736 of 14 July 2026 - the reference can be found on EUR-Lex.

This citation is the truly decisive step, and it is regularly underestimated. It turns a technical standard into a harmonised standard - and with that, the presumption of conformity applies.

In plain terms: anyone designing their product passport in line with a standard listed in the Official Journal is presumed as a matter of law to meet the corresponding requirements of the Ecodesign Regulation (EU) 2024/1781. The burden of proof is reversed. You do not have to demonstrate to market surveillance that your technical implementation is sufficient - the authority would have to demonstrate the opposite. What else the ESPR covers is summarised in the article ESPR explained.

Are the standards mandatory?

No - and this answer is frequently reported incorrectly.

Harmonised European standards are voluntary. Only the law is ever mandatory, here the ESPR and the delegated acts still to come. The standard is the route recognised by the EU for meeting that obligation, not the only one.

So you may choose a different technical approach. You simply lose the presumption of conformity in doing so and carry the burden of proof yourself: in case of doubt you would have to document to the market surveillance authority that your solution meets the same requirements. For a company with its own standardisation department that is feasible. For a brand with 400 articles it is the more expensive route - with no discernible benefit in return.

What the standards do NOT govern

This is where the biggest misunderstanding lies. The EN 18216 ff. series is horizontal: it describes the pipework, not the water.

The standards set out how a product passport is identified, transported, stored and queried. They do not say what content has to be in it. Whether a textile passport must contain the fibre composition in percentages, the place of manufacture or information on chemicals appears in none of these standards - it appears in the delegated act for the respective product group.

And that is exactly where things stand: at the beginning of September 2026 no delegated act had been adopted for any of the prioritised ESPR product groups - textiles, furniture, tires, mattresses. The technical foundation is therefore largely in place, while the catalogue of mandatory content is still missing. Anyone preparing today builds on stable technology and will later have to add data fields, not replace the architecture. Which deadlines follow from this per sector is shown in the overview of DPP deadlines; your own exposure is clarified in a few minutes by the ESPR deadline checker.

What this means in practice for brands and retailers

The good news first: you do not implement EN 18220 yourself. No fashion retailer builds a standards-compliant data carrier stack, just as no online shop writes its own TLS libraries. That work belongs in the software that creates and delivers your product passports.

Your task is a different one: to put the right question to the provider. Five questions that create clarity in a demo appointment - evasive answers are the real signal here:

1. Which standards of the EN 18216 ff. series do you implement today - and which not yet? A serious answer names specific numbers, not a phrase like “standards-compliant”.
2. How do you generate unique identifiers under EN 18219, and who owns them? If the identifier is tied to a provider domain, your printed QR code depends on it.
3. What commitment do you give on data persistence within the meaning of EN 18221? The passport has to outlast the product lifetime, not the contract term.
4. How will you handle EN 18239 and EN 18246 once they have appeared? Retrofitting access rights and data integrity is architecture work, not a configuration switch.
5. What happens if the delegated act for my product group brings new mandatory fields - and who bears the effort?

The further selection criteria and the four types of provider on the market are covered in the DPP software comparison. Who has to answer for the passport in regulatory terms - manufacturer, importer or distributor - is clarified in the article Who is responsible for the DPP?

Where to obtain the standards

Inconvenient but important: European standards are not free of charge. There is no free download from the European Commission, not even for harmonised standards. They are distributed through the national standards institutes - via DIN in Germany, Austrian Standards in Austria and the SNV in Switzerland. They are sold per document.

With eight standards that adds up, and for smaller companies it is a genuine obstacle - all the more so when you do not know in advance which of the eight are relevant at all. Freely accessible are only the reference lists in the Official Journal and the public announcements from CEN-CENELEC, which name the titles and scope of the standards.

The practical consequence: for most brands and retailers, buying the complete set is not worthwhile. It makes more sense to demand conformity with the standards where it is technically implemented - from the software provider, in writing and with the standard number.

This is exactly where SolveDPP comes in: product passports are created directly from your existing Shopify catalogue, validated against the mandatory information and published publicly via QR code - the technical side stays with the provider, your work stays with the data. If you are still at the start of your selection process, the DPP software comparison helps you place the provider types; which requirements apply specifically to your range is shown by the DPP configurator.