One Base, Many Shades: How Many CNFs Do You File
A single base formula sold in five shades or three scents raises a real question: one Cosmetic Notification Form, or several?
A lip balm line with the same wax and oil base sold in six flavors. A pressed powder foundation in twelve shades built off one identical formula, differing only by the iron oxide blend. A lotion sold unscented and in two fragrance options. Every maker who builds a product line this way eventually asks the same question: does each variant need its own Cosmetic Notification Form, or does the base formula cover the whole family?
The short answer
Each distinct formula generally needs its own notification. What counts as a distinct formula, though, is exactly where the nuance lives, and it comes down to whether the change between variants alters the actual ingredient composition being reviewed, not just how the product looks or smells on the outside.
If shade A and shade B share the exact same base and differ only in which color additive is used and at what level, those are, in ingredient terms, two different formulas, because the ingredient list itself is different between them, even if every other ingredient and percentage is identical. The same logic applies to scent variants: an unscented lotion and a lavender-scented version of that same lotion are two different ingredient lists once you account for the fragrance material added to one and not the other.
Why this isn't just bureaucratic box-checking
The whole point of a notification is that the ingredients get properly declared with concentrations and screened against the Cosmetic Ingredient Hotlist. A color additive used in a foundation shade and a fragrance material used in a scented variant are both themselves subject to their own restrictions and, in the case of fragrance, allergen disclosure obligations. If one shade in a twelve-shade line uses a colorant at a level or type the others don't, that shade's specific ingredient list is what needs to be reviewed on its own terms. Bundling twelve different ingredient lists under one notification defeats the purpose of the notification actually reflecting what is in each product being sold.
What does NOT necessarily require a brand new filing from scratch
This is the part that saves makers real time. If your shades or scents share a common base and only vary in a small, well-defined way, you are not starting from zero for each one. This is precisely the kind of minor variant situation where duplicating a previous filing and adjusting only the piece that changed, the colorant, the fragrance, the specific percentage, is both appropriate and efficient. You are not reinventing the whole ingredient list and safety picture each time, you are carrying forward everything that is genuinely unchanged and updating only what actually differs.
| Scenario | Typical approach |
|---|---|
| Same base, different shade via colorant | Separate notification per shade, but built from the shared base as a duplicate with the colorant swapped |
| Same base, different fragrance | Separate notification per scent, since the fragrance ingredient list differs |
| Same base, unscented vs. scented version | Separate notifications, since the fragrance materials are present in one and absent in the other |
| True duplicate, no ingredient change, different pack size only | Generally still tied to the same product identity, but always confirm current guidance if you are unsure whether packaging changes alone trigger a new filing |
Keeping a shade or scent line organized
The practical failure mode here is not usually filing too many notifications. It's losing track of which notification and Cosmetic Notification number belongs to which variant once you have eight or ten of them in a product line. A few habits help:
- Keep a master spreadsheet mapping each shade or scent name to its own CN number, filing date, and the specific ingredient that differs from the base.
- When you introduce a new shade or scent later, treat it the same way, a new variant of the base, filed as its own notification, referencing the shared formula.
- If you ever discontinue one shade in a line but keep the others active, remember discontinuations are filed individually too, tied to the specific product that is being withdrawn, not the whole line.
- When a shared base ingredient changes for the entire line, for instance you reformulate the emollient system across all twelve shades, that is an amendment that needs to be filed for each affected variant, not just the one you happened to be testing.
Product lines built on one shared base are extremely common and entirely manageable from a filing standpoint once you treat each variant as its own small notification built efficiently off a shared foundation. Cosmetic Comply supports exactly this pattern by letting you duplicate a past filing for a minor variant, so a new shade or scent doesn't mean rebuilding the ingredient matching and screening from scratch every single time.
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
How to file a Cosmetic Notification Form in Canada
A plain walkthrough of the CNF, from what Health Canada actually wants to the CN number that lands in your inbox, plus the 10 day deadline everyone trips on.
Same Formula, Two Brand Names: One CNF or Two
Whether an identical formula sold under two different brand names needs its own separate Cosmetic Notification Form.
Do Free Samples and In Store Testers Need a CNF
Whether giveaway samples, deluxe minis, and retail testers count as a sale that triggers Canada's Cosmetic Notification requirement.
Listing Colour Additives and Pigments on a CNF
How CI numbers, mica, and other colourants get declared on a Health Canada Cosmetic Notification Form, and where restrictions hide.