The EU Digital Product Passport Is Not the Destination. It Is an Output.
By Egoyibo Okoro · August 2026
On 20 July 2026 the European Union's Digital Product Passport Registry became operational. Most of the coverage filed it under sustainability compliance: one more disclosure regime, one more deadline table. I think that reading misses what actually changed.
The Digital Product Passport is not really asking brands to disclose more. It is forcing a harder question underneath the disclosure: where does trustworthy product knowledge come from in the first place? At Akwa, that question is the one we have been building around from the beginning, so this piece is both a reading of the regulation and an explanation of our approach.
The registry is an index, not the passport
The design of the registry itself makes the EU's position clear. It does not store product data. It stores a unique product identifier, metadata, access rights and the address where a passport lives. The passport's actual content stays decentralised, held by the brand or its service providers. The registry is a discovery layer; the knowledge remains yours to maintain.
Two things follow from that architecture. First, the deadline that passed in July was the Commission's infrastructure milestone, not a date by which brands had to register anything; the binding obligations arrive per sector, starting with batteries in February 2027, with textiles following through later delegated acts. Second, and more important: the EU has quietly told every brand that the passport is not a document someone will host for you. It is a view of product knowledge you are assumed to already have, structured, governed and reachable.
Many brands do not have that. That is the real story.
Fashion has a data problem, not a passport problem
Walk into almost any fashion business and ask where a garment's knowledge lives. The answer is: everywhere. Illustrator files, PDFs, emails, spreadsheets, chat threads, supplier documents, tech packs, factory comments. Every stage of the lifecycle recreates information that already existed somewhere else, slightly differently, and the copies drift. The brief says invisible zip, the drawing shows buttons, and the person about to cut fabric has to guess.
A passport generated from that landscape inherits its fragmentation. If your product knowledge contradicts itself internally, a legally mandated public view of it does not fix the contradiction. It publishes it.
That is why treating the DPP as a compliance project is backwards. The passport is downstream. The upstream problem is that most product knowledge was never structured as knowledge at all.
Treat the garment as knowledge, and the passport becomes an output
Akwa's answer is the Semantic Garment Graph: one governed record per garment, carrying its identity, colour, closure, measurements, trims, versions and production history, with every document generated from that record as a view. The tailor brief and the tech pack cannot disagree about the closure, because there is only one closure fact for either of them to name. That is live in production today; it is how every Akwa design already works.
Seen from that architecture, a Digital Product Passport is not a new document to assemble. It is one more projection of the same governed record, alongside the briefs, the packs and the storefront. The flow is not design, then documents, then a separately compiled passport. It is: the graph holds the garment; everything else, passport included, is a way of looking at it.
We have not shipped DPP generation, and the textile delegated acts that will define its exact fields do not exist yet. But this is the shape the graph is built to serve: when the passport's field list arrives, it lands as an export of facts the record already carries, not as a second system of truth to reconcile against the first.
Governance is the part fashion underestimates
The registry's brand-facing guidance leans on words fashion tooling rarely takes seriously: roles, responsibilities, access rights, retention, auditability. This is where our approach is opinionated, because I came to fashion from law and governance, and Akwa is built on the belief that honesty is a data type.
In the graph, every fact carries its provenance and a state: observed from the design's own image, confirmed by a person, or inferred by a model and awaiting review. Documents disclose those states instead of flattening them into false confidence. A colour read from the render says so, and asks your tailor to confirm before fabric purchase. A derived measurement says it was derived. Model output never silently outranks the design image or your own words. None of that was built for the DPP. But a passport regime that requires trustworthy, auditable product claims is exactly the environment where provenance-first records stop looking like philosophy and start looking like infrastructure.
Explainability, for factories rather than regulators
Most conversations about explainable AI are regulatory. Ours is practical: factories do not manufacture prompts, they manufacture decisions, and someone eventually asks why. Why this fabric, why this ease allowance, why confirm this seam at sampling. Akwa's documents already answer in that register, because the disclosures come from the graph's states: this detail was read from the image, this one was confirmed, this one needs a decision at first fitting. A passport built on records like that can explain a garment rather than merely describe it, which is the difference between transparency as a legal posture and transparency a customer or a maker can actually use.
The person and the garment stay separate
One more architectural choice matters here. The Digital Product Passport is about products, not people, and we think the boundary is worth defending. In Akwa's approach, personal measurements belong to the person and stay under their control; garment knowledge lives in the graph; the two meet only when a recommendation or a fit needs them to, and part ways after. Product records should never become a place where personal body data quietly accumulates. As passports make product records more public, that separation stops being a privacy preference and becomes basic hygiene.
What this means in practice
Akwa's own house, Egoyibo Okoro, is the working proof: its collection is designed on the platform, its technical documentation is generated from the graph, and its storefront reads the same governed record the documents are built from. The house is also designing a Garment Passport for its numbered pieces, the physical companion to exactly the digital record this article describes.
For everyone else, the takeaway is simpler. The passport deadlines that matter for textiles are still ahead, which means the window to fix the upstream problem is open now. Brands that spend it building structured, governed product knowledge will find the passport is nearly free. Brands that spend it preparing a compliance document will do the same work again for every regime that follows.
Frequently asked questions
Is the EU DPP Registry a database of product information? No. It is an index: it stores identifiers, metadata, access rights and the address of each passport. The passport's content stays with the brand or its service providers.
Do fashion brands have to comply already? No. The registry going live in July 2026 was an infrastructure milestone for the Commission. Batteries are the first mandatory category in February 2027; textile requirements arrive through later delegated acts.
Does Akwa generate Digital Product Passports today? Not yet, and the textile field definitions do not exist yet either. What Akwa runs today is the layer a passport depends on: a governed record per garment, with provenance and epistemic states on every fact, projecting into tailor briefs, tech packs and storefront data. The passport is designed to be one more projection when its requirements land.
What should a small brand do about the DPP now? Do not buy a compliance document. Fix where your product truth lives: one record per garment, structured, with sources. Whether you do that with Akwa or otherwise, it is the work the passport will eventually assume you have done.
Design something only you would make, and let one governed record carry it from idea to passport.