CPNP SCPN: Common Reasons Cosmetic Products Fail Notification
Share
Spectra Cosmetic Compliance
This complements our guide to SCPN portal mistakes, which covers errors in the notification itself. Here we look at the deeper compliance failures behind them.
No valid CPSR
The most fundamental failure is having no valid CPSR. Notification presupposes that the product has been properly assessed and is safe; a product with no safety report, or one that is incomplete or signed by an unqualified person, has not met the basic precondition for sale. Notification cannot cure a missing or invalid assessment.
This is why the CPSR should be secured well before notification. A brand that reaches the notification stage without a sound CPSR has skipped the foundation, and the gap will surface at notification, at inspection, or if a problem arises. Our guide to what a CPSR is covers the requirement.
No Responsible Person in the right market
Every product needs a Responsible Person established in the market of sale a UK-established RP for Great Britain, an EU-established RP for the EU. A common failure is having no properly established Responsible Person, or having one in the wrong market. Since Brexit, a brand selling into both the UK and EU needs an RP in each, and many trip over this.
Without a valid Responsible Person, the product cannot be properly notified or lawfully placed on the market, because the RP is the entity that carries the legal obligations, including notification itself. Our Responsible Person guide explains the role and who can fill it.
A non-compliant ingredient
A product may fail because it contains a prohibited ingredient, or a restricted ingredient used above its permitted limit or outside its conditions of use. The regulatory annexes list prohibited substances, and set limits and conditions for restricted substances, preservatives, colourants and UV filters. A formulation that breaches these cannot be made compliant simply by notifying it.
These issues ideally surface during the safety assessment, which checks every ingredient against the annexes. Where they are missed until later, they force a reformulation. This is a strong argument for a thorough CPSR and an early ingredient review, rather than discovering a non-compliant ingredient at the last moment.
Non-compliant labelling
Labelling failures are common. A product may lack mandatory information the ingredient list, Responsible Person details, net quantity, durability, batch code, warnings or may carry claims that are not permitted or supportable. Because the label must also reflect the warnings the CPSR specifies, a mismatch between the assessment and the label is a compliance gap.
Since notification generally requires a label image, labelling problems often become visible at this stage. Ensuring the label is complete, accurate and consistent with the CPSR and the notification before submitting avoids this. Labelling is a whole discipline in itself, and getting it right is essential to passing notification cleanly.
Incomplete or inaccurate notification information
A product can also fail because the notification information itself is incomplete or wrong an inaccurate frame formulation, missing declarations of CMR substances or nanomaterials, or incorrect Responsible Person details. These are the errors covered in our SCPN mistakes guide, and they can hold up or invalidate a notification even where the underlying product is compliant.
The remedy is care and accuracy: knowing the formulation in detail, selecting the correct frame formulation, and making all required declarations. An accurate notification is the visible expression of underlying compliance, so getting it right depends on the substance being right first.
Missing testing or documentation
A product may fail because required testing or documentation is missing no challenge test for a water-based product, no stability data, or gaps in ingredient documentation. These gaps usually surface during the assessment, but where a product is rushed, they can persist and undermine the whole compliance position, including the ability to respond to an authority's request.
This reinforces the value of preparing thoroughly: gathering ingredient documentation and completing testing before assessment, so the product's compliance rests on solid evidence. A product built on incomplete evidence is fragile, however far it gets toward launch.
The common thread: skipping the foundations
Almost every notification failure traces back to the same root cause: a foundational step was skipped or rushed. Notification is the visible gate, but it exposes weaknesses that originate earlier no CPSR, no RP, a non-compliant ingredient, a bad label. The failure appears at notification, but its cause lies upstream.
The practical lesson is that passing notification cleanly is a by-product of doing the earlier work properly. Brands that build compliance in order assessment, file, label, then notification rarely fail at the gate. Those that treat notification as the first serious compliance step are the ones who get caught out.
Catching failures before they happen
Because notification failures almost always originate upstream, the way to avoid them is a pre-launch compliance review a deliberate check, before notification, that every foundation is in place. Is there a valid CPSR with a qualified sign-off? Is there a Responsible Person established in each market of sale? Has every ingredient been confirmed against the annexes? Is the label complete and consistent with the assessment, and is everything correctly reflected in the product information file?
Running this review before reaching the notification stage turns notification into a formality rather than a moment of exposure. Problems found at this point are fixable in an orderly way gathering a missing document, correcting a label, or resolving an ingredient issue rather than surfacing disruptively once a product is on sale or under scrutiny. It is far cheaper to catch a gap deliberately than to have it caught for you.
For brands launching regularly, building this review into a standard pre-launch checklist means every product passes through the same gate. It is the practical embodiment of the principle that clean notification is a by-product of sound earlier work. A short, disciplined review before each launch prevents most of the failures described in this guide.
Not sure whether your product is ready for notification?
Spectra can review your cosmetic compliance before launch, helping identify gaps in your CPSR, Responsible Person setup, ingredients, labelling, testing and documentation before they cause problems.
Frequently asked questions
Why do cosmetic products fail notification?
Usually because a foundational requirement was skipped no valid CPSR, no Responsible Person in the market of sale, a non-compliant ingredient, a non-compliant label, or missing testing — as well as errors in the notification information itself.
Can notification fix a missing CPSR?
No. Notification presupposes the product has been properly assessed. A missing, incomplete or unqualified CPSR is a fundamental gap that notification cannot cure the assessment must be sound first.
Do I need a Responsible Person to notify?
Yes, and it must be established in the market of sale UK-established for Great Britain, EU-established for the EU. Without a valid RP, the product can't be properly notified or lawfully sold.
What if my product contains a non-compliant ingredient?
A prohibited ingredient, or a restricted one used above its limit or outside its conditions, makes the product non-compliant, and notification can't fix it. Such issues should surface in the CPSR; if missed, they force a reformulation.
How does labelling cause notification failure?
Missing mandatory information, unsupportable claims, or a label inconsistent with the CPSR's required warnings are all failures. Since notification usually needs a label image, these often become visible at that stage.
How can I avoid failing notification?
Build compliance in order assessment, file, label, then notification. Passing the notification gate cleanly is a by-product of doing the earlier work properly, so the foundations must be right first.
What's the single most common cause?
Skipping or rushing a foundational step. Notification is the visible gate, but it exposes weaknesses that originate earlier, so the true cause usually lies upstream of the notification itself.
How can I catch these failures before launch?
Run a pre-launch compliance review before notifying: confirm a valid CPSR with qualified sign-off, a Responsible Person in each market, every ingredient checked against the annexes, and a complete label consistent with the assessment. Problems found here are fixable in an orderly way.
References: Regulation (EC) No 1223/2009, Articles 4–5, 10, 13, 19 and Annexes II–VI (EUR-Lex); UK Cosmetics Regulation as retained; OPSS guidance. General information only, not legal advice.