Multi-plant, multi-warehouse inventory: the pitfalls that actually cost money

Single-warehouse inventory is comparatively forgiving, most discrepancies get caught by someone physically noticing the shelf doesn't match the screen. Multi-plant and multi-warehouse setups lose that safety net. Stock can be technically correct in the system and still be functionally wrong, because it's sitting in the wrong place, in-transit and double-counted, or reserved against an order nobody remembers.

In-transit stock is the most common silent break

Stock transferred between warehouses needs a clear in-transit state, not instantly deducted from the source and added to the destination, and not left sitting in the source location's count until someone remembers to confirm receipt. Both extremes produce a system that's confidently wrong. A proper stock transfer entry with a distinct in-transit status, closed out on actual receipt confirmation, is the fix, and it's more often skipped than you'd expect.

Reserved stock that never gets released

• Sales order reservations that outlive a cancelled or expired order, quietly locking stock that's actually available
• Manufacturing reservations against a work order that got restarted with different quantities, doubling the reservation
• Reservations that don't expire and don't get audited, so "available stock" on the dashboard slowly diverges from reality

The fix isn't complicated, it's a scheduled job that flags reservations against closed or cancelled documents, but it's the kind of housekeeping that only gets built if someone specifically asks for it, because it never shows up as a feature request until stock numbers are already wrong.

Valuation method inconsistency across warehouses

Running FIFO in one warehouse and a moving average in another, sometimes unintentionally, through inconsistent item-level configuration, makes consolidated stock valuation reports meaningless for anyone comparing plant to plant. This needs to be a company-wide policy decision made once, not a per-item default that drifts as new items get added by different people.

Batch and serial tracking gaps at transfer points

• Batch numbers that get regenerated at a receiving warehouse instead of carried through from the source, breaking traceability
• Serial-tracked items where the serial isn't validated at both ends of a transfer, allowing a mismatch to go unnoticed
• Expiry-date tracking that isn't enforced consistently across every warehouse an item passes through

The audit that actually catches these

A monthly reconciliation between system stock and a physical count, per warehouse, is the only reliable way to catch drift before it compounds. Most teams do this annually if at all. For multi-location operations, monthly (or even weekly for high-velocity items) is the difference between catching a process gap early and discovering a six-figure valuation error at year-end audit.