Keeping INCI and CAS Data Organized Across 40 Products

Somewhere around product fifteen or twenty, a lot of cosmetic brands hit the same wall. Not a formulation wall, an admin wall. You've researched the INCI name and CAS number for shea butter four separate times because three different team members formulated three different products and nobody checked what the last person already found. Multiply that across forty SKUs and you've got a mess of spreadsheets, each one slightly different, none of them the source of truth.

Why this happens even to careful brands

It's not carelessness, it's structure. Most small brands build ingredient data product by product, because that's how the work arrives: someone finalizes a lip balm formula, looks up its five ingredients, files the notification, moves on to the next product. There's no natural moment where someone steps back and says "let's build one list of every ingredient we've ever used, once, correctly."

The result is duplication with drift. Ingredient data isn't static, supplier documentation gets updated, a botanical extract's CAS status gets clarified, and if the same ingredient exists in six different product-level lists, only one of which gets updated when new information comes in, you've got five stale records sitting in old files that someone might reuse for the next product without realizing they're outdated.

What a single ingredient library actually looks like

The concept is simple: one master table, every ingredient your brand has ever used or is considering, with a fixed set of fields that never has to be re-derived once populated.

Field	Why it's there
Trade/supplier name	What shows up on your supplier's invoice or spec sheet
INCI name	The standardized name that goes on the label and the filing
CAS number (if applicable)	Unique chemical identifier, some extracts won't have one
Supplier & source	So you can trace back if a question comes up later
Blend components (if applicable)	For supplier blends, list what's inside and at what ratio
Known restrictions	Any concentration limit or market-specific flag you've already researched
Last verified date	So stale entries are visible, not hidden

Once shea butter (Butyrospermum Parkii Butter) is in this table with its CAS number and any relevant notes, every future product that uses shea butter pulls from the same verified row. Nobody re-researches it. Nobody accidentally uses a slightly different INCI spelling that creates label inconsistency across your catalog.

Handling supplier blends in the library

Blends deserve their own treatment in the library because they're the most common source of filing errors. A supplier's "moisturizing complex" or "preservative blend" needs to be broken into its actual INCI components at the library level, with the ratio documented, so that when a new product uses 3% of that blend, whoever's filing it can immediately calculate that, say, a preservative component present at 20% of the blend is really 0.6% of the finished product. Do that calculation once, document the blend's breakdown permanently, and every future product using that same blend skips the re-derivation entirely.

Why this compounds as you grow

At five products, redundant lookups cost you an afternoon here and there. At forty, they cost real money, both in research time and in the risk of a filing error slipping through because someone typed an INCI name slightly differently than last time, or missed that an ingredient sits close to a concentration limit in one market but not another. Regulatory reviewers and notification systems care about exact INCI matching; small inconsistencies (Aqua versus Water, or a missing hyphen in a chemical name) create friction even when they're not safety issues.

There's also a practical business reason to keep this clean: due diligence. If you're raising money, seeking a wholesale partnership, or eventually selling the brand, a buyer or partner asking "show me your ingredient compliance records" gets a very different answer from a brand with one clean library versus one with forty scattered spreadsheets of varying vintage.

Getting started without a full rebuild

You don't need to reconstruct your entire catalog's ingredient data in one sitting. Start the library with your next filing, current or new product, and backfill previous products opportunistically, whenever you touch one for an amendment or a reformulation anyway. Within a year of consistent discipline, most of your catalog will have flowed through the library naturally.

This is essentially the structural problem Cosmetic Comply is built to solve at the platform level: every ingredient you submit gets matched to its INCI name and CAS number once, supplier blends get expanded into their real components with percentages carried through, and that mapping persists so the next product reusing the same ingredient doesn't start from zero. Filing an amendment or duplicating a past filing for a minor variant works the same way, building on what's already been verified rather than re-litigating it.