If you run production, you've probably said some version of this: don't make me enter the same information three times.
You'd file that under convenience. File it under records instead, because every copy of a value is one more place that value can change.
01. Where the second copy comes from
Plenty of small producers I know start on paper. A check gets written on a log sheet at the equipment, and later someone copies it into a spreadsheet. That's two entries for one value, and the second one gets made from handwriting, at the end of a long day.
At Off The Deck Hot Sauce, we'd cleared out most of our duplicate entry before FourFoxes existed. The one that stayed was ingredient lot numbers.
One lot of an ingredient goes into several batches, and every batch that used it needed that lot code typed in again.
02. What retyping does to a record
None of this fails loudly.
A product name picks up a typo, then a second spelling, and over time the list of names gets dirty enough that a filter quietly misses rows. A date gets fat-fingered into 2125. A lot code goes in with two characters swapped.
Each one looks like nothing on the day it happens. It shows up later, when you search for a lot and a batch that used it doesn't come back, because the code on that batch doesn't match. During a trace, that missing row is the whole question. (More on that in A trace request starts with the code on the jar.)
03. Enter the lot once
In FourFoxes, you record the supplier purchase once. Packaging purchases link to the bill of materials. Ingredient purchases get attached to the batch record.
When one ingredient lot goes into several batches, you attach it to each batch. You don't retype it. The lot code and its details come across from the purchase record, and the amount used is deducted from ingredient inventory automatically.
The code on every batch is the code you entered when the ingredient came in.
04. The one step we kept manual
We could have tried to automate the link between ingredient lots and batches. We chose not to.
That link is the traceability record. If software guesses which lot went into which batch and guesses wrong, nothing warns you. The record looks complete. You'd find the drift at the worst possible time: in the middle of a trace, with a supplier recall or an inspector waiting on the answer.
So attaching an ingredient lot to a batch is a deliberate step, and we want you to take it on purpose. We removed the retyping. We left the decision with you.
05. On the floor and at the desk
The phone views in FourFoxes are optimized for production. Everything else is fully functional on mobile too.
06. What the inspector gets
When an inspector asks for records, the export pulls from what was logged. Nothing gets retyped for the report. Yearly batch and CCP reports export ready to email.
Three entries of the same lot code are three chances to get it wrong. Enter it once. Then make the link on purpose.
Questions people ask
Why is duplicate data entry a problem for batch records?
Every copy of a value is a chance for a typo, a misdated entry, or a mistyped lot code. Those errors are quiet. They tend to surface when you search for a lot during a trace and a batch doesn't come back.
How do you track one ingredient lot across several batches?
Record the lot once when it's purchased, then attach that purchase record to each batch that uses it instead of retyping the code. In FourFoxes the lot details carry across and the amount used is deducted from ingredient inventory automatically.
Should software link ingredient lots to batches automatically?
FourFoxes doesn't. The link between an ingredient lot and a batch is the traceability record, and an automated wrong guess would look complete until a trace exposed it.
Do I have to retype records for an inspector?
Not in FourFoxes. Exports pull directly from the logged records.