The DPP Is a Mirror, Not a Label
There is a particular moment organisations encounter when they move from reading about the Digital Product Passport to actually examining what it would require of them. The regulation, until that point, has been an abstraction — a compliance horizon, a project, a deadline. Then someone asks a specific question: what data do we actually have, for a specific product, that would go into a passport today?
The answer to that question is the mirror. And for most organisations, the reflection is instructive.
What the DPP requires at its first phase is not, in isolation, unreasonable. Material composition, traceable to source. Key manufacturing processes, linked to specific products. Core environmental indicators, substantiated rather than estimated. Chemical compliance references. Basic traceability through the supply chain. None of those data points are exotic. Most organisations would say, if asked, that they have most of this information somewhere.
That is where the mirror becomes uncomfortable. Somewhere in a supplier portal that three people know how to access. Somewhere in a spreadsheet maintained by someone who left eighteen months ago. Somewhere in a certification document that covers a material category, not a specific product. Somewhere that is not, in the language the DPP requires, verified, structured, product-specific, and retrievable on demand.
The DPP does not create a new data requirement. It applies a standard of evidence to data that organisations believed they already had.
What that standard reveals, in most cases, is not an absence of information but an absence of governance. The data exists, in fragments, across systems and functions and supplier relationships that were never designed to work together. Nobody decided what the authoritative source for material composition data was. Nobody owns the process of keeping it current when suppliers change inputs mid-season. Nobody is accountable when the figure in the sustainability report and the figure in the sourcing system don't match.
This is why readiness for the DPP is as much a governance question as a technology question — and why organisations that approach it primarily as a technology question tend to discover, partway through implementation, that the technology cannot do what they hoped. A system can store and retrieve data. It cannot decide what the data should mean, who is responsible for its accuracy, or what happens when two functions disagree about which version is correct. Those are human decisions. They require organisational clarity that most fashion and textiles companies have not established around product data.
Genuine readiness looks less like a software implementation and more like a set of organisational decisions that have been made and held. The technology question — which system, which platform, which integration — is actually the easier half.
The harder half is the clarity that has to precede the technology: who owns product data end to end, with genuine mandate rather than nominal accountability; how quality is defined and maintained when supplier inputs change mid-season; what happens when two functions are working from different versions of the same information; and how data governance connects to the commercial, sourcing, and design decisions that determine what data will ever be collectible in the first place.
Those decisions cannot be delegated to an implementation team. They belong to the organisation's leadership, and they have to be made before the technology has anything solid to build on.
There is something else the mirror shows, for organisations willing to look at it that way. The data infrastructure genuine DPP readiness requires is not narrowly useful. An organisation that knows its products — their composition, their provenance, their environmental footprint — with the precision a passport demands has built something that reaches well beyond compliance. That knowledge changes how sourcing decisions get made, how sustainability claims get defended, how supply chain disruption gets anticipated. It is also the operational foundation that circular business models — rental, resale, repair — require before they can scale.
The organisations building that capability now are not simply preparing for a regulation. They are accumulating something that will take compliance-led competitors years to replicate — not because the technology is proprietary, but because the governance, the culture, and the organisational habits that make data trustworthy cannot be installed. They have to be developed, over time, through decisions made and sustained across functions and supplier relationships and leadership priorities.
That is the competitive advantage concealed inside a regulation that most organisations are still treating as a cost.
The DPP is a mirror. What it reflects is not a technology gap. It is an organisational one — in governance, in accountability, in the willingness to treat product data as something worth owning rather than assembling on demand. The organisations that recognise that distinction earliest are the ones that will find, when the deadline arrives, that they have built something worth far more than compliance.
Michael Shea is a digital excellence advisor, non-executive director, and leadership coach working with organisations navigating the human and technical dimensions of digital transformation. He hosts The Aeolian Discourse and writes at The Aeolian.
Photo by Serge Le Strat on Unsplash