Standards
CEN/CENELEC JTC 24 and the M/604 Request
Who wrote the DPP standards? The CEN/CENELEC JTC 24 committee, the M/604 standardisation request, its working groups and the OJEU citation process.
The Digital Product Passport standards were written by JTC 24, the joint CEN and CENELEC technical committee, under the European Commission's M/604 standardisation request. The committee produced eight system-level standards in under two years.
What a standardisation request is
When the Commission wants a piece of legislation's technical requirements delivered through standards, it sends a formal mandate to the standardisation bodies. M/604 is the request that produced the technical counterpart to ESPR's DPP provisions.
The working groups
| Group | Topic | Standards produced |
|---|---|---|
| WG1 | Framework and interoperability | EN 18223 |
| WG2 | Identity and carriers | EN 18219, EN 18220 |
| WG3 | Security and access | FprEN 18239, FprEN 18246 |
| WG4 | Data exchange and lifecycle | EN 18216, EN 18221, EN 18222 |
See the DPP standards guide.
Presumption of conformity and OJEU citation
A published European standard is not yet "harmonised". It becomes so when it is cited against the relevant legislation in the Official Journal of the European Union. That citation creates a presumption that those applying the standard meet the legal requirement.
The practical consequence: "how do you demonstrate conformity with EN 18219, 18220 and 18222?" is the cleanest compliance question you can ask a vendor. See choosing DPP software.
Going international
ISO/IEC JTC 5, operational from September 2026, aims to internationalise this work, and comparable frameworks are expected outside the EU — meaning preparation done for the EU today should carry into other markets.
Frequently asked questions
How do I get the standard texts?
Through national standards bodies, for a fee. Most manufacturers rely on a platform that documents its conformity rather than buying the texts.
Will the standards change?
Yes — standards are living documents revised as experience accumulates. That is another reason to build flexible data infrastructure.
