Expiry write-offs in food manufacturing are almost never a surprise at the end. They are a surprise at the point of discovery — when someone walks the warehouse and finds pallets that should have been used weeks ago, or when the monthly inventory reconciliation surfaces write-offs that accumulated invisibly through individually reasonable decisions. The data to prevent these write-offs was available throughout. The system holding the data just was not connected to the decisions that produced the waste. --- Why Expiry Problems Persist Despite FEFO Systems Most food manufacturers have FEFO logic — First Expiry First Out — configured in their ERP or WMS. They know it matters. They have set it up. And they still write off expired stock. The gap is not in the policy. It is in the execution. FEFO logic in ERP calculates the correct pick sequence at the time of a transaction. But the decision to allocate a specific batch to a production run, to commit it to a customer order, or to prioritise its use over a newer batch happens earlier. In planning, in scheduling, in informal conversations between the warehouse team and production. Those decisions are frequently made without the system's FEFO calculation being consulted, because the calculation requires a system query that is slower than a verbal instruction. Decision Point Where It Currently Happens What FEFO Compliance Requires Batch allocation to production run Planner selects from available batches in ERP — often by most recent arrival Automatic allocation to earliest-expiring eligible batch Order fulfilment batch selection Warehouse operator picks from nearest pallet System-enforced pick from FEFO batch regardless of location Near-expiry stock identification Physical walk or periodic ERP report Real-time alert when a batch reaches defined days-to-expiry threshold Near-expiry prioritisation Informal escalation to planner or sales team Automated schedule and order prioritisation for at-risk batches Each decision point in the table above is currently managed informally, with variable adherence to FEFO logic depending on the individual making the decision. System failure is not a missing feature in ERP — it is the absence of enforcement at the point of decision. --- The Three System Failures That Produce Expiry Write-Offs Batch allocation without expiry visibility. When a production planner allocates raw material batches to a production run, the allocation is typically made against availability. Which batches are in stock Unless the planner actively queries the expiry dates of available batches and manually selects the earliest-expiring ones, FEFO logic is not applied. This is not negligence; it is a workflow design that does not surface expiry information at the point of allocation. Pick instructions without FEFO enforcement. Warehouse operators receive pick instructions that specify item and quantity but may not specify which physical batch to pick from. When multiple batches of the same item are in the warehouse, the operator picks from the most accessible location. Typically the most recently received stock at the front of the rack. The earlier-expiring stock at the back continues to age. By the time it is reached, it may be beyond the customer's minimum shelf-life requirement. No proactive near-expiry escalation. The moment a batch should be escalated. When it passes the threshold of days remaining where it becomes an at-risk item The escalation happens when someone notices, which is days or weeks after the threshold was crossed. The options available at that point are fewer and more expensive than they would have been at threshold crossing. --- What a System Fix Looks Like A system fix for expiry management connects the data that already exists in ERP to the decisions that currently happen without it. Automated batch allocation with FEFO enforcement. Production planning and allocation should default to the earliest-expiring eligible batch for every production run and order, with system enforcement rather than planner discretion. Where a specific batch is required for quality or process reasons, the deviation should require explicit override with documentation. Pick instruction enforcement. Pick instructions should specify the batch, not just the item. The warehouse management system or the production planning layer should generate FEFO-compliant pick instructions that identify the specific pallet or batch to be picked — not just the item and quantity — removing the operator's location-of-convenience decision. Near-expiry alerts with defined escalation paths. When a batch crosses a defined days-to-expiry threshold, an alert should route automatically to the people who can act on it: the production planner (to prioritise the batch in upcoming runs), the sales team (to offer the stock for near-expiry promotions or to customers with matching shelf-life requirements), and the quality manager (to review and confirm the batch remains usable). The alert should include the batch's remaining shelf life, its quantity, its current allocation status, and the suggested action. --- The Commercial Dimension of Expiry Management Expiry write-offs are not just an operations cost. They affect commercial relationships. A customer who receives a delivery with insufficient remaining shelf life will reject it, raise a claim, and reconsider the supplier relationship. The direct cost of the rejection is the return logistics and credit note. The indirect cost is the commercial trust that was damaged. System-level expiry management, combined with supply chain visibility into customer shelf-life requirements at the point of order allocation, prevents the commercial dimension of the problem by ensuring that batches are never allocated to orders where the remaining shelf life will be insufficient at the expected delivery date. This is the complete picture of the system failure: not just write-offs in the warehouse, but deliveries that reach customers who cannot use them. Both are preventable from the same data, through the same system fix.