Do ISO/IEC JTC 5 and ISO 25534-1 Change the EU DPP Standards?

What changed in 2026

The 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. So 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.

Neither fact means “ISO now has a global DPP standard”. A committee exists and a project exists. The International Standard does not yet.

ISO 25534-1 is a project, not a finished standard

Read the current position as a decision ladder, not as a substitute for ISO’s formal development-stage catalogue.

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.

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.

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 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.

Four layers matter:

For the detailed legal status and the subject matter of the European series, use the page on which European DPP standards currently carry a presumption of conformity. This page covers the different question: what is happening at the international ISO/IEC layer and how it relates to Europe.

CEN-CENELEC 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. If you want to try a product web identifier now, you can build a GS1 Digital Link for one GTIN.

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:

1. Is the ISO document finished and published? Today, no.
2. 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.

Two ITU-T Recommendations are also relevant. ITU-T L.1070 (11/2023) is Global digital sustainable product passport opportunities to achieve a circular economy. ITU-T L.1071 (11/2024) is A model for digital product passport information on sustainability and circularity and is listed by ITU as in force. L.1071 defines an information model for environmental sustainability and circularity information for ICT products and describes itself as complementing regional and global DPP work.

These are ITU-T Recommendations, not EU legal instruments. Their existence does not create an ESPR obligation, does not replace product-specific delegated acts and does not give them the legal effect of an EU harmonised standard reference. They show that global DPP standardisation is broader than ISO/IEC JTC 5 and CEN-CENELEC alone.

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 conclusion isn't that a single global standard has won. It's 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 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 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, see what signing a passport record can and cannot prove.

What to watch next

ISO’s committee record lists the inaugural ISO/IEC JTC 5 plenary for 7 to 9 September 2026 in Berlin. As at this page’s 7 September 2026 verification point, that meeting is in progress and no public committee record reviewed here establishes a post-plenary change to ISO/AWI 25534-1. Do not infer meeting outcomes before ISO publishes them.

ISO/AWI 25534-1 remains under development at stage 10.99, New project approved, with the project approval dated 12 February 2026. It is not a finished International Standard and it does not become an EU legal requirement merely because the work item exists.

Concrete signals to watch after it:

• 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

Revisit this answer 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.

Sources

• ISO/IEC JTC 5, Digital Product Passport, ISO, committee record checked 6 September 2026.
• ISO/AWI 25534-1, Digital product passport, Part 1: Overview and fundamental principles, ISO, stage record checked 6 September 2026.
• Digital product passports explained, ISO.
• New ISO/IEC JTC 5 Digital Product Passport Bridges European Development and Global Standardization, CEN-CENELEC / DIN, 29 July 2026.
• Regulation (EU) 2024/1781, Ecodesign for Sustainable Products Regulation, EUR-Lex.
  EU law
• Commission Implementing Decision (EU) 2026/1736 on harmonised standards for digital product passports, EUR-Lex.
  Delegated or implementing act
• UN/CEFACT Highlights 2026, UNECE, used only to show that international DPP standardisation is not a single-framework process.