Skip to content

Compliance: allergens, shelf life, INCI

The Compliance & data quality section of each ingredient page holds the facts you need once a recipe leaves the kitchen: which allergens it brings in, how long it keeps, how dense it is. Fill them once per ingredient and they follow the ingredient into recipe sheets and declarations.

Field What it holds
Allergens Tags such as gluten, milk, egg
Shelf life (days) How long the raw ingredient keeps
Density Grams per ml, for volume to mass conversion
Nutrition (per 100 g/ml) Facts per 100 g, e.g. energy_kcal, protein_g
INCI name The cosmetic nomenclature, e.g. Olea Europaea Fruit Oil
CAS number The registry number, for safety data sheets
Country of origin Two-letter code, e.g. FR
Supplier reference Your vendor’s own code for this ingredient
Declare by what stays in the product For added water: labels list it by its weight in the finished product

Click Edit on the section to change any of them.

Labeled as is not here. It is the name your labels declare, Raspberries for Frozen raspberries, so it sits under the ingredient’s own name in the Edit dialog at the top of the page. Its other languages live on the Translations page with every other word your labels print.

Allergens roll up from ingredients into the recipes that use them, so a recipe sheet can state what a batch contains without you re-checking fifty records. Density is load-bearing: formula math runs in grams, and density is the bridge whenever you measure by volume (mass-based formulas explains why). Shelf life documents how long the ingredient keeps, which is worth having on the record when you log delivery lots with expiry dates.

Turn on Declare by what stays in the product for the water you add to a batch. An EU label lists added water by what is left of it in the finished product, the batch’s output minus every other ingredient, and every batch with an output recorded then declares it that way. At 5% or less of the product, the list may leave it out, and you decide that on each batch’s label. Label data shows both.

A US label lists water by what went in, like any other ingredient, so leave the switch off if your labels are for the US. The card shows an Added water row only while the switch is on.

Each field carries a verification state: Human-verified or Unverified. Unverified values are excluded from labels and compliance until a person confirms them. The distinction exists because values can arrive from AI enrichment or bulk imports: convenient, but nothing to print on a jar unchecked. Editing a field yourself, or accepting an AI suggestion with Accept & verify, marks it verified.

The same section serves a skincare bench. Record the density of your oils and butters (formula percentages need mass), tag the fragrance allergens (linalool, limonene, citral), and give each ingredient its INCI name (“Butyrospermum Parkii Butter”) beside the name you call it by on the shelf.

That field is what a batch’s label data builds a cosmetic declaration from: a flat INCI list in descending order of what went in. The INCI option stays unavailable until every ingredient over 1% of the batch carries a name, and it tells you which ones are missing.

Why this matters to a cosmetics maker, in one page: cosmetics manufacturing software.

Nutrition figures are per 100 g of the ingredient, keyed by name: energy_kcal, fat_g, saturated_fat_g, carbohydrate_g, sugars_g, protein_g, salt_g, sodium_mg. A batch’s nutrition panel sums them across what went in, so when an ingredient has nothing recorded, the panel says it is incomplete. A zero you record (water, salt) counts as data; a blank does not.

Why this matters to a food maker, in one page: food manufacturing software.