This summer, a Salmonella outbreak tied to fresh jalapeños moved through the supply chain the way these things always do: it branched. The peppers came from one distributor. They ended up in salsas, guacamole, prepared meals, and dressings made by companies that never grew a single pepper. When the recall landed, the FDA said the quiet part plainly: any manufacturer who used the recalled peppers should figure out whether they need to recall their own product too.
Read that again if you make food for a living. The recall didn't start with those manufacturers. It started two or three steps upstream, with an ingredient they bought in good faith. And it still became their problem to solve, on their clock, with their name on the label.
That is the recall most small producers never plan for. You plan for your own mistake. You don't plan for a supplier's.
01The question that decides your week
When a supplier tells you a lot you received has been recalled, one question determines how the next few days go: which of my finished batches used that lot, and where did they go?
Everything hangs on it. If you can answer it precisely, you pull the batches that actually touched the bad lot, you notify the buyers who actually received them, and you're done. If you can't answer it precisely, you pull everything you're unsure about. That's the difference between a contained recall and a guess.
I've lived both versions.
02Two ways to answer, and the hours between them
Before I built FourFoxes, I ran the records for Off The Deck Hot Sauce out of a spreadsheet. Here's how that same question would have played out.
If, and this is a real if, we'd written the supplier lot numbers into the spreadsheet, we could have pieced it together in maybe a couple of hours. Cross-reference the lot against the batch sheets, find the batches, work out where they shipped. Slow and manual, but possible.
If we hadn't logged the lot numbers, and plenty of producers don't, it gets ugly. Now you're tracing every purchase back to its source, trying to reconstruct which batches a given delivery might have gone into, and when you can't be sure, you pull all of it. You throw out clean product because you can't prove it's clean.
In FourFoxes, the same question is a lookup. You find the ingredient lot, click Trace Back, and see every batch that lot went into. From there the finished batch records tell you where each one shipped. In seconds, not hours.
The difference isn't the software being clever. It's that the link between a supplier lot and a finished batch got recorded the moment it happened, instead of being reconstructed from memory under pressure.
03What's actually on the line
People assume the worst part of a recall is the health risk, and of course that comes first. But talk to a founder who has been through one and they'll tell you what keeps them up at night afterward: reputation.
Your brand is a promise that your product is safe and good. A recall tests that promise in public. Handle it fast and precisely and you can come out with your credibility intact, sometimes stronger. Handle it slow and sloppy, pulling product you can't account for and missing buyers you should have notified, and you've spent trust you may never fully earn back. Trust is the hardest thing for a small brand to rebuild.
Overpulling doesn't only cost you the product you destroy. It tells your retailers and your customers that you don't actually know what's in your own jars. That's the message you can't afford to send.
04Why Off The Deck could answer fast
When the jalapeño recall hit, it didn't touch us. Our supply chain is short by design: we work directly with our farmers. Fewer hands, fewer hops, fewer places for a problem to hide.
A short supply chain isn't the whole answer, though, and I want to be honest about that. A short chain lowers the odds. Records tell you what actually happened. We track lot numbers on what comes in, so if a farmer ever called us about a specific harvest lot, we wouldn't be guessing which batches to look at. We'd know. The short chain and the records do different jobs, and you want both.
05The mistake almost everyone makes
Here's the uncomfortable part. Tracking supplier lot numbers is frighteningly uncommon among small producers.
It's understandable. At receiving, a lot number feels like noise. You've got product to make. Writing down a string of digits off the side of a case feels like the least urgent thing in your day, right up until the moment it's the only thing that matters.
A jar code that can't reach back to a supplier lot can't survive a trace. If your batch record says "peppers" but not which peppers, from which delivery, on which lot, then when a supplier recall comes you have nothing to trace with. You're back to pulling everything.
The fix is boring and it works: capture the supplier lot at receiving, tie it to the batch when you produce, and keep the two connected. Do that consistently and a supplier recall becomes a lookup instead of a crisis.
06The plan the rule assumes you have
For food with a hazard requiring a preventive control, the FDA requires a written recall plan (21 CFR 117.139). That plan has to spell out how you'll notify the buyers you shipped to, how you'll check that the recall actually reached them, and how you'll dispose of the affected product.
Notice what every one of those steps takes for granted: that you can identify the affected product in the first place. The plan is the choreography. Traceability is what lets you dance it. A recall plan you can't execute, because your records won't tell you which batches are involved, is choreography for a dance you can't do.
07Be able to answer before you're asked
You can't control whether a supplier's ingredient gets recalled. You can control whether that turns into a two-minute lookup or a two-day scramble.
FourFoxes keeps the link between every supplier lot and every batch it touched, so when the question comes, you answer it precisely, pull only what you have to, and protect the reputation you spent years building.
Questions producers ask
If my supplier recalls an ingredient lot, do I have to recall my finished product?
Possibly. FDA advises manufacturers who used a recalled ingredient to determine whether their own product needs a recall. If any of your finished batches used the recalled lot, those batches are implicated, and you need to identify and address them.
How do I find which of my batches used a recalled ingredient lot?
If you record the supplier lot at receiving and tie it to each batch, it's a lookup: find the lot, trace it to every batch that used it, then to the buyers who received them. Without those links you're reconstructing it by hand, and usually pulling more product than you have to.
Does the FDA require a written recall plan?
For food with a hazard requiring a preventive control, yes. 21 CFR 117.139 requires a written recall plan that covers notifying direct consignees, conducting effectiveness checks, and appropriately disposing of recalled product.
What records make a supplier recall manageable?
Supplier lot numbers captured at receiving, linked to the finished batches that used them, and linked forward to the buyers who received those batches. That chain turns a recall from a guess into a targeted action.