You have done the safety compliance work. How much of it counts towards a passport?
Some of it, and less than you would hope. What you assembled about your company carries across almost completely. What you assembled about your products carries across at the identity layer and then stops, and three of the attributes that look like they transfer are the ones that fail quietly. This page says which is which, because nobody else does.
Navigate this page
The short answer
The two obligations are separate instruments with different legal bases, and neither one discharges the other.
The General Product Safety Regulation has applied since December 2024. It is in force, it is enforced by platforms today, and it asks about identity and safety.
The textile passport is not in force. It sits under the ecodesign framework, which is a framework, and no product act has been adopted for textiles. Nothing about it binds a clothing business today.
What carries across is the record about your company, and one attribute about your product. Almost nothing else does.
| What you assembled | Does it carry to a passport? |
|---|---|
| Manufacturer identity, with a postal address and an electronic contact | Yes, essentially whole |
| The person inside the Union who answers for the product | Yes |
| The product identifier you already had | Yes, and it is the only universal join key |
| Warnings and safety information, per language | Partly. Different requirement, same underlying content |
| Composition, weight and brand as you hold them in a catalogue | No. See the section on why below |
| Recycled content, care instructions, environmental figures | No, because the safety work never asked for them |
| Product category as any system holds it | No. Nothing maps here at all |
Why the party record is the part that carries
Product safety law requires an offer made at a distance to identify the manufacturer with a postal and an electronic contact, and to name the person inside the Union who answers for the product where the manufacturer is outside it.
That is an accountable legal entity with an address, and it is the same object the passport framework works with when it defines an operator. It is also the object every marketplace gate tests. So the work you did to satisfy one of those is genuinely reusable across all three, and it is the single most re-entered dataset in this whole chain.
What that record has to contain to be worth holding, and why it belongs somewhere other than a column on a product, is set out on the registrations that gate a listing.
Why the product attributes do not carry
Three attributes appear in both a commerce catalogue and a compliance format under the same name, and they describe different objects. They fail in both directions, which is what makes them expensive: a value good enough for one is not a compliance value, and the compliance value pushed the other way arrives as a string the catalogue cannot use.
Material. A commerce feed wants a primary material as a short string. Textile labelling wants a percentage per fibre, drawn from a closed statutory list of names, with separate treatment for non-textile parts. Same word, incompatible granularity.
Weight. A commerce system means shipping weight. Producer responsibility reporting means mass placed on the market. Four or more systems hold a field called weight and none of them describes the same thing.
Brand. A catalogue holds a marketing string. The regulatory side wants the accountable party. Mapping one into the other produces a record that passes validation and names nobody.
Those three, and three more pairs underneath them, are taken apart properly on where product data stops meaning the same thing. The point for this page is narrower: if you are counting your safety compliance work as progress towards a passport, do not count those three.
There is a fourth thing that does not carry at all, and it is worse than the three. The category a product belongs to is expressed in several mutually non-mappable hierarchies: a global classification standard, a shopping taxonomy, a marketplace browse tree, and a different national schedule for every producer responsibility scheme. There is no crosswalk between them and maintaining one is permanent work rather than a mapping exercise. Why the same attribute name describes different objects across systems is worked through on where product data stops meaning the same thing.
What the safety work never asked you for
This is the honest measure of how much is left to do.
Recycled content, recyclability, care instructions and environmental figures have no home in any commerce or search feed specification checked, and the safety regime does not ask for them either. That data has to be sourced, verified and maintained entirely outside the commerce stack, and there is no reuse argument available in either direction.
Which of those attributes is hard, which is size-sensitive and what evidence each actually needs is the subject of the field set, which is where that work is described.
What this page will not tell you
It will not answer a safety compliance question. Responsible person designation, safety labelling and technical documentation belong to a different regulation with different obligations, and this estate does not work on them. If somebody is selling you a passport product that presents itself as a safety compliance initiative, those are two separate instruments and the claim is wrong.
It will not tell you a passport obligation is coming on a date. No product act has been adopted for textiles, none has been published in draft, and the Commission marks its own planned timing as indicative. What is actually settled, and what the arithmetic behind the timing looks like, is on the status tracker and on what already applies today.
It will not tell you the safety work was preparation. It was its own obligation with its own deadline, and it was worth doing on its own terms. The overlap described above is a bonus rather than a plan.
What to do with this
Separate the two records now, while you still remember which is which. Party data in one place, keyed on the legal entity. Product data in another, keyed on the identifier. Almost every merchant who did the safety work in a hurry has the party data pasted into product rows, and unpicking it later is the expensive version.
Stop counting composition twice. If your catalogue holds a one-word material value, you have satisfied a commerce field and produced nothing towards a passport. That is not a criticism of the value. It is a different object.
Do the identifier work, because it is the one thing every destination wants. It is also the only part of this chain where an error becomes unfixable once goods ship. What allocating one commits you to is a subject in its own right.
Do not buy against a passport deadline. There is not one yet. There are things worth doing anyway and they are sequenced by whether they can be undone rather than by a date, which is set out on what to do now. What already binds a clothing brand today, product safety rules included, is on what already applies.
What would change this page
A textile product act being adopted, which would replace most of the second half of this page with a specification instead of an expectation.
Any commerce or feed specification adding a home for recycled content, care instructions or a textile certification. That would create a reuse argument where none currently exists, and it would be the first time.
Sources
-
General Product Safety Regulation (EU) 2023/988In force
Used for one proposition: that an offer made at a distance has to identify the manufacturer with a postal and an electronic contact, and name the person inside the Union where the manufacturer is outside it. The articles imposing these duties have not been read at the Official Journal in this estate and no article number is published here. Nothing on this page describes any other duty under this instrument.
-
CELEX 02024R1781-20240628In forceIn force
Used for the operator definition and for the fact that the passport duty is conditional on a delegated act existing for the product group. No textile act has been adopted.
-
A cross-system attribute reuse analysis across seven product data systems, compiled 27 August 2026Field research
The load bearing source for which attributes carry and which do not. Used for the party identity overlap, for the three false friends, for the absence of any home for recycled content and care instructions in commerce and feed specifications, and for the finding that product category classification has no cross-system mapping at all.
-
Search demand evidence on the two subjects, compiled 27 August 2026Field research
Cited for one proposition only, which is that the two subjects are disconnected in every result page checked, including the platform's own help page and the government guidance. Demand throughout that research is qualitative and no volume figure exists, so none appears here.
Sources as at 30 August 2026.
Keep going
The question this one usually raises next.
Also worth reading
- ImplementationWhere product data stops meaning the same thingThe three attributes that fail in both directions, and the three harder pairs underneath them.
- Rules & scopeThe registrations that gate a listing are about your company, not your productsThe record that does carry across, and where it should actually live.
Does this reach your products?
Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.
Help someone else make sense of product passports.