
If you’re planning to sell a cosmetic product anywhere in the European Union, there’s one step you can’t skip, negotiate around, or postpone until after launch: CPNP notification. Not a label review. Not a safety assessment on its own. The actual notification itself, filed before a single unit reaches an EU shelf or an EU customer’s doorbell.
A surprising number of brands find this out the hard way — usually when a shipment gets stopped at customs, or a marketplace pulls a listing without warning. So let’s cover what CPNP actually is, who it applies to, and why getting it right the first time matters more than most brands assume.
What CPNP Actually Stands For
CPNP stands for the Cosmetic Products Notification Portal. It’s an online system run by the European Commission, and it’s where every cosmetic product has to be registered before it can legally be placed on the EU market. This isn’t a licensing scheme in the way pharmaceuticals are licensed — there’s no approval process where an official signs off on your formula. Instead, it’s a notification requirement: you tell the Commission (and, through the system, the poison control centres of every member state you’re selling into) exactly what the product is, who’s responsible for it, and where the safety data behind it lives.
The legal basis for this sits in EU Regulation (EC) No 1223/2009, the Cosmetics Regulation. Article 13 spells out the notification obligation, and it applies regardless of whether you’re a multinational skincare brand or a solo founder shipping a single hand cream from a rented unit.
Who Actually Needs to File It
This is where a lot of confusion creeps in. CPNP notification isn’t something only EU-based manufacturers deal with — it applies to:
- Brands manufactured inside the EU and sold within the EU
- Brands manufactured outside the EU (UK, US, Pakistan, China, wherever) but sold to EU consumers
- Private label and white label products, where the brand owner is legally responsible even if a third party makes the product
- Products sold through EU-based online marketplaces, not just physical retail
The common thread is the destination market, not the origin. If your customer is in the EU, CPNP applies to you. A lot of brands outside Europe assume this is “someone else’s problem” — their distributor’s, their marketplace’s, their fulfilment partner’s. Legally, it’s the Responsible Person’s problem, and if nobody has been formally designated as that Responsible Person, the obligation doesn’t disappear. It just sits there, unresolved, until a regulator or a retailer asks the question nobody has an answer for.
Why This Isn’t Just Paperwork
It’s easy to file CPNP under “regulatory admin” and move on. That undersells what’s actually happening here.
The notification links every product to a Cosmetic Product Safety Report (CPSR) and a Product Information File (PIF) — the documents that prove the formula is safe, the claims are substantiated, and someone can be held accountable if something goes wrong. When a consumer has an adverse reaction, poison control centres pull information straight from what was submitted through CPNP. When a market surveillance authority does a spot check, CPNP is the first place they look. Without a valid notification behind it, a product isn’t just non-compliant on a technicality — it has no legal basis to be on the market at all.
That has real consequences:
- Customs can and does hold shipments that lack proper documentation
- Retailers and distributors increasingly ask for proof of CPNP notification before listing a product, especially larger EU chains
- Non-compliance can mean product recalls, fines, or a forced market withdrawal — after you’ve already spent on manufacturing, packaging, and marketing
- Marketplaces like Amazon EU have been tightening enforcement, removing listings that can’t produce a valid notification number on request
For a brand that’s already invested in formulation, packaging, and a launch date, discovering a compliance gap after the fact is the expensive way to learn this.
What the Process Actually Involves
At a high level, notifying a product through CPNP requires:
- A formula breakdown and safety data, compiled into a CPSR by a qualified safety assessor
- Product and packaging details, including the actual label as it will appear to consumers
- A designated Responsible Person based in the EU (or UK, for SCPN) who takes on the legal accountability for the product
- Submission through the CPNP portal itself, generating the notification numbers per member state and per formula variant
Where brands usually run into trouble isn’t the portal — it’s everything that has to be correct before you get there. An incomplete CPSR, a label that doesn’t match what’s actually notified, or missing responsible-person documentation will all stall a submission, sometimes for weeks.
Where This Fits With SCPN, CPSR, PIF, and Label Review
If you’ve come across CPNP alongside terms like SCPN, CPSR, PIF, and Label Review and aren’t sure how they connect — that’s normal, and it’s worth untangling separately. In short: CPSR is the safety assessment that CPNP notification depends on, PIF is the compiled dossier that has to be kept on file and ready for inspection, Label Review checks that your packaging claims and mandatory information meet EU labelling law, and SCPN is the parallel system for the UK market post-Brexit. None of these stand alone — CPNP is the step that ties them together into an actual market entry.
Getting It Right the First Time
CPNP notification isn’t complicated once someone’s walked through it correctly — but it’s unforgiving of shortcuts, and the cost of getting it wrong shows up later, not immediately. A rejected or incomplete notification rarely announces itself until a shipment is held, a retailer asks a question you can’t answer, or a regulator comes calling.
If you’re preparing to launch a cosmetic product in the EU — or you’ve already launched and aren’t sure your notification is actually complete — it’s worth having it checked properly rather than assuming it’s fine. That’s exactly the gap our CPNP notification service is built to close, from the safety documentation through to the final submission.