Serialized Inventory and Batch Tracking: The Full Guide

SECTION 01What is serialized inventory tracking?

In brief: Serialized inventory tracking assigns a unique serial number to every individual unit, not just every SKU, and records that identifier at each step: receiving, putaway, sale, and return. It means knowing not just how many units you hold, but exactly which unit went where, enabling warranty verification, theft tracing, and unit-level history.

Standard inventory tracking treats units as interchangeable: 4,000 units of SKU-2214 is a quantity, and any unit is as good as any other. Serialization breaks that anonymity. Each unit carries its own identity, printed and barcoded, and the system records which specific serial arrived on which GRN, sat in which bin, shipped on which order, and came back on which return. The unit stops being a tally mark and becomes a record with a biography.

That biography is the product. When a customer claims a warranty, you know precisely which unit they bought and when. When a unit walks out unrecorded, you know which one is missing, not just that the count is short. When a marketplace return arrives, you can verify the device in the box is the device you shipped. None of that is possible at SKU level, which is why serialization is standard practice in electronics, appliances, and other high-value categories. It sits inside the wider discipline our ecommerce warehouse management pillar covers end to end.

SECTION 02What are batch numbers and lot tracking?

In brief: A batch number (also called a lot number; the terms are interchangeable) identifies a group of units produced or received together, typically carrying the manufacture date and expiry date. Lot tracking records which batch every unit belongs to, enabling expiry-based rotation, targeted recalls, and quality tracing back to a specific production run.

Where a serial number says "this one," a batch number says "these together." Every jar of moisturizer bottled in the same production run shares one lot number, and that shared identity carries the data that matters at group level: when the run was made, when it expires, and which raw materials went in. First thing to settle, because the terminology confuses everyone: batch number and lot number mean the same thing. "Lot" leans American and pharmaceutical, "batch" leans British and FMCG, and regulated industries use both freely.

Batch tracking is the machinery behind two disciplines this blog family keeps returning to. It powers FEFO rotation (first expired, first out), because the system can only pick the shortest-shelf-life stock first if it knows each unit's expiry via its lot. And it makes recalls surgical: when a supplier flags a contaminated run, lot tracking tells you exactly which units, in which bins, on which orders, to which customers, so you recall hundreds of units instead of freezing thousands. For anything edible, spreadable, or ingestible, batch tracking is not an optimization; it is the compliance floor.

SECTION 03Serial number vs lot number: what is the difference?

In brief: A serial number is unique to one unit; a lot or batch number is shared by every unit made in the same run. Serial tracking gives unit-level history for warranties, theft, and fraud verification; lot tracking gives group-level traceability for expiry rotation and recalls. High-value durable goods need serials; perishable and regulated goods need lots; some products carry both.

The two are complements, not competitors, and some products rightly carry both: a medical device has a serial for its own identity and a lot for its production run. The decision logic per product is simpler than it looks, and the next section maps it.

SECTION 04Which products need serial, batch, or neither?

In brief: Serialize when unit identity matters: high value, warranty-backed, theft-prone, or resale-fraud-prone goods. Batch-track when group history matters: anything with expiry, regulated categories, and quality-sensitive production. Plain SKU tracking is enough for low-value, stable, interchangeable goods. The test: what question would you need answered in a dispute or recall?

The last row matters as much as the rest: identifier tracking has a real per-unit cost in scanning time and label discipline, and applying it where no dispute, recall, or expiry question will ever need it is pure overhead. Track at the level your worst realistic incident requires, and no deeper.

SECTION 05What problems does identifier-level tracking actually solve?

In brief: Four concrete ones: recalls become targeted (freeze one lot, not the whole SKU), warranty and service claims verify against the exact unit sold, expiry-driven stock rotates automatically by FEFO before it becomes write-off, and return fraud, swapped or misrepresented units, gets caught at the grading bench with proof instead of suspicion.

• Surgical recalls. Without lot tracking, a supplier quality alert means quarantining every unit of the SKU and contacting every buyer. With it, the blast radius shrinks to one run: exactly which bins, which open orders, which shipped customers. The difference is measured in both cost and brand damage.
• Warranty truth. A serial on the invoice means a service claim can be checked against the exact unit and sale date, ending both honest confusion and deliberate claim-stretching on units bought elsewhere or out of warranty.
• Expiry money. Batch-level expiry data is what lets the system pick short-dated stock first and alert on approaching write-offs while there is still time to discount or redistribute. Expired stock discovered at annual stocktake is margin already lost.
• Fraud caught at the bench. With roughly 13.7% of returns involving fraud or abuse (NRF), the swap, returning an older or different unit in the right box, is a live threat for serialized categories. A serial check at return grading settles it in seconds, with evidence. This is the returns-side discipline our returns management playbook covers in full.

SECTION 06How does serialized and batch tracking work in the warehouse?

In brief: Identifiers enter the system by scan at receiving, alongside the GRN, and are verified at every subsequent touch: putaway, picking, packing, invoicing, and return grading. Serials are scanned per unit; lots are captured once per group with expiry dates. Capture at first touch is the make-or-break rule, since an identifier missed at the dock is unrecoverable later.

• Receiving: the capture moment. Serials are scanned unit by unit; lot numbers and expiry dates are captured per batch as goods are counted against the purchase order, on the same pass as the goods received note. This is the one chance: a unit that enters stock without its identifier is anonymous forever.
• Putaway and storage. The system now knows not just what is in each bin but which serials and lots, which is what makes identifier-level cycle counts and lot-locatable recalls possible.
• Picking and packing. For serialized goods, the pick scan records which exact unit fulfils which order; for batch goods, FEFO logic directs the picker to the shortest-dated lot. The scan discipline is the same one covered in our RF scanner guide, carrying one extra field.
• Invoice and dispatch. The serial rides on the invoice and the order record, arming every future warranty and dispute conversation.
• Returns. The grading bench scans the returned unit's serial against the order. Match: process normally. Mismatch: fraud evidence, timestamped.

SECTION 07What are the best practices for an identifier program?

In brief: Capture at first touch, always by scan rather than keyboard, verify label quality at receiving, print serials on invoices, track identifiers through returns as rigorously as through sales, alert on expiry ahead of write-off windows, and audit identifier records with cycle counts. Partial discipline is the program-killer: identifiers only pay when coverage is complete.

• First touch or never. Identifier capture belongs at receiving, not "when we get time." Backfilling serials on stocked goods means re-handling everything.
• Scan, never type. Keyed entry runs at roughly one error per 300 characters (GS1 benchmark); a mistyped serial is worse than none, because it creates a unit that does not exist. This is a big part of why human error still plagues ~43% of warehouses (Opensend, 2025).
• Police label quality inbound. Unreadable or duplicated supplier labels get fixed at the dock, or they poison every downstream scan.
• Put serials on paperwork. Invoices and dispatch records carrying the serial turn future disputes into lookups.
• Close the returns loop. An identifier program that stops at dispatch misses the fraud check that often justifies the whole investment.
• Alert ahead of expiry. Batch data should trigger action windows, discount, redistribute, donate, before write-off dates, not after.
• Audit the identifiers. Cycle counts at serial and lot level confirm the records match the shelf, the same accuracy discipline that keeps well-run operations at ~97.7% (Opensend, 2025).

SECTION 08Why identifier tracking is WMS work

In brief: Identifier tracking multiplies the data per unit, which spreadsheets and basic tools cannot orchestrate: capture prompts at receiving, FEFO-aware pick logic, serial verification at returns, and instant which-lot-where lookup during a recall. A warehouse management system runs all of it as workflow rules rather than human vigilance.

Everything above depends on the identifier being demanded, validated, and consulted at the right moments automatically. A warehouse management system is what turns the program from vigilance into workflow: receiving screens that will not close without the serial or lot scan, pick tasks that name the lot to take, return grading that flags a serial mismatch on the spot, and the recall query that answers "where is lot 2417?" in seconds instead of a weekend.

On EasyEcom, serialization and batch tracking run natively through exactly these touchpoints: unit and lot capture at receiving, expiry-aware FEFO picking, serial-carrying invoices, and verification at returns, with everything synced across channels in real time. Good Bug runs its shelf-life-sensitive catalog this way, batch and expiry tracked from the receiving dock onward while fulfilling B2B, B2C, and quick commerce from one warehouse, and the scan discipline underneath is the same one that holds RedTape's bin-level accuracy at roughly 99.99%.

If your category has warranties, expiry dates, or high-value units, the identifier layer is your next accuracy upgrade: explore the EasyEcom warehouse management system, check our pricing, or book a demo and we will map serial and batch flows for your actual catalog.