Your supplier emails on a Friday afternoon. Lot 4471 of a spice blend is being recalled. The notice is two paragraphs long and it is asking you four questions, even if it does not phrase them that way.
- Did you receive any of the affected lot?
- Which of your batches did it go into?
- What did those batches become, and how much of each?
- Who received the finished product, on what date, in what pack size?
Answering one and two is usually possible. Three and four are where producers discover what their records are actually worth. This page is the procedure for answering all four, the two directions you have to be able to trace in, and the specific gaps that force a wider withdrawal than the contamination justifies.
Why the answer has to be narrow
A recall costs what it touches. If you can prove that lot 4471 went into three batches, and those three batches became 412 jars that went to two clients on two delivery dates, you withdraw 412 jars.
If you cannot, you withdraw everything made in the window the lot could plausibly have been open — which is every batch of every product using that spice blend, for however many weeks the bag lasted. The contamination did not get worse. Your records did.
That gap between what is affected and what you can prove is affected is the entire cost of poor traceability, and it is paid in product, freight, client relationships and the week you spend on it.
The chain you need intact
Every question above is answerable if five links are recorded and connected:
| Link | What it has to say |
|---|---|
| Ingredient and supplier lot | Which lot of which ingredient, received when |
| Recipe version | The exact version used, not "the recipe" |
| Batch | Quantities in, yield out, when, by whom |
| Packaging | Units produced and the pack size they went into |
| Client and delivery | Who took how many, and on what date |
Break any one link and the chain stops carrying information. The commonest break is between ingredient lot and batch — the batch is recorded, the lot is not, so you know what you made and have no idea what went into it.
Tracing forward: from a lot to the clients affected
Forward tracing answers "who has the product". Work in this order and do not skip step two.
Confirm you received the lot. Goods-in records or supplier invoices. If you never took delivery of 4471, you are done in ten minutes, and it is worth documenting that you checked.
Find every batch that drew on it. This is the step that needs a lot code against a batch, not against a delivery. If your records say "spice blend, 2 kg" with no lot, you cannot distinguish the batch made from the recalled bag from the one made from the bag before it, and every batch in the window becomes suspect.
List what those batches became. Product, batch code, units produced. A batch that was split across two products needs both.
Match units to despatch. Which clients received units from those batches, how many, and when. Partial deliveries matter — 200 jars of a 412-jar batch going to one client and 212 to another is two different notifications.
Account for what is still yours. Stock on hand, product still in your own warehouse, samples retained. This is the part you can act on immediately, and the part an investigator will ask you to quarantine first.
Write down what you did. The trace itself is a record. It is what you show a client who asks whether you were affected, and it is what stops you repeating the work when the second question arrives on Monday.
Tracing backward: from a complaint to the cause
Backward tracing answers "what went wrong". It starts from a single unit — a customer complaint, a failed test, an off-flavor report — and runs the chain in reverse: unit to batch, batch to recipe version, recipe version to every ingredient lot that went in.
The recipe version is the link people miss. If a recipe was changed three months ago and the record says only "Chili Oil, v-current", you cannot tell whether the batch in question was made to the old formulation or the new one. That distinction is often the whole investigation — a process step that changed, a supplier that changed, a quantity that changed.
This is why a published recipe version has to be frozen rather than edited in place. A batch record that points at a mutable recipe is a batch record that describes something that no longer exists.
The five gaps that widen a recall
In roughly the order they cost people money:
- Lot codes recorded at delivery but not at use. You know the lot came in. You cannot say which batch it went into. Scope becomes the whole window.
- A recipe edited in place. The batch record points at a formulation that has since changed, so you cannot say what was actually made.
- Despatch recorded in units, production recorded in batches. No link between them, so you can name affected batches and not the clients who got them.
- Partial deliveries collapsed into one line. Two clients got product from one batch, the record shows one delivery, and both get notified because you cannot split it.
- Sub-recipes untracked. A base sauce made on Tuesday went into four products on Thursday. If the base is not itself a traceable batch, the lot trail stops at the base and every downstream product is suspect.
The 24-hour problem
If you handle foods on FDA's Food Traceability List, the agency can ask for your traceability information as an electronic sortable spreadsheet within 24 hours of the request. That requirement is what makes paper records genuinely inadequate rather than merely awkward — not because paper is unreliable, but because a binder cannot be sorted and sent inside a day.
Whether that rule binds you specifically is a narrower question than most vendors imply. Which producers FSMA 204 actually covers works through the scope, the exemptions and the July 2028 date.
Run the drill before you need it
A traceability exercise is picking one ingredient lot at random and tracing it all the way to clients, then picking one finished unit and tracing it back to lots, against the clock. Auditors ask for it. More usefully, it tells you which of the five gaps above you have, on a day when nothing is actually contaminated.
Do it once a quarter, write down how long it took, and keep the result. If it takes more than a couple of hours, you have found the link that will cost you.