Serialization gets talked about as if it were the natural next step for every brand. For some products it clearly is. For many others, it adds cost and complexity without a matching benefit. This article gives you an honest way to decide.
For the basics — what serialization is and how a serial lives through its lifecycle — start with what is product serialization?
Start from the decision, not the technology
Serialization gives each unit its own identity. That is only useful if someone will act on the difference between two units of the same product. So the first question is not "should we serialize?" but "what would we do with unit-level identity that we cannot do today?"
Good answers sound specific:
- "We need to credit loyalty points once per pack, not once per product."
- "We need to know when the same code is scanned in two cities on the same day."
- "A regulator requires a unique identifier on each pack of this product."
- "We need to recall units 4,000 to 9,000 of a batch, not the whole batch."
Weak answers sound like "it's the future" or "our competitor is doing it". If you can't name the decision, a GTIN with batch and expiry is probably enough for now.
The five factors
1. Value per unit
Serialization has a cost per unit (data generation, printing, inspection, storage) and a fixed cost (line equipment, integration, process change). On a premium fragrance or an electrical appliance, that cost is a small fraction of the unit price. On a low-cost sachet sold by the million, it can be a meaningful share of margin. Value per unit is not decisive alone, but it sets how much the other factors need to be worth.
2. Regulation
In some sectors, rules decide for you, and pharmaceuticals are the clearest example. India, for instance, requires a bar code or QR code holding defined data elements — including a unique product identification code — on the labels of 300 listed drug brands, with the manufacturer setting that code under its own procedures. Read any such rule carefully: it may specify data elements without requiring GS1 standards or a unique serial on every pack, and it applies to the listed products, not to consumer goods generally.
Outside regulated sectors, there is usually no legal requirement to serialize.
3. Counterfeiting and diversion risk
If counterfeits or grey-market diversion are costing you sales or reputation, unit-level identity is a useful ingredient. Unique, random serials let a server spot codes scanned in impossible places or impossible numbers. Be clear about what this does and does not do: serialization makes copying detectable, not impossible. See how serialized QR codes support anti-counterfeit programmes.
4. Loyalty, warranty and engagement
Any programme that rewards or registers one physical unit needs unit identity. Without it, a single photographed code can be claimed endlessly. This is often the most commercially compelling reason for consumer and channel-partner brands — electricians scanning cable boxes, painters scanning paint tins, consumers registering an appliance warranty. See how product identity can support loyalty and rewards.
5. The cost of printing variable data
This is the factor most often underestimated. Printing the same artwork on every pack is easy. Printing different data on every pack, at line speed, and confirming each one, is a different operation:
- the coder must receive and print unique data for every unit without slowing the line;
- a camera or reader must check each code and reject failures;
- serials must flow from a system of record and back, with an audit trail;
- someone must handle rejects, reprints and unused serials.
If your current lines only print a batch and date, assess them before you commit — see how to evaluate whether your printer can handle serialized 2D codes.
A simple decision grid
| Your situation | Typical answer |
|---|---|
| Regulation requires a unique identifier on each unit of this product | Serialize, to the regulation's specification |
| High value per unit and known counterfeit or diversion problem | Strong case to serialize |
| Per-unit loyalty, rewards or warranty registration planned | Serialize the products in the programme |
| Recall precision matters but units are low-value | Batch and expiry in a 2D code; consider carton-level identity |
| Low value per unit, no unit-level use case | GTIN, or GTIN with batch and expiry, is usually enough |
| Lines cannot yet print and check variable data | Fix the line first, or start with a pilot line |
No grid replaces judgement, but if none of the top four rows applies, you probably don't need serialization yet.
The middle ground
The choice is not binary. Many brands land in between:
- Batch and expiry in a 2D code. Moving from a GTIN-only barcode to a 2D barcode carrying GTIN, batch and expiry gives retailers better stock rotation and you better recall targeting, without unit-level data. See batch-level vs unit-level identification.
- Serialize a subset. Serialize premium ranges or products sold through channels where counterfeits appear, and leave the rest at batch level.
- Serialize higher packaging levels. Identify cartons and pallets for logistics while units stay at batch level.
- Pilot first. Serialize one product on one line for a defined period, measure what changed, then decide.
A worked example
Surya Laminates, a fictional building-materials brand, sells decorative laminate sheets through dealers and wants carpenters to scan sheets for rewards. It also sells low-cost adhesive tubes through the same dealers.
- Laminate sheets: high value per unit, a loyalty programme that must pay once per sheet, and reports of look-alike products in some regions. Serialization is justified, and the lines that print sheet backs are assessed for variable-data printing first.
- Adhesive tubes: low value, no unit-level programme planned. The tubes keep a GTIN barcode and add batch and expiry. If a scan-to-learn page is wanted, a GTIN-level QR code carrying a GS1 Digital Link is enough.
Same company, same dealers, two different answers — which is usually what a sound decision looks like.
Talk to us about scoping a serialization pilot