Six Reasons a CPNP Notification Gets Bounced Back
The recurring data-entry and formulation mistakes that stall an EU CPNP notification, and how to catch each one before submission.
There's a particular kind of frustration in getting a CPNP submission kicked back over something that has nothing to do with your formula being unsafe. It's usually a data problem, not a safety problem, and most of them are the same handful of mistakes on repeat.
1. The Responsible Person field doesn't hold up
Under Regulation (EC) No 1223/2009, every product notified through the CPNP portal needs a Responsible Person established in the EU. This isn't a formality field, it's a legal role, and the portal (or a downstream check) can bounce a submission where that role isn't properly filled by an entity actually established within the EU. If you're a maker based outside the EU trying to notify without a genuine EU-established Responsible Person in place, that's the structural fix needed before the data-entry details even matter.
2. INCI names that don't match the standard nomenclature
This is the most common data-entry rejection reason across nearly every regulatory portal, not just CPNP. Typing "Vitamin E" instead of the actual INCI name, or using a trade name instead of the standardized nomenclature, creates a mismatch the system can't reconcile. Every ingredient needs its correct INCI name, the same standardized system used globally, where something as basic as water has a specific required form (Aqua) rather than whatever a formula sheet happens to call it.
3. Percentages that don't add up
Formulas get revised over time. Someone swaps an emulsifier, tweaks a fragrance load, or adjusts a humectant, and the percentage sheet doesn't get fully updated to match. If the ingredient percentages on your notification don't sum sensibly, or don't match the formula documented in your Product Information File, that inconsistency between what's filed and what's actually in the product is exactly the kind of gap a review step is designed to catch, and it stalls things while it gets resolved.
4. Missing or incomplete Cosmetic Product Safety Report
The Product Information File needs a Cosmetic Product Safety Report signed by a qualified safety assessor. A notification submitted before that CPSR is genuinely complete and properly signed is submitted too early. This is less a data-entry slip and more a sequencing mistake, treating the CPNP submission as a step that can run in parallel with finishing the safety assessment rather than a step that comes after it.
5. Category or function selections that don't match the actual product
The portal asks you to categorize the product and, often, to characterize the function of certain ingredients. A body lotion categorized in a way that doesn't match its actual use, or an ingredient whose declared function doesn't match how it's actually used in that formula, creates friction. This tends to happen when notifications are filed quickly by copying a similar past product's categorization without double-checking it against the product actually in front of you.
6. Formula changes that never triggered an update
A notification filed accurately at the time can go stale. If the formula changes after the fact, whether that's a new supplier's version of an extract, a reformulated fragrance, or a different preservative system, and the CPNP record is never updated to reflect it, you end up with a live notification that describes a product that no longer exists in that exact form. This isn't always caught immediately, but it's a liability sitting quietly until an inspection or a query surfaces the mismatch.
A pre-submission checklist worth running every time
| Check | What to confirm |
|---|---|
| Responsible Person | Genuinely established in the EU, correctly listed |
| INCI names | Every ingredient in standard INCI form, no trade names |
| Percentages | Sum and match the current, actual formula |
| CPSR | Complete, signed by a qualified assessor, before submission |
| Category and function | Matches the real product and real ingredient roles |
| Formula currency | Notification reflects the formula as currently manufactured |
Running through this list before you submit, rather than after a rejection, is the difference between a five-minute check and a multi-week resubmission cycle.
Cosmetic Comply's EU pathway is on the way alongside the currently live Canadian filing process, and the same underlying discipline applies across both: matching every ingredient to its correct INCI name and CAS number, expanding supplier blends into their real components, and having a human reviewer confirm the result before anything gets submitted, so the paperwork holds up the first time rather than bouncing back on something avoidable.
Send your ingredients and we take it from here
A short intake form is all it takes to start. Every ingredient gets checked against your market's prohibited and restricted lists, then we file your notification and hand you a number you can track.
Start a filingKeep reading
Reporting Serious Undesirable Effects Through the CPNP
A customer complaint about a burning rash is not just feedback, it may be a serious undesirable effect you are obligated to report.
Minimum Durability Dates on EU Cosmetic Labels
How the EU hourglass symbol differs from PAO, and what stability data actually has to back up each one on your label.
Stating the Function on an EU Label When It Is Not Obvious
When EU Regulation 1223/2009 requires a stated product function on the label, with soap and serum examples showing where it applies.
Can You Sell a CBD Cosmetic in the EU CPNP
The CosIng entry situation for cannabidiol, and why THC content and narcotic status constrain whether a CBD cosmetic can be notified in the EU at all.