AI export track & trace — five regulatory languages, one single case.

The problem

One line, five regulators, one single person keeping the calendar.

Serialization is no longer optional if you export. The plant already has a printer, an aggregation station and a T&T software vendor. But this is the operational reality you see on the shop floor:

1. Five different hubs — DSCSA wholesaler in the USA, EU Hub for FMD, Chestny Znak for Russia, SNCM ANVISA for Brazil, NMPA for China — each with its own format and its own cadence.
2. An EPCIS event schedule that lives in the head of the regulatory affairs manager. The day they go on holiday, their stand-in prays that nothing fails.
3. Broken parent-child aggregation — a master case with a duplicate that the palletizer tunnel did not notice. It surfaces when the wholesaler complains.
4. A national rule change — one country adds a field, the T&T vendor takes 6 weeks to update, and meanwhile you load it from a spreadsheet and pray.

The problem is not serialization; it is the coordination between five regimes and an MES that only understands its own line. The orchestrator is a person, and the day they fall ill everyone notices.

How it fits the IRIS system

iLEAN does not replace your T&T — it adds the conductor it is missing.

Multi-country T&T is the textbook example of the problem iLEAN solves: data islands + nobody acting on the result in time. iLEAN works as the glue that stitches together your serializer, your aggregation station, your MES, your ERP and the five hubs — without throwing anything away.

Connect talks to each country's hub. The agents orchestrate event by event, with no mental schedule. Edge verifies parent-child on the line. The person signs submissions and exceptions.

The three iLEAN pieces applied to export track & trace:

• Edge — a terminal with computer vision (CNN) over the case packer and the palletizer tunnel. It verifies that the units entering the master case are the ones the packing event declares, reads the pallet SSCC and blocks if the parent-child does not add up. It works with no network.
• Connect — a two-way channel with the national repositories: DSCSA wholesaler over AS2, EU Hub for FMD, Chestny Znak over its cryptographic API, SNCM ANVISA, NMPA. It also captures wholesaler and importer alerts at second zero (messaging app, email, EDI).
• Agent — orchestrates the event schedule (commissioning → packing → shipping → receiving) per country and signs each submission when it is due. When a serial is disputed downstream, it cross-checks the evidence and returns an answer in minutes. The person validates any external communication.

See the full IRIS architecture →

Before and after

Manual multi-country T&T vs. T&T orchestrated with iLEAN

Aspect	Classic T&T + human regulatory affairs	With iLEAN Connect + Agents + Edge
EPCIS event calendar	In the regulatory manager's head	Orchestrated by an agent, signed by a person
Rule change in one country	6 weeks + a temporary spreadsheet	Country profile updated, person validates
Parent-child aggregation	Case with a duplicate found at the customer	On-line verification by Edge vision
Wholesaler claim	3 days on the phone + spreadsheet	Composed evidence in minutes
Regulatory cover	Holidays = risk	24/7 backing from the agent; the person still signs
Repetitive tasks	Manual, human error	Done inside the rings, without touching OT

Impact estimate

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

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

• A plant exporting to 2-3 regimes (typically USA + EU + a third one) with serialization already in place and T&T from a third-party vendor.
• Pilot: one EPCIS event signed on time on the most troublesome regime + Edge verifying aggregation at the case packer. First value expected within a few weeks.
• Indicative payback between 4 and 9 months, driven by: a ≥ 30% reduction in returns caused by faulty T&T + fewer regulatory affairs hours + lower regulatory risk if a recall lands.
• The hard lever: a single avoided market recall pays for the system. The European AI Act also requires human oversight in high-risk systems — iLEAN complies by architecture (the rings).

And the CAIO's reasonable doubt

«What if an agent publishes something wrong to a national repository?» — the three rings solve this by architecture. The agent lives in ring 3 (power); any external publication goes through ring 2 (validation) and only ring 1 launches the signed action. On reliability: hallucination is a problem of free generation, not of anchored tasks such as recontextualising a packing event into EPCIS 2.0 format; the best models have brought the error rate below 1.5% ^[1].

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

See also: GS1 DataMatrix with AI → · See all traceability solutions →