ERP for the food industry is often built disconnected from the maintenance system, under the implicit assumption that batch status depends only on quality test results. The reality is more complex: under ISO 22002-100:2025 §9.3, every line stoppage — even a short repair — requires a post-repair sanitation sign-off with two-tier approval (technician and QA) before the line is allowed to run again. If that sign-off hasn't been completed but the ERP has no visibility into that fact, a batch produced right after that stop can still show as "ready to ship" in the system — a direct break point between maintenance data and the shipping decision.
This is the core difference between food-industry ERP and generic manufacturing ERP: it's not just about managing inventory and orders, but about knowing when to REFUSE to move a batch into ready-to-ship status because of an open maintenance event tied to the equipment that produced it.
Why batch status in a food-industry ERP isn't just about test results
An FSSC 22000 auditor uses a "backward trace" technique: pick a released batch, trace it back to the line and production window, then cross-check it against the maintenance work-order history for that exact window. If there was a stoppage during that production window without a matching, correctly timestamped sanitation sign-off, that's a major nonconformity under Clause 9 — regardless of whether the batch's quality test results passed. In other words, a batch can pass 100% of its quality specs and still be "not clean" from a compliance-record standpoint if the ERP never cross-checks it against the maintenance event.
Similarly, when equipment goes through a Management of Change (MOC) process under FSSC 22000 Clause 2.5.15(b), the relevant HACCP plan must be updated accordingly. If a batch is produced on equipment mid-MOC, before its Hygienic Design Risk Assessment is closed, that batch should in principle be assessed separately before release — a decision the ERP cannot make on its own unless it receives a signal from the equipment change-management system.
Three common batch-status break points
Break point 1 — ERP doesn't get a signal when a sanitation sign-off is missing its second signature
When the CMMS logs "task complete" right after the technician's signature, before the independent QA signature exists, and the ERP reads that as "equipment ready to run," batches produced right after can be processed as normal while the actual compliance record is still incomplete.
Break point 2 — Allergen changeover doesn't lock the adjacent batch
When a line switches from an allergen-containing product to one without, the changeover cleaning process needs swab validation before line clearance. If the ERP has no mechanism to lock the first batch produced after a changeover until swab confirmation passes, the risk of cross-contact from the prior run can slip through without a system-level checkpoint.
Break point 3 — Master Asset Register isn't linked to batch scope
ISO 22002-100:2025 §9.3 requires every food-safety-relevant asset to be within preventive-maintenance scope, tracked via a Master Asset Register. When the ERP doesn't know which equipment falls under this scope, or whether that equipment is under a temporary repair pending a permanent fix, assessing risk for a batch produced on that equipment becomes a manual, easily-missed task.
The QA lens: what conditions must be met before a batch can go to ready-to-ship
Before a batch is allowed to move to "ready to ship" status, QA needs to confirm at minimum: quality test results meet specification, no maintenance event during that batch's production window is still missing a two-signature sanitation sign-off, no MOC process tied to that equipment is still open on its risk assessment, and if an allergen changeover preceded that batch, the swab confirmation passed. When these conditions live scattered across a disconnected CMMS and ERP, QA has to cross-check manually — exactly the kind of task most likely to get missed under shipping-deadline pressure.
Illustrative scenario: closing the gap between a maintenance event and batch status
This is an illustrative scenario for a common type of problem in the industry, not a specific case from any named plant: a packaging line has a short stop to fix a sensor, signed off immediately by the technician, but the second QA signature isn't added until end of shift — meanwhile, three batches are produced and the ERP moves all three to "ready to ship" based on passing quality results. When the QA signature delay is discovered, those three batches have to be held for additional assessment — something that wouldn't have needed to happen if the ERP had received a "pending confirmation" signal the moment the sanitation form was still missing its second signature, instead of assuming the equipment was "ready" as soon as the technician closed the work order.
Reference table: maintenance event — batch-status impact — evidence needed — system link
| Maintenance event | Batch-status impact | Evidence needed | System link |
|---|---|---|---|
| Sanitation sign-off missing second signature | Hold batches from that production window in pending status | Technician + QA signature, timestamp | ERP receives real-time "pending confirmation" signal from CMMS |
| Equipment MOC with open risk assessment | Separate assessment for batches on that equipment | MOC record, Hygienic Design Risk Assessment | ERP locks batch status until MOC closes |
| Allergen changeover without passed swab | Lock the first batch produced after changeover | Swab result, line-clearance checklist | ERP blocks status change for the adjacent batch |
| Equipment under temporary repair | Additional risk assessment for related batches | Temporary-repair record, planned permanent-fix date | ERP cross-checks Master Asset Register in real time |
Conclusion
"A good food-industry ERP isn't the one that ships fastest — it's the one that knows to refuse 'ready to ship' status when an open maintenance event sits behind that batch."
Three things worth doing this week if you are evaluating or running an ERP at a food plant:
- Check whether the ERP receives a real-time signal from the CMMS when a post-repair sanitation sign-off is still missing its second signature.
- Confirm the lock mechanism on the first batch produced after an allergen changeover, held until swab confirmation passes.
- Try a backward trace: pick a released batch and check whether any maintenance event during its production window is still open — if the ERP can't answer that in a few minutes, that's the break point to prioritize.