Serial number and lot/batch tracking
Stock tells you how many you have; serial and lot tracking tells you which unit went to whom. Build tracing, expiry control and recall readiness.
The phone rings at a food wholesaler's office. A supermarket chain's quality manager reports that a jar shipped three weeks ago arrived with a swollen lid, and asks one question: "Where else did that batch go?" The warehouse lead opens the system. The product name is there. The quantity on hand is there. Even the delivery note is there. The answer is not. Two options remain: do nothing, or ask for every jar of that product back. The first is an indefensible risk; the second is money burned on purpose.
Serial number and lot/batch tracking closes exactly that gap. Ordinary stock control answers "how many do we have." Serial and lot tracking answers "which unit went to whom, which batch was it from, and who else received that batch." Below: the difference between the two identifiers, the industries with no real choice, where records must be captured, how barcodes make capture survivable, how a recall scenario runs, and which metrics prove the system is alive.
"How many" and "which one went where" are different questions
Most companies build stock control around quantity: goods in, goods out, remaining balance. That is enough to fulfill orders and avoid tying up cash, and we cover that foundation in our guide to inventory management. But quantity tracking treats units as interchangeable: to the system, two boxes on the same product card are identical twins with no history.
Traceability breaks that assumption. Every unit gets an individual or a group identity, and when it leaves the building that identity is matched to a buyer. The stock record stops being a number and becomes a story: where it came from, where it sat, who received it. Complaints, warranty claims and recalls are all solved by reading that story back.
Serial number or lot/batch? The real difference
A serial number points to one physical object: that machine, that motor, that control panel. There is no second unit with the same number. A lot or batch points to a group produced under the same conditions: a thousand jars from one cook, five hundred tubes filled from one mix, cable cut from one reel. Units inside a lot are not distinguished from each other, but they are distinguished from everything outside the lot.
The choice follows the product and the depth of your liability. Anything you warrant, service or tie to a named customer needs a serial. Homogeneous consumables, where per-unit capture would never pay for itself, belong at lot level. Plenty of manufacturers use both: the device carries a serial, the critical component inside it a recorded lot.
| Criterion | Serial number | Lot / batch |
|---|---|---|
| Scope | One single unit | Group made under same conditions |
| Typical field | Electronics, machinery, medical devices | Food, cosmetics, chemicals, pharma |
| Main use | Warranty, service, theft tracing | Quality, expiry, recall |
| Capture cost | High, one action per unit | Low, one action per group |
Industries where this is not optional
In food and beverage, batch tracking is the job itself: an ingredient problem reaches finished goods only through the batch. In cosmetics, the batch printed on the pack opens every complaint file. Pharma and medical devices typically demand serial, lot and expiry together. In electronics the serial carries the warranty. In automotive spare parts the batch links to the installation record, and without it, as we discuss in spare parts and service inventory management, you cannot say which vehicle carries which component. In chemicals the batch travels with the safety data sheet.
Traceability obligations differ by industry and country and get revised over time. What I describe here is the operational frame. Confirm which records your category requires, and for how long, against your local legislation and sector rules, and bring in a specialist if the answer is not obvious.
Expiry dates and the FEFO principle
For anything with a shelf life, batch tracking earns its keep a second way: knowing which batch dies first. Classic FIFO says first in, first out, but a batch that arrived later may well expire sooner. So the correct rule for perishables is FEFO: first expired, first out.
Running FEFO requires the expiry date on the batch record and a pick list sorted by that date. Otherwise the picker grabs the nearest carton and a batch quietly ages out on a back shelf. Your system should warn before a batch reaches its cutoff, so it can be promoted, redirected to a dealer, or written down deliberately.
Capture points: receiving, production, shipping
Traceability is built at three points, and skipping any one snaps the chain. At receiving you record the supplier's batch and, where relevant, the expiry date. If you produce or repack, you generate your own batch code and link input batches to the output batch. At shipping you attach outgoing serials or batches to the order and the customer.
- Receiving: The supplier batch and expiry belong in the record at the first scan, because reconstructing them later almost never works.
- Production or packing: Without a link between input and output batches, a raw material issue can never be followed forward to finished goods.
- Shipping: If nobody writes down which batch went to which customer, the last link of the chain is missing and the whole structure stops paying off.
- Location: Batch-level picking assumes you know which shelf holds which batch, which makes warehouse and shelf management the quiet partner of traceability.
Barcodes and 2D codes: scan it, don't type it
Ask people to type serial and batch numbers by hand and the system collapses within a quarter. The strings are long, similar characters blur, and nobody types carefully on a heavy dispatch day. Turn data entry into scanning instead: a barcode inventory setup is the direct foundation of traceability, not a separate project.
A plain linear barcode usually carries only the product code. To move batch, expiry and serial in a single scan you need two-dimensional codes; the logic behind creating QR and 2D codes applies here too, only the embedded fields differ. If you print your own labels, encode fields in a fixed order and always leave a human-readable line. On the day a scanner dies, that line is your only backup.
Tying the serial to the customer and the warranty
A serial number becomes valuable the moment it lands on a customer record. Scanned at dispatch and written to the order, it answers two questions at once: who holds this unit, and when its coverage started. When a unit returns for service, scanning the serial beats asking the customer to dig out an invoice.
With that link in place the warranty process organizes itself, and we cover how to run the clock in our piece on warranty tracking and warranty process management. In Rocketly, because bookkeeping, stock and customer records live in one place, attaching a serial to an order line does not require a separate system; you read the product's history and the customer's history on the same screen.
The traceability scenario: complaint to batch, batch to buyers
Traceability runs in two directions, and you need both. Backward tracing starts from the unit in your hand: read the batch code on the pack, find which input batches produced it, and identify the supplier and delivery date. Forward tracing does the opposite, listing every unit made from that batch, the orders that carried them, the customers and the dates.
What it looks like in practice
A complaint ticket opens with the batch code in it. The system produces the shipment list for that batch, grouped by customer, with affected quantities calculated and a contact order set. All of it should finish in an afternoon. If it takes days, what you own is an archive, not a tracking system.
When a recall starts, you either hold a list or you hold a guess. The distance between them is one field somebody made a habit of filling in months earlier.
Run a recall drill before you need one
Building the system is not the finish line; you have to watch it work before a real crisis tests it. Run a drill at least once a year. Pick a batch at random, assume it is compromised, run the process end to end and time it. How many minutes to a complete buyer list? Any shipments missing? Contact details current? Which warehouse area receives returned goods?
Drills expose the same three gaps almost every time: a capture point where the batch was left blank, a partial shipment that was never split correctly, and stale customer contact details. None of the three surface on their own, and during a real recall there is no time left to fix them.
Split shipments, returns and supplier batches
In real operations an order rarely comes from one batch. Sixty units of a hundred come from one batch, forty from another. The shipment line has to carry that split; otherwise two batches left the building while the record shows one, and every trace built on it returns the wrong answer. The same trap applies across sizes and colors, so product variant management and batch tracking must be designed together.
On the returns side, the serial or batch of the incoming unit must be recorded; that is the traceability leg of the flow described in product returns and the RMA process. A returned unit going back into sellable stock has to re-enter under its own batch, not dissolve into a generic pool. Ask for the same discipline upstream: getting batch numbers and expiry dates printed on supplier delivery notes is a matter of asking, and it is one of the cheapest clauses you can add within supplier management and the procurement process.
Phased rollout, metrics and common mistakes
Trying to make the entire catalog traceable over one weekend is the classic opening error. Start with a critical product group: the highest risk, the most complained about, or the one where records are already required. Once the flow settles, the team scans without reminders and a drill runs clean, move to the next group. Phased rollout looks slow and beats half-finished big-bang projects by a wide margin.
Three things deserve measurement. Traceability coverage: the share of shipment lines carrying a valid serial or batch. Trace time: how long it takes to get from a batch code to a complete buyer list. Shelf-life loss: the value written off to expiry. Without regular reporting these numbers rot quietly. With Rocketly's report builder all three become scheduled reports that reach the operations team weekly.
Other recurring mistakes look small and are not: writing the batch code into the product name as free text, reusing a code across different products, leaving returns and samples outside the records, sticking the label where it peels off first, and letting one person be the only one who understands the system. They all break the chain at a single link.
Knowing where your product went defines the quality of the answer you can give under pressure. If you want stock, customers, orders and service history to live in one place, create your free Rocketly account and start with a small pilot on your most critical product group.