TL;DR: A recall notice doesn't give you days to figure out your exposure — it gives you hours. This post walks through exactly what the clock looks like, what you need to produce, and why the records you have right now will either save you or sink you.
A few years ago, a garlic recall landed close to home.
I'm the co-founder of Off The Deck Hot Sauce, a fermented hot sauce brand we've been running out of Fargo since 2016. Garlic is in nearly everything we make. When the recall hit the news, I did what most small producers do: I pulled up the FDA announcement and started comparing it against what we had on the shelf.
We got lucky. The recall covered small consumer pouches, not the bulk bags we were sourcing. We were fine.
But I remember exactly how that morning felt. And I remember the thought I couldn't shake afterward: what if it had been the bulk bags?
At that point, we would have needed to answer three questions fast:
- Which of our batches used garlic from that specific lot?
- Which finished products came from those batches?
- Where did those products go — which markets, which retailers, which customers?
I didn't have clean answers to any of them. Not quickly, anyway. We were tracking things in a production spreadsheet, but keeping it current was a lot of work. During a normal week it was imprecise. During peak harvest — when we're running 12 to 18 fermentation batches across two fermentation styles, pulling peppers from three different farms and ingredients from five other suppliers — it would have been chaos.
What I realized in the days after that scare is that a recall doesn't punish negligence. It punishes imprecision. And being a small producer isn't a shield. It just means the consequences land harder.
What the clock actually looks like
Most small producers think of a recall as something that unfolds over days. It doesn't.
When the FDA contacts you, traceability records can be requested within 24 hours. That's not a future requirement — it's the standard. And that 24-hour window starts from the moment you receive the request, not from when you feel ready.
The first few hours of a recall look something like this:
Hour 0–2: Identify your exposure. You need to know, fast, whether any of your ingredient lots match the affected product. This sounds simple. If your records live in a binder, a spreadsheet, or your memory, it's not.
Hour 2–6: Map the affected batches. Once you know which ingredient lot is implicated, you need every batch it touched. Not roughly. Not probably. Exactly. Because what you can't account for, you have to assume is contaminated.
Hour 6–12: Identify finished products and distribution. Which finished SKUs came from the affected batches? Where did they go? Are any still on retail shelves? In your warehouse? In a customer's hands? This is where vague records become a financial decision: destroy what you can't account for, or risk a far worse outcome.
Hour 12–24: Prepare your FDA response. Records must be produced in an electronic, sortable format. If you're assembling that from handwritten logs, binder sheets, and three different spreadsheet tabs, you're not going to make it.
The part nobody talks about: the destruction decision
Here's what the garlic scare taught me that no compliance guide puts in plain terms.
When you can't prove which batches are clean, you can't keep them. You have to destroy everything you can't account for.
For us, a week of peak harvest production represents somewhere between 10% and 17% of our annual gross revenue. We're farm-to-bottle, sourcing fresh peppers from the Red River Valley during a compressed 6-to-10-week window. Lose a week of that, and you're looking at a five-figure hit — ingredients, kitchen time, labor, fermentation vessels sitting empty — before you've accounted for any recall logistics or legal exposure.
That loss wouldn't be caused by contamination. It would be caused by uncertainty. The inability to say, with precision, which batches used which lot.
That distinction matters. Contamination is a food safety problem. Uncertainty is a records problem. And records problems are solvable before a recall happens.
What "being small" actually means in a recall
Small producers sometimes assume that size is protection. If you're not a large national brand, the thinking goes, you're not a high-profile recall target.
That's not how it works.
Recalls aren't triggered by brand size. They're triggered by contamination events, supplier failures, and label errors — all of which happen to small operations at the same rate they happen to large ones. The number of food recalls rose 15% between 2020 and 2024, with roughly 300 food recalls in 2024 alone, leading to nearly 1,400 reported illnesses and 487 hospitalizations. Undeclared allergens, Listeria, Salmonella — these don't check your revenue line before they show up in your ingredient supply.
What size does affect is your ability to absorb the hit. Industry research from the Grocery Manufacturers Association estimates the average direct cost of a recall event at $10 million. That's the large-brand average. For a brand doing $300K a year, the proportional math is worse — not because the recall costs more in absolute terms, but because you have less runway, less insurance, and less margin to absorb a production stoppage while you sort it out.
Being small is an advantage in a lot of ways. It's not a shield.
What your records need to do in a recall
A lot of small producers have records. The problem isn't that nothing was written down. The problem is that what was written down can't answer the questions a recall asks.
Here's what your records need to do — specifically — when a recall clock starts:
Lot-level ingredient tracking. Every ingredient in every batch needs to be tied to a specific supplier lot. Not "we bought garlic from Farm X in October." The specific lot, the specific purchase, the specific bags that went into which batches on which dates.
Batch-to-ingredient linkage. Given a suspect lot, you need to surface every batch that touched it. In seconds, not hours.
Batch-to-product linkage. Given those batches, which finished SKUs did they produce? What were the lot numbers on the finished products?
Distribution records. Where did those finished products go? Do you have the invoices, the market dates, the wholesale accounts?
If you can walk that chain — ingredient lot to batch to finished product to destination — you've contained your exposure to what's actually affected. Everything else stays.
If you can't, you're making destruction decisions based on what you can't rule out.
What we built so the answer is always ready
The garlic scare is part of why FourFoxes exists.
When we started building the platform, the traceability question was the first thing we solved for. Every ingredient that comes into the kitchen gets a QR code label, printed at receiving. When a batch goes into production, every ingredient going into it gets scanned. The batch record is built in real time, not reconstructed at the end of the day from memory.
That 7am recall phone call now looks like this: open FourFoxes, find the affected ingredient purchase, and see every batch that contains it. The chain is already there. It was built at the moment the ingredient hit the production floor.
The difference isn't just speed. It's the difference between a manageable recall and a catastrophic one. Between pulling the three batches that are actually affected and destroying an entire week of production because you can't say with confidence which ones are clean.
What to do right now, before a recall happens
You don't get a warm-up round. The time to build the paper trail is before you need it.
A few concrete things worth doing this week:
Audit your current ingredient records. For your last five batches, can you tell me which supplier lot every ingredient came from? If the answer is "roughly" or "I'd have to dig," that's the gap.
Run a mock traceback. Pick an ingredient you used in the last 60 days. Try to trace it from the purchase receipt, through every batch it touched, to the finished products it produced. Time yourself. If it takes more than five minutes, you won't make the 24-hour window under pressure.
Check your distribution records. Do you know where your last three production runs ended up? Farmers markets, wholesale accounts, direct sales — do you have the documentation to contact those buyers quickly?
Evaluate your logging system. Not whether records exist, but whether they're precise enough to survive a regulatory request. A general note that "garlic from Valley Farm" was used isn't a lot number. It won't answer the question.
Frequently asked questions
What triggers a food recall?
Recalls are triggered by contamination events (Listeria, Salmonella, E. coli), undeclared allergens, foreign material, or label errors — either identified by the producer, flagged by a retailer, or detected through an FDA investigation or illness report. Supplier contamination, like a tainted ingredient lot, is one of the most common triggers for small producers who source from multiple farms or vendors.
How much time do I have to respond to an FDA recall request?
Under FSMA traceability requirements, records must be made available to the FDA within 24 hours of a request. That clock runs from the moment FDA contacts you — not from when you've assembled your records. Electronic, sortable format is required.
Do I need to destroy product during a recall?
Only product that is confirmed or suspected to be affected. The problem is that "suspected" is determined by your records. If you can't definitively rule a batch out, regulators will typically require it to be treated as affected. Precise lot-level traceability is what lets you contain a recall to the batches that are actually implicated.
Does this apply to small producers, not just large brands?
Yes. Recalls are triggered by contamination events and ingredient sourcing issues, not by brand size. Small producers face the same exposure — and proportionally less capacity to absorb the financial impact of destroying product or halting production during an investigation.
What's the simplest thing I can do today to improve my recall readiness?
Start tracking ingredient lot numbers at receiving — not just supplier name, but the specific lot or batch code on the bag or container. Link that to every batch you make. That single habit closes the biggest gap in most small-producer traceability systems.
FourFoxes is batch traceability and quality management software built for small food and beverage producers. Built for the batch. Ready for the audit.