The European Union’s Digital Product Passport is moving from a sustainability concept towards practical data infrastructure as regulators define how records are registered and technology companies begin showing how individual products could be verified. French provider SealTrust has published an item-level demonstration intended to show that a passport can be checked independently rather than functioning simply as a QR code pointing to a company-controlled web page.

The company’s approach combines a product identifier, machine-readable data, signed credentials, and cryptographic proofs designed to establish that the digital record presented for an item corresponds with information anchored in its system. SealTrust uses blockchain technology within that architecture, although the European regulatory framework does not mandate blockchain and instead focuses on identifiers, interoperability, accessibility, and data structure.

That difference will become important as manufacturers begin choosing software and integration suppliers. A compliant passport may be built using conventional databases, cloud services, distributed ledgers, signed credentials, or combinations of those technologies, provided the resulting system can meet the rules applicable to the relevant product category.

Consequently, the procurement question is shifting from whether a supplier can generate an attractive digital label towards whether its data can survive across companies and systems for the lifetime of a product. The passport has to remain useful to regulators, repairers, recyclers, customers, and other authorised parties even when the manufacturer changes software provider or the item moves through several owners.

The registry turns policy into systems work

The Digital Product Passport sits within the Ecodesign for Sustainable Products Regulation, which entered into force in 2024 and establishes a framework under which product-specific requirements are introduced progressively. Rather than imposing one passport deadline across the entire economy, delegated measures and related legislation determine which information must be provided for individual product groups and when those rules apply.

The European Commission has now adopted detailed arrangements for the central DPP registry through Implementing Regulation 2026/1778. The system is designed to verify economic operators, register passports, check aspects of submitted data, and transfer responsibility when another operator assumes the relevant obligations.

Registration can take place through a secure interface or an API, which immediately turns compliance into an enterprise-integration problem for businesses handling large catalogues. Manufacturers producing thousands or millions of items cannot maintain passports manually, so product lifecycle management, ERP, supplier, compliance, and logistics systems will need to generate and exchange structured records reliably.

The registry can perform checks around the semantic structure and granularity of data, pushing quality requirements further upstream. If product identifiers are duplicated, supplier information is inconsistent, or data required for a particular passport is missing, the defect becomes more than an internal master-data problem because it can prevent compliance information from functioning as intended.

Verification cannot repair bad source data

SealTrust’s demonstration focuses on the authenticity and integrity of records, an area likely to become more important once passports are consumed automatically by software. Procurement platforms could check product information, repair applications could retrieve component details, marketplaces could validate identity records, and market-surveillance authorities could compare declarations with registry data.

Machine-readable access also opens the door to AI agents and automated compliance tools querying product records without human users opening a web page. SealTrust has already demonstrated interfaces intended to make public passport information accessible to compatible software agents, suggesting that DPP data could become part of ordinary enterprise workflows rather than remaining a consumer-facing label.

However, cryptographic verification solves only part of the trust problem because proving that a record has not changed does not prove the original information was correct. Product data can originate with component suppliers, laboratories, certification bodies, factories, logistics companies, importers, and repair organisations, leaving manufacturers responsible for deciding which source should be trusted for each field.

That work can be difficult in sectors where supplier data is incomplete or historically stored in documents rather than structured systems. Companies may therefore discover that the expensive part of Digital Product Passport compliance is not producing the passport itself but cleaning identifiers, tracing materials, integrating systems, and establishing governance around who can change a record.

Vendor portability will be another practical test. The regulation is intended to avoid lock-in, yet manufacturers will still need to examine whether a supplier’s data model, APIs, identifiers, and export mechanisms allow a passport estate to move elsewhere without breaking the links attached to products already in circulation.

SealTrust’s demonstration provides one technical answer to those requirements rather than a regulatory template for the market. As the EU registry and product-specific rules take shape, the more consequential shift is that product identity, lifecycle data, and verification are becoming shared digital infrastructure across supply chains, leaving manufacturers with an implementation problem extending far beyond the QR code printed on the packaging.