Mon – Sat: 9:00 AM – 7:00 PM IST
Quality

What is serialisation in pharma?

Unique identity at the saleable-unit level — and the aggregation that makes it workable at pallet scale.

In short

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.

Why It Matters

Why this matters in practice

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.

Each saleable pack carries a unique, verifiable identifier
Aggregation links packs to cartons to pallets
Status changes must be reported to the relevant repository
Requirements differ by market and have to be handled per destination
How It Works

How it works in practice

Serial number management

Numbers requested or generated, allocated to a production run, and their state tracked through the process.

Printing and verification

The 2D code is printed and immediately read back. A printed code that cannot be scanned is a defective pack.

Aggregation

Parent-child relationships recorded as packs go into cartons and cartons onto pallets, so a pallet scan resolves to its contents.

Reporting

Commissioning, shipping and status events reported to the repository the destination market requires.

Exception handling

Damaged packs, rejects and reworks all change serial status. These flows cause more operational difficulty than the happy path.

Worked example

A worked example: why aggregation is the hard part

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Treating it as a labelling project

It touches production, warehouse, quality and ERP. Scoping it as printing understates it substantially.

No aggregation

Without it, every pack must be scanned individually at despatch, which is unworkable at volume.

Ignoring rework and returns

Serial status on reworked or returned stock is where most operational exceptions arise.

Market differences assumed uniform

Requirements and repositories differ by market. A single implementation rarely satisfies all destinations.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

Aggregation records which serials sit inside which carton and pallet. It lets a whole pallet be received or despatched by scanning one label instead of every pack.
No. Batch remains the unit for quality and recall decisions; serialisation adds individual pack identity on top of it. Both are maintained.
Regulation, and it differs by market. Different jurisdictions have their own schemes with their own identifiers, reporting systems, deadlines and verification models, and a manufacturer exporting to several markets may need to satisfy several simultaneously. Because the requirements change and vary, confirm the current obligations for each destination market rather than designing to a general description — including this one.
Granularity, and consequently effort. Batch traceability identifies a quantity produced together; serialisation identifies each individual saleable unit. Serialisation is a superset — it gives you batch traceability and more — but it requires unique code generation, printing and verification at line speed, aggregation through packaging levels, and regulatory reporting. It is an order of magnitude more demanding, so it should be driven by obligation rather than ambition.
They need handling explicitly, because a returned pack carries a serial that is already commissioned and already recorded as shipped. Depending on the scheme and the condition, it may be verified and returned to saleable stock, or decommissioned and destroyed. The process must prevent a serial being shipped twice, which is both a regulatory issue and the mechanism counterfeits exploit.
Yes, and it needs designing for rather than discovering. Printing and verifying a unique code on every pack at line speed requires vision systems, reliable printing and rejection handling for unreadable codes. Lines typically need modification and some lose throughput. This is the part of serialisation that is a capital and engineering project rather than a software one, and it is usually the longest lead time in the programme.
Related

Where to read next

Batch traceability and lot genealogy

Read more

Our ePharma CRM

Read more

Quality management in ERP

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.