What it means
Many products are made or received in batches, so if one batch has a defect, a business needs to know which supplier delivery it came from and which customers received it. Without lot records, it may have to hold or recall every similar item, increasing cost and disruption, while a sound process can narrow the affected population and still protect customers.
Record the lot identifier at receipt and check it against packaging and supplier documents. If goods are repacked or combined, retain the link between original and new identifiers, and track movements between locations and the lot selected for each order.
A system that records only total SKU quantity cannot reliably answer which customer received which batch, so staff should scan or verify lot numbers at the points where mixing can occur. A barcode system helps only if staff use the right code at the right step, and records should be retained for the period required by product rules and contracts.
When a problem appears, isolate the suspect lot and gather evidence by checking supplier notice, quality tests, manufacturing dates and warehouse records, and identify stock on hand, in transit, returned and sold. A traceback may run backward from a customer complaint to its supplier batch, or forward from a known bad batch to all recipients, and both directions should be tested.
Do not release held goods until the authorised quality or safety owner clears them. Confirm the chain with samples, because a lot number typed incorrectly on one receipt can misdirect the whole investigation, so compare physical labels, system movements and shipment records.
If records are incomplete, state the uncertainty and widen the review where safety requires it, since a false sense of precision can be more dangerous than admitting a gap. Follow current product-specific and jurisdictional recall requirements when relevant.
Coordinate communications, since quality, operations, supplier management and customer service may each hold part of the story, so give the incident a named lead and a single approved description of affected lots. Do not send customer names or private order information to a supplier without a valid need and permission, and customers should receive clear instructions if action is required, based on verified scope rather than speculation.
Practise traceability before an incident with a mock exercise asking the team to identify all recipients of one lot within a set time, then measure missing links and correct receiving, picking or repacking processes. For owners, lot traceback limits harm when something goes wrong.
It supports targeted action, accurate supplier claims and confidence that unaffected products can continue to serve customers safely.
In practice
Real-world examples.
Example
A food distributor identifies which restaurants received one supplier batch after a contamination warning and follows the applicable recall process.
Example
A retailer traces a defective appliance serial range back to two warehouse receipts and the orders fulfilled from them.
Example
A repacker links new carton labels to original supplier lot codes so the history remains visible after packaging changes.
Formula
Calculation
Traceback completeness = Units in the affected lot with verified current location or recipient / Total units received or produced in that lot x 100
Worked example. An invented business received 1,000 units in a lot and can account for 940 through stock, shipments and documented scrap.
- Completeness = 940 / 1,000 x 100 = 94%.
- The remaining 60 units require investigation; 94% is not enough to assume they are safe or unshipped.
Reconcile units without double counting returns or transfers. For example, if 30 of the 940 accounted units were returned and then reshipped, count them once in their current location, otherwise completeness is overstated.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Valley Foods, an invented packaged-snack company. A supplier reported a possible defect in one batch of a seasoning. Valley knew how many cases it had received but had mixed some lots during repacking and did not record the original batch on final cartons. The quality lead held potentially affected stock and reconstructed production and shipment records.
Because some links were missing, Valley treated a wider group as potentially affected and followed the appropriate safety process. It then changed repacking labels to preserve source lot identifiers and tested a sample traceback every quarter. The owner learned that traceability is not only a database field. It depends on physical labels, scanning discipline and honest treatment of uncertainty when a customer safety decision is needed.
Watch out
Common mistakes.
- Assuming all units from the same SKU belong to one lot.
- Losing original batch links during repacking, transfers or returns.
- Narrowing a safety action based on incomplete records without acknowledging uncertainty.
Questions
People also ask.
Is a lot number the same as a SKU?
No. A SKU identifies a product type, while a lot identifies a particular batch or production group.
Can a spreadsheet support traceback?
It can for simple operations if records are complete and tested, but manual errors and scale need attention.
What happens when some units cannot be traced?
Investigate the gap and use a suitably cautious product-safety and recall decision under the applicable rules.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%