CPNP vs the UK SCPN: Two Portals You Now Need

Before Brexit, one notification covered the UK and the EU together. Now it takes two, on two different systems, and brands who built their process around the old single-portal world sometimes still have not fully separated the two in their heads.

The split, in short

If you sell a cosmetic product in the European Union, you notify it through the CPNP, the Cosmetic Products Notification Portal, under Regulation (EC) No 1223/2009. If you sell the same product in the United Kingdom, you separately notify it through the OPSS Submit Cosmetic Product Notification (SCPN) service. They are not linked. A CPNP notification does not cover UK sales, and an SCPN notification does not cover EU sales. If your product is on shelves in both markets, you are filing twice.

What each requires

EU / CPNP:

• A Responsible Person established in the EU who takes on the legal accountability for the product in that market.
• A Product Information File (PIF), maintained and made available on request, documenting the formula, manufacturing, and safety basis of the product.
• A Cosmetic Product Safety Report (CPSR), which must be signed off by a qualified safety assessor, forming the technical backbone of the PIF.
• Notification of the product through the CPNP itself before it goes on the market.

UK / SCPN:

• A UK-based Responsible Person, separate from your EU one. The same person or company generally cannot fulfill both roles at once, since each role requires establishment in that specific market.
• Notification through the OPSS SCPN service.
• Broadly similar underlying expectations around product safety documentation, though administered through the UK's own post-Brexit regulatory framework rather than the EU's.

The practical headache is the Responsible Person requirement. You need someone (or some company) established in the EU for your EU filing, and someone established in the UK for your UK filing. A lot of small brands either partner with a Responsible Person service in each market or, if they have an entity or trusted contact in both places, use that.

Where brands get tripped up

Assuming one PIF covers both markets. Your safety documentation can often be substantially reused (the CPSR technical content does not need to be reinvented for each market if the formula is identical), but the notification itself, the assigned Responsible Person, and the portal submission are separate acts in each jurisdiction. Reusing the underlying safety work is efficient. Treating one notification as covering both markets is not correct.

Not noticing a formula difference triggers two updates, not one. If you make a small reformulation for one market (a different preservative to suit local sourcing, for instance) you need to track that the CPNP and SCPN records for that product might now describe two subtly different formulas, and both need to reflect what is actually being sold in each market.

Missing that ingredient rules do not always match perfectly. The UK and EU restricted and prohibited ingredient lists started from the same place post-Brexit but can diverge over time as each jurisdiction updates its own rules independently. A formula compliant in one market is usually, but not guaranteed to be, compliant in the other. Checking both is worth the extra few minutes rather than assuming alignment.

A simple comparison

	EU (CPNP)	UK (SCPN)
Portal	CPNP	OPSS SCPN
Responsible Person	Must be EU-established	Must be UK-established
Core safety document	CPSR within the PIF	Analogous safety documentation
Governing framework	Regulation (EC) No 1223/2009	UK post-Brexit cosmetics framework
Covers the other market?	No	No

The practical takeaway

If you are expanding from one market into the other, budget time and, likely, a small cost for a second Responsible Person arrangement, and plan on a second notification, not an extension of the first. It is more administrative overhead than it used to be under the pre-Brexit single system, but it is manageable once you know it is two separate tracks rather than one.

Cosmetic Comply's notification workflow is built market by market, starting with Canada and expanding from there, precisely because a single generic filing does not hold up once you are selling across borders. Keeping each market's ingredient screening, Responsible Person details, and filing history clearly separated is the whole point, rather than something bolted on after the fact.