Many of our conversations about Digital Product Passports (DPPs) begin the same way. A sustainability or compliance lead reads the regulation, attends a few webinars, and comes away with an overview that is mostly accurate, yet misinformed on critical details.
These gaps rarely concern broad principles. Instead, they involve scope, timelines, data governance, and access controls.
TalkPod brings a distinct vantage point. We build conversational product knowledge interfaces on top of passport data.
To understand the underlying infrastructure, we enrolled in the EU’s Digital Product Passport registry and attempted to register demo passports within its test environment. The insights below reflect both the formal regulations and our practical experience in the registry’s pre-live environment.
Compliance applies to the product itself, regardless of company size
The Ecodesign for Sustainable Products Regulation (ESPR) governs products placed on the EU market. When a delegated act brings a product category into scope, the passport requirement attaches to the product itself. Consequently, the business placing the product on the market must comply, regardless of its headcount or revenue.
Confusion often stems from two sources. First, the Corporate Sustainability Reporting Directive (CSRD) applies explicit size thresholds that have received significant attention.
Second, ESPR includes its own size-based exemptions, but these apply elsewhere. Micro and small enterprises are exempt from the ban on destroying unsold apparel and footwear, while medium-sized enterprises have until 2030 to comply.
Neither exemption applies to digital product passports. A ten-person brand selling an in-scope product into the EU must provide a passport just like a global enterprise.
Furthermore, this is not exclusively a manufacturer’s obligation. Retailers and distributors share explicit duties under ESPR to ensure customers can access the passport at the point of sale, including online.
Why waiting for statutory enforcement dates creates a compliance bottleneck
ESPR entered into force in July 2024. The European Commission’s first working plan, published in April 2025, prioritised textiles among the initial product groups, with the delegated act expected in 2027.
Once adopted, delegated acts typically grant an 18-month transition window before enforcement begins. This places mandatory textile passports around 2028 or 2029.
While that timeline appears generous, substantial groundwork is required: scoping products, identifying data sources, establishing ownership, gathering supplier data, selecting hosting providers, integrating systems, and conducting pilot rollouts.
Most of this internal preparation can proceed independently of the final delegated act’s specific wording.
The EU Batteries Regulation serves as a useful precedent. As a separate framework with firm statutory deadlines, it requires electric vehicle batteries, light means of transport (LMT) batteries, and industrial batteries over 2 kWh placed on the EU market to carry a passport starting 18 February 2027.
Companies in this sector have already transitioned from planning to execution.
Current status and real-world limitations of the EU central registry
The EU central registry launched on schedule in July 2026. It stores unique identifiers and registration metadata that direct queries to where each passport is hosted.
It does not store the passport content itself, which remains hosted by the brand or its designated service provider.
Our hands-on testing illustrates the registry’s current state. Operator onboarding went smoothly, and we completed verification in the acceptance environment in September 2026.
However, when we attempted to register demo battery passports hosted on talkpod.ai, the system rejected them because semantic validation was not yet operational.
The Commission’s helpdesk confirmed that the registry currently supports operator onboarding only. API access and semantic validation are expected in Q4 2026, while the framework for third-party passport service providers (PSPs) will be finalised via a delegated act around Q2 2027.
In short, while the central infrastructure is advancing on schedule, any vendor claiming fully automated, end-to-end production registration today should be asked to demonstrate it.
How to initiate passport setup with incomplete data sets
A product passport is a dynamic record, not a static publication. A product can be assigned its identifier and data carrier early in the lifecycle, with the underlying data populated and refined as sourcing and manufacturing finalize.
Deferring setup until every data point is finalized compresses execution into an unnecessarily tight timeframe.
A more pressing early decision is data granularity. Each delegated act will specify whether passports are required at the model, batch, or individual item level, a decision that fundamentally dictates downstream data architecture.
A model-level passport for a standard garment presents a vastly different operational scope than an item-level passport for an industrial battery.
In practice, most necessary information already exists across PIM systems, compliance records, supplier certifications, and test reports.
The primary challenge is that data remains fragmented across internal teams without unified ownership. Defining data ownership internally should precede vendor or software selection.
Strategic lifecycle decisions beyond hardware and data carriers
QR codes, NFC tags, RFID, and blockchain are frequently debated as competing passport technologies. They are not. ESPR requires a unique product identifier and a physical data carrier linking the product to its digital record.
Delegated acts will specify approved carriers and placement rules on the product, packaging, or accompanying documentation. QR codes are the logical standard for consumer goods due to universal smartphone compatibility.
NFC and RFID excel where existing logistics workflows demand them. While blockchain can assist with supply chain traceability or authentication, ESPR does not mandate it.
The core challenges lie in lifecycle management. Passports must remain accessible for specified retention periods, which may outlast product lines, supplier contracts, or corporate entities.
Consequently, ESPR requires backup copies to be maintained by independent passport service providers. Determining where primary passports are hosted, selecting backup providers, and ensuring long-term data availability require careful, deliberate planning.
Managing role-based access and protecting proprietary product data
A frequent concern among brands is that passports will expose proprietary supplier lists to competitors. ESPR does not work this way.
Access to passport data is role-based and segmented. Consumers, repairers, recyclers, and market surveillance authorities each receive tailored views.
Furthermore, ESPR explicitly safeguards trade secrets and commercially sensitive information. Specific public disclosures will be defined on a category-by-category basis.
A practical immediate step is categorising existing product data by target audience. Identifying which data is intended for consumers, recyclers, or regulatory authorities simplifies compliance mapping when final rules are published.
Transforming compliance data into commercial value
ESPR mandates that passports be accessible, but not that they create commercial value. That distinction is where standard compliance efforts end.
However, the same structured data compiled for regulators can answer common customer inquiries regarding care instructions, component replacement, and material composition. Thoughtfully implemented, compliance data can reduce product returns and customer support overhead.
TalkPod helps brands bridge this gap by transforming structured passport data into interactive customer interfaces. If you are assessing your compliance readiness, our DPP review offers a practical starting point.