Finished product traceability means that from any unit on a shelf you can get back to the batch and its ingredients, and from any batch you can get forward to every customer who received it, with quantities that add up. It breaks in predictable places: a case without a code, an order that doesn't say which lot shipped, samples nobody wrote down. The checklist below has fifteen checks in six groups. Most are things to confirm on every batch or order; three are a test to run each quarter. Print it, tick it, and treat every cross as a job to do before an auditor finds it.
The short version
- Codes: on every unit and case, one code for one batch.
- Batch record: every ingredient and packaging lot, and counts that add up.
- Stock: stored and counted by lot; held lots kept apart.
- Shipping: the lot and quantity on every order, samples included.
- A quarterly test in both directions, timed.
- TaroStack covers most of the list by recording lots as you make and ship. More below.
The checklist
| Area | Check | How often |
|---|---|---|
| Codes | Every unit carries a lot code that can be read without opening it | Each batch |
| Codes | Every case carries the same lot code as the units inside | Each batch |
| Codes | One lot code means one batch: no two batches share a code | Each batch |
| Batch record | The record names every ingredient lot and packaging lot used | Each batch |
| Batch record | Units made, units rejected and units to stock add up | Each batch |
| Batch record | Rework is recorded with the lot it came from | When it happens |
| Stock | Finished stock is stored and counted by lot | Monthly |
| Stock | Held or quarantined lots are kept apart and marked | When it happens |
| Shipping | Each order's record names the lot or lots shipped and the quantity of each | Each order |
| Shipping | Samples, donations and staff sales are recorded with their lot | When it happens |
| Returns | Returned product is recorded against its lot | When it happens |
| Customers | A current contact for every wholesale customer | Quarterly |
| Test | Pick a lot: list every customer and quantity, and what is still here, inside the time you've set | Quarterly |
| Test | Pick an ingredient lot: list every finished lot it went into | Quarterly |
| Test | The quantities account for the whole lot: made = here + shipped + rejected | Quarterly |
Where it usually breaks
The case. Units get a printed code; the outer case gets a marker scrawl or nothing. A warehouse picks cases, not units, so that's the code that needs to be right.
The order. This is the big one. A packing slip says "6 cases granola bars." Which lot? If your orders don't say, then every lot that was in stock that week went to every customer who ordered that week, as far as you can prove. One recalled lot becomes four.
The leaks. Samples for a buyer, a donation to the food bank, a box for the staff room, a replacement sent for a damaged case. Each is product leaving without an order. A dozen bags of a 564-bag lot is 2%, and it's the 2% you won't be able to explain during a recall.
Mixed pallets and returns. Stock goes back on the shelf with a different lot, or a return is put into "the granola bars" instead of its own lot.
Running the quarterly test
Pick a finished lot at random, a few weeks old so it has shipped. Start a timer. List who got it and how much, count what's still here, and add it up against the batch record. Then pick one ingredient from that batch and go the other way: every finished lot that used the same ingredient lot.
Write down the time and anything that didn't add up. The first one usually takes an hour or two and turns up a gap. A walk-through with numbers is in food mock recall example, and a fuller exercise in mock recall and traceability exercise.
Set yourself a time limit. Many buyers and audit schemes expect a trace in a few hours; your own target can be tighter.
Get the checklist
Download the finished product traceability checklist. The fifteen checks with a tick box for each quarter, a count of what's done, and a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. What buyers mean when they ask about this is in what buyers mean by lot tracking.
Where this stops working
A checklist finds the gaps. Closing them by hand means more writing at the two busiest moments of the day: when a batch is being packed and when a truck is being loaded. The checks that fail are the ones that depend on someone copying a code under pressure.
How TaroStack does it
TaroStack makes most of the fifteen checks true by default.
Codes and batch records. Each batch gets its own lot, and its record notes the ingredient lots it consumed, automatically. Lot labels print with the code and date.
Stock by lot. Finished stock is held and counted by lot; a held lot is out of what can be picked.
Orders name their lots. Picking takes the earliest-expiring lot by default and records it on the order, with the quantity.
The leaks have a place. A sample or a donation is an adjustment with a reason, against a lot.
Returns go home. A return goes back into the lot it left in.
The test is a button. A traceability drill is timed and saved, and Home reminds you a month before a year passes without one.
| Check | By hand | In TaroStack |
|---|---|---|
| Ingredient lots on the batch record | Written each time | Recorded with the batch |
| Lot on every order | Written, if remembered | Recorded when picked |
| Samples and donations | Usually missed | Adjustments with a reason |
| The quarterly test | An afternoon | A timed drill |
Lots, batches and recalls are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
