A traceability system is a set of records that lets you follow any one thing you made back to what went into it and forward to who received it. It doesn't have to be software. It has to be four records that connect: what came in, what was made, what went out, and what's left. What connects them is the lot: a code that names one delivery or one batch, written on the goods and on every record that touches them. If a supplier calls about a bad drum, the system tells you which batches used it and which customers have those batches. If a customer calls about a bottle, it tells you what was in it. A manufacturer of anything, food, cosmetics, candles or parts, needs the same four. Below are the records for a made-up hot sauce maker, a test, and a file.
The short version
- Four records: received, made, shipped, on hand. Each one carries a lot.
- A lot names one delivery or one batch. It's on the goods and on the paper.
- Back: from a finished lot to every input lot and its supplier.
- Forward: from an input lot to every batch, and every customer.
- The amounts have to add up: made = shipped + left + thrown away.
- Test it: pick a lot, trace it both ways, and time it.
- TaroStack notes the lots a batch used when you record it. More below.
The four records
| Record | What it holds | Example |
|---|---|---|
| 1 What came in | Item, supplier, the supplier's lot, date, amount, and your lot | Nov 3: 400 lb red jalapeños, Valley Growers, their lot VG-2291, our lot P-1103 |
| 2 What was made | The batch's lot, date, amount made, and the lot of every input | Nov 5: batch HS-1105, 480 bottles. Peppers P-1103, vinegar V-0928, bottles B-0714, caps C-0802 |
| 3 What went out | Customer, date, product, lot, amount | Nov 9: 120 bottles of HS-1105 to Corner Market, 240 to Island Grocers. Nov 12: 60 at the farmers market |
| 4 What's left | Stock on hand by lot, and what was thrown away | Nov 20: 60 bottles of HS-1105 on the shelf |
Each record alone is something most businesses already keep: a receiving log, a batch sheet, invoices, a count. What makes them a system is the lot appearing in each. Record 2 names the lots from record 1. Record 3 names the lot from record 2. Take the lot off any one of them and the chain is cut there.
What a lot is
A lot is a quantity of one thing that can be treated as the same: one delivery from one supplier, or one batch made in one go. You decide how big. A lot that covers a whole week of production is easy to keep and means that one bad bottle puts a week of product in question. A lot for each batch keeps a problem small.
The code can be anything that doesn't repeat. This maker uses letters for the item and the date: HS-1105 is hot sauce made on November 5. It's printed on every bottle and written on every case. Building one is in how to create lot numbers, and the two words are untangled in batch number vs lot number.
Back and forward
Back starts from a finished product. A customer has a bottle marked HS-1105. Record 2 says that batch used peppers P-1103, vinegar V-0928, bottles B-0714 and caps C-0802. Record 1 says P-1103 came from Valley Growers on November 3, their lot VG-2291.
Forward starts from an input. Valley Growers calls about VG-2291. Record 1 says that's your P-1103. Record 2 says P-1103 went into HS-1105, and only that batch. Record 3 says who has HS-1105, and record 4 says how much is still yours to pull.
The rule of thumb is one step each way: you know who you got it from and who you gave it to. Your supplier and your customer do the same, and the chain reaches from the field to the shelf. That idea is in one up, one back traceability.
It has to add up
A trace that finds names isn't finished until the amounts agree.
| Lot HS-1105 | Bottles |
|---|---|
| Made | 480 |
| Corner Market | 120 |
| Island Grocers | 240 |
| Farmers market | 60 |
| On the shelf | 60 |
| Accounted for | 480 |
Four hundred and eighty made, 480 found. The same goes for the peppers: 400 pounds received, 380 into the batch, 20 trimmed and thrown away. If 30 bottles can't be found, you don't know whether they were sold, given away or broken, and in a recall those are the ones that matter.
The test
Pick a lot. Trace it forward to every customer and back to every supplier, from your records alone. Check the amounts. Write down how long it took and what you couldn't find.
| Lot | Direction | Minutes | Gap found |
|---|---|---|---|
| HS-1105 | Forward | 12 | Farmers market sales had no customer |
| P-1103, peppers | Forward | 6 | |
| HS-1105 | Back | 4 | Salt had no lot written down |
This maker's first test found two gaps. Sales at a market can't name a buyer, so they're recorded as one line for the day. And salt, bought at a warehouse club, had never been given a lot. Both are small, and both would have been found the hard way otherwise. A fuller exercise is in mock recall and traceability exercise.
What it's kept in
| Kept in | Works when | Breaks when |
|---|---|---|
| Paper logs | A few batches a week, one person | Two people, or a search across months |
| Spreadsheets | A few products, careful typing | A lot code is mistyped once; blends and rework |
| Software | Lots are recorded as part of doing the work | It's set up and then worked around |
A spreadsheet version is in food traceability Excel template. The test above is the same whatever it's kept in.
Get the file
Download the traceability system sheet. Two sheets and a read-me: the four records with what each holds and what it links to, and a trace test log. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The weak record is nearly always the second. Receiving has a delivery slip to copy from, and shipping has an invoice. The batch sheet is filled in by someone with wet hands in the middle of a production day, and "which lot of vinegar" gets a dash. One dash, and every bottle from that batch traces back to a question mark.
How TaroStack does it
TaroStack fills in the second record as the batch is recorded.
Receiving gives each delivery a lot, with the supplier's own lot number beside yours. A supplier's GS1-128 case label can be scanned to fill it in.
Record a batch and it notes which lots it used, automatically. Nobody writes them down.
What ships is recorded by lot, and stock on hand is kept by lot.
One report, both ways: which supplier lots went into which batches, which customers got them, and what's still on your shelves.
Timed, logged traceability drills you can show a buyer or an inspector.
| The job | Four separate records | In TaroStack |
|---|---|---|
| Which lots a batch used | Written on the batch sheet, or not | Noted with the batch |
| Who got a lot | Search the invoices | One report |
| Does it add up | A sum by hand | Stock by lot |
| The trace test | An afternoon | A timed drill, logged |
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.
