What it means
Batch tracking records the path of goods identified as a group, so a manufacturer may assign a lot code to material received and a new code to finished products made from it. If a defect appears, these links help identify the affected units and recipients, so the business can act on evidence instead of guessing whether every product is involved.
A batch can mean different things in different operations, such as one production shift, a mixer load, a supplier's delivery or a packaging run, and it should be defined, with where it starts and ends, before numbers are assigned, because a code that groups too much makes a quality incident expensive while one that is too narrow can be hard to manage. The US Food and Drug Administration explains traceability lot codes and additional records for specified foods under its rule, and those legal obligations apply only within the rule's scope and dates.
GS1's global traceability standard gives a broader framework for identification and trace events, and businesses should check their own product and market requirements. Retention periods likewise depend on industry and jurisdiction, so a food producer, medical-device maker and clothing seller may face very different rules, and retention and access should be defined from applicable law, product life and customer contracts while protecting commercially sensitive supplier and customer data and keeping it available to authorised responders.
Start with incoming materials by recording supplier, lot, quantity, receipt date and inspection result, and keep the lot identity if materials are split across stores or production lines, since a delivery note without an actual lot number may not be enough to trace a later issue back to its source. Production records should link input lots to finished lots, so when one machine uses ingredients from two supplier lots both links matter, and relevant equipment, time, operator and process checks should be recorded where needed in enough detail to investigate a real failure rather than merely fill a form.
Finished goods need a code that travels with them, placed on units or cases as appropriate and captured when items move between warehouses, and a batch on the factory's internal sheet is less useful if retailers cannot identify it on shelves, so check that ink, labels or barcodes stay readable through transport. Outbound records connect lots to customers, destinations and quantities, because if a company only knows that it shipped 1,000 boxes last month it cannot quickly tell which customers received the affected lot.
Returns and transfers must be recorded too, since a returned item placed back into saleable stock without a lot link breaks the chain. Traceability can work backward, asking which supplier materials fed a defective item, or forward, asking where every unit from a suspect lot went, and both directions need tested links because a one-way receipt log will not tell a recall team which stores to notify.
For an illustrative measure, calculate the percentage of sampled finished batches whose input lots and customer destinations can both be retrieved within a target time, so that if 18 of 20 sampled batches pass, the test result is 90%. This is an internal control measure, not a regulatory compliance certificate, and each failed trace should be investigated.
Conduct mock recalls by picking a finished lot without warning the team and asking it to identify materials, quantities, stock and customers, comparing the recorded balance with physical stock and shipments and noting the time taken and missing links, because the exercise finds problems before an actual safety incident makes speed critical. A useful system makes it possible to identify what was made, from what, when and where it went, so establish stable lot codes, capture each transfer and test retrieval.
Suppliers and customers may use different batch formats, so map those identifiers in a shared transaction record and do not relabel a lot casually during transport. When an issue arises, use the record to determine scope and next steps under the applicable safety rules, since good tracking makes a targeted response possible, not automatic.
In practice
Real-world examples.
Example
A food maker recalls only one batch of sauce after a labelling error, because its records show the other batches used a different label run. The recall covers 2,000 jars instead of the whole month's output. Customers of the other batches are not disrupted.
Example
A pharmacy tracks the batch numbers of medicines sold, recording the batch against each dispensing record. When a manufacturer withdraws one batch, the pharmacy searches its records and contacts only the patients who received it. Shelf stock is checked by batch number at the same time.
Example
A supplier's faulty ingredient is traced to three batches of finished product. The producer's production records show which batches used the lot, and the dispatch records show the customers. The affected stock is held while the other batches continue to ship.
Formula
Calculation
Recall scope = Units in affected batches / Total units sold x 100
Worked example. 2,000 affected units out of 100,000 sold gives a recall scope of 2,000 / 100,000 x 100 = 2%. If handling each recalled unit costs $6, a recall limited to the affected batches costs 2,000 x $6 = $12,000, whereas a blanket recall of all 100,000 units would cost 100,000 x $6 = $600,000. The internal trace test described above is a separate measure: 18 of 20 sampled batches retrievable within the target time is 18 / 20 x 100 = 90%.Case study
Seen in the real world.
This illustrative and entirely fictional case follows Palm Orchard Foods, an invented packaged-fruit producer. When a seal fault is reported, its team traces finished-goods lot F-26 to packaging material, production shift and customer shipments. It checks the affected scope before deciding on corrective action.
The story does not claim that every unit is unsafe or that a recall is automatically required. Because the records link F-26 to specific packaging rolls and shifts, the team can test sampled stock from those shifts first and define the affected range from evidence. Its findings then feed a revised packaging inspection step.
Watch out
Common mistakes.
- Assigning lot codes but failing to link inputs, production runs and customer shipments.
- Mixing old and new material without recording which finished batches used each lot.
- Assuming a spreadsheet trace is reliable without testing retrieval under recall conditions.
Questions
People also ask.
What is batch tracking?
Recording which batch each product came from.
Why use it?
To trace problems and limit recalls.
Who needs it?
Any business that needs lot-level traceability; legal duties depend on product and jurisdiction.
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%