WMS for 3PL See Cargohold

How-tos

Lot Numbers vs Serial Numbers: Which to Track

Published 15 Oct 2026 Last verified 15 Oct 2026

Pallet of identical cartons with blank labels beside a single labelled box and a handheld scanner on a warehouse floor

A lot number tells you which batch a unit came from. A serial number tells you which single unit it is. Most 3PL clients need neither. A few need one, and a small number need both, and the difference decides how much scanning your team does all day.

What each one means

A lot number (also called a batch number) is a code shared by every unit made or received together. Forty cartons of the same shampoo from one production run carry one lot code. If the maker finds a problem with that run, the lot is how you find every carton affected.

A serial number is unique to one unit. A router, a power drill or a pair of headphones might each carry its own. Serials matter when a single item has to be traced: for a warranty claim, a repair, a theft report or a return.

A product can have both. A tub of protein powder has a lot and an expiry date but no serial. A laptop has a serial and usually no lot. A medical device may have a serial and a lot on the same label.

If you want the short definitions next to the other warehouse terms, the WMS for 3PL glossary has them.

When a client needs lot tracking

Lot tracking tends to come up when a product can go bad, be recalled, or vary between production runs. Typical cases:

  • food and drink, where the lot and expiry date drive what can be shipped;
  • cosmetics and supplements;
  • chemicals and adhesives with a shelf life;
  • products where colour or finish can differ between runs, so a customer should not get two lots in one order.

Whether a rule or regulation applies to a particular product is for the client to say, and for you to confirm with them in writing. Do not guess on the client's behalf.

When a client needs serial tracking

Serial tracking comes up for items that are worth enough to follow one by one, or that carry a warranty:

  • electronics and appliances;
  • tools and equipment;
  • anything the client repairs or refurbishes and sends back out.

With serials, the 3PL usually has to record which serial left on which order, so the client can answer "which unit did this customer get?" later.

Expiry dates and FEFO

Lot tracking is often paired with an expiry date stored against the lot. That lets the system pick first expired, first out (FEFO) instead of first in, first out. The oldest arrival is not always the first to expire, so a plain first-in rule can leave short-dated stock sitting at the back of the rack.

For FEFO to work, three things have to be true:

  1. The expiry date is captured at receiving, not guessed later.
  2. The system stores stock by lot, so two lots of the same SKU in one location stay separate or are at least recorded separately.
  3. Picking is directed by the system, or pickers know to check the date.

You can also set a minimum remaining shelf life per client, for example "do not ship anything with less than a set number of days left". That is a client decision, and it should be in the agreement.

What it adds on the floor

This is the part that gets forgotten when a client asks for tracking in a sales call.

At receiving. Each line needs a lot code, and maybe an expiry date, scanned or typed. A pallet of mixed lots has to be split and counted by lot. A receiver reading a blurry carton label can lose minutes per pallet.

At putaway. Different lots of the same SKU need to be recorded separately, which may mean separate locations.

At picking. The picker confirms the lot, or the system picks the lot for them. A serial-tracked item means one scan per unit instead of one per carton.

At packing. For serials, every unit in the box is scanned and linked to the order.

At billing. The extra labour is real. If tracking adds time on every receipt and pick, your price list should say so. Billing detail belongs to a different page, but do not agree to tracking at the same rate as untracked stock without thinking about it.

What to ask the client before you agree

  • Which products need lot tracking, which need serials, and which need neither?
  • Will the lot code and expiry date be on the advance notice? Without that, receivers read it off the carton. See the advance ship notice for what a good one carries.
  • Is the code printed on the carton in a place the receiver can see it, and in a format a scanner can read?
  • Is there a minimum remaining shelf life for outbound orders?
  • Do they need a report of which lots or serials went to which orders, and how often?
  • What should happen if a recall notice arrives? Who contacts whom, and how fast?

Write the answers down. A line like "client A: lot and expiry on SKUs 100 to 140, no serials" is better than a memory.

Tracking a recall in practice

Imagine, with invented numbers, that a client tells you lot K7 of one SKU has a problem. You need three answers quickly: how many units of K7 are still on your shelves, how many went out and to whom, and what is on its way. If your system stores lot against stock and against shipped lines, that is a search. If it does not, it is a day with spreadsheets and pick tickets.

Test this before you need it. Ask your system, or a vendor you are considering, to show it for one lot from receipt to shipped orders. A discrepancy at receiving is also easier to untangle when lots were captured at the dock, because you know which lot was short.

Common mistakes

  • Agreeing to track lots without agreeing who supplies the lot data.
  • Storing two lots in one location without recording which is which.
  • Letting a picker "just take any" of a lot-controlled SKU.
  • Tracking serials on every item for a client who only needed it on one product line.
  • Treating the lot as an open field that people can retype later without a record of the change.

Start narrow. Track what a client needs, prove you can trace it end to end, and add more only when someone asks and pays for it.

Questions people ask

What is the difference between a lot number and a serial number?

A lot number is shared by every unit made or received together, so it traces a batch. A serial number is unique to one unit, so it traces that single item.

Do I need to track lots and serials for every client?

No. Track them only for clients whose products need it, and agree it in writing before the first delivery. Tracking costs scan time on every receipt and every pick.

What is FEFO?

First expired, first out. Stock with the earliest expiry date is picked first, whatever order it arrived in. It needs an expiry date stored against each lot.

What does a client need to send for lot tracking?

The lot code and, if it matters, the expiry date for every line on the advance notice, printed on the cartons where the receiver can read it.

Sources

  • No third-party facts, prices or vendor claims are used on this page.