What Is Product Serialization?

Your products already have a barcode, and every pack of the same product carries exactly the same one. So what does it mean when a retailer, a regulator or your own marketing team asks for products to be "serialized" — and what changes on the packaging line, in your systems and in the market when you do it?

This guide explains product serialization from first principles: what unit identity is, how it is built from a GTIN and a serial number, where serials come from, and how a single serial lives from the factory to the end of the product's life.

From product identity to unit identity

Most products are identified at the level of the product type. The GTIN (Global Trade Item Number) under a retail barcode tells a checkout which product this is: a 100 ml bottle of a particular perfume, a 1 kg box of a particular detergent. Every 100 ml bottle of that perfume carries the same GTIN, because to the till they are interchangeable.

Serialization adds a second layer. It gives each individual unit its own serial number, so that the bottle in your hand can be distinguished from every other bottle with the same GTIN. The unit's full identity is the GTIN and the serial together, and the GS1 General Specifications define a standard place for the serial: Application Identifier (21), which can hold up to 20 characters.

An analogy helps. A GTIN is like a car's make and model. The serial is like its vehicle identification number. Both are useful, but only one tells you about this car.

Between the two sits the batch or lot number, which identifies a production run. A batch tells you that a unit was made with a particular set of materials on a particular day; a serial tells you which unit it is. The difference is covered in batch-level vs unit-level identification.

What a serialized code looks like

Serial numbers are usually printed inside a 2D barcode alongside the GTIN, because a 2D code can carry several pieces of data in a small space and a coder can change its content for every pack.

Take a fictional perfume house, Maison Ardent. Its 100 ml bottle has a GTIN, and each bottle gets its own serial. In a QR code carrying a GS1 Digital Link, one bottle's identity could look like this:

https://id.maisonardent.example/01/09512345678901/10/LOT2610A/21/X7KQ94MZ2RTA

Reading left to right: /01/ introduces the GTIN (always written as 14 digits in a Digital Link), /10/ the batch, and /21/ the serial. The Digital Link syntax requires those qualifiers to appear in that order. The neighbouring bottle on the line has the same GTIN and batch but a different serial. The same data can also be encoded as a GS1 element string in a GS1 DataMatrix, which is common in factory and regulated settings.

We walk through how the two parts combine, and why the serial only has to be unique within its GTIN, in GTIN + serial: how an individual product gets its identity.

Why random, non-sequential serials matter

Nothing in the basic idea of a serial number requires it to be random. Many factories have historically used counters — 000001, 000002, 000003 — because they are simple to generate and easy for people to read.

For any programme where consumers, retailers or channel partners scan codes, sequential serials are a real weakness:

• They can be guessed. If one pack ends in 004517, a fraudster can reasonably assume 004518 exists. Loyalty points, warranty registrations or "genuine product" checks attached to serials can then be claimed for units nobody has bought.
• They leak business information. Two scans a month apart reveal roughly how many units you produced in between.
• They make enumeration easy. Anyone can write a script that walks through a range and records which codes your system accepts.

The practical answer is to generate serials as random values drawn from a space so large that guessing a valid one is impractical, and to issue them from a system that guarantees no duplicates. Random serials do not stop someone copying a code that already exists — that is a separate problem, discussed in why a QR code does not automatically prove authenticity — but they do stop people inventing codes that look valid.

Where serial numbers come from

A common assumption is that the printer makes up the serials. In a well-run operation it does not. Serials are a business record, so they should come from a system that can guarantee uniqueness and keep a history.

There are three usual sources:

1. The ERP. Many manufacturers generate or reserve serial ranges in their enterprise resource planning system, especially where serials also appear on invoices, shipping documents or regulatory reports.
2. A serialization or connected-product platform. A dedicated platform generates serials (often random) per GTIN and batch, tracks their status and makes them available to consumer-facing services.
3. A line-level system that draws from either. On the factory floor, a line controller or gateway takes a pool of pre-issued serials and feeds them to the coder one by one. It does not invent serials; it consumes them.

Whichever system is the source, the principle is the same: one authority issues each serial, and every other system refers back to it. Two systems independently generating serials for the same GTIN is how duplicates happen. For what happens after the serial leaves the ERP, see what happens after an ERP creates a serial number.

The lifecycle of a serial

A serial is not just printed and forgotten. It moves through a series of states, and a serialization programme is only as good as its record of those states.

Two of these stages deserve special attention.

Printed is not verified. A coder reporting that it sent or printed a code does not prove the code is on the pack, readable and correct. A camera or reader on the line should check each code before the unit is accepted, and units that fail should be rejected. This gap is the subject of why "printed" is not the same as "verified".

Unused serials must be closed out. Serials that were generated but never printed, or printed on packs that were then rejected, should be marked as such. GS1's Core Business Vocabulary, used with EPCIS event data, has standard terms for these moments: a business step called commissioning when an identity is first associated with a physical object, and decommissioning when it is taken out of use. Status values such as active, recalled, expired and destroyed describe what happened next.

The point is not to use every standard term from day one. It is to make sure that, for any serial someone scans in the market, you can answer: did we make this, did it pass inspection, and what has happened to it since?

Why serialization matters to the business

Serialization earns its cost when unit-level identity enables something batch-level identity cannot:

• Engagement that counts per unit. Loyalty points, warranty registration and promotions can be tied to one physical unit, so the same pack cannot be claimed twice.
• Anti-counterfeit programmes. A unique serial lets a server notice when the same code is scanned in two distant places, or far more often than one genuine pack ever would be. It is one ingredient, not a guarantee.
• Traceability. When units are packed into cartons and pallets and those relationships are recorded, a single scan can reveal where a unit was made and where it was shipped. See how individual products become cartons and pallets.
• Precise recalls and returns. If a problem is traced to a specific range of units, you can act on those units rather than an entire batch.
• Diversion signals. Scans in places a unit was never shipped to can reveal grey-market movement.

How serialization relates to neighbouring concepts

Serialization sits between several ideas that are easy to confuse:

• GTIN — identifies the product type. Serialization builds on it, never replaces it.
• Barcode or QR code — the data carrier that holds the identity. The serial is data; the code is the container. See GTIN vs barcode vs QR code vs serial number.
• Verification — checking that a code is present, correct and readable. Formal verification also includes grading print quality against ISO standards.
• Authentication — deciding whether a physical item is genuine. A serial supports this but does not prove it on its own.
• GS1's role — GS1 defines how serials are structured and carried. It does not issue or store them; Verified by GS1 confirms who a GTIN belongs to, not what happened to an individual unit.

Where to go next

If serialization is new to you, the next step is to see exactly how the GTIN and the serial combine, covered in the next article in this series. To see the factory side in motion, read the journey of a serialized product through a packaging line.