The registrations that gate a listing are about your company, not your products
Almost everything blocking a listing today is a fact about the business rather than a fact about the garment. Who made it. Who answers for it inside the Union. Which producer scheme the company is registered with, in which country, for which waste stream. None of that is a product attribute, all of it is stored as one, and that is why it gets typed again in every system.
Navigate this page
The short answer
There are two records here and most tooling has only modelled one.
The product record describes a garment. It changes when the product changes and it is different for every line.
The party record describes the company. Who the manufacturer is, with a postal address and an electronic contact. Who the responsible person inside the Union is, where the manufacturer is outside it. And a set of producer registration numbers, one per country, per scheme, per waste stream.
The party record is small, it is stable, it changes rarely, and it applies to a whole catalogue rather than to a product. It is also the single most re-entered dataset in this chain. Every commerce system stores it against products or does not store it at all, and the systems that actually demand it are the ones with the power to stop you trading.
The three ways the two records differ
| Product record | Party record | |
|---|---|---|
| What it describes | This garment | This company, in this market |
| How many there are | One per line, often one per size and colour | One per company, plus one registration per country per scheme |
| How often it changes | Every season | Rarely, and usually because a market or a scheme changed |
| What happens if it is wrong | A wrong value on a passport | A blocked account, or an offer that cannot go live |
The last row is the one that gets underestimated. A wrong composition percentage is a compliance exposure that surfaces if somebody tests the garment. A missing producer registration is a listing that does not appear.
Why it ends up stored in the wrong place
A commerce system stores a brand. A brand in that context is a marketing string, used to filter, group and display. Nothing stands behind the string and nothing needs to.
The regulatory side asks for a party. An online offer has to identify the manufacturer and give a postal and an electronic contact, and where the manufacturer sits outside the Union it has to name the person inside it who answers for the product instead. That is an accountable entity with an address, not a word on a label.
Those two objects share a field name in most catalogues, and the estate takes that failure apart in detail on where product data stops meaning the same thing. What follows from it here is narrower and structural. Because the party is stored as a string on a product, there is nowhere in the catalogue for the rest of the party record to live, so the producer registration numbers end up in a spreadsheet, in a seller portal, in somebody's email, or nowhere.
The producer registration is the clearest case. It is not a product attribute at all. It is a company, market and scheme tuple: this company, registered in this country, for this waste stream, under this number, issued by this authority. There is no field for it in any commerce platform data model we have seen described, because it is not a fact about anything a commerce platform models.
What the gates actually test
The pattern across the platform rules read for this research is consistent, and it is worth separating from what the category talks about.
Marketplaces gate on who you are and on whether the product is safe. They do not gate on what the product is made of.
The mechanics recur, and several of them are published by the platforms themselves. An account cannot publish an offer until an identity block is complete. An offer naming nobody inside the Union to answer for the product is held: bol has run that gate since April 2026 and has begun taking existing catalogue offline as well. A producer registration is checked against a national scheme before a listing is allowed, and Kaufland applies that across nine national schemes with nine different authorities and nine different numbering systems, stating that offers without the information will be systematically excluded from selling. Amazon verifies producer registration in every EU country a seller is active in. eBay, Allegro and OTTO each run a version of the same identity and safety gate.
There is also now a rule requiring the platform itself to verify a packaging producer registration before it takes a seller on, which moves the check from something the seller declares to something the intermediary is obliged to confirm.
Two things about the platforms above. They are named because the rules are their own published policy and describing them accurately reflects a platform doing what the law asks. The dates are given sparingly and the mechanics are what matters, because a mechanic survives a policy edit and a specific date does not: all of these changed within the last two years and several will change again. The legal half of this, meaning which parts of a refused listing are fixed by law and which are a commercial decision by the platform, is set out on what a listing has to carry, and nothing on this page repeats it. What law actually fixes for a distance offer, and what platforms add on top, is on what a listing has to carry.
What none of this is
It is not a passport requirement. Nothing read for this research supports the idea that any marketplace, retailer or platform refuses a listing today for want of passport data. The gates that are running test identity and safety. That is a different subject from the one the category spends its time on.
It is not evidence that the sustainability data matters commercially. It is closer to the opposite. The data being gated is the data about your company. The data everybody is being asked about is gated by nothing here.
It is not a deadline list. Dates in this area move, schemes are added, and a page carrying a table of platform dates would be wrong within a quarter. What is durable is the shape of the requirement, not the calendar.
What a party record has to contain to be worth having
Four things, and the fourth is the one people leave out.
The legal entity, not the trade name. With a registered address and an electronic contact that a person actually monitors. Where the manufacturer is outside the Union, the entity inside it that answers for the product, which is a separate appointment with its own paperwork.
The role you occupy in each market. The duties in this area are written by role rather than by sector, one business can occupy more than one at once, and which role you are in decides which duties reach you. That question has a settled answer and a page of its own, on which role you occupy.
Every registration, keyed by country, scheme and stream. Not one number. A brand selling into several member states holds several, issued by different authorities in different formats, with different renewal cycles and different reporting obligations attached. Held as a list keyed on those three things, it is maintainable. Held as free text on a product, it is not.
A renewal and change date against each one. Registrations lapse. Schemes get added when a country brings a new stream into scope. Nothing tells you, and the first sign is usually a listing that stopped working.
What to do with this
Pull the party record out of the product record. If your producer registration numbers currently live inside a spreadsheet column beside product lines, they are stored against the wrong object and they will be re-entered every time a channel asks. One list, keyed on country and scheme, is the whole fix.
Establish who inside the business owns it. This record is not the product team's and it is not the compliance team's by default. It is the one somebody has to be able to produce on demand, and who signs off a published field is a governance question the estate treats separately, on who has to own this.
Treat a blocked listing as a diagnosis before a task. A refusal has two candidate causes, a legal one and a platform one, and they look identical from inside a seller account. Fixing the wrong one costs a quarter.
Do not build the passport work on this. The party record feeds a passport, and it is also the thing that unblocks a listing today with no passport anywhere in sight. Those are two reasons to hold it well, and only one of them has a date attached. Which role the passport duty itself attaches to is a separate question, answered on who carries the obligation.
What would change this page
A marketplace or a retailer making passport data an onboarding condition. Nothing read for this research does, and the first one that does would change the sequencing argument above rather than the structural one.
A commerce platform modelling producer registration as a first-class object rather than leaving it to sellers. That would close the structural gap this page describes, and it is the kind of thing a platform can ship in one release.
Sources
-
General Product Safety Regulation (EU) 2023/988In force
Used here 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 responsible 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.
-
Packaging and packaging waste rules on platform verification of producer registrationIn force
Cited for one proposition: that an online platform is obliged to verify a packaging producer registration before onboarding a seller. Described rather than quoted, and the article number is not published because the instrument has not been read at source here.
-
Platform seller policies and marketplace requirement research, compiled 27 August 2026Field research, first-party platform policy
Used for the gate mechanics and for the existence of multi-scheme registration checks. No platform is named, because a mechanic survives a policy edit and a name does not. Dates are deliberately not carried.
-
A cross-system attribute reuse analysis across seven product data systems, compiled 27 August 2026Field research
Used for two propositions: that party identity is required across the regulatory and marketplace systems and absent from the commerce feed systems, and that a producer registration number has no home in any commerce data model examined.
Sources as at 30 August 2026.
Keep going
The question this one usually raises next.
Also worth reading
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.