Why One Product Now Needs Both EU CPNP and UK SCPN Entries

A maker asked us recently why their UK sales suddenly needed a whole separate notification when they'd already done everything through CPNP for the EU. The short version: since Brexit, the UK runs its own cosmetic notification system, OPSS's Submit Cosmetic Product Notification service, and it does not automatically receive or recognize a CPNP filing made for the EU market. If you sell the same product on both sides of the Channel, you file twice, in two different portals, with two different Responsible Persons potentially involved.

Two systems, two legal bases

CPNP, the Cosmetic Products Notification Portal, exists under EU Regulation (EC) No 1223/2009 and covers the 27 member states. SCPN, Submit Cosmetic Product Notification, is the UK's post-Brexit system run through the Office for Product Safety and Standards, OPSS. They were built to do a similar job, notify authorities about products entering the market, but they are legally and administratively separate. A product notified in one system has not been notified in the other, full stop.

Where the Responsible Person requirement diverges

This is the field that surprises people most. The EU requires a Responsible Person established within the EU. The UK requires a Responsible Person established within the UK. If your business is based in, say, Germany, and you've been shipping into the UK using your EU Responsible Person's details, that arrangement generally doesn't satisfy the UK's requirement post-Brexit. You need a UK-established Responsible Person for UK sales, which in practice means either a UK entity of your own or a third-party Responsible Person service based there.

Side-by-side comparison

Field or requirement	EU (CPNP)	UK (SCPN)
Governing framework	Regulation (EC) No 1223/2009	Post-Brexit UK cosmetics framework
Notification portal	CPNP	OPSS SCPN
Responsible Person location	Must be established in the EU	Must be established in the UK
Product Information File	Required, held by RP	Required, held by RP
Safety report (CPSR)	Required, signed by safety assessor	Required, broadly equivalent obligation
Covers sales in	EU member states	Great Britain / UK market

What this means practically

If you're a maker who's been treating "notified in Europe" as covering the whole region including the UK, it's worth auditing your product line now rather than after a customs or market surveillance question comes up. The practical steps look like this:

• List every product you currently sell into the UK
• Confirm each one has an actual SCPN entry, not just a CPNP one
• Confirm your Responsible Person for UK sales is genuinely UK-established, not just your EU RP handling it informally
• Keep separate PIFs organized by market if your formulations or claims differ even slightly between the EU and UK versions, since a PIF tied to the wrong market's notification is a real audit gap

A note on formula differences

Sometimes makers adjust a formula slightly between EU and UK versions, whether for a supply chain reason or a labeling preference, and don't realize that even a small change means the UK version needs its own accurate SCPN entry reflecting the actual formula sold there, not a copy of the EU filing with the country box changed. Treat each market's notification as tied to the specific formula and label actually sold in that market.

The bigger pattern

This EU-versus-UK split is a good reminder that "notified" is always market-specific, never global. The same logic applies elsewhere. A Canadian Cosmetic Notification through Health Canada's system doesn't touch your EU or UK obligations, and an EU CPNP filing doesn't touch Canada's either. Each market runs its own system, its own Responsible Person or notifier requirements, and its own ingredient rules, and treating any one filing as a passport to another market is one of the more common and avoidable mistakes we see makers make when they expand internationally.

Cosmetic Comply currently handles the Canadian Cosmetic Notification System, with the US, EU, and Australia in development, and the multi-market build-out is deliberately structured around this exact reality: each market gets its own notification workflow rather than one filing pretending to cover them all.