Labeling the 26 fragrance allergens with AI — Annex III of EU Regulation 1223/2009, cross-checked against label and BOM.

The problem

The allergen information passes through four pairs of hands before it reaches the label.

Compliance with Annex III of EU Regulation 1223/2009 does not fail because people do not know the rule — it fails because of a broken information chain:

1. The fragrance supplier sends the composition and allergen percentages in a PDF attached to an email. Every time they adjust the formula (an ingredient change, a reformulation driven by an IFRA restriction), they send a new PDF that can take days to reach regulatory.
2. Formulation calculates the allergen's final concentration in the product from the batch's fragrance percentage — if the batch's percentage went up or down for an intensity adjustment, the calculation changes, and so does the INCI list.
3. Regulatory updates the product's INCI list. If the supplier's new composition arrived after the current batch's labels were printed, there is a mismatch.
4. Packaging and the print house produce the label with the version current in their system, which is not always regulatory's latest.

The typical result of the broken chain: a batch packed with an above-threshold allergen not declared in the INCI. The claim arrives as Safety Gate (formerly RAPEX), a recall from the EU market, and brand damage. The classic system works 99% of the time. That 1% is what ends up on the consumer portal — and each case costs time and money that are never recovered.

How it fits the IRIS system

iLEAN Tracer seals the information flow between supplier, formula and label.

The Annex III problem is not a missing procedure — it is information scattered across four pairs of hands and four systems that do not talk to each other at second zero. iLEAN acts as the putty that seals those cracks, without asking you to change your PLM, your ERP, your regulatory system or the print house.

Tracer reads the supplier's PDF as soon as it arrives. It cross-checks it against the batch formula and against the printed label that Edge captures in line. If an allergen exceeds the threshold and is not in the INCI, the batch is held. The regulatory lead signs.

The specific piece for this pain:

• iLEAN Tracer — iLEAN's rule-driven traceability layer, specialized in cosmetic compliance. It keeps the Annex III table versioned by market (EU, UK, others), receives the fragrance supplier's composition as soon as it arrives (Connect reads the attachment on the buyer's email, without asking anyone to forward anything), calculates the allergen's final concentration per batch and compares it against the current INCI list.
• iLEAN Connect — captures the supplier's email at second zero, reads the attached PDF/Excel with the fragrance composition, extracts allergens and percentages; and captures the BOM and the fragrance percentage from the ERP/PLM. Bidirectional: if a new allergen comes in through a delegated regulation, the agent prepares the notice back to the supplier through the same channel — the person signs.
• iLEAN Edge — a vision-equipped terminal on the packing line. It reads the INCI printed on the label (OCR + CNN) and cross-checks it against the list calculated by Tracer. If an above-threshold allergen is missing, it holds the batch before the packaging closes. It works without a network.

See the full IRIS architecture →

Before and after

Regulatory management via Excel vs. automatic cross-checking with iLEAN Tracer

Aspect	Excel + PLM + manual label control	With iLEAN Tracer + Connect + Edge
Arrival of the supplier's composition	Manual email, forwarded to regulatory	Automatic capture of the PDF at second zero
INCI recalculation after a fragrance % change	Manual, risk of mismatch with the batch in progress	Automatic the moment the BOM changes
Printed label verification	Visual, by sample at the start of the batch	Edge reads and cross-checks 100% of the batch
Versions of the Annex III list	A PDF in the regulatory folder	A living table, versioned by market
CPNP file / product dossier	Rebuilt when the inspector calls	Built batch by batch, ready to hand over
Safety Gate / RAPEX risk	Post-market detection	Hold before packing

Impact estimate

Impact estimate for your plant — to be validated with your numbers.

The block below is an estimate to be validated with the specific data of your regulatory operation. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• A cosmetics brand with a multi-market fragranced range (EU, UK, international), 50-200 live SKUs, 1-3 main fragrance suppliers.
• Tracer + Connect pilot on the supplier → formulation → regulatory flow + Edge on the packing line of the main fragranced range. First value expected within a few weeks (the capture of the supplier's PDF starts delivering value from day one).
• Indicative payback between 4 and 9 months, depending on the annual number of fragrance composition changes and the average regulatory management cost per SKU.
• The hard lever is the avoided cost of a single Safety Gate recall (product pulled from the shelf, label reprinting, brand damage). One avoided recall pays for the pilot.

And the regulatory lead's reasonable doubt

"What if the AI misreads the supplier's PDF and miscalculates an allergen?" — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI merely recontextualizes a piece of data from one system to another (reading the PDF, extracting the allergen percentage, calculating the final concentration with the BOM), the best models brought error below 1.5% ^[1]. And even so, what is critical is never decided alone: Tracer proposes the calculated INCI list, the regulatory lead signs. The three safety rings exist precisely for this.

^[1] OpenAI paper “Why Language Models Hallucinate”, 2025 — on the reliability of AI in anchored tasks.