WTO TBT notifications: what they are and how to read a draft cosmetic regulation

• Before a cosmetics restriction reaches the Official Journal of the EU, the European Commission has to notify the draft to the World Trade Organization (WTO), weeks in advance and with a public comment deadline.
• A TBT notification is identified by a document symbol (for example, G/TBT/N/EU/1227), a distribution date and a comment deadline. With those three fields you find the notification that affects you in minutes; without them it disappears among hundreds that have nothing to do with cosmetics.
• A draft is a proposal, not a rule in force. It can change before it reaches the Official Journal, in scope or in conditions, and some drafts are never adopted in the form they were notified.
• This source completes the five our regulatory watch playbook covers: CosIng, SCCS, Safety Gate and EUR-Lex tell you about changes already in motion or already in force. The WTO tells you earliest of all.

1. What a TBT notification is (and why the obligation exists)

The Agreement on Technical Barriers to Trade (TBT) is one of the agreements every country signs when joining the World Trade Organization (WTO). What it requires fits in one line: if a member is about to adopt a technical measure that may affect international trade — a standard, a regulation, a conformity assessment procedure — it has to tell the other members before adopting it, not after.

The European Union meets that obligation through the Commission. When a regulation in preparation is going to amend the Annexes of Regulation (EC) 1223/2009 in a way that could affect trade in cosmetic products with third countries, the Commission notifies the draft to the WTO before pushing it into the final adoption process.

From the outside it looks like diplomatic paperwork. It stops looking that way once you see what it enables: while the notice is open the text can still be argued over, and anyone who knows where to look can read it. That is where the value sits for a regulatory team. This is not decorative transparency — it is the first moment the actual wording exists in public.

2. Where a draft sits in the real timeline

Nobody working in regulatory affairs finds out about a restriction on the day it lands in the Official Journal. Or nobody should. The path has several stages, and the TBT notification occupies a fairly specific slot in the middle:

1. SCCS opinion. The Scientific Committee on Consumer Safety assesses a substance and publishes its technical opinion. We work through that step in the regulatory watch playbook.
2. Drafting. The Commission turns the scientific recommendation into regulation text: affected Annexes, conditions of use, proposed transitional dates.
3. TBT notification to the WTO. Before entering the formal adoption procedure, the Commission notifies the draft.
4. Adoption and publication in the Official Journal. The regulation is adopted and published in the Official Journal, reachable through EUR-Lex.
5. Application date. The text starts to apply, usually with separate deadlines for when the product can no longer be placed on the market and when it can no longer be made available.

Between step 3 and step 4 there are typically three to eight weeks. In the daily life of a regulatory department, three weeks is the difference between reviewing the portfolio calmly and reviewing it with the application date breathing down your neck.

3. How to read a TBT notification

Opening the WTO ePing portal or the European Commission's TBT database for the first time is discouraging. The system covers every sector: for each cosmetics notification there are dozens on tyres, toys, animal feed or food labelling. Three fields separate a useful search from the noise.

3.1. The document symbol

Every notification carries an identifier in the format G/TBT/N/[country or bloc]/[number]. For the EU the pattern is G/TBT/N/EU/xxxx, for example G/TBT/N/EU/1227. That number is your stable reference: use it to cite the notification, to find it again months later, and to make sure everyone in a meeting is talking about the same filing rather than an earlier version or a different one touching a similar substance. It sounds like a minor detail until two people on the team spend half an hour arguing about conditions that live in different documents.

3.2. Distribution date and comment deadline

Every notification states its distribution date (when it became public) and its comment deadline. The second one sets your working calendar: it closes the window in which the draft is still open to observations. Across the EU notifications we track, that deadline falls fairly consistently 60 days after distribution. Past that date the text moves toward its final stage, but it remains a draft until it is published in the Official Journal.

3.3. The notified document

The notification itself is a summary record: notifying member, products covered, objective of the measure, legislative reference. The notified document is the attachment with the actual draft text, listing the Annexes it amends, the specific entries and the proposed conditions.

It is usually a short PDF, written in implementing-act language, with amendments expressed as replacements of table rows that are not in the document itself. It reads badly and it reads slowly. Read it anyway: it is the only reliable account of what the draft says. Not trade press headlines, not a newsletter summary, not what somebody posted on LinkedIn.

4. What the comment window is actually for

Any WTO member — and, through the appropriate national channels, interested industry parties — can file technical observations during that period: objections to methodology, questions about the scope of a restriction, requests for clarification on transitional deadlines.

For most regulatory teams the value is not in taking part in that process, although it sometimes makes sense through industry associations. It is in using the window to work: checking which references in the portfolio the draft touches, opening the conversation with formulation if needed, and arriving at publication day with the analysis already done rather than starting it that morning.

5. The rule you cannot break: a draft is a proposal

This is worth saying without hedging: a TBT notification is not a rule in force. It is what it claims to be, a draft notified ahead of adoption and open to comments. The text can change in conditions of use, in transitional dates, in scope. And some drafts end up adopted with differences from what was notified.

Reformulating a product, sending a client communication or touching the Product Information File on the strength of a draft is an expensive mistake, and not a hypothetical one. The right discipline fits in one sentence: read the draft, assess the impact, plan ahead, and wait for the adopted text published in EUR-Lex before treating it as an obligation.

6. Real case: the notification on silver entries

This post comes out of a specific case. In late July a client asked us about a change to the silver entries they had seen discussed on LinkedIn. It was not in EUR-Lex, not in the Official Journal and not in any of the sources we were monitoring at the time, simply because it was not a published act yet. It was at the WTO.

On 30 July 2026 the Commission notified the draft with symbol G/TBT/N/EU/1227, amending the silver entries of Regulation (EC) 1223/2009. The comment period is open until 28 September 2026.

Here is what it proposes, taken from the notified document rather than from third-party summaries: the substance concerned is Silver (powder) [100 nm < particle diameter < 1 mm], INCI Silver, CAS 7440-22-4, with four maximum concentrations depending on the product type.

The scopes are reproduced as they appear in the notified document, not paraphrased. Rewording them is the kind of convenience that later turns into an argument about whether "oral care" covers a toothpaste.

Four entries for a single substance, with a specific and lower limit for mouthwash for children. That is the usual pattern when the scientific opinion separates exposure by route and by population.

We are repeating the rule from the previous section here, because this is where it is hardest to respect: those are the draft's figures. If you work with silver-derived ingredients — the Commission already touched related entries in Regulation (EU) 2026/909, which rewrote Annex II entry 1597 and created Annex V entry 61 — they are good for sizing the impact and starting to look at formulations, not for closing anything. Check the current status of your ingredients on BD-API's CosIng search tool and wait for the text published in EUR-Lex before you move a dossier.

7. How BD-API handles it

That client question ended up becoming a source of its own. TBT notifications relevant to cosmetics now sit in our daily monitoring at the same level as CosIng, SCCS, Safety Gate and EUR-Lex, rather than as a footnote to EUR-Lex.

Every draft we detect is explicitly labelled as a proposal, never as a rule in force: the distinction this post defends from top to bottom arrives marked in the alert itself. And because the notification summary almost never carries the figures, the analysis downloads the notified document, reads it and extracts the substances with name, INCI, CAS, proposed action, concentration and product scope. It is exactly the work we did by hand on the silver notification, done every morning across everything that gets published.

8. Bottom line

WTO TBT notifications are the earliest source in the EU cosmetics regulatory ecosystem: they warn you weeks before the change reaches the Official Journal. That advantage only works if you know how to read them — document symbol, distribution date, comment deadline — if you go to the notified document instead of to what is said about it, and if you respect the rule that governs them: a draft is a proposal, not a law, until EUR-Lex says otherwise.