The one-lot test: seven questions every food processor should answer in minutes

Every serious buyer eventually asks a processor the same thing, in different words: "Show me where this came from."

It might come from an auditor, a retailer's quality team, an export buyer or a customer with a complaint. The request is always small. One lot number, one carton, one bottle. And the answer tells them almost everything about how the plant is run.

I call it the one-lot test. Pick any finished lot in your warehouse today and see how quickly, and how confidently, your team can answer the seven questions below. If the answers live in one system, it takes minutes. If they live in notebooks, spreadsheets and a WhatsApp group, it can take days, and the buyer will notice.

1. Which raw material went into this lot?

Start at the beginning. Which intake, from which supplier or farm, on which date, went into this batch? If several deliveries were blended, can you name all of them?

A good record links each finished lot back to the intake records that fed it, not just to "milk, Tuesday" or "cherry, week 42".

2. What did the intake checks say?

Most plants test at intake: weight, moisture, grade, a lab reading. The question is whether those results are attached to the delivery that went into this lot, or sitting in a separate book.

If a buyer asks "was this raw material within spec when it arrived?", the answer should come from the same record, not a search through a shelf of binders.

3. Which recipe and production run made it?

Which recipe or formulation was used, on which line, in which shift? Was the recipe the current version? Did the yield look normal for that run?

This is where a lot of traceability breaks quietly. The plant knows what it usually does. The buyer wants to know what it actually did that day.

4. Which quality checkpoints did it pass, and who signed them?

In-process checks, final checks, any holds and releases. For each one, the record should show the result, the time and the name of the person responsible.

A checkpoint without a name is a tick in a box. A checkpoint with a name and a timestamp is evidence.

5. What were the conditions while it was made and stored?

Temperatures, cold-room readings, anything that affects safety or quality. If the plant uses sensors, the readings should stay with the batch that was in the room. If a reading drifted, the record should show the alert and who acknowledged it.

This is the question that separates "we monitor our cold rooms" from "here is what this lot experienced".

6. Where is every unit of it now?

How much was produced, how much is still in stock, which location it sits in, and which customers or dispatches received the rest. If you had to stop this lot today, could you name everyone who has it?

That's the forward half of traceability, and it's the half that matters most on the worst day a plant can have.

7. Can you hand the buyer the record?

Finally, can you produce the whole story as one clean document, without retyping it? An answer pieced together from five sources in a hurry invites more questions. A single batch record, exported from the system that captured it, closes them.

Running the test

Try it this week. Pick a lot at random, not your best one, and time how long it takes to answer all seven questions. Note where the trail goes cold. That gap is usually where re-entry happens: data written on paper, then typed into a spreadsheet, then copied into a report.

Then ask the harder question: if a buyer picked a different lot tomorrow, would the answer be just as fast?

Why we built FactoraERP around one record

When we designed FactoraERP, this test was the point. Production, inventory, quality and finance sit on one record of what the plant actually did, with batch-level traceability from farm intake to dispatch. Quality checkpoints and lab tests live next to the batches they belong to, every action is logged in an audit trail, and staff can capture data on mobile even offline, syncing when the signal returns.

Our IIoT module, FactoraIoT, adds the conditions: live sensor readings that stay with the batch, alerts that are acknowledged by a named person, and a batch record the plant can export as a PDF.

None of this replaces a good quality team. It gives that team a record they can stand behind when someone asks, "Show me where this came from."

If your plant runs the one-lot test and the trail goes cold somewhere, I'd like to hear where. And if you'd like to see the test run in FactoraERP, our founding customer programme is open: factoraerp.com (pricing on request).