What Triggers a Post-Introduction Declaration in AICIS

You reported an ingredient introduction to AICIS, moved on, and now something in your workflow says a declaration is due. If that sounds like it should already be finished business, you're not alone in being surprised by it. AICIS structures things differently from a one-and-done cosmetic notification, and the reporting doesn't always stop at the initial introduction.

AICIS works differently from a per-product filing

Australia doesn't ask you to notify each finished cosmetic product the way Health Canada's CNF does. Instead, AICIS regulates the ingredients themselves as industrial chemicals, introduced into Australia through defined categories, and tracked against an Inventory of chemicals already known to the system. Your obligations depend on which introduction category your ingredient falls into and whether it's already listed.

Because the system is chemical-based rather than product-based, the same ingredient can carry different reporting duties depending on volume, existing inventory status, and how it was categorized when first introduced.

Why some introductions need a later declaration

Certain introduction categories are conditional on ongoing information, not just the initial act of bringing the chemical in. If your ingredient was introduced under a category with reporting conditions attached, whether tied to volume thresholds, categorization rules, or a time-based reporting cycle, that category can require a follow-up declaration after the fact confirming what actually happened with the introduction. This is the mechanism that surprises makers: they treat the initial report as the finish line, when for some categories it's actually the start of an ongoing obligation.

This is exactly the kind of category-specific detail where the safest move is checking the current AICIS category rules directly, because the specific triggers and reporting windows tied to each introduction category are something AICIS documents in detail and updates from time to time. Treat the general shape here as a heads-up to go look, not as the final word on your specific category.

What tends to make makers miss it

• Assuming it's a one-time filing. Small cosmetic brands are used to Canada's one-shot CNF model and project that expectation onto AICIS without realizing the ingredient-based system works differently.
• Not tracking which introduction category was used. If you didn't record which category applied when you first introduced the ingredient, you won't know later whether a declaration condition attaches to it.
• Changing suppliers without re-checking. A new supplier for the "same" ingredient can mean a different actual substance, a different existing Inventory status, or a different introduction history, none of which carries over automatically.
• Volume creep. An ingredient introduced under a low-volume category can trigger different obligations once your actual usage grows past what the category assumed.

A practical way to stay ahead of it

Keep a simple internal record, ingredient by ingredient, of the AICIS introduction category used, the date of introduction, and any conditions or reporting windows attached to that category. This is the same instinct that serves you well with Health Canada's CNF amendments and discontinuations: don't rely on memory for what you filed and when. Revisit that record at least once a year, particularly for ingredients where volume has grown or where you've changed suppliers.

Where this fits into your bigger compliance picture

If you're selling into Australia and Canada, or planning to expand into both, it helps to understand that "cosmetic compliance" isn't one shape everywhere. Health Canada wants a per-product notification with an INCI ingredient list. AICIS wants ingredient-level introduction tracking against an industrial chemicals framework. The EU wants a Responsible Person, a Product Information File, and a signed safety report. None of these map cleanly onto each other, which is exactly why makers expanding across markets get tripped up assuming one market's paperwork logic applies to the next.

Cosmetic Comply is live for Canada's CNF process today, with the US, EU, and Australia on the roadmap. If AICIS is on your radar, the same instinct that helps with a CNF filing, keeping your ingredient list, INCI mapping, and filing history in one place instead of scattered across emails and supplier PDFs, is worth building now even before your Australian filing tool is in hand.