The Form and Function Fields on the CNF, Line by Line

Two fields on the CNF get filled out in about four seconds by most people, and those are exactly the fields I see cause the most trouble six months later. Form and function feel like formalities, dropdown busywork on the way to the part that actually matters, the ingredient list. They're not busywork. They shape how your product gets read by anyone who looks at the notification later, including you.

Why these two fields carry more weight than they look like

The Cosmetic Notification Form isn't a pre-market approval, it's a notification, which means nobody at Health Canada is going to reject your filing because they disagree with your product form selection. But the CNF is a record, and it's the record that a regulator, an auditor, or even a future version of you cross-references against your actual label, your ingredient concentrations, and your marketing claims. If your form and function selections don't match reality, that mismatch is a flag, not a technicality.

The form field

Form describes the physical nature of the product as manufactured and sold, things like cream, lotion, gel, liquid, powder, solid stick, aerosol, or bar. This sounds obvious until you hit an edge case:

• A whipped body butter that's soft and scoopable at room temperature but not pourable. Is it a cream or a solid? Pick based on how it actually behaves and how the CNS categories are defined, not on what sounds closest to your marketing copy.
• A solid shampoo bar. It's a solid form even though its function is identical to a liquid shampoo, and treating it as "liquid because it's shampoo" creates a mismatch between form and function that doesn't reflect the product.
• A liquid that separates into layers and needs shaking. Still a liquid form, but worth noting in your own internal records since it affects how you'd describe stability, not the CNF form field itself.

Get the form field wrong and the immediate consequence is usually small, a slightly odd-looking notification. The larger risk is that it's one more inconsistency for a reviewer to notice if your product ever draws closer attention for another reason.

The function field

Function describes what the product does, its cosmetic purpose: moisturizing, cleansing, hair conditioning, color cosmetic, sun protection styling as a claim (careful here), and so on. This is where the classification stakes get higher, because function shades into the soap-versus-cosmetic and cosmetic-versus-drug lines.

A few things worth remembering:

• If your product's function as described edges into therapeutic territory, anti-acne, anti-dandruff, antiperspirant, that's often a drug function, not a cosmetic one, and drugs are regulated on an entirely different track. Fluoride toothpaste is a classic example of a product that looks like a cosmetic on the shelf but is functionally a drug.
• "True soap," meaning alkali salts of fatty acids sold purely on a cleansing claim, can sit outside standard cosmetic treatment. The moment you add a cosmetic-style function claim, moisturizing, softening, anti-aging, it's a cosmetic, and the function field needs to reflect that shift honestly.
• Multi-function products, a wash that also claims to condition hair, need their function field (and the rest of the notification) to reflect every relevant function, not just the primary one you'd put on packaging.

A quick reference table

Product example	Likely form	Likely function	Watch for
Solid shampoo bar	Solid	Cleansing / hair conditioning	Don't classify as liquid out of habit
Whipped body butter	Cream or solid, depending on texture	Moisturizing	Texture-dependent, check current CNS definitions
Bar soap with added "moisturizing" claim	Solid	Cleansing plus moisturizing (cosmetic, not just soap)	Claim triggers full cosmetic treatment
Antiperspirant stick	Solid	Likely a drug function, not cosmetic	May fall outside cosmetic notification entirely
Liquid castile-style soap, no cosmetic claims	Liquid	Cleansing only	Confirm it truly stays in "true soap" territory

Where the downstream issues actually show up

Misclassified form and function fields rarely cause a problem the day you file. They cause problems later: when you file an amendment and the system flags an inconsistency with the original notification, when a retailer's compliance team cross-checks your CNF against your label and function claims don't line up, or when you're trying to reuse a past filing as a template for a new product variant and realize the original classification doesn't actually describe what you're selling.

Getting it right the first time

• Base form on physical state at time of sale, not on how the product is marketed.
• Base function on every claim your label and marketing actually make, not just the headline one.
• Watch for claims that tip a product from cosmetic into drug territory, and stop before filing a CNF for something that needs a different regulatory path entirely.
• If you're filing an amendment later, check that your original form and function selections still make sense for the updated product, and update them if the formula or claims changed.

Cosmetic Comply's filing workflow prompts for these classification details as part of the notification process itself, and it lets you duplicate a past filing for a minor variant, which helps a lot when you're trying to keep form and function consistent across a whole product line instead of re-deriving the logic every time.