Batch traceability for medicines and supplements, without a full serialisation programme
Full track and trace is a multi year programme. Unit level verification gets you most of the recall and authenticity benefit in weeks, and it is what patients can actually use.
Product·29 August 2026·7 min read
In medicines and supplements, a counterfeit is not a lost sale. It is a patient taking something unknown, and a brand carrying the consequences. That raises the stakes enough that most manufacturers eventually look at serialisation, see the price and the timeline, and put the file back on the shelf.
There is a useful middle step that gets deployed in weeks rather than years.
What full serialisation asks of you
Proper track and trace means every unit is serialised, aggregated into cartons and pallets, and scanned at every handover, with each party reporting to a shared system. It requires line level hardware, integration with distributors, and cooperation from everyone downstream. In markets where distribution is fragmented, getting that cooperation is the hard part, not the technology.
The result is genuinely valuable, but you cannot start there. You can start with identity.
Unit level verification, without the chain
Give every pack a unique, unguessable code tied to its batch, print it as a QR label, and let anyone verify it: patient, pharmacist, hospital storekeeper, or your own field team. Nobody downstream has to install anything or agree to anything for it to work.
You immediately gain three things a batch number printed on a carton never gave you: the pack becomes individually identifiable, the first check is recorded, and repeat checks of the same code become visible as a signal.
What it does for a recall
That is the difference between a recall announcement and a recall you can evidence.
- You can enumerate exactly which codes belong to the affected batch.
- You can see how many of them were verified, which tells you roughly how much of the batch reached consumers.
- You can invalidate the range so that any later scan warns instead of reassuring.
- You can export the record for your quality file and for the regulator, rather than reconstructing it from delivery notes.
Pharmacists are the underrated user
Consumer scanning gets the attention, but the pharmacist and the hospital storekeeper are the highest value scanners in the chain. They handle volume, they are professionally motivated to avoid fakes, and they check on receipt rather than after consumption.
Design for them. Codes readable under shop lighting, a verification page that loads on a weak connection, and an answer that does not require reading a paragraph.
Practical constraints worth planning for
- Apply codes after quality control, never before, so rejected stock never carries live codes.
- Keep label placement consistent across SKUs so scanning becomes habit rather than a hunt.
- Do not put the code where the pack is opened, or the first thing the patient does is destroy it.
- Print quality matters more than code density. A slightly larger code that scans first time beats a dense one that fails in a dim pharmacy.
- Keep the code space enormous and random, so guessing a valid code is impractical.
Where the software fits
BrandProtection generates codes in bulk against real products and batches, produces print-ready QR labels, runs the verification portal on your own domain, and keeps the scan record with analytics and CSV export for your quality and audit files. It is deliberately narrow: it does identity and verification well, and leaves your ERP to be your ERP.
If you later invest in full aggregation and chain reporting, the unit identities you have been issuing all along are the foundation that programme needs anyway.
Do not let the size of a serialisation programme stop you from doing the part that protects patients now. Identity per pack, verification in one scan, and an exportable record cover most of the real world risk, and they are a normal quarter of work rather than a corporate initiative.
Frequently asked questions
What is the difference between serialisation and verification?
Serialisation assigns a unique identity to each saleable unit and tracks its movement through the supply chain, which requires every party to scan and report. Verification assigns the identity and lets anyone check it, without requiring the whole chain to participate. Verification is far faster to deploy and delivers the authenticity and recall benefits; full track and trace adds custody visibility at a much higher cost.
How does unit level coding help in a recall?
It turns a recall from a broadcast into a list. If codes are issued per batch, you know exactly which codes belong to the affected batch, how many were verified, and roughly where. You can invalidate that range so any later scan returns a warning instead of a green tick, which reaches the patient holding the pack rather than only the distributor.
Does this satisfy regulatory requirements?
Treat it as a control that supports your compliance position rather than a substitute for whatever your regulator specifically mandates. Requirements differ by market and change over time, so confirm the current rules with your regulatory affairs advisor. What unit level verification reliably gives you is documented batch identity, a scan record and exportable evidence.