CosIng doesn't tell you when it changes — here's why that matters

• No schedule. No changelog. No notification.
• Updates are downstream of SCCS opinions and OJEU regulations — not the other way around.
• If your monitoring strategy is "check CosIng quarterly," you are flying blind.

1. What CosIng is, and where it sits in the regulatory stack

Ask any Regulatory Affairs lead which database they check first when sourcing a new ingredient and CosIng comes up nine times out of ten. CosIng is the European Commission's public reference for cosmetic ingredients — INCI names, function, restrictions under Regulation (EC) No 1223/2009, and links to SCCS opinions.

Useful, yes. Authoritative, no. CosIng is downstream of the law. The actual binding text lives in Regulation 1223/2009 and its Annexes II through VI, amended over time by Commission Regulations published in the Official Journal of the European Union (OJEU).

That distinction matters because it splits "update frequency" into two questions: when the law changes, and when the database catches up. The lag between them is where most compliance gaps quietly open.

2. How CosIng officially gets updated

The update path looks like this:

1. SCCS issues an opinion on an ingredient's safety. Months to years from the original mandate.
2. The Commission drafts a Commission Regulation (through the comitology procedure with the Standing Committee on Cosmetic Products) if the opinion warrants action — amending Annexes II through VI.
3. The regulation lands in the OJEU with an application date, usually with a grace period for products already on shelves.
4. CosIng catches up. Eventually. With a lag.

How much lag? Public observations put it anywhere from a few days to several weeks. There is no email, no RSS feed, no "recent changes" endpoint. CosIng is built for ad-hoc lookups, not for surveillance.

Worth a return visit. As BD-API starts logging real changes against CosIng, this post gets refreshed with live data: most recent modification date, Annexes that moved, frequency patterns over time. Treat it as a living reference, not a one-time read. Pin it.

3. The operational reality: what moves, and when

Pull from regulations published over recent years (EU 2022/1531, 2023/1490, and several others) and some patterns hold:

• Annex II (prohibited substances) expands in waves whenever new CMRs get reclassified under CLP. Slow, but predictable.
• Annex III (restricted substances) is the volatile one. Concentration caps shift, use scopes get redefined, warning labels appear out of nowhere.
• Annex V (preservatives) and Annex VI (UV filters) move on SCCS schedule — which is to say, whenever the Committee decides a substance needs another look.

Bottom line: annual review cycles do not cut it anymore. For a portfolio of any meaningful size, monitoring has to be continuous.

4. What to do about it

If you run Regulatory Affairs

• Audit your critical portfolio against CosIng and the OJEU at least monthly. Tighten that cadence for sensitive categories — preservatives, UV filters, fragrance allergens.
• Build a dependency map: which formulations rely on which ingredient. When an Annex shifts, you need impact analysis in minutes, not days.
• Subscribe upstream. Commission RSS, Safety Gate alerts, SCCS newsletters. Treat CosIng as a verifier, not a detector.

If you sign off on regulatory risk

• The real cost of manual monitoring is not the headcount it consumes. It is the recall, the rejected import, the retail account walked away from because a banned ingredient slipped through.
• Run the math: how many unique ingredients are in your portfolio? Past 50 to 100 SKUs, manual tracking quietly stops working long before anyone notices.
• Automation does not replace your regulatory function — it returns time to the work that actually needs human judgment.

5. The right question

CosIng updates when the regulatory ecosystem decides to move — not when it suits your review calendar. The wrong question is "how often does CosIng change?"

The right one is: "how do I find out the day it does?"

And the answer lives upstream of CosIng, not inside it.

Sound like your team's weekly headache?

If chasing CosIng, the OJEU and SCCS opinions is eating into your team's calendar, BD-API was built to take that off your plate. We monitor the sources you already check manually, alert you by email or webhook the moment an Annex moves, and hand over the patch ready to apply.