Both identify products, but at completely different resolutions. A serial number points to one individual item; a lot number points to everything made in the same run. Choosing the wrong one makes recalls expensive, warranties unenforceable and counterfeits invisible.
| Serial number | Lot / batch number | |
|---|---|---|
| What it identifies | One single physical item — one bottle, one device, one garment. | A production batch — everything made from the same run, recipe or shift. |
| Granularity | 1:1. Every unit carries a different number. | 1:many. Thousands of units share the same number. |
| Typical use | Warranty, ownership, activation, anti-counterfeiting, per-item history. | Quality control, expiry management, recalls, raw-material traceability. |
| Recall scope | Pinpoint — withdraw exactly the affected units. | Broad — withdraw the whole batch, including good product. |
| Cost to operate | Higher: unique marking, per-unit data capture, a system of record. | Lower: one code printed per run. |
| Counterfeit resistance | Only if the number is secret or cryptographically bound to the item. | None — a batch code is public and trivially reprinted. |
The practical question is not which identifier is better, but which risk you are managing: a process risk that affects a whole run, or a value risk that lives in the individual item.
Food, chemicals, cosmetics and pharmaceuticals share process risk across a run. If a raw material is contaminated, every unit from that run is suspect, so tracking at batch level is both sufficient and cheap.
Devices, luxury goods, spare parts and regulated products need per-item identity for warranty, ownership transfer, resale and targeted recalls. A batch code cannot answer 'is this specific unit genuine?'.
EU FMD, UDI for medical devices and the upcoming Digital Product Passport expect a serial for the item plus lot and expiry for the batch. The two are complementary, not alternatives.
Printed or encoded as a QR code, a serial is public the moment the product ships. Anyone who photographs one can reprint it across an entire counterfeit run — and every copy verifies as valid.
Systems that flag duplicates catch cloning only after the fact, and usually punish the honest buyer who scans second. It is a detection heuristic, not authentication.
A batch code is shared by design. It tells you when and where something was made, assuming the label is genuine — which is exactly what a counterfeiter controls.
TAGBASE keeps the serial-plus-lot data model regulators expect, but replaces the printed number with a dynamic identity that a counterfeiter cannot reproduce.
A TAGBASE NFC tag gives each unit a unique identity backed by a key stored on certified, attack-resistant silicon. The key never leaves the chip, so the identity cannot be read out and copied into another tag.
Each tap produces a fresh, single-use cryptographic message. A copied URL, a screenshot or a reprinted code fails verification — the gap that plain serialisation leaves open.
Lot number, production date, expiry and material data travel with the item record, so recalls can be scoped by batch while enforcement stays per unit.
Every scan records where and when an item was checked, making diversion, grey-market activity and failed-scan clusters measurable instead of anecdotal.
For a deeper comparison of static identifiers and dynamic authentication, read TAGBASE versus printed serial numbers or see how the same principle applies to preventing counterfeit alcohol.
See how TAGBASE gives every unit an identity that cannot be copied — while keeping lot, expiry and compliance data attached.