Unique identity at the saleable-unit level — and the aggregation that makes it workable at pallet scale.
Serialisation assigns a unique identifier to each saleable pharmaceutical pack, encoded in a 2D barcode alongside product code, batch and expiry. Aggregation records which serials are in which carton, and which cartons on which pallet, so an entire pallet can be scanned and accounted for without opening it.
Serialisation exists to keep falsified medicines out of the legitimate supply chain, by making every pack individually identifiable and verifiable. For a manufacturer the implication is operational rather than regulatory: serial numbers have to be generated, applied, verified, aggregated and reported, and every one of those steps touches production lines and systems.
Numbers requested or generated, allocated to a production run, and their state tracked through the process.
The 2D code is printed and immediately read back. A printed code that cannot be scanned is a defective pack.
Parent-child relationships recorded as packs go into cartons and cartons onto pallets, so a pallet scan resolves to its contents.
Commissioning, shipping and status events reported to the repository the destination market requires.
Damaged packs, rejects and reworks all change serial status. These flows cause more operational difficulty than the happy path.
Serialising individual packs is conceptually simple: print a unique code, record it, report it. Most implementations handle this part without great difficulty.
Aggregation is where the effort actually goes. The system must record which serials went into which carton, which cartons onto which pallet, and maintain that hierarchy through every subsequent event. If a carton is opened to remove one damaged pack, the hierarchy must be updated. If a pallet is broken down for a part shipment, the remaining structure must stay accurate. Every one of those events is a place where the parent-child record can drift from physical reality.
The payoff is that a correctly aggregated pallet can be shipped with one scan rather than by reading several hundred individual codes, and a customer can receive it the same way. The cost is that every exception handling process — damage, sampling, returns, repacking — must maintain the hierarchy. Implementations that serialise without properly designing exception handling work until the first damaged carton, which is usually within the first week.
| Term | What it means |
|---|---|
| Serial number | A unique identifier for a single saleable unit. |
| Aggregation | Recording which serials are inside a carton, and which cartons on a pallet. |
| Parent-child | The hierarchical relationship created by aggregation, which lets a pallet be scanned instead of its contents. |
| Commissioning | Activating a serial number as a valid, issued identifier. |
| Decommissioning | Retiring a serial — destroyed, sampled, returned — so it cannot be reused. |
It touches production, warehouse, quality and ERP. Scoping it as printing understates it substantially.
Without it, every pack must be scanned individually at despatch, which is unworkable at volume.
Serial status on reworked or returned stock is where most operational exceptions arise.
Requirements and repositories differ by market. A single implementation rarely satisfies all destinations.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Serialisation coverage | Share of production serialised, against regulatory scope. | |
| Aggregation accuracy | Whether the recorded hierarchy matches physical reality. Verified by sample scanning. | |
| Reporting success rate | Submissions to regulatory systems accepted first time. | |
| Exception events | Damage, repacking, sampling — each of which must maintain the hierarchy. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.