Low-migration food ink in rotogravure — one photoinitiator that slipped into SVHC is a recall.

The problem

Three regulatory truths living on three islands.

A correct low-migration ink is the intersection of three pieces of data that, in most plants, each live on their own:

1. Which destination markets the SKU covers — EU, Switzerland, USA, UK. It sits in the ERP, in the customer field, and it almost never reaches the formulation lab in that form.
2. What the current recipe says — which pigments, which resins, which photoinitiators, which additives. The recipe lives in an Excel sheet owned by the formulation lead, with a version history that gets overwritten at the pace of the changes.
3. What the live lists say — REACH SVHC, REACH Annex XVII, CLP, EuPIA exclusion list, Swiss Ordinance A/B. These lists move without telling the plant. A photoinitiator that was free yesterday enters SVHC today.

The technical department knows all this, but it cannot be in three places at once. The supplier reformulates a pigment, sends the new SDS by email, someone files it — and the production recipe takes months to update, if it ever does. The classic system works 99% of the time. That 1% is the one that ends up as a complaint from the packer — and every complaint means product pulled from the shelf, a destroyed batch, brand damage.

How it fits the IRIS system

iLEAN Brain does not replace the ERP or the lab notebook — it seals the cracks between the two.

The low-migration problem is not a lack of information: it is information living on islands and moving out of sync. SVHC is updated twice a year. Suppliers reformulate when it suits them. And the packer demands the low-migration dossier per batch, not per year. iLEAN acts as the putty covering the dead zones between the ERP, the formulation lab and the live regulatory lists, without asking you to change your ERP or redo your lab notebook.

Brain keeps the REACH/CLP, EuPIA and Swiss matrix live per SKU. Connect captures new SDS at second zero. The agent cross-references, blocks and builds the dossier. The person in the technical department signs — never the other way round.

The iLEAN pieces applied to low-migration food ink in rotogravure:

• Connect — captures supplier SDS by email/WhatsApp/portal at second zero. It also captures updates to SVHC, to EuPIA and to the Swiss Ordinance from their official channels. And it captures the effective recipe weighed in the room — the truth of what actually went into the batch, not the theoretical version.
• Brain (Agents + Central) — keeps the matrix live per SKU: which destination markets it covers, which lists apply, which substances are in force, which SDS carry the current version. When the lab loads a new recipe for production, the agent cross-references it against the matrix and, if something does not add up, holds the recipe before it reaches the weighing room. It also builds the low-migration dossier per batch: effective recipe, current SDS, EuPIA/Swiss/REACH declarations, batch test results, OCR photo of the printed reel.
• Edge — optional, on the rotogravure line: OCR of the reel traceability plus visual reading of the ink drum status, so the printed batch data also enters the dossier automatically.

See the full IRIS architecture →

Before and after

Manual compliance vs. a live matrix with iLEAN

Aspect	Excel sheets + SDS in a folder	With iLEAN Brain + Connect + Edge
SVHC update	Manual, weekly, if someone remembers	Captured by Connect on publication day
Reformulated supplier SDS	Email filed away, no automatic cross-check	Cross-referenced with every SKU using the component
Recipe non-compliant for a destination market	Detected when the customer complains	Held before it reaches the weighing room
Low-migration dossier per batch	Rebuilt by hand, weeks	Automatic per batch, ready for the IFS PACsecure auditor
Printed reel traceability	The production lead's sheet	Edge OCR + MES integration
Substance added to SVHC between versions	Discovered at the next routine test	Immediate alert + hold on the affected SKUs

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 plant. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• Maker of inks for flexible food packaging, rotogravure + UV/LED flexo, a portfolio of several hundred SKUs spread across the EU, Switzerland, the UK and export, several pigment and photoinitiator suppliers.
• iLEAN Brain deployment with a REACH/CLP/EuPIA/Swiss matrix per SKU + Connect for SDS and live lists + automatic dossier per batch. First value expected within a few weeks: matrix loaded and the first automatic holds on non-compliant recipes.
• Indicative payback between 4 and 9 months, depending on the historical frequency of supplier reformulations, the number of SKUs affected by SVHC changes and the average cost of a dossier rebuilt by hand for an audit.
• Expected reduction in technical department time spent building dossiers ≥ 30%, recoverable as capacity for new formulation and green reformulation.
• The hard lever is a single non-compliant recipe held in time: batch not destroyed, packer not complaining, brand not damaged.

And the technical lead's reasonable doubt

“What if the AI misreads a regulatory list and blocks a recipe that does comply?” — hallucination is a problem of free generation, not of anchored tasks. In tasks where the AI merely compares a recipe against a published list (cross-referencing CAS numbers against SVHC, against the EuPIA exclusion list, against the Swiss Ordinance), the best models brought error below 1.5% ^[1]. And even so, what is critical is never decided alone: iLEAN holds and the person signs the release. The three safety rings exist precisely for this.

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