How JTC 24 Defines the Digital Product Passport Framework 

Published
, 23 minute read

Quick summary: Learn how JTC 24 defines the Digital Product Passport framework under ESPR, including data standards, architecture, interoperability, and compliance implications.

If you’re preparing for the Digital Product Passport (DPP), you’ve probably asked yourself: “What exactly will the EU expect our system to look like?” Not just what data to provide but how it should be structured, stored, accessed, and verified. That’s where uncertainty becomes expensive. Many manufacturers are investing in traceability tools, QR codes, and ESG platforms without clarity on the technical standards that will ultimately determine compliance. The risk? Building infrastructure that doesn’t align with the framework regulators will use to assess conformity. This is precisely where JTC 24 becomes critical. 

CEN-CENELEC JTC 24 is the technical body shaping the standards that will define how the Digital Product Passport operates across the EU. While the Ecodesign for Sustainable Products Regulation (ESPR) creates the legal obligation, JTC 24 defines the architecture behind it. 

In other words: 

ESPR tells you that you must implement DPP. 
JTC 24 defines how it must function. 

For battery manufacturers, textile producers, electronics suppliers, and automotive players, understanding JTC 24 isn’t an optional technical curiosity; it’s the difference between building scalable compliance infrastructure and retrofitting systems under regulatory pressure. 

Let’s break down how JTC 24 defines the Digital Product Passport framework and what it means for your implementation strategy. 

Key Takeaways 

  • CEN-CENELEC JTC 24 is the technical body shaping how the Digital Product Passport (DPP) will function under the Ecodesign for Sustainable Products Regulation.  
  • While ESPR creates the legal obligation to implement DPP, JTC 24 defines the operational standards from data structure and interoperability to digital product identifiers and access control.  
  • For manufacturers, this means DPP compliance is not just about adding a QR code, but about aligning digital infrastructure with harmonized EU standards. 
  • Understanding JTC 24’s objectives, architecture, evolving timeline, and common misconceptions helps companies reduce compliance risk, avoid fragmented systems, and build scalable, future-proof product data frameworks. 

What Is JTC 24? 

At the centre of Europe’s Digital Product Passport standardization work sits CEN-CENELEC JTC 24. 

JTC 24 is the Joint Technical Committee responsible for developing the harmonized European standards that will underpin the Digital Product Passport (DPP) across industries. 

While regulations define what companies must comply with, technical committees define how that compliance should work in practice. JTC 24 is the body translating policy ambition into operational standards. 

Where Does JTC 24 Sit in the EU Framework? 

JTC 24 operates under two major European standardization organizations: 

  • CEN 
  • CENELEC 

Together, CEN and CENELEC develop voluntary European standards that support EU legislation. When these standards are harmonized and referenced in the Official Journal of the EU, they provide a presumption of conformity”   meaning companies following them are assumed to comply with the legal requirements. 

JTC 24 was specifically created to address the technical standardization needs of the Digital Product Passport across product categories. 

Ready to operationalize Digital Product Passport (DPP) compliance? 

Explore how TraceX DPP Compliance solutions help you structure product data, ensure interoperability, and stay ahead of evolving EU requirements. 

Why JTC 24 Exists 

The Digital Product Passport is introduced under the Ecodesign for Sustainable Products Regulation (ESPR). 

ESPR establishes: 

  • The legal requirement for DPP 
  • The scope of products 
  • Sustainability and transparency objectives 
  • Data accessibility principles 

However, ESPR does not define: 

  • The technical data model 
  • How product identifiers should function 
  • How interoperability should be ensured 
  • How data should be structured and exchanged 
  • The architecture of access rights 

This is where JTC 24 comes in. 

What Exactly Does JTC 24 Define? 

JTC 24 is tasked with developing standards for: 

1️. Data Architecture 

How product information should be structured so that it is machine-readable, interoperable, and scalable across the EU. 

2️. Interoperability Framework 

Ensuring that DPP systems can communicate across different platforms, companies, and Member States without fragmentation. 

3️. Digital Product Identifiers 

Standards for unique, persistent product IDs that link physical goods to their digital records. 

4️. Data Carriers 

Specifications around how DPP information is accessed (e.g., QR codes or equivalent technologies). 

5️. Data Access & Governance 

Principles governing: 

  • Public vs restricted information 
  • Regulator access 
  • Commercial confidentiality 
  • Secure data exchange 

In short, JTC 24 defines the technical backbone that makes Digital Product Passports function consistently across Europe. 

Want to understand how the Digital Product Passport is technically structured? 
Read: “Inside the Digital Product Passport Architecture” 

Curious how product-specific DPP requirements will actually be defined? 
Read: “How DPP Delegated Acts Will Shape Your Compliance Strategy” 

Why JTC 24 Matters for Manufacturers 

For manufacturers, suppliers, and OEMs, JTC 24 is not just a regulatory footnote. 

It determines: 

  • Whether your ERP/PLM integration will align with EU standards 
  • Whether your product identifiers meet harmonized requirements 
  • Whether your data model will scale across markets 
  • Whether your compliance approach will be future-proof 

Building DPP infrastructure without understanding JTC 24 risks creating isolated systems that later require costly redesign. 

The Strategic Role of JTC 24 

Think of the structure like this: 

  • ESPR sets the legal obligation. 
  • Delegated Acts define product-specific requirements. 
  • JTC 24 develops the harmonized technical standards enabling implementation. 

Without JTC 24, DPP would risk becoming fragmented across Member States, creating digital silos and compliance confusion. 

With JTC 24, the EU aims to create a single, interoperable, standardized digital product transparency system. 

JTC 24 is the technical architect behind Europe’s Digital Product Passport framework. 

For companies investing in traceability, sustainability data systems, or DPP infrastructure, monitoring JTC 24 developments is essential because it defines the operational rules that your systems will ultimately need to follow. 

Why JTC 24 Matters for Digital Product Passports 

The Digital Product Passport (DPP) is one of the most ambitious digital compliance frameworks ever introduced in the EU. But ambition alone doesn’t create interoperability, scalability, or legal certainty. 

That’s why CEN-CENELEC JTC 24 plays such a strategic role. 

It does not create the law. 
It makes the law operational. 

Here’s why that distinction matters. 

It Translates Regulation into Technical Standards 

The Ecodesign for Sustainable Products Regulation (ESPR) mandates that products must carry a Digital Product Passport. 

But legislation speaks in legal terms: 

  • Products must be digitally identifiable 
  • Data must be accessible 
  • Information must be structured 
  • Interoperability must be ensured 

What ESPR does not define is: 

  • The exact data model 
  • The technical format of product identifiers 
  • The structure of machine-readable datasets 
  • The rules for digital exchange between systems 

That translation from legal obligation to technical specification is the job of JTC 24. 

Without this translation, companies would interpret requirements differently creating inconsistent and incompatible systems. 

It Defines Interoperability Requirements 

Digital Product Passports must work: 

  • Across industries 
  • Across supply chains 
  • Across EU Member States 
  • Across digital platforms 

If each company builds its own proprietary DPP format, the system collapses into fragmentation. 

JTC 24 establishes: 

  • Common data structures 
  • Shared terminology 
  • Interoperability principles 
  • Standardized identifiers 

This ensures that: 

A battery manufacturer in Germany, 
a textile producer in Italy, 
and an electronics supplier in France 

can operate within the same digital ecosystem. 

Interoperability is not optional. It is foundational to the DPP vision  and JTC 24 defines how it is achieved. 

It Ensures Harmonized Implementation Across the EU 

One of the EU’s core objectives is to prevent regulatory divergence between Member States. 

Without harmonized standards: 

  • Each country could interpret DPP differently 
  • National technical requirements could emerge 
  • Cross-border trade could become complicated 

JTC 24 supports harmonized European standards that, once referenced officially, provide a presumption of conformity. 

That means: 

If a company follows the harmonized standards developed under JTC 24, it is assumed to comply with ESPR requirements across the EU. 

This creates legal certainty. 

It Prevents Fragmented National Systems 

Europe has seen fragmentation before in digital and environmental regulation. 

Without centralized technical standardization: 

  • Different digital ID systems could arise 
  • Competing data formats could develop 
  • Companies would face multiple compliance architectures 

That would increase costs, complexity, and implementation risk. 

JTC 24 acts as the coordination mechanism preventing this fragmentation by: 

  • Aligning technical requirements at EU level 
  • Coordinating cross-sector input 
  • Ensuring consistency between industries 

In short, it protects the integrity of the Digital Product Passport framework. 

For manufacturers, suppliers, and OEMs, JTC 24 determines: 

  • Whether your digital architecture aligns with EU expectations 
  • Whether your product identifiers meet harmonized standards 
  • Whether your systems will scale across markets 
  • Whether your compliance approach will be future-proof 

Ignoring JTC 24 developments risks building infrastructure that later requires redesign. 

Monitoring JTC 24 developments, on the other hand, allows companies to align early reducing rework, integration costs, and regulatory uncertainty. 

Core Objectives of JTC 24 in the Digital Product Passport Framework 

To understand the strategic role of CEN-CENELEC JTC 24, it’s important to look at its core objectives within the Digital Product Passport (DPP) ecosystem. 

JTC 24 is not defining sustainability metrics themselves it is defining the digital infrastructure principles that ensure DPP functions consistently, securely, and at scale across the European Union. 

Below are the four foundational objectives shaping the framework. 

1️. Interoperability Across the EU 

One of the primary goals of JTC 24 is ensuring that Digital Product Passport data can move seamlessly across systems, companies, and Member States. 

Interoperability means: 

  • A product passport created in one country can be accessed and validated in another 
  • Different software systems (ERP, PLM, traceability platforms) can communicate using shared standards 
  • Regulators can verify data regardless of the originating system 

Without interoperability, DPP would fragment into isolated digital silos. 

JTC 24 works to prevent: 

  • Incompatible national systems 
  • Vendor-specific proprietary formats 
  • Closed digital ecosystems that restrict competition 

The objective is a unified, EU-wide digital transparency infrastructure not a patchwork of disconnected tools. 

2️. Standardized Data Models 

A Digital Product Passport is only as useful as its structure. 

JTC 24 focuses on defining: 

  • Common data fields 
  • Shared terminology 
  • Consistent formatting rules 
  • Machine-readable datasets 

This ensures that product information whether it concerns material composition, carbon footprint, repairability, or recyclability follows a standardized architecture. 

Why this matters: 

If every company defines product attributes differently, data cannot be compared, verified, or aggregated effectively. 

Standardized data models allow: 

  • Automated compliance checks 
  • Cross-industry benchmarking 
  • Reliable digital exchange 
  • Long-term scalability 

This is a shift from document-based compliance to structured digital information systems. 

3️. Unique Product Identification 

A central pillar of the DPP framework is linking physical products to their digital records. 

JTC 24 addresses this through standards for: 

  • Digital product identifiers 
  • Persistent, unique IDs 
  • Lifecycle traceability mechanisms 

These identifiers must: 

  • Remain stable over time 
  • Connect to updated product data 
  • Work across supply chain stages 

For example, a battery module or textile product must have a digital identity that: 

  • Links to its sustainability data 
  • Tracks changes over its lifecycle 
  • Remains accessible throughout repair, resale, or recycling 

Without standardized identification, traceability collapses. 

Unique product identification ensures continuity between the physical and digital worlds. 

4️. Secure & Controlled Data Access 

Digital transparency must be balanced with confidentiality. 

JTC 24 therefore incorporates principles for: 

  • Role-based visibility 
  • Data governance frameworks 
  • Secure authentication 
  • Controlled access levels 

Not all DPP data will be public. 

Some information may be: 

  • Accessible to regulators only 
  • Available to supply chain partners 
  • Restricted due to commercial sensitivity 

The framework must protect: 

  • Proprietary formulations 
  • Bill of materials structures 
  • Commercial relationships 
  • Trade secrets 

At the same time, it must ensure sufficient transparency for regulatory and sustainability purposes. 

Security and governance are not secondary considerations they are foundational to trust in the DPP ecosystem. 

Why These Objectives Matter Strategically 

Together, these four objectives define the operational backbone of Digital Product Passports: 

  • Interoperability prevents fragmentation. 
  • Standardized data models enable automation. 
  • Unique identifiers ensure traceability. 
  • Secure access safeguards commercial interests. 

Through these pillars, JTC 24 transforms the legal requirements of the Ecodesign for Sustainable Products Regulation into a functional, scalable digital system. 

For manufacturers and supply chain operators, aligning with these objectives early reduces the risk of building isolated or non-compliant infrastructure. 

Because in a digital regulatory framework, architecture determines compliance success. 

Key Components of the JTC 24 Digital Product Passport Architecture 

The Digital Product Passport (DPP) framework being developed under CEN-CENELEC JTC 24 is not just about adding sustainability data to products. It defines a structured digital architecture that connects physical goods to verified, accessible, and interoperable information systems. 

Below are the core architectural components shaping how DPP will function in practice. 

Digital Product Identifier 

At the foundation of the DPP architecture is the Digital Product Identifier (DPI). 

This identifier must be: 

  • Unique — no two products share the same identity 
  • Persistent — it remains valid throughout the product’s lifecycle 
  • Traceable — it links to evolving product data over time 

The identifier connects the physical product to its digital record. This ensures that when a product moves through the supply chain from manufacturer to distributor to recycler its digital passport remains accessible and verifiable. 

In practical terms, this identifier is embedded into the product via: 

  • QR codes 
  • RFID tags 
  • Other machine-readable data carriers 

The identifier is not just a label it is the anchor point for the entire DPP ecosystem. 

Data Carrier 

The data carrier is the access mechanism that allows stakeholders to retrieve the Digital Product Passport. 

It answers the question: 

How does someone access the product’s digital information? 

Most commonly, this will involve: 

  • A QR code printed or affixed to the product 
  • A scannable digital marker 
  • A connected interface embedded into the product system 

The data carrier does not store all product information directly. Instead, it acts as a secure gateway linking the user to the digital data environment. 

This design ensures: 

  • Real-time updates 
  • Version control 
  • Lifecycle traceability 
  • Reduced risk of outdated static information 

The data carrier bridges the physical and digital worlds. 

Data Storage & Hosting 

A critical architectural question in the DPP framework is where and how the data is stored. 

JTC 24 addresses two broad architectural models: 

Centralized Architecture 
  • Data stored in centralized EU-level systems 
  • Easier standardization 
  • Strong regulatory oversight 
Decentralized Architecture 
  • Data hosted by manufacturers or third-party providers 
  • Interconnected through standardized protocols 
  • Greater flexibility and scalability 

The likely approach combines interoperability with distributed hosting. This allows companies to retain control of their data while ensuring it can be accessed consistently across the EU. 

Key principles include: 

  • Machine-readable data formats 
  • API-based interoperability 
  • Harmonized registry references 
  • Long-term accessibility 

The goal is not to create one massive database but a connected ecosystem. 

Data Access Layers 

Not all DPP information is meant to be publicly visible. 

JTC 24’s framework distinguishes between different access levels: 

Public Data 
  • Sustainability characteristics 
  • Repairability information 
  • Environmental footprint data 
  • Consumer-facing transparency 

This data supports market transparency and informed purchasing decisions. 

Restricted Data 
  • Proprietary material compositions 
  • Supplier identities 
  • Detailed bill of materials 
  • Sensitive commercial information 

Access to restricted data may be limited to: 

  • Regulatory authorities 
  • Market surveillance bodies 
  • Specific supply chain actors 

This layered approach ensures a balance between: 

Transparency and confidentiality 
Regulatory oversight and commercial protection 

Role-based access controls and authentication protocols will define who sees what. 

Why These Components Matter Strategically 

Together, these architectural elements ensure that the Digital Product Passport is: 

  • Scalable across industries 
  • Interoperable across Member States 
  • Secure for commercial operators 
  • Reliable for regulators 

The architecture developed under JTC 24 transforms the legal obligations of the Ecodesign for Sustainable Products Regulation into a functional digital ecosystem. 

For manufacturers, this means DPP compliance is not simply about uploading data. It requires: 

  • A clear digital identity strategy 
  • Structured data governance 
  • System integration planning 
  • Access control frameworks 

In short, DPP is digital infrastructure and its architecture determines long-term compliance success. 

How JTC 24 Supports ESPR Compliance 

The Ecodesign for Sustainable Products Regulation (ESPR) introduces the legal requirement for Digital Product Passports (DPP) across prioritized product categories. 

But while ESPR defines the obligation, it does not provide the full technical blueprint for implementation. 

This is where CEN-CENELEC JTC 24 plays a decisive role. 

ESPR Mandates the Digital Product Passport 

Under ESPR: 

  • Certain product categories (such as batteries, textiles, electronics, and others to follow) must carry a Digital Product Passport. 
  • Manufacturers must provide structured product information. 
  • Data must be digitally accessible and interoperable. 
  • Information must remain available throughout the product lifecycle. 

These are legal requirements. 

However, ESPR intentionally avoids prescribing specific technical formats, software architectures, or digital identifiers. That level of detail belongs in harmonized standards not in legislation. 

JTC 24 Provides the Harmonized Standards 

JTC 24 develops the technical standards that translate ESPR’s legal language into operational rules. 

This includes defining: 

  • Common data structures 
  • Digital product identifier requirements 
  • Interoperability protocols 
  • Access control principles 
  • Data exchange specifications 

Once adopted and referenced, these harmonized standards provide manufacturers with a clear pathway to compliance. 

If a company builds its DPP system according to JTC 24 standards, it benefits from presumption of conformity  meaning it is assumed to meet the legal requirements of ESPR. 

Why Standards Are Necessary 

Without harmonized standards: 

  • Each manufacturer might structure DPP data differently. 
  • National authorities could interpret requirements inconsistently. 
  • Interoperability across Member States would fail. 
  • Market fragmentation would increase compliance costs. 

Standards ensure that: 

  • A DPP created in one country works across the entire EU. 
  • Regulators can verify information using consistent criteria. 
  • Supply chains operate within a shared digital ecosystem. 

In short, standards prevent regulatory chaos. 

Clarifying the Relationship 

The relationship between ESPR and JTC 24 can be summarized simply: 

Regulation = Obligation 
ESPR creates the legal duty to implement Digital Product Passports. 

JTC 24 Standards = Implementation Pathway 
JTC 24 defines how those Digital Product Passports must function technically. 

The regulation sets the destination. 
The standards define the road to get there. 

Strategic Implication for Manufacturers 

For companies preparing for DPP: 

  • Monitoring ESPR tells you what is required. 
  • Monitoring JTC 24 tells you how to build your system correctly. 

Ignoring either creates risk. 

Aligning early with JTC 24 standards ensures that your Digital Product Passport infrastructure is: 

  • Interoperable 
  • Scalable 
  • Legally defensible 
  • Future-proof 

Because in EU regulatory frameworks, compliance is not only about meeting the obligation  it is about building according to the recognized standards that operationalize it. 

TraceX DPP solutions help manufacturers and supply chain operators build interoperable, standards-aligned Digital Product Passport infrastructure without disrupting existing ERP and PLM systems. 

By automating data collection, structuring product-level datasets, and enabling secure access controls, TraceX reduces compliance risk while future-proofing EU market access. 

Common Misconceptions About JTC 24 

As discussion around the Digital Product Passport accelerates, several misunderstandings about CEN-CENELEC JTC 24 continue to surface. 

These misconceptions can delay preparation, distort implementation strategy, and create unnecessary compliance risk. 

Let’s clarify the most common ones. 

“JTC 24 is just about QR codes.” 

This is one of the most persistent myths. 

Yes, QR codes (or similar data carriers) will likely be one way users access a Digital Product Passport. But JTC 24’s scope goes far beyond defining a scannable label. 

In reality, JTC 24 defines the entire digital architecture behind the DPP ecosystem, including: 

  • Data models and structure 
  • Interoperability requirements 
  • Digital product identifiers 
  • Access control frameworks 
  • Data governance principles 

The QR code is simply the entry point. 

The real work lies in: 

  • Structuring machine-readable datasets 
  • Ensuring cross-system compatibility 
  • Linking product identities to lifecycle data 
  • Managing controlled data visibility 

Reducing JTC 24’s role to “QR code standards” overlooks the fundamental infrastructure transformation required for compliance. 

“Standards are optional.” 

Technically, European standards are voluntary. 

But in practice, harmonized standards play a critical legal role. 

When standards developed under JTC 24 are officially referenced under the Ecodesign for Sustainable Products Regulation (ESPR), they provide what is known as presumption of conformity. 

This means: 

If your Digital Product Passport system follows the harmonized standards, it is presumed to comply with the legal requirements of ESPR. 

You are not legally required to follow the standard word-for-word — but if you choose an alternative approach, you must independently prove that your system meets all regulatory requirements. 

In practical terms: 

Following harmonized standards significantly reduces legal uncertainty and compliance risk. 

Ignoring them increases the burden of proof. 

“We can wait until product-specific rules are finalized.” 

Many companies assume that full preparation can begin only after delegated acts define the exact product-level requirements. 

This is risky. 

While product-specific rules will define: 

  • Which data points are mandatory 
  • Which sustainability metrics apply 
  • Which performance indicators must be included 

The core digital infrastructure identifiers, data architecture, interoperability models, access layers takes time to build. 

Digital transformation projects involving: 

  • ERP integration 
  • PLM restructuring 
  • Supplier data alignment 
  • Governance redesign 

rarely happen overnight. 

Infrastructure lead times often exceed regulatory timelines. 

Waiting for full specificity may compress implementation windows and increase cost. 

Forward-looking companies are: 

  • Designing scalable data models 
  • Preparing digital ID strategies 
  • Aligning system architecture with JTC 24 principles 

so that when product-specific rules arrive, adaptation is incremental, not structural. 

Timeline and What Comes Next for JTC 24 

The work of CEN-CENELEC JTC 24 is not a one-time publication of technical rules. It is an evolving standardization process that will unfold in phases closely aligned with the implementation of the Ecodesign for Sustainable Products Regulation (ESPR). 

For companies preparing for Digital Product Passports (DPP), understanding this timeline is critical. Compliance readiness will depend not just on the regulation itself, but on how the supporting standards mature over time. 

Standards Development Phases 

Like all European standardization work, JTC 24 follows a structured development lifecycle. 

The typical phases include: 

Proposal & Scope Definition 

  • Identification of the need for a standard 
  • Definition of objectives and technical scope 
  • Agreement among Member State representatives 

Working Group Drafting 

  • Technical experts draft the standard text 
  • Data models, definitions, and architecture principles are refined 
  • Industry stakeholders contribute technical input 

Public Consultation (Enquiry Stage) 

  • Draft standards are published for public comment 
  • Industry associations, companies, and national bodies can submit feedback 
  • Technical adjustments are made based on consultation input 

Formal Adoption 

  • Finalized standards are voted on and adopted 
  • Once approved, they are published as European standards 

This structured process ensures transparency, industry participation, and technical robustness, but it also means development takes time. 

Consultation and Drafting Process 

One of the most important aspects of JTC 24’s work is stakeholder involvement. 

Participants in the drafting process typically include: 

  • Industry representatives 
  • Digital infrastructure experts 
  • National standardization bodies 
  • Regulatory observers 

This collaborative structure ensures that standards are technically feasible and aligned with real-world implementation needs. 

For manufacturers, this consultation phase presents both: 

  • A risk, if ignored 
  • An opportunity, if engaged early 

Companies that monitor drafts and participate through industry associations gain early visibility into emerging requirements. 

Alignment with Delegated Acts Under ESPR 

ESPR establishes the legal framework for DPP but relies on delegated acts to define product-specific requirements. 

These delegated acts will determine: 

  • Which product categories are prioritized 
  • What data fields are mandatory 
  • Which sustainability metrics apply 
  • Timelines for implementation 

JTC 24 standards must align with these delegated acts. 

This means the standardization process will evolve alongside regulatory clarification. 

In practice: 

  • Core architectural standards are being developed first (interoperability, identifiers, access principles). 
  • Product-specific technical standards will follow as delegated acts are published. 

This synchronized evolution ensures that DPP standards remain legally relevant and technically aligned. 

An Evolving Framework Companies Must Track 

The key strategic insight is this: 

JTC 24 is not producing a static rulebook. 
It is building a living technical framework that will evolve as new product categories and regulatory details emerge. 

For companies, this means: 

  • Monitoring standard drafts 
  • Aligning digital infrastructure early 
  • Avoiding hard-coded proprietary systems 
  • Designing scalable and adaptable data models 

Waiting for complete finalization may appear cautious but infrastructure lead times often exceed regulatory timelines. 

Forward-looking organizations treat JTC 24 developments as strategic signals shaping long-term digital architecture. 

Strategic Takeaway: JTC 24 Is the Technical Backbone of DPP 

At its core, CEN-CENELEC JTC 24 is not just another standards body operating in the background of EU regulation. It is shaping the digital architecture that will determine how the Digital Product Passport functions in practice. CEN-CENELEC JTC 24 is the technical backbone of the Digital Product Passport under the Ecodesign for Sustainable Products Regulation. While ESPR creates the legal obligation, JTC 24 defines how DPP systems must function in practice   from data structure and interoperability to digital identifiers and access control. Companies that align early with JTC 24 standards reduce compliance risk, avoid costly redesigns, and build future-proof digital infrastructure for EU market access. 

Interoperability is the foundation of Digital Product Passports. 
Read: “DPP Interoperability: What It Really Requires” 

Are you building DPP the right way as a manufacturer? 
Read: “Digital Product Passports for Manufacturers: A Practical Guide” 

Do you know exactly what data your Digital Product Passport must contain?

Read: “DPP Data Requirements Explained” 

Frequently Asked Questions (FAQ’s)


What is JTC 24? 

CEN-CENELEC JTC 24 develops the technical standards that support the Digital Product Passport (DPP) under the Ecodesign for Sustainable Products Regulation. 
ESPR creates the obligation JTC 24 defines how DPP must technically function. 

Is following JTC 24 standards mandatory?

Standards are technically voluntary. 
However, harmonized standards provide presumption of conformity, making compliance significantly easier and lower risk.

What does JTC 24 standardize for DPP?

It defines: 

  • Data structure and formats 
  • Digital product identifiers 
  • Interoperability requirements 
  • Access control and governance rules 

In short, the digital architecture behind DPP.

Why does interoperability matter?

DPP must work across industries and EU Member States. 
JTC 24 ensures systems can communicate, preventing fragmented national or proprietary solutions. 

Why should companies monitor JTC 24 now? 

Digital infrastructure takes time to build. 
Aligning early with JTC 24 standards reduces redesign costs, compliance risk, and future implementation pressure. 

Start using TraceX
Transparency, Trust, & Success for your Climate Journey.
Get the demo

Get your free trial

Request for a Demo Session

Download your How JTC 24 Defines the Digital Product Passport Framework  here

Download your How JTC 24 Defines the Digital Product Passport Framework  here

Download your How JTC 24 Defines the Digital Product Passport Framework  here

[hubspot type=form portal=8343454 id=304874ea-d4e0-4653-9825-707360746edb]
[hubspot type=form portal=8343454 id=b8321ac0-687a-4075-8035-ce57dd47662a]
food traceability, food supply chain, blockchain traceability, agriculture traceability software

Is Your Supply Chain Audit-Ready for 2026?

Get the free TraceX Playbook — 10 traceability failures to fix before your next audit, a 10-point maturity scorecard.

Grab your Free Trial now

Ensure your supply chain is EUDR-ready with TraceX.

Don’t miss out on your chance to grab access to our early bird offer!

food traceability, food supply chain

Are you EUDR Due-Diligence Ready?

Your essential compliance guide

food traceability, food supply chain

Please leave your details with us and we will connect with you for relevant positions.

[hubspot type=form portal=8343454 id=e6eb5c02-8b9e-4194-85cc-7fe3f41fe0f4]
food traceability, food supply chain

Please fill the form for all Media Enquiries, we will contact you shortly.

[hubspot type=form portal=8343454 id=a77c8d9d-0f99-4aba-9ea6-3b5c5d2f53dd]
food traceability, food supply chain

Kindly fill the form and our Partnership team will get in touch with you!

[hubspot type=form portal=8343454 id=b8cad09c-2e22-404d-acd4-659b965205ec]