
Ingredient lots you must answer for
Goods-in books the lot, cert and best-before; a supplier alert traces forward in seconds.
A supplier flags a lot and the mock recall is a day of batch sheets and phone calls. Bulk traces it to every pallet before the call ends, and the CCP checks are signed where they happened, so the auditor sees what the line saw.

Goods-in books the lot, cert and best-before; a supplier alert traces forward in seconds.

CCP temperatures and metal-detector checks signed where they happen, held against the batch.

The allergen matrix and cleandown sign-off go on the record, not one person's head.

Keep the accounts system; Bulk runs the plant floor between the lines and it.

OCR reads the delivery note and COA; lot, cert and best-before land on the batch.
See data threadLot FL-2291 · COA attached · best-before 14 Nov · 24 sacks

Mix, cook, fill, pack: each step stamps operator, line and time; CCP checks land in line.
See productionR. Mensah · Kettle K-02 · core 84 °C at 09:15

A CCP out of limit holds the batch on the spot; no suspect pallet leaves the store.
See qualityMetal detector test piece missed on Line 2 · 3 pallets held

A supplier flags a lot; every batch, pallet and delivery it reached lists in one query.
See data thread6 batches · 41 pallets · 9 deliveries · 4 customers reached

A supplier alert means a day of batch sheets and phone calls.
A missed temperature check surfaces at the audit, not at the line.
The changeover sign-off rides on whoever knows the line today.

Ingredient lot to pallet, one genealogy, no batch-sheet archaeology.
Data threadA failing check holds the pallet now, not weeks later at audit.
QualityTrace a lot forward or a pallet back in one query.
Data threadFEFO and a shelf-life risk warn before the write-off reaches the dock.
InventoryThe audit becomes an export, not a fortnight of folder-hunting.
AuditsA slow changeover shows on the wall TV while you can still act.
OEE & analyticsNeither, on purpose. An MES assumes an integrator and a PLC network; an ERP wants your whole business re-platformed. Bulk is the batch-traceability, production-tracking and food-safety layer for the plant floor. It captures lot genealogy, drives the recipe and CCP checks and holds the audit record, and sits alongside whatever ERP or accounts system you already run. Most plants our size are replacing clipboards and spreadsheets, not systems.
Minutes, not a day. Every batch carries the ingredient lots booked at goods-in and every process step, so you trace a suspect lot forward to every batch, pallet and customer it reached, or a finished pallet back to its ingredients, in one query. A mock recall is timed against that, and the real one is contained before it spreads.
Yes. Critical control points, metal-detector checks, temperatures and QC results are captured in line and stay attached to the batch. A failed or missed check holds the pallet on the spot and escalates, and the food-safety record an auditor asks for assembles from the production record rather than a folder of paper.
Yes, that is a side effect of holding the work on one record. The genealogy, CCP logs, allergen checks and cleandown sign-offs an auditor wants are drawn from the same live data, so preparing for a BRCGS, SALSA or customer audit becomes an export instead of a fortnight of reconstruction.
No. Bulk runs the plant floor and its records; inventory and dispatch draw from the same batch data, but your ERP or accounts platform stays. This is the layer between the lines and the back office, not a rip-and-replace project, and not a big-bang cutover.
One product, end to end first (goods-in to dispatch, proven on real batches in weeks), then the rest of your lines follow on the same pattern. You are an early-access customer, so you work directly with the build team and the configuration is shaped around your HACCP plan and your plant, not a template.