A material traceability log has one row for each material in each batch you make: the batch code, the material, who supplied it, the supplier's lot number, the date you received it and how much the batch used. That's all it is. And it's the single record that connects what comes in your back door to what goes out the front. When a supplier phones about a lot of peanuts, you filter the log by that lot number and read off every batch it went into. Without the log, the honest answer is "everything we've made since it arrived." Here's a log with two batches filled in.
The short version
- One row for each material in each batch. Five ingredients and a pouch are six rows.
- The supplier's lot comes off the bag, box or case label. Copy it exactly.
- Packaging counts: pouches, jars and labels have lots.
- Write it when you make the batch, at the scale, not afterwards.
- TaroStack records the lots a batch used automatically. More below.
An example: two batches, one shared ingredient
A made-up snack maker, the first week of November:
| Made | Batch | Material | Supplier's lot | Received | Used |
|---|---|---|---|---|---|
| Nov 4 | TM-1104-1 (trail mix) | Peanuts, roasted | PN-4471 | Oct 28 | 90 lb |
| Nov 4 | TM-1104-1 | Raisins | RS-25-2203 | Oct 14 | 60 lb |
| Nov 4 | TM-1104-1 | Chocolate gems | CG-88140 | Oct 21 | 40 lb |
| Nov 4 | TM-1104-1 | Sunflower kernels | SK-3920 | Sep 30 | 22 lb |
| Nov 4 | TM-1104-1 | Pouches, 6 oz | PCH-2510-07 | Oct 7 | 564 |
| Nov 6 | GB-1106-1 (granola bars) | Peanuts, roasted | PN-4471 | Oct 28 | 35 lb |
| Nov 6 | GB-1106-1 | Rolled oats | OAT-0917 | Sep 22 | 120 lb |
Reading it both ways
Backward: what's in this batch? A customer reports a problem with trail mix TM-1104-1. Five rows tell you every lot that went in, and who supplied each.
Forward: where did this lot go? The nut supplier recalls PN-4471. Filter the lot column: 90 lb went into TM-1104-1 and 35 lb into GB-1106-1. Two batches, not a month's production. Add what's left in the bag and it should match what you received: if you took in 150 lb, then 90 plus 35 plus 25 still on the shelf accounts for all of it.
That second check matters. If the numbers leave 20 lb unexplained, some batch used that lot and didn't write it down.
The log gets you from an ingredient lot to your batches. To get from a batch to your customers you need the other half: the lot written on every order. That's the "one step back, one step forward" a buyer's questionnaire means; it's explained in one up, one back traceability.
The awkward cases
Two lots in one batch. The bag runs out mid-batch. Write two rows for that material, each with its lot and the amount from it.
Bins and silos. Flour poured into a bin loses its bag. Label the bin with the lot, and when you top it up before it's empty, write both lots on every batch until the older one is surely gone.
Things you make ahead. A caramel or a spice blend made on Monday and used all week needs its own batch code and its own rows, and then appears as a material, with that code as its lot, in the batches that use it.
Water, salt, the small stuff. Record anything with a lot number. Municipal water doesn't have one.
Get the log
Download the material traceability log. The log with the example and a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. A fuller workbook that adds shipments is in food traceability Excel template, and capturing lots as they arrive in food receiving log template.
Where this stops working
Six rows a batch, four batches a day, lot numbers of twelve characters copied by hand with flour on your fingers. Transposed digits are the common failure, and you find out when you filter for a recalled lot and get nothing.
How TaroStack does it
TaroStack writes these rows for you.
The lot is captured once, at receiving. Type it, or scan the supplier's GS1-128 case label and the lot and use-by date fill in.
A batch takes from lots. Record the batch and each ingredient comes off the lot that's due first. The batch record notes which lots were consumed, automatically. Two lots in one batch are both recorded.
Sub-recipes carry through. A blend made ahead is its own batch and lot, and the trace follows it into whatever used it.
Both directions, one screen. Start from the supplier's lot and see every batch it reached, what's still on the shelf, and every customer who got those batches.
| The job | Log sheet | In TaroStack |
|---|---|---|
| Supplier's lot | Copied by hand, each batch | Captured once, at receiving |
| Lots used in a batch | Six rows written | Recorded with the batch |
| Where a lot went | Filter the sheet | The lot's trace |
| On to customers | A second record | Same trace |
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.
