TL;DR
When a supplier calls about a bad lot, you have hours, not days, to figure out which of your finished products it touched. That answer lives in your intake records. For most small producers, the gap opens at receiving: an ingredient shows up with a handwritten receipt, gets stacked next to last week's delivery, and the link between that lot and the batch it ends up in is gone before you ever fire up a kettle. Closing the gap comes down to three habits: capture the purchase cleanly when it arrives, tag the physical container so it can be identified later, and record which lot went into which batch at the moment you use it. FourFoxes is built to make each of those fast. What it will not do is stop someone from dumping two deliveries into one bin. That part is still on you.
You built your brand on knowing your ingredients. You know which farm grows the peppers you want, which salt you trust, which supplier ships on time. But knowing your ingredients and being able to prove where a specific lot went are two different things. The first is why customers love you. The second is what stands between a supplier's phone call and a very bad week.
This is a Founder problem more than an Operator one, because you are the one who answers when something goes wrong. So here is where the trail breaks, what your records have to show, and how to build a chain that holds up without turning receiving into a data-entry shift.
What ingredient and lot traceability means
Traceability is the ability to follow a specific ingredient lot forward into every finished product it became, and backward from a finished product to every ingredient lot in it. A "lot" is not an abstraction. Under the preventive controls rule that covers most food facilities, a lot is the food produced during a period of time and identified by an establishment's specific code (21 CFR 117.3). Acidified foods producers work from the same idea, defined as the product produced during a period indicated by a specific code (21 CFR 114.3(c)). Whichever rule you fall under, the principle is identical: your incoming ingredients arrive in their suppliers' lots, your finished product leaves in yours, and traceability is the bridge between the two. It is only as strong as the record you make when the two meet.
Miss that record once, and you have a mystery ingredient: something in a batch that you cannot tie back to a supplier or a purchase. One mystery ingredient is all it takes to turn "which products do we pull?" into "we have no idea, so we pull everything."
01The Three Ways Ingredients Show Up: And Why the Paperwork Rarely Matches.
Small producers take in ingredients in a few very different ways, and each one hands you a different kind of paperwork:
- Straight from a farm or ag producer. You drive out, you write a check, you load up. Sometimes you get an invoice. Sometimes a receipt. Sometimes it is handwritten on the back of something. At the height of harvest, you might make this run twice a week.
- A delivery from a supplier. Usually the cleanest case: a printed invoice or packing slip with lot information already on it.
- A pickup at a wholesaler. A register receipt that may or may not identify the lot at all.
Three intake paths, three formats, and only one of them reliably comes with the lot detail you need. The farm run, which is often your most important and most perishable ingredient, tends to come with the worst paperwork. That mismatch is where records go missing, and it happens before production even starts.
02The Question You Cannot Answer Fast Enough: "Which Batches Used That Lot?"
Here is the moment this all exists for. A supplier texts: one lot of an ingredient may have a problem. Now you need to answer one question, fast: which of your batches used that lot, and where did those batches go?
If your intake records are clean, that is a lookup. If they are not, it is an archaeology project across binders, texts, and memory, while the clock runs. The difference between those two experiences is not how careful you are in the moment. It is whether the link was captured back when the ingredient came in the door, calmly, when nothing was wrong yet.
This is the same spreadsheet-versus-system split you already know, pointed at receiving. A spreadsheet can hold the data, but it cannot connect an incoming lot to a finished batch on its own, and it certainly cannot do it in seconds while a supplier waits on the phone.
03What Your Records Actually Have to Show: Straight From the Rule.
Whatever you make, the recordkeeping duty is not vague, and it is not optional. Two rules cover most small producers.
If you are a food facility under the preventive controls rule, the baseline is straightforward. The records you are required to keep have to be retained for at least two years after you make them, and they have to be retrievable. Offsite or electronic storage is fine, as long as you can produce the records onsite within 24 hours of an FDA request, and electronic records count as onsite when you can pull them up there (21 CFR 117.315). On the supplier side, if you rely on a supplier to control a hazard in an ingredient, you need a written supply-chain program that documents how you approve and verify that supplier (21 CFR Part 117, Subpart G). Your supplier paperwork is part of the record, not a nicety.
If you make acidified foods, like we do at Off The Deck Hot Sauce, Part 114 is more specific and, in one way, stricter:
- Raw material and supplier records. You must maintain records of examinations of raw materials and packaging materials, and of suppliers' guarantees or certifications that verify compliance with FDA regulations (21 CFR 114.100(a)).
- Lot-level detail. Production records have to carry enough information, including product code and date, to permit a hazard evaluation of each lot or batch (21 CFR 114.100(b)).
- Distribution and segregation. You must be able to identify where finished product went so specific lots can be segregated if they turn out to be contaminated (21 CFR 114.100(d)). That is the recall lookup, written into the rule.
- Retention. These records must be kept for three years from the date of manufacture, a year longer than the preventive controls baseline, at the plant or another reasonably accessible location (21 CFR 114.100(e)).
Whichever bar applies to you, notice what it adds up to: you are already required to keep supplier records, tie production to lots, and hold a multi-year trail an inspector can ask to see. You have to do this either way. The open question is whether your method survives a busy harvest week.
04Capturing Intake Without the Data-Entry Tax: Scan, Confirm, Save.
The reason intake records go missing is rarely laziness. It is friction. Nobody wants to hand-key an invoice at the end of a delivery run. So FourFoxes starts by taking the typing out of it.
Scan the invoice with the invoice scanning tool, confirm the details it pulled are correct, and hit save. For a normal printed supplier or wholesaler invoice, that is the whole job. The purchase, the supplier, and the lot information land in your records without you transcribing a thing.
An honest caveat, because you will hit it: the scanner handles printed invoices well, but a generic register receipt with no lot detail, or a farm receipt scrawled by hand, is still going to need a manual touch. The tool cannot read what the paper does not clearly say. For those cases you enter it yourself, which is the same work you would do anyway, just captured in one place instead of a binder that lives in a wet production room.
05From Bin to Batch: Tag It, Then Scan It.
Capturing the purchase is half of it. The other half is connecting the physical thing in your hands to that record, so the link survives all the way into a batch.
FourFoxes lets you print QR tags for your ingredients. Put a tag on the bin of onions from the farm, the bag of salt from the wholesaler, any container tied to a specific purchase. The tag carries the lot's identity on the outside of the container, where your team can see it.
Then, when you make product, you scan the QR code as you pull each ingredient. That scan writes the ingredient lot straight into the batch record, building the traceability chain as you work instead of reconstructing it later. When the supplier calls, the chain is already there: this lot went into these batches, which became these finished products. That is the lookup instead of the archaeology.
06What a System Will Not Fix for You: The Part That Is Still on You.
No software earns your trust by pretending it does everything, so here is the honest line.
In peak season, when produce is coming in faster than you can process it, the discipline that matters is not combining lots. It is tempting to top off a half-empty bin of today's peppers with tomorrow's delivery, and the moment you do, you have blended two lots into one and broken the very traceability you are trying to keep. A tagging system makes the right habit easier and the record cleaner, but it cannot reach into your cooler and stop the mixing. That habit is yours to hold.
We would rather tell you that plainly than sell you a false sense of security. The tool removes the friction that makes people cut corners. The judgment is still human.
Frequently Asked Questions
How long do I have to keep ingredient and supplier records?
It depends on the rule you fall under. Under the preventive controls rule, records must be retained at least two years after they are prepared, and be retrievable onsite within 24 hours of an FDA request (21 CFR 117.315). Acidified foods producers keep records for three years from the date of manufacture (21 CFR 114.100(e)). Electronic records that stay accessible satisfy either bar.
What counts as a "lot"?
Under the preventive controls rule, a lot is the food produced during a period of time and identified by an establishment's specific code (21 CFR 117.3). Acidified foods use the same idea, the product produced during a period indicated by a specific code (21 CFR 114.3(c)). Your incoming ingredients arrive in your suppliers' lots; your finished product ships in yours. Traceability is the documented link between them.
Do I really need supplier certifications on file, or just my own records?
Both, in most cases. If you make acidified foods, the rule is explicit: you must keep records of suppliers' guarantees or certifications that verify compliance, along with your own examinations of raw materials (21 CFR 114.100(a)). More broadly, if you rely on a supplier to control a hazard in an ingredient, the preventive controls rule requires a written supply-chain program documenting how you approve and verify that supplier (21 CFR Part 117, Subpart G).
Can I keep all of this electronically instead of in binders?
Yes. Under the preventive controls rule, offsite and electronic storage are fine as long as you can produce the records onsite within 24 hours of a request, and electronic records count as onsite when you can access them there (21 CFR 117.315). A system that keeps records accessible for the full retention period meets the bar and is far easier to search when you need one specific lot.
What happens if my ingredient came with a handwritten or generic receipt?
The invoice scanner handles printed invoices cleanly, but a handwritten farm receipt or a generic register receipt without lot detail will need manual entry. You capture what the paper does not clearly show, once, at intake, so the record still exists when you need it.
Ready to close the gap at receiving?
Every ingredient that comes through your door is a link in a chain you may one day have to walk backward under pressure. FourFoxes is built to capture that link the moment it arrives and carry it all the way into the batch, so the answer is already waiting when the question comes.
See how FourFoxes worksBuilt for the batch. Ready for the audit.