EU regulatory guide
CPNP Notification: How to File on the Portal, Field by Field
A CPNP notification is the entry a cosmetic product must have on the Cosmetic Products Notification Portal before it is placed on the EU market. It is filed under Article 13 of Regulation (EC) No 1223/2009, and it is not an approval — it is a registration that must be complete and accurate before the first sale.
This guide covers the part most pages skip: what the portal actually asks for, who is allowed to enter it, which fields cause rejections, and what the resulting CPNP number, reference and code mean. For the commercial overview of the portal itself, see what CPNP notification is and who files it.
What is a CPNP notification? A CPNP notification is the registration a cosmetic product must have on the EU's Cosmetic Products Notification Portal before it is placed on the market. It is filed by the Responsible Person under Article 13 of Regulation (EC) No 1223/2009. It is a registration, not an approval.
Reviewed by Cassandra Maddocks, chemist & biochemist · last reviewed 26 July 2026
What is the CPNP?
New to the topic? Start with our plain-language explainer, What is CPNP?, then come back here for the filing walkthrough.
The portal is operated by the European Commission, and its official information page is published by DG Internal Market. Notification is a record, not an approval: the Commission does not review or clear the product. Compliance remains the responsibility of the product's EU Responsible Person at all times.
What the CPNP portal actually asks for, field by field
The portal is a structured form, not a document upload. Every notification is built from the same field set, and each field has a defined owner. Understanding who owns which field is what prevents a rejected or incomplete filing.
Who enters what
The Responsible Person files the notification. Under Article 13, the notification is made by the Responsible Person established in the EU before the product is placed on the market. A distributor or brand owner cannot file on their own behalf unless they are the Responsible Person.
Where the Responsible Person is a compliance partner acting in that role, the partner holds the portal account and enters the data. The brand supplies the inputs. The distinction matters at audit: the account holder is the party the competent authority contacts.
The field set
Product identification. Product name as it appears on the label, product category, and the product's intended use. The name must match the label exactly — a marketing name on the portal and a different name on pack is a mismatch that surfaces at market surveillance.
Responsible Person details. Legal entity name, registered address, and contact details for the Responsible Person. For non-EU brands, this is the EU-established entity, not the exporting brand.
Product formulation. The qualitative and quantitative composition, expressed to the level required for the notification. This is the field brands are most cautious about, and the portal's access model is built around that caution.
Nanomaterials. Where the product contains nanomaterials, the notification must identify them, specify the nanomaterial and the reasonably foreseeable exposure conditions, and be filed ahead of the standard timeline. Nanomaterial notifications are a separate filing obligation, not a checkbox on the main form.
CMR substances. Where a substance classified as CMR is present, the notification carries the additional identification required by Article 13.
Frame formulation. For products where a frame formulation applies, the notification references the frame rather than the full quantitative formula.
Label and packaging. The product label as it will be placed on the market, and where relevant the packaging, submitted as the notification's visual record.
Responsible Person confirmation. The declaration that the product complies and that the Cosmetic Product Safety Report is in place. This is the field that converts a data entry into a valid notification.
The error patterns that cause rejection or rework
Name mismatch. The product name on the portal differs from the name on the label. The most common cause is a late rebrand that was applied to artwork but not to the notification.
Wrong Responsible Person entity. The notification names the brand or the manufacturer instead of the EU-established Responsible Person. The filing is invalid on its face.
Missing CPSR at filing. The notification is submitted before the Cosmetic Product Safety Report exists. The portal accepts the entry; the product is still non-compliant. See what a Cosmetic Product Safety Report must contain.
Nanomaterial filed on the standard timeline. The nanomaterial notification is treated as part of the ordinary filing and misses its earlier deadline.
Variant handling. Shades and variants are filed as separate products when they share a formulation, or bundled when they do not. Both directions create rework.
Post-market change not notified. A reformulation, a rename or a change of Responsible Person happens without an update to the notification. The portal record goes stale while the product keeps selling.
The practical rule: build the notification from the finished label and the signed safety report, not from the product brief. Every field that can be checked against a document should be checked against that document before submission.
Who files the CPNP notification?
Under Article 13(3), a distributor who translates a label or otherwise makes a product available in a member state under its own initiative also notifies certain details, but this never replaces the Responsible Person's product notification. For the full picture of the EU regime around the notification, see selling in the EU and the complete EU guide.
What information does a CPNP notification contain?
In practice, the notification is only as ready as the dossier behind it. The formulation details come from the same work that produces the Cosmetic Product Safety Report, and the label you upload should already have passed a label and claims review. A notification that contradicts the label invites market-surveillance questions later.
CPNP notification requirements: the pre-filing checklist
A notification is only as valid as the documents behind it. Work through this list before the portal session, not during it.
Before you open the portal
Responsible Person in place. An EU-established Responsible Person is appointed and has accepted the role in writing. Without this, there is no party entitled to file. See EU Responsible Person.
Cosmetic Product Safety Report signed. The CPSR is complete and signed by a qualified safety assessor. The notification declares that it exists; it must exist first.
Product Information File assembled. The PIF is compiled and held for the product, available to the competent authority on request. See what the Product Information File must contain.
Label finalised and compliant. The label carries the Responsible Person's name and address, the nominal content, the batch code, the PAO or best-before date, the function and the ingredient list in INCI nomenclature. A label review before filing prevents a re-notification after. See label and claims review.
Claims checked. Every claim on pack and in the listing is substantiated and consistent with the formulation.
Nanomaterial status confirmed. You know whether the product contains nanomaterials, because that answer changes both the deadline and the filing route.
CMR status confirmed. You know whether any substance classified as CMR is present, because that answer changes the data the notification must carry.
Frame formulation decision made. You know whether the product can be notified against a frame formulation or requires full quantitative composition.
Product name locked. The name on the portal will match the name on the label. Lock it before filing.
After filing
Number recorded. The assigned CPNP number is stored in the product's compliance file and shared with distributors who ask for it.
Change process defined. Someone owns the trigger for re-notification: reformulation, rename, change of Responsible Person, discontinuation.
UK position checked separately. A CPNP notification does not cover Great Britain. If the product is sold there, it needs a separate notification under the UK SCPN regime. See the SCPN notification guide and the UK cosmetics regulation guide.
If any line above is unresolved, the notification can still be submitted — but it will be a filing that has to be corrected later, and corrections cost more than preparation.
When must the notification be filed?
The filing itself takes minutes when the documentation is ready. The realistic timeline is set by everything upstream: appointing the Responsible Person, completing the safety assessment and assembling the Product Information File. Plan those weeks before your launch date, not the notification.
Do nanomaterials need a separate notification?
The six-month lead time is the detail that catches brands out: a formulation containing an in-scope nanomaterial effectively adds half a year to the launch runway unless the material is already listed in the regulation's annexes.
Who can see my formula on CPNP?
This is the most common confidentiality worry we hear, and the answer is consistent across the EU: the portal exists so that authorities and poison centres can act, not as a public register of formulas.
Does a CPNP notification cover the UK?
A brand selling into both markets files twice, with two Responsible Persons. The GB side is covered in the official GOV.UK guidance in our SCPN notification guide, and in our UK cosmetics regulation guide.
What does CPNP notification cost?
Full pricing for the surrounding work (the Responsible Person mandate, CPSR and PIF) is on the pricing page.
What happens after notification?
This is why notification is best treated as part of an ongoing compliance system rather than a launch-day task; keeping records current across markets is exactly what Compliance Care exists for.
CPNP number, CPNP reference and CPNP code: what each one is
Three different things get called "the CPNP number". They are not interchangeable, and using the wrong one in a supplier questionnaire or a marketplace listing causes avoidable back-and-forth.
CPNP number
The identifier the portal assigns to a notification when it is successfully submitted. It is the reference a competent authority or a retailer will ask for when they want to confirm that a product has been notified. It is not a product approval number and it does not certify safety.
CPNP reference
The term used for the same identifier when it appears in correspondence, on a distributor request or in a marketplace onboarding form. "CPNP reference" and "CPNP number" usually point to the same portal-assigned value; the difference is the context, not the data.
CPNP code
A code is not a notification identifier. Where "CPNP code" appears, it generally refers to a product category or classification value used inside the portal, or to an internal reference a brand has created for its own records. A CPNP code cannot be used to look up a notification.
CPNP search
There is no public search of CPNP notifications. The portal is not a public register, and the formula data inside it is not visible to competitors or to the general public. Verification of a notification happens through the Responsible Person or through the competent authority, not through a lookup page.
Keep the assigned number with the product's compliance file. When a retailer asks for a CPNP number, they are asking for that value — not for a category code and not for a safety report reference.
Primary sources cited in this guide. Regulatory status last verified 26 July 2026.
Put this into practice
From reading to notifying.
FAQ
