What Are ISO/IEC JTC 5 and ISO 25534-1, and Do They Change the EU Digital Product Passport Standards?
ISO/IEC JTC 5 now coordinates global DPP standardisation, but ISO 25534-1 is still an early work item. See how it relates to Europe’s EN 182xx standards and ESPR.

A new ISO/IEC committee now coordinates international Digital Product Passport standardisation, but its first project is still at an early work-item stage. Europe’s EN 182xx standards and EU law still determine the current EU standards route.
Direct answer
ISO/IEC JTC 5 was created in 2026 to coordinate international Digital Product Passport standardisation across sectors and systems. Its first project, ISO/AWI 25534-1, is still under development at ISO stage 10.99, “new project approved”. It is not a published International Standard.
That means there is now a real international coordination layer, but there is not yet a finished ISO 25534-1 standard for a product team to implement. CEN-CENELEC describes the new international committee as building on and cooperating with Europe’s JTC 24 work, not replacing it.
For the EU, the legal position is separate. ESPR remains the framework law. A presumption of conformity under ESPR depends on harmonised-standard references being published in the Official Journal. As at 6 September 2026, ISO 25534-1 is not one of those references.
Navigate this page
- Overview
- Direct answer
- What changed in 2026
- ISO 25534-1 is a project, not a finished standard
- What JTC 5 owns, and what it leaves to other committees
- How this relates to Europe’s EN 182xx standards
- Why “international standard” and “EU harmonised standard” ar
- The global DPP landscape is still plural
- What product and architecture teams should do now
- What to watch next
- What would change this page
- Keep exploring
- Sources
What changed in 2026
The important change is organisational before it is technical.
ISO/IEC created JTC 5 as a joint technical committee for Digital Product Passport standardisation. Its public scope is cross-sector and cross-system: the DPP system and ecosystem, interoperable supply-chain information flow and common foundations that can work across existing technical domains.
The committee is also deliberately bounded. Its scope excludes sector-specific standards and work already covered by other ISO or IEC technical committees. That matters because JTC 5 should not be read as an attempt to pull every identifier, data carrier, cybersecurity, product-sector or supply-chain standard into one new stack.
The second change was the approval of ISO/AWI 25534-1, titled Digital product passport, Part 1: Overview and fundamental principles. ISO’s record shows it at stage 10.99, with the new project approved on 12 February 2026.
Those two facts are easy to collapse into the claim that “ISO now has a global DPP standard”. It does not. A committee exists and a project exists. The International Standard does not yet.
ISO 25534-1 is a project, not a finished standard
The simplest way to read the current position is as a decision ladder, not as a substitute for ISO’s formal development-stage catalogue.
| Question | Position at 6 September 2026 | What that lets you conclude |
|---|---|---|
| Does the international DPP committee exist? | Yes | ISO/IEC JTC 5 is an active international standardisation body. |
| Has its first DPP project been approved? | Yes | ISO/AWI 25534-1 is an approved work item at stage 10.99. |
| Is there a finished ISO 25534-1 standard to implement? | No | The project is still under development. |
| Has ISO 25534-1 become an EU harmonised-standard route? | No | It has no current OJEU reference under the ESPR DPP presumption mechanism. |
| Is one global DPP architecture now settled? | No | International convergence is still active and plural. |
ISO describes the intended scope of 25534-1 as foundational. It includes common terminology, principles, data categories, governance and trust, plus relationships to existing standards. That is useful direction for architecture teams, but the intended scope can still change while the work item develops.
The practical rule is simple: monitor it, design so you can accommodate it and do not claim conformance to a finished standard that does not yet exist.
What JTC 5 owns, and what it leaves to other committees
JTC 5 is best understood as a coordination and foundations layer.
Its public scope points to common DPP system concepts and interoperable information flow across sectors. It also says the committee will not duplicate sector-specific standards or work already owned elsewhere in ISO and IEC.
That boundary is important for product teams. A future international DPP foundation could reduce the amount of bespoke integration needed across jurisdictions, but it would not make product-sector requirements disappear. A battery, textile, construction product or electronic product can still sit under sector-specific law and sector-specific technical rules even if some DPP foundations converge internationally.
So the architectural opportunity is reuse, not replacement: common identity, data-governance, provenance and access foundations that can serve more than one destination where the standards genuinely align.
How this relates to Europe’s EN 182xx standards
Europe is further ahead in a different sense. CEN-CENELEC JTC 24 developed eight horizontal European DPP standards. Six references are currently published in the Official Journal under Commission Implementing Decision (EU) 2026/1736. The other two cover access-rights management and data authentication, reliability and integrity, but are not listed in that decision as at this page’s verification date.
The useful distinction is between four layers:
| Layer | What it currently does | What it does not do |
|---|---|---|
| ESPR | Creates the EU legal framework for DPP requirements and the harmonised-standards mechanism. | It does not turn every international standard into an EU compliance route. |
| CEN-CENELEC JTC 24 | Developed Europe’s horizontal DPP standardisation stack. | It does not decide every product-specific DPP data requirement. |
| EN 182xx standards | Provide European horizontal technical standards, with six references currently OJEU-cited. | Conformance does not prove overall product compliance. |
| ISO/IEC JTC 5 and ISO/AWI 25534-1 | Coordinate emerging international DPP foundations and common principles. | They do not replace ESPR, JTC 24 or the current EN 182xx legal effect in the EU. |
For the detailed legal status, use the page on which European DPP standards currently carry a presumption of conformity. For the subject matter of the European series, use what the horizontal DPP standards cover. This page owns the different question: what is happening at the international ISO/IEC layer and how it relates to Europe.
CEN-CENELEC’s own description of the relationship is helpful. It says JTC 5 builds on European JTC 24 work and is intended to broaden coordination towards a global DPP ecosystem. That is evidence of cooperation and likely influence. It is not evidence that the final ISO text will be clause-for-clause equivalent to the EN series.
Why “international standard” and “EU harmonised standard” are different things
An international standard can be technically influential without creating an EU legal presumption.
Under ESPR, the presumption of conformity for DPP requirements is tied to harmonised standards whose references are published in the Official Journal, and only for the Article 10 and 11 requirements the cited standard or part actually covers.
ISO itself also draws the line clearly: international standards can provide compatible foundations across different national and sector requirements, but they do not replace regulation.
So there are two questions to ask whenever ISO 25534-1 is mentioned in an EU DPP discussion:
- Is the ISO document finished and published? Today, no.
- Has the EU created a legal mechanism that gives it the claimed effect? Today, no evidence supports treating ISO 25534-1 as an ESPR harmonised-standard route.
That does not make the ISO work unimportant. It means technical influence and legal effect should be tracked separately.
The global DPP landscape is still plural
ISO/IEC JTC 5 is not the only international DPP initiative.
UN/CEFACT also has 2026 work on Digital Product Passport overview and fundamental principles, with project P1143 entering public review in August 2026. That work belongs to a different institutional context and should not be folded into ISO 25534-1 as if the two were one programme.
The sensible conclusion is therefore not that a single global standard has won. It is that several international bodies are now trying to make DPP foundations more reusable and interoperable, while Europe already has a legal framework and a comparatively mature horizontal standards programme.
If convergence works, organisations may eventually be able to reuse more of the same governed product facts and technical foundations across jurisdictions. That is an intended benefit, not yet a proven outcome.
What product and architecture teams should do now
You do not need to redesign an EU DPP programme around ISO 25534-1 today.
A better preparation plan is:
- Keep EU legal requirements separate from international standards monitoring. Build the EU route against applicable EU law and the standards that actually carry the relevant legal status.
- Keep product facts governed independently of one destination. Identity, provenance, source evidence and access policy are more reusable when they are not hard-coded to one passport output.
- Avoid irreversible choices around a proposal-stage document. Do not make a supplier, software or data-model commitment solely because it is described as “the ISO DPP standard”.
- Track interfaces rather than labels. Watch whether future ISO work changes terminology, governance expectations, trust mechanisms or relationships to standards you already use.
- Retain the ability to map one governed record into more than one standard profile. That is useful even if international convergence takes longer than expected.
For the trust and authentication question inside the current European DPP layer, the separate page on what signing a passport record can and cannot prove goes deeper without turning this page into a security-standard explainer.
What to watch next
ISO’s committee record schedules the inaugural ISO/IEC JTC 5 plenary for 7 to 9 September 2026 in Berlin. That meeting falls immediately after this page’s evidence cut-off.
The useful signals after it are concrete:
- a change in ISO 25534-1 from stage 10.99
- new JTC 5 work items or working groups
- published liaison or coordination decisions with CEN-CENELEC JTC 24
- clearer public scope for future parts of the ISO 25534 series
- any EU legal or Official Journal reference that gives an ISO document a defined EU role.
Do not infer those outcomes before the official records change.
What would change this page
This answer should be revisited if any of the following happens:
- ISO 25534-1 moves beyond its current approved-work-item stage
- ISO publishes a draft or final International Standard that materially changes the intended scope described here
- the 7 to 9 September 2026 JTC 5 plenary publishes decisions that alter the work programme
- CEN-CENELEC or ISO publishes a formal alignment or adoption decision that changes the JTC 24 and JTC 5 relationship
- the EU references ISO 25534-1, or a successor document, in legislation or Official Journal material.
Until then, the reliable position is narrower than the headlines: a global committee now exists, its first foundational project is real, and Europe’s current legal and harmonised-standards route remains separate.
Keep exploring
The questions this page usually raises next.
- CompareNext questionDPP Standards and Presumption of ConformityWhich passport standards have their references published in the Official Journal, which do not, and what a presumption of…
- CompareNext questionWhat Do the European Digital Product Passport Standards Cover?The eight European horizontal Digital Product Passport standards, what each one covers, which references are published in the…
- Related questionNext questionSigned Passport Data and What a Signature Does Not ProveA European standard on data authentication for passports is at formal vote.
Sources
-
EU law
-
Delegated act
Does this reach your products?
Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.