Notifying a Lipstick Range With Many Shades on CPNP

Twenty lipstick shades and one base formula. That's the situation that makes new brands nervous about the CPNP portal, because it looks like twenty separate notifications waiting to happen. In practice, the EU system is built around exactly this scenario, and understanding how a "range" is treated saves a lot of duplicated paperwork.

The logic behind grouping shades

Under Regulation (EC) No 1223/2009, notification through the CPNP portal is tied to the product as placed on the market, and the EU's framework specifically anticipates that a single base formula can be sold in multiple shades using different colorants or different concentrations of the same colorants. Where the products share a common base formula and differ only in colorant composition, they can typically be notified as a single frame formulation, sometimes called a range or family notification, rather than twenty independent product notifications.

The practical logic is straightforward: your Product Information File and Cosmetic Product Safety Report cover the shared base and the safety profile of the range of colorants used across shades, rather than treating each lipstick as if it were a chemically unrelated product. This is a significant time and cost saver for color cosmetics brands, where shade proliferation is the entire business model.

What actually has to be true for grouping to work

Grouping isn't automatic just because you call it a "collection" in your marketing. The base formula, the emollients, waxes, preservatives, and everything besides the color system, needs to be genuinely the same across the shades in the group. If shade 12 uses a completely different wax system because it needed more slip for a metallic finish, that's arguably not the same base formula anymore, and it may need to sit outside the group or get its own safety assessment attention.

The colorant differences need to stay within the range your Cosmetic Product Safety Report actually evaluated. If your safety assessor signed off on a colorant palette of, say, ten approved colorants used in varying combinations and concentrations, every shade in the notified range needs to draw only from that assessed palette. Introduce a colorant that wasn't part of the original safety assessment and you've created a product that falls outside what was notified, which means new safety assessment work, not just a quick portal update.

When shades need to be split out

A few situations reliably force individual notifications rather than one grouped filing:

• A shade uses a colorant or concentration outside the assessed range. If the safety assessor never evaluated it, it can't ride on the group's CPSR.
• The base formula genuinely changes. A different preservative system, a shift from a cream lipstick base to a liquid matte base, or a different SPF-adjacent additive all break the "same base" premise.
• A shade is reformulated later for performance or supply reasons. If you swap an ingredient in shade 7 only, six months after launch, that shade now needs its own safety review even if it stays in the same numbered collection on your website.
• Regional colorant restrictions differ. Some colorants approved in one shade combination may not be approved for use in certain product types (lip products often have their own restricted list nuances), so cross-check the colorant restrictions specific to lip products, not just the general list.

A quick reference for what travels together

Element	Can vary within a grouped range	Needs individual review if changed
Colorant type/shade	Yes, within the CPSR-assessed palette	Yes, if a new colorant is introduced
Colorant concentration	Yes, within assessed limits	Yes, if it exceeds assessed range
Base formula (waxes, emollients)	No, must stay consistent	Always, if the base changes
Preservative system	No, must stay consistent	Always, if the preservative changes
Packaging/pack size	Generally yes	Rarely triggers new notification alone

The paperwork that actually backs this up

Whichever way you group or split, someone still has to appoint a Responsible Person established in the EU, keep the Product Information File current for every notified product or range, and have a signed Cosmetic Product Safety Report from a qualified safety assessor. The grouping decision affects how much duplicate assessment work you're doing, not whether the underlying safety documentation obligations exist.

If you're mapping out a large shade range before you approach CPNP, it helps to lay out every SKU's full ingredient list side by side first, so you can see at a glance which shades genuinely share a base and which ones quietly drifted. Cosmetic Comply's ingredient matching makes that comparison fast across a large range, though the EU side of the platform is still on its way, with Canada live today.