We use cookies to understand site performance and improve follow-up from our team.
Topic
Every cosmetic product placed on the EU market must be notified to the Cosmetic Products Notification Portal (CPNP) before sale, by the Responsible Person. The data feeds Poison Centres and market surveillance authorities across the EU.
Last reviewed by the Worldover regulatory team.
Quick answer
CPNP (Cosmetic Products Notification Portal) is the centralised EU portal for cosmetic product notification under Regulation (EC) 1223/2009. The Responsible Person submits the notification before the product is placed on the EU market, covering category, formulation framework, labelling, packaging and Responsible Person contact details. The UK runs a separate but similar regime called SCPN (Submit Cosmetic Product Notifications). Notifications must be kept current with formulation, labelling and packaging changes.
See how Worldover handles CPNP at scaleHow this connects to Worldover
Managing INCI, PIF, CPSR and CPNP across a growing product range?
Worldover holds INCI, formulation, PIF, CPSR, CPNP, SCPN and MoCRA on one substance-first record, with Willow AI drafting and filing on your live data.
See AI ERP for cosmeticsCPNP is the EU's central submission portal for cosmetic products. The Responsible Person submits product category, frame formulation, labelling, packaging type, presence of nanomaterials and contact details. The system distributes the data to national Poison Centres and to competent market surveillance authorities. The PIF, including the CPSR, is not uploaded to CPNP but must be held available for inspection.
For products placed on the GB market, the equivalent regime is SCPN (Submit Cosmetic Product Notifications), operated by OPSS. The data set is similar but the submission is separate and a UK Responsible Person is required. Northern Ireland continues to follow CPNP under the Windsor Framework arrangements.
Three questions, answered here. You get your band and your two biggest gaps straight away, with nothing gated and no email needed.
1 of 3 · EU CPNP
Are your regulatory filings complete and current for every product you sell (FDA listings, CPNP notifications, PIFs)?
Notifications must be updated when the formulation, labelling, packaging or Responsible Person contact details change. A new product (different brand, different category, or material formulation change) requires a new notification.
Worldover for this
Worldover holds the cosmetic formula once and generates CPNP, SCPN and MoCRA filings, plus the PIF and CPSR, as a byproduct. Notifications stay in sync as labels and packs evolve.
See cosmetic ERP softwareCPNP notification is free and is completed by the Responsible Person before the product is placed on the EU market. There is no approval step and no waiting period: the notification is a declaration, not an application.
For GB, repeat the exercise in SCPN with a UK Responsible Person. For the US, the parallel duty is MoCRA facility registration and product listing.
For a brand with five SKUs, CPNP is a manual project. For a brand with hundreds of SKUs across CPNP, SCPN and US MoCRA, it is a data orchestration problem: one approved formula must produce three regulator-ready submissions and stay in sync as labels and packs evolve. Worldover holds the formula once and generates CPNP, SCPN and MoCRA submissions from the same record.
The rule most teams get wrong is not whether to notify, it is what a given change requires. This decision matrix covers the changes that actually occur in a live portfolio.
| Change | CPNP action | Knock-on |
|---|---|---|
| Responsible Person address or contact changes | Update the existing notification. | PIF location and on-pack RP address both change. |
| Pack size or packaging type added | Update the notification for the new pack. | Label artwork, EPR and packaging data per market. |
| Fragrance compound changed | Update the frame formulation and any allergen data. | Ingredient list, PIF safety assessment, allergen labelling. |
| Colourant added for a shade extension | Usually a new notification per shade or a shade range declaration. | Each shade needs its own ingredient list on pack. |
| Preservative system changed | New notification where the frame formulation category changes. | Challenge test, CPSR update, stability data. |
| Product name or brand changes | New notification. | Artwork, listings and, where relevant, UK SCPN and MoCRA listing. |
| Manufacturer or site changes | Update the notification. | GMP evidence in the PIF, supplier qualification records. |
| Nanomaterial introduced | Update, plus separate Article 16 notification six months before placing on the market. | Safety assessment and specific labelling with the (nano) suffix. |
One deadline is driving most of the current update volume. Regulation (EU) 2023/1545 expands individually labelled fragrance allergens from 26 to 81 substances: products newly placed on the EU market must comply from 31 July 2026, and products already on the market have until 31 July 2028. Every affected SKU means a recalculated allergen list, revised artwork and an updated notification, which is exactly the kind of portfolio-wide sweep that cosmetic ERP software is built to run from the formula rather than from a spreadsheet of SKUs.
Every cosmetic placed on the EU market needs a CPNP notification before launch, kept current as formulations, labelling and Responsible Person details change. Run across CPNP, UK SCPN and US MoCRA without one source of truth, the same approved formula ends up filed three different ways, and small label tweaks quietly fall out of sync with what regulators hold.
Cosmetic regulatory software holds the formula, PIF, RP and packaging spec as one record, with CPNP submission status tracked per SKU and per market. When a formula or label changes, affected notifications are flagged, Willow drafts the update and the regulatory team approves the change in one place.
CPNP data is not separate data. The frame formulation, the CMR check and the label all come from the formulation and the PIF. When those live in different systems, notification becomes re-keying, and re-notification becomes guesswork about what changed. A cosmetics regulatory workflow platform generates the submission from the live product record, and flags the changes that trigger a re-notification.
For the document that sits behind the notification, see the Product Information File guide.
FAQs
Related
The role under EU and UK cosmetics law, who can play it, and what brands need.
ReadFormulation, PIF and CPNP/SCPN/MoCRA filings from one record.
ReadRegulation (EU) 655/2013, MoCRA and the FTC on claim evidence.
ReadUS cosmetic regulation: facility registration, product listing and safety substantiation.
ReadA 20-minute working session. Your SKUs, your customers, your documentation. No slide deck.