DSCSA DataMatrix for saleable units in the US — a badly printed code is not a defect, it is a verification that bounces back at the wholesaler.

The problem

Printing the DataMatrix is not serializing — verifying that it is right and that it matches the unit is.

In a pharmaceutical plant exporting to the US, the DSCSA flow touches at least three levels that rarely meet at second zero:

1. The corporate serialization system (Adents, Systech, Antares, Tracelink…) that manages the serial pool and the EPCIS repository.
2. The packaging line — cartoner or blister line — with its thermal or laser printer that prints the DataMatrix on every saleable unit.
3. The operator who changes SKU, mounts the new reel, adjusts the print head and signs off the first pack.

The problem is not serialization itself; your corporate system solves that. The problem is the gaps in between: the code printed badly because of head wear, the duplicated serial from a bad resynchronization between system and line, the batch change that never reached the serial pool. The wholesaler detects the problem during saleable unit verification, and the whole shipment comes back. Every rejection is hard cost (reverse logistics, recoding, possible repackaging) plus reputational cost with the wholesaler — which weighs more in the medium term.

How it fits into the IRIS system

iLEAN Tracer does not compete with your serialization system — it seals the gap between the serial pool, the printer and the real unit coming off the belt.

Corporate serialization does its job well: it manages the pool, maintains the EPCIS repository, talks to the chain. What stays exposed is the last metre — the actual print on the capsule carton, the readability verification, the cross-check with the physical unit entering the master case. iLEAN Tracer is the piece of the IRIS category that acts as filler in that last metre, without asking you to change your serialization system or your line.

Edge sees the printed DataMatrix. Connect reads MES, serial pool and badge wherever they are. The agent cross-checks, validates and composes the signed EPCIS event. A person signs — the system does not decide for them.

How the work is split between the iLEAN pieces for this case:

• Edge — a terminal on the cartoner/blister line with an industrial camera. It reads the printed DataMatrix in milliseconds, validates the ANSI/ISO grade, checks that the serial matches the range assigned to the batch. If the code is unreadable, does not match or is duplicated, it triggers the rejector before the master case. It works without network: Edge keeps verifying on cabinet power.
• Connect — captures the manufacturing order from the MES, the serial range reserved in the corporate serialization system, the operator badge at SKU changeover. It also captures what arrives from outside (an email from the US wholesaler about a verification that bounced) at second zero.
• Tracer agent — composes the signed EPCIS event (commission, aggregation, decommission, shipping) with timestamp, batch, location and operator. If tree integrity fails during aggregation (one serial in two master cases at once), it holds and alerts the manager. A person signs — the line does not restart on its own.

See the full IRIS architecture →

Before and after

Classic serialization vs. serialization with iLEAN Tracer verification

Aspect	Serialization system + printer	With iLEAN Tracer
Serial assignment	Central pool → line	Pool + cross-check with MES + operator badge
Print verification	Presence sensor, sometimes ANSI grade	CNN vision + ANSI/ISO grade + hold
Duplicated serial detection	Later verification by the wholesaler	In line, before the master case
Aggregation integrity	Trust in the physical order	Validated by the agent, hold if it fails
Operation without network	n/a — depends on the repository	Edge keeps verifying, events signed locally
Dossier for FDA/inspection	Reconstructed afterwards	Signed EPCIS, self-contained

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 set it out so the committee has an order of magnitude; we refine it during the diagnostic.

• Pharma plant with 1-4 packaging lines (cartoner/blister line) under active DSCSA, with a corporate serialization system already running.
• Tracer pilot on one line (Edge with a DataMatrix camera + integration with MES and serial pool + EPCIS agent). First expected value within a few weeks: the first unit rejected for an unreadable code or an out-of-range serial.
• Indicative payback between 4 and 9 months, depending on the documented frequency of shipments rejected in the US and the average cost of reverse logistics + recoding.
• Expected reduction of rejections in saleable unit verification ≥ 30%. The hard lever is a single shipment rejected at customs avoided.

And the reasonable doubt of the serialization manager

«What if the AI puts noise into the EPCIS event and the repository rejects it?» — hallucination is a problem of free generation, not of anchored tasks. Composing an EPCIS event from MES + pool + camera is exactly an anchored task, where the best models brought the error below 1.5% ^[1]. And even so, the critical part is not signed on its own: Tracer holds the unit and a person signs. The three iLEAN security rings are designed precisely so that the OT network only accepts what has been validated, packaged, signed and approved by a person.

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