In this article
The short answer
The CPNP errors we find most often fall into four groups: the wrong party notified, or nobody is properly appointed as Responsible Person; a field that does not describe the product (category, frame formulation, product name, labelling); a change in the product that never reached the notification; and notifications locked in an account nobody can reach. Each has a specific fix. A changed formula needs an update, which creates a new version. A wrong entry on an unchanged product needs a correction. A discontinued product is marked as no longer manufactured, because a submitted notification cannot be deleted. Fix who is responsible first, then the content, then catch up on changes.
Key takeaways
- Most CPNP errors are maintenance errors: the notification was accurate at launch and the product changed afterwards.
- Settle who the Responsible Person is before touching any field, because every correction has to come from the right account.
- Use an update when the real product changed and a correction when the data was wrong but the product was not. Article 13(7) requires updates without delay.
- A submitted notification cannot be deleted. Discontinued products are flagged as no longer manufactured, and the Product Information File stays for ten years after the last batch.
- The CPNP records the one Member State where the product is first placed on the market. Selling in more EU countries does not mean updating a market list.
- An annual review plus one line in your change control prevents most of these errors.
Last spring a skincare brand asked us to look over nineteen CPNP notifications before a retailer's compliance team got to them. The founder expected a clean bill. We found something in fourteen. None of it was scandalous: a toner still notified under its lab code, a serum whose preservative had changed eighteen months earlier, a body oil whose label image was the designer's draft with a typo the printer had fixed. Individually trivial. Together, the picture of a brand that notified once and never looked again.
That is the normal state of a notification nobody has reviewed. The record is accurate on the day it is made, then the product moves on. Article 13 of Regulation (EC) No 1223/2009 makes the notification the authorities' first view of your product and of who answers for it, so when it no longer matches the shelf, a narrow question about one field turns into a broad one about whether anything in your system is kept up to date. If you need a refresher on the portal itself, start with what the CPNP is.
What follows is the diagnostic we use in audits. It groups the common CPNP errors by type, says what each one risks, and names the tool in the portal that fixes it. Keep your own product list open as you read.
First, know which fix you need: update, correction or a new notification
Half the confusion in CPNP remediation comes from treating every edit the same. The Commission's user guide for Responsible Persons gives you three different tools, and picking the right one keeps the record honest.
- Update. The real product changed: a new formula, a different frame formulation, an ingredient of concern added or removed, a new product name or category. An update creates a new version, and poison centres keep both versions in view, because bottles of the old formula are still in bathroom cabinets. Article 13(7) requires updates without delay when the Article 13(1) information changes.
- Correction. The data was wrong but the product never changed: a typo in the name, a category chosen badly at launch, a contact person who was never right. A correction fixes the record without suggesting there are two products on the market.
- New notification. The change is big enough that it is really a different product, or it was never notified at all, such as a new shade with its own formula.
There is no fourth option called delete. Once you press "Notify", a notification can be updated or corrected but not removed. That shapes several of the fixes below.
Group one: who notified, and who is responsible
Structural errors come first because every later correction has to be made from the right account by the right legal person.
- No Responsible Person properly in place. Article 4(1) only allows a product on the market if a legal or natural person established in the EU is designated as Responsible Person. Without one, the products are not lawfully on sale, however good the notification looks. Appoint one, sign a written mandate if it is a third party, and put its name and address on the label under Article 19.
- The notifier had no standing. We still see notifications made by a consultant, a sales agent or a manufacturer outside the EU, with no mandate behind them. Nobody can then say who the Responsible Person is. Establish the role properly and make sure the notification sits with the Responsible Person.
- Your importer became Responsible Person without anyone deciding it. Under Article 4(5), each importer is the Responsible Person for the imported products it places on the market, unless it designates an EU-established person by written mandate and that person accepts in writing. Many brands discover this only when the importer relationship sours and the importer is holding their notifications. Decide whether you accept that arrangement or want an independent Responsible Person, and document it either way. Our guide on whether you need an EU Responsible Person covers the options.
- No written mandate. If neither side can produce a signed, dated mandate listing the products, the arrangement will not survive an authority's first question. Sign one now.
- Duplicate notifications by two parties. This happens after a change of distributor or Responsible Person. It is untidy rather than fatal, but it shows nobody owns the position. Agree who is responsible today and keep that notification current. Because the other party cannot delete its notification, ask it to enter an end date for its responsibility, or tick "product no longer manufactured" if it no longer supplies the product, so the record shows who holds the product now.
- Assuming the CPNP covers Great Britain. It does not. Products sold in Great Britain need a UK Responsible Person and a notification on the SCPN, while Northern Ireland still follows EU rules and the CPNP. See SCPN vs CPNP and our guide to selling cosmetics in Northern Ireland.
A one-sentence test
For each product, can you name the legal entity that is Responsible Person and point to the document that makes it so? If not, start here rather than with the fields.
Group two: fields that do not describe the product
These errors live in the notification itself. Most are desk corrections that take minutes once you know the right answer. If you are unsure what a field is for, our full CPNP field list explains each one.
| Error | Why it matters | How to fix it |
|---|---|---|
| Product notified under an internal code or development name | Nobody searching by the name on the pack can find it | Correct the product name to the market name on the artwork, in each language version |
| Several different formulas squeezed into one notification | Shades can share a notification only if the notified information fully covers every one of them | Notify separately any shade or scent whose composition differs from what was notified |
| Category chosen for marketing, not function | The category drives which formulation questions the portal asks, so poison centres get the wrong picture | Correct to the category that matches the main function and keep a note of why |
| Frame formulation that no longer fits | A poison centre treating an exposure works from that frame | Pick a frame that genuinely fits, or declare exact concentrations or ranges; the portal requires that route when ingredients exceed the frame's limits |
| pH left out where the portal requires it | The CPNP asks for pH when it is below 3 or above 10, and for hair dyes, which are exactly the cases where it matters clinically | Measure with a calibrated meter (on an aqueous solution for solids, saying so in the notes) and update |
| Ethanol or isopropanol content out of date | The CPNP asks for these in every product and sets update thresholds | Update when the content moves by more than 5 points (if under 30%) or more than 10 points (if 30% or over) |
| Nanomaterial status assumed rather than checked | Article 13(1)(f) needs the nano declaration, and some nanomaterials also need an Article 16 notification six months before sale | Get written particle data from the supplier and act on it |
| Responsible Person address is not where the file is | Article 11(3) requires the Product Information File to be readily accessible at the address on the label | Move the file there, or update the address on the label and in the notification |
| A generic inbox as contact person | Article 13(1)(e) asks for a physical person who can be reached if something goes wrong | Name a real person, with a phone number including the international code |
| Draft artwork or an unreadable photo as the labelling | Article 13(2) asks for the original labelling and, where reasonably legible, a photo of the packaging | Upload the printed artwork as PDF or JPG (2 MB limit for all attachments) or type the label text into the free text box |
| Imported product with no country of origin | The CPNP asks for the country of origin of imported products, one notification per origin | Correct it; for UK-made goods sold in the EU since Brexit, the answer is the United Kingdom |
A word on the market list, because it is the error we are most often asked to fix and it does not exist. The CPNP asks for the one country where the product is first placed on the market, as Article 13(1)(d) sets out. It does not keep a list of every Member State you ship to, and adding Spain to your distribution next year changes nothing in your notification. What can change things is a distributor that translates part of your labelling on its own initiative to sell in its country: under Article 13(3) it makes its own notification.
Group three: the product moved on, the notification did not
This is the biggest group by far. A notification is a description of a product at one moment, and products keep changing.
- Reformulation never updated. A new preservative, a different fragrance, a supplier swap that changed the frame formulation. The safety assessment should have been revised first, then the notification. For ingredients of concern, the CPNP user guide sets numbers: an update is needed when a declared concentration moves by more than 20% of the value previously declared, or when the ingredient enters or leaves the formula.
- New variants never notified. A new shade on the same base can be added to an existing notification if the notified information still covers it. A new scent with a different composition usually cannot.
- Name or category changes. A rebrand that changes the product name is an Article 13(1) change, so update it. The same goes for a change in the Responsible Person's name or address.
- A new CMR classification. Article 13(1)(g) requires the name and CAS or EC number of substances classified as CMR category 1A or 1B. When a reclassification catches an ingredient, it is usually banned under Article 15 unless an exemption applies, so you will be reformulating and updating, not just ticking a box. Our article on CMR reclassification explains the knock-on effects.
- Discontinued products left as if live. Tick "product no longer manufactured", note the date of the last batch, and keep the Product Information File for ten years after that batch, as Article 11(1) requires.
- Label redesigns. Strictly, Article 13(7) covers changes to the Article 13(1) information, and the labelling under Article 13(2) is the original one from first placing. A purely visual refresh is not on that list. In practice we upload the current label anyway, so whoever opens the record sees what is on the shelf, and any change to the name or address on pack is an update in its own right.
Group four: notifications you cannot get into
These sound administrative until the day an authority asks for a change and nobody can log in.
- A single user who left. EU Login accounts are personal, and the Commission's EU Login tutorial asks users not to register with generic or functional mailboxes. The fix is not a shared inbox but at least two named users, ideally both local administrators, and removing leavers on their last day. Our guide to CPNP login and access walks through the roles.
- Notifications held by a former partner. If you are moving to a new Responsible Person, the CPNP has a function called "Copy your products to another Responsible Person". The old Responsible Person runs it, and the copies arrive under the new one as drafts, without labelling, packaging images or contact persons, which the new one completes and submits. If the old partner will not cooperate, the new Responsible Person notifies again from scratch, and the old one should set an end date for its responsibility.
- A consultant's account. If your notifications sit in a consultant's organisation and they are not your Responsible Person, you have an access problem and possibly a standing problem too. Move them to the Responsible Person's organisation.
The order to fix things in
- Settle who is Responsible Person for every product and sign or find the mandates.
- Get access: two named users in the Responsible Person's organisation.
- Move or copy notifications that sit in the wrong account, and agree end dates on any duplicates.
- Check each safety assessment matches the product as sold today. Notification answers should come from the assessment, not the other way round, and selling a product without a valid assessment breaches Article 10.
- Make the content corrections and updates, choosing update or correction for each.
- Notify anything that was never notified and flag anything discontinued.
- Build a register so the same drift does not happen again.
Working out of order wastes effort. Correcting fields in an account you are about to leave, or updating a notification before the assessment behind it is revised, means doing the work twice.
Errors you cannot simply undo
Most CPNP errors are paperwork. A few are not, because the record only reflects a problem in the product or the business.
- Products sold before the safety assessment was finished. The notification can be tidied, but the sales happened. Under Article 5(2), a Responsible Person who has reason to believe a product does not conform must take corrective action straight away, and where there is a risk to human health, inform the competent authorities. Get the assessment done, and take advice on whether stock in the market needs action. Our recall and withdrawal guide sets out the steps.
- A missed Article 16 notification. If a product contains a nanomaterial that is not covered by an entry in Annex IV, V or VI as a colourant, preservative or UV filter, and does not comply with an Annex III entry, it should have been notified to the Commission six months before sale under Article 16. You cannot backdate that window.
- A notifier who has vanished. If a defunct distributor notified your product, its record will stay in the portal. You cannot delete it, so make sure your own notification is correct and complete, and keep a note in the Product Information File explaining the history.
How to audit your own notifications in an afternoon
You do not need software for this. You need the CPNP list, your product list, your mandates and your safety assessments.
- Export or copy the list of notifications from the CPNP.
- Put it next to your current product list, including discontinued lines from the last ten years.
- Mark each product as notified correctly, notified with differences, not notified, or discontinued.
- For every "with differences", write down whether it needs an update or a correction.
- Check the Responsible Person name and address in each notification against the label.
- Check who can log in.
Most brands with a range under thirty products finish this in an afternoon. The fixes may take longer, especially where a safety assessment needs revising first.
How the nineteen-product audit ended
Back to that skincare brand. Of the fourteen findings, nine were corrections that took one sitting: names, two categories, the draft label images. Three were updates following old reformulations, each needing a short addendum to the safety assessment first. One was a new shade that had never been notified. The last was the one that worried the founder. Every product had been notified as not imported, although the whole range was made in the UK and shipped into the EU after Brexit. That made the EU distributor importing it the Responsible Person by law under Article 4(5), while the notifications sat in an account the brand ran under its own name, with no mandate anywhere. The distributor designated an independent EU Responsible Person by written mandate, that person accepted in writing, the notifications were copied across, and the import answer and country of origin (United Kingdom) were corrected throughout.
None of this was visible to the retailer, and none of it would have been a headline. It would have been a slow, awkward month if their compliance team had found it first.
The two habits that stop CPNP errors coming back
First, add one question to your change control: "Does this change affect the notification?" Any formula, supplier, name, category, label address or Responsible Person change gets a yes or no, and every yes gets an update or correction before the product ships. Second, book an annual review: an hour once a year, matching the CPNP list against the product list. Between them they catch nearly everything in this article.
If the review turns up questions you cannot answer, such as whether a change needs an update or a fresh notification, or whether your notifications are in the right hands, it is worth getting a second opinion before you edit. Our pages on why notification is not approval, where your CPSR fits in, CPNP timelines and what CPNP work actually costs fill in the background, and you can ask us for an expert consultation or have us act as your EU Responsible Person.
Related reading on the Phoenix blog
- What is CPNP? EU cosmetic product notification explained
- What information does the CPNP ask for? The full field list
- CPNP login and access: EU Login, SAAS roles and who holds the keys
- CPNP registration: why notification is not approval
- Does the CPNP check product safety? Where your CPSR fits in
- How long does a CPNP notification take?
- CPNP cost: the portal is free, so what are you paying for?
- Cosmetic frame formulations explained
- SCPN vs CPNP: notifying cosmetics in the UK vs EU
- Cosmetic product recall and withdrawal: what to do
Myths we hear
- Selling in more EU countries means updating the notification. One notification covers the EU market. The CPNP asks for the country of first placing on the market, not a list of every country you ship to. A distributor that translates labels on its own initiative makes its own Article 13(3) notification.
- A discontinued product should be deleted from the CPNP. You cannot delete a notification once it is submitted. Tick the "product no longer manufactured" box, and keep the Product Information File for ten years after the last batch was placed on the market.
- Any edit counts as an update. The CPNP separates updates, for a product that really changed, from corrections, for data entered wrongly. Poison centres treat them differently, so choosing the wrong one muddles the record.
- A shared compliance inbox keeps the account safe when staff leave. EU Login accounts are personal, and the Commission asks users not to register with generic mailboxes. Resilience comes from having at least two named users, not from a shared password.
- If the old Responsible Person will not cooperate, the products are lost. A new Responsible Person can always notify the products again. Cooperation only makes it faster, because the old one can copy the notifications across inside the portal.
What to do this week
- Write down the legal entity that is Responsible Person for each product, with the mandate that proves it.
- Export a list of every notification in your CPNP account and match it line by line against your current product list.
- For each match, compare product name, category, frame formulation or composition, and labelling with the product on the shelf today.
- Decide for every difference whether it needs an update (the product changed) or a correction (the data was wrong), and check the safety assessment covers the current version first.
- Tick "product no longer manufactured" on anything discontinued, and record the date of the last batch for your ten-year file retention.
- Make sure at least two named people can log in, and remove anyone who has left.
- Add a "notification impact?" question to your change control and book a yearly review.
Frequently asked questions
What are the most common CPNP errors?
In our audits: products notified under a development name, frame formulations that no longer match the formula, labelling images that are draft artwork or unreadable, reformulations never updated, new variants never notified, and notifications sitting in an account the brand cannot access. Structural problems, such as no written mandate for the Responsible Person, are rarer but more serious.
How do I fix a mistake in a CPNP notification?
Open the notification in the CPNP and choose the right action. If the product itself changed, make an update, which creates a new version. If the product is unchanged and you simply entered something wrong, make a correction. Either way, check the safety assessment matches the product before you submit.
What is the difference between an update and a correction in the CPNP?
An update records a real change to the product, such as a new formula, and creates a new version; poison centres keep both versions in view. A correction fixes data that was wrong from the start while the product on the market stays the same.
Can I delete a CPNP notification?
No. Once a notification is submitted it cannot be deleted, only updated or corrected. For a product you have stopped making, tick "product no longer manufactured". A Responsible Person that hands a product over can also enter an end date for its responsibility.
Do I need to update the CPNP when I start selling in another EU country?
Not as the Responsible Person. The notification records the Member State where the product was first placed on the market, and one notification covers the EU. A distributor that translates part of the labelling on its own initiative must make its own notification under Article 13(3).
What happens to my notifications if I change Responsible Person?
The new Responsible Person must hold the notifications, and its name and address go on the label. If the old one cooperates, it can copy the products across in the CPNP; the copies arrive as drafts without labelling or contact persons, which the new Responsible Person completes. Otherwise the new one notifies from scratch.
Does a label redesign require a CPNP update?
Article 13(7) requires updates when the information in Article 13(1) changes, such as the product name, category, formulation or Responsible Person. A purely visual redesign is not on that list, although many Responsible Persons upload the current label so the record matches the shelf. Any change to the name or address on pack does need an update.
Who can see if my CPNP notification is wrong?
Competent authorities of the Member States can see the full notification, and poison centres see the information they need to treat poisonings. The public cannot. Errors usually come to light during a market surveillance check, a consumer complaint or an exposure call.
Official sources and legislation
- Regulation (EC) No 1223/2009, Article 4: responsible person (as adopted, legislation.gov.uk)
- Regulation (EC) No 1223/2009, Article 5: obligations of responsible persons (as adopted, legislation.gov.uk)
- Regulation (EC) No 1223/2009, Article 10: safety assessment (as adopted, legislation.gov.uk)
- Regulation (EC) No 1223/2009, Article 11: product information file (as adopted, legislation.gov.uk)
- Regulation (EC) No 1223/2009, Article 13: notification (as adopted, legislation.gov.uk)
- Regulation (EC) No 1223/2009, Article 15: CMR substances (as adopted, legislation.gov.uk)
- Regulation (EC) No 1223/2009, Article 16: nanomaterials (as adopted, legislation.gov.uk)
- Regulation (EC) No 1223/2009, Article 19: labelling (as adopted, legislation.gov.uk)
- European Commission: Cosmetics legislation, Regulation (EC) No 1223/2009 and consolidated text
- European Commission: Cosmetic Products Notification Portal (CPNP)
- European Commission: Guide to using CPNP for Responsible Persons and distributors, Article 13 (PDF)
- CPNP frequently asked questions
- CPNP tutorial: creating an EU Login account
Join the conversation