A recall names cartons, not SKUs
Traceability is invisible until the day you need it, at which point the difference between knowing a lot number and knowing a SKU is the difference between a targeted recall and a total one.
The cost of tracking at SKU level only
If your system knows you sold 4,000 units of a product and nothing more, then a supplier defect affecting one production run forces you to treat all 4,000 as suspect. You pull stock that was never affected, refund customers who were never at risk, and destroy inventory that was fine. Lot and batch tracking narrows the blast radius to what was actually involved - and it has to be captured at receipt, because there is no way to reconstruct it afterwards.
Three levels, different jobs
Lot and batch
A production run, captured at receipt against the purchase order that brought it in and carried through putaway, picking and despatch. This is what makes expiry management, shelf-life rules and targeted recalls possible, and what most audits are actually asking to see.
Serial numbers
Identity at the individual unit. Relevant where warranty, registration, high value or theft make it necessary to know which specific unit went to which specific customer, rather than which batch it came from.
Traceability and stock rotation are the same mechanism
Once the system knows which lot a carton belongs to, it also knows how old that carton is - and that is what lets wave building release oldest-first on stock age rather than order date. The two capabilities are usually sold separately and are really one thing: a warehouse that cannot identify a lot cannot rotate it either, and ends up shipping newest-first by accident while the dated stock quietly ages out at the back.
Which platforms actually have it
This is a thinner row than most buyers expect. Across the shipping and warehouse systems on our comparison tables, ShipStation and Veeqo do not offer lot, batch or serial tracking at all, and ShipHero's public documentation does not cover it - we score that unconfirmed rather than absent, because marking a competitor down on silence is exactly the sort of thing those pages exist to avoid. If you carry anything dated, regulated or serialised, ask for this explicitly during an evaluation. It is rarely on the first slide.
Related capabilities
Traceability: common questions
Yes. Lot and batch are captured at receipt against the purchase order that brought the stock in, then carried through putaway, picking and despatch, which is what makes expiration date management, product traceability and targeted recalls workable rather than theoretical.
Yes. Serial tracking identifies the individual unit rather than the production run, which matters for warranty, registration, high-value goods and any category where you need to know which specific unit reached which specific customer.
It narrows the recall to the units actually affected. Without it, a defect in one production run makes every unit of that SKU suspect, so you pull, refund and destroy far more stock than the problem warrants and contact customers who were never at risk.
Yes. Once a lot is identified at receipt the system knows the age and dating of the stock behind it, which is what drives expiry management and lets picking release oldest-first by stock age rather than by the date the order happened to arrive.
Often, yes. Anything with a warranty, a shelf life, a supplier quality history or a resale channel that audits provenance benefits from it, and the capture has to be in place before the incident that needs it, because lot identity cannot be reconstructed after the fact.
