A structured record of what a product is and what is known about it, reachable from the product itself through a code on the label. The mechanism is in force. The textile content rules are not, and the gap between those two sentences is where most of the confusion in this subject lives.
A textile Digital Product Passport is a structured record of what a garment is and what is known about it. It is reachable from the garment itself through a code on the label. The mechanism is in force. The textile content rules are not.
Article 9 of the Ecodesign for Sustainable Products Regulation establishes the passport. No delegated act for textiles has been adopted.
The registry implementing regulation was adopted on 16 July 2026 and entered into force on 6 August 2026. It sets no compliance deadline of its own.
The registry portal has been operational since 20 July 2026.
Requirements apply no earlier than 18 months after a delegated act enters into force. That is a floor, not a schedule.
The one delegated act adopted under the framework so far concerns destruction of unsold goods, not product data.
The Ecodesign for Sustainable Products Regulation creates the passport, the unique product identifier and the carrier, and it is in force. What a pair of jeans has to carry needs a textile delegated act, and none has been adopted.
A Digital Product Passport is a record attached to a product, holding structured information about that product, reachable by anyone who scans the code on it. For a garment that means a data carrier on a swing tag or a sewn-in label, a unique identifier inside it and a service that answers when the identifier is presented.
The Ecodesign for Sustainable Products Regulation creates all three, and it is in force. Article 9 establishes the passport. The provisions defining the unique product identifier, requiring the carrier to stay reachable across the product's lifetime and placing the passport within a registry sit further into the same instrument, and this page names them by what they do rather than by number.
What the framework does not do is say what a pair of jeans has to carry. That comes from a delegated act for textiles, and no such act has been adopted.
Why one article number appears here and the others do not
An article citation is the first thing a lawyer checks, so a wrong number costs more than a missing one. An earlier version of this page put the identifier and the registry at articles that a second reading of the same regulation did not support, and a separate reading attributed the passport itself to Article 8. Article 9 for the passport is settled and is stated. Everything else is being confirmed against a consolidated rendering of the text, and the numbers go back on the page when they can go on it correctly.
What it connects to
The passport is the last link in a short chain, and each link is a different problem.
An identifier. In practice a GTIN, the number behind a barcode. It identifies the product, and it goes onto goods that then stay in circulation for years.
An address. A URL grammar that carries the identifier, so a code resolves to something specific rather than to a home page.
A carrier. The printed code itself, where error correction level, module size and quiet zone decide whether the thing still scans in five years on a garment that has been washed forty times.
A resolver. The service that answers. A well formed request for an identifier nobody holds should return a not-found, and a request that is malformed should say so instead. Conflating those two is the usual way a resolver stops being trustworthy.
What each layer does at the moment somebody scans, what a conformant resolver is required to do and the five things its standard does not specify at all are set out on what happens when you scan.
The four layers of identity. The four separable things behind a scan, drawn small here as an orientation and drawn in full on the mechanism page. The resolver box carries the word redirect because a redirect is what the resolver standard specifies, and it is a weaker thing than the word resolver suggests. No scheme is drawn as the incumbent, because the framework names none. Drawn from the framework's identifier and carrier provisions and from the conformant resolver standard as read at the reference site, sources as at 28 August 2026.
The reason the chain matters is permanence. A code printed into a garment in 2026 is in somebody's wardrobe in 2032, and none of the decisions above can be revised afterwards.
One thing about the identifier that is not settled
This page used to say, in absolute terms, that an identifier cannot be reassigned once it is printed onto goods in circulation. That statement was never confirmed and it has been withdrawn. Reuse is governed by the numbering scheme's general specifications, which have historically permitted it after a defined period for some categories of identifier while prohibiting it outright for others. We have not read the current release of those specifications, so we don't assert the absolute form.
Permanence of identity is the assumption underneath a good deal of planning in this subject, some of it ours. Nobody has checked it, so today it is an open check rather than a settled fact, and it is recorded as one.
What is settled, and what is not
Three separate things get collapsed into one sentence constantly.
The three layers, and where each one currently stands.
Layer
What it covers
Where it stands
The framework
That passports exist, what an identifier is, what a carrier has to do.
In force
The infrastructure
The registry, the portal that operates it and the standards work that supports it.
In force
The textile rules
Which attributes a textile passport carries, at what granularity, from when.
Indicative only
Note the order of that table: the plumbing was legislated first.
The registry carries no compliance deadline of its own
The implementing regulation that establishes the registry sets up how registration works and who answers for what. It does not create a duty for a textile business to register anything by any point, and a live registry with almost no mandatory users is not a countdown.
The rest is dates, and they are properties of the instrument rather than of an obligation. It was adopted on 16 July 2026 and entered into force on 6 August 2026. The registry portal it establishes has been operational since 20 July 2026.
One delegated act has been adopted under the framework so far, and it concerns the destruction of unsold goods rather than product data. It is regularly cited as evidence that product rules have begun to arrive. It is not that.
When any of this applies
Not from this page. Which parts are in force, which are adopted and which have only been signalled is tracked row by row, with sources and verification dates, on the status page. It is the only page here that states dates for the textile rules.
Adoption is not application. The Commission's working plan names textiles as a first priority with an indicative adoption year; an adopted act then has to enter into force, and requirements apply no earlier than 18 months after that, except in duly justified cases. An indication plus a floor gives no date your products must comply by, so this page publishes the working, not a result that would be read as a deadline.
What actually goes in one
Since the textile act does not exist, every published attribute set is an anticipation of it, including ours. The attributes we track were chosen from the framework, from the instruments that already apply to textiles and from what a passport has to hold to be useful to somebody other than the brand.
The evidence behind that set is unevenly distributed. Some fields are already in the business and need tidying. Some belong to a mill or a factory and cannot be produced by the brand alone. A few have no settled method behind them anywhere, and for those the correct behaviour today is to wait and record why.
The field guide sets the whole set out with that difficulty on the face of the table.
What a passport is not
It is not proof of compliance. A passport is a record of what is known about a product, and a complete-looking passport can sit on a product that meets nothing.
It is not a marketing surface. The audience includes a consumer, a recycler, a customs officer and a market surveillance authority. Three of those four have no interest at all in the brand story.
It is not a replacement for the label. Whether a passport eventually displaces any part of the sewn-in label is open, and nobody should be planning around an answer yet.
And it is not an assertion that everything in it is true. The honest version distinguishes what resolved, what could not be established and what does not apply, which is the subject of the evidence page.
ActivateDigital builds a governed textile record from the catalogue data, documents and evidence you already hold, and keeps the basis for every answer.
Three of the sources below are published by the organisation that runs a numbering scheme, and a publication guard governs whether such a specification may be cited here. They appear because they are registered with a read depth, which is the accepted alternative to that guard: the page states how far each was read rather than leaning on the fact of citation.
EU lawArt. 9, plus the identifier, carrier and registry provisionsCELEX 02024R1781-20240628In forceRelevant provisions reviewed
Creates the passport, the unique product identifier and the data carrier, and says nothing about textile attributes. Article 9 is the provision establishing the passport and is the one article number this page states. The provisions on the identifier, on carrier reachability and on the registry are named here by what they do and not by number, because two independent reads of this instrument disagreed about where they sit. The numbering is being confirmed against a consolidated rendering of the text and the page will carry numbers when it can carry the right ones.
Official guidanceIndicativeRelevant provisions reviewed
Names textiles as a first priority and gives an indicative adoption year. An indication in a work plan rather than an adopted instrument. The year is stated on the status page, which is the only page here that carries one.
Delegated or implementing actCELEX 32026R1778In forceRelevant provisions reviewed
Read at article level for the registration and responsibility provisions and, as an absence, for the finding this page leads with: the instrument carries no compliance deadline of its own. Its adoption and entry into force dates are properties of the instrument and are stated as such. Its internal article numbering has still to be checked against the Official Journal rendering, so no article number from it appears here.
GS1 GTIN management standard
StandardRelevant provisions reviewed
Read for the allocation rules. The reassignment question, whether an identifier may ever be reused once it is printed onto goods in circulation, is governed by the general specifications rather than by this document. Those specifications have not been read at their current release, which is why this page softened an absolute statement it used to make.
The address grammar that carries an identifier. Named so that the address layer in the chain below can be told apart from the resolver layer. The document itself has not been read, so nothing here describes a requirement inside it.
Read at the reference site for the behaviours a conformant resolver must exhibit. Used here for one thing only: the difference between a well formed request for an identifier nobody holds and a request that is malformed. What a resolver does not specify is taken apart on the mechanism page rather than here.
