Your overnight batch run finished at 3:14 AM. The stock-out happened at 1:47 PM. By then, nobody could do anything about it.
This is how most mid-market distributors actually run their inventory. The ERP crunches overnight numbers, generates a replenishment report before dawn, and someone in procurement spends their morning triaging 847 lines. Meanwhile, real demand happens in real time. The system is always looking backward.
The gap between when a problem occurs and when your system responds is where money leaks. For a typical 15,000-SKU operation across three distribution centres, that gap costs roughly $1.64 million a year in expedited freight, split shipments, lost margin from competitor substitution, and the salary of a procurement team doing manual triage instead of actual planning.
These aren't supply chain costs. They're a tax on a business decision: choosing batch processing over real-time response.
Here's what the failure looks like in practice. A wholesale customer places a bulk order and picks 68% of a SKU's available stock in a single transaction. Nobody notices until someone flags it in a chat channel. The SKU wasn't on the morning's replenishment report because it was above reorder point at midnight. Now it's at 10% of safety stock. The next batch run is 13 hours away. The purchase order goes out tomorrow, arrives in five business days, and the stock runs dry Thursday morning. You pay $2,840 in expedited freight and eat 14 backorders by Friday.
At the following week's S&OP meeting, the fix is to increase safety stock by 15%. Nobody touches the actual process. The same failure repeats next quarter under a different SKU number.
There's a better way, and it doesn't involve running your ERP batch job more frequently. Hourly batches still leave you with a PO waiting for a human. That's a bandage, not a fix.
The alternative is event-driven replenishment. Every inventory-affecting transaction, a pick, a receipt, a return, a supplier lead time change, becomes a signal that flows through a rules engine in real time. When that bulk pick happens at 8:14 AM, the system recalculates the SKU's position instantly, sees a 97% stock-out probability within the lead time window, evaluates two suppliers automatically, selects the faster one, and issues a purchase order in under five seconds. The procurement manager gets a notification that it happened. No manual action required.
Downstream, the WMS dock schedule updates, the TMS pre-checks carrier capacity, the ERP posts an accrual, and the CRM recalculates promise dates for every open order on that SKU. The sales team sees accurate availability before the customer even asks.
The stock-out that would have hit Thursday never materialises. Standard freight, no expedite, no backorders.
The numbers stack up fast. Replenishment cycle time drops from 24-72 hours to under five seconds. Stock-out incidents fall 88%, from roughly 150 a year to about 18. Expedited freight spend drops from $450,000 to $54,000. Safety stock carrying cost drops 36%. Procurement triage time drops from 3.5 hours a day to 24 minutes. Total annual recovered value: about $1.42 million for a mid-market operation.
The question isn't whether you can afford to implement this. At $1.64 million a year in waste from batch-driven replenishment, the question is whether you can afford not to.
The batch run isn't your operations cadence. It's your operations ceiling.