In 2026, most inventory systems carry one quantity number per SKU per location. That single figure has to mean different things to different teams across the business. Procurement reads it as available stock. Sales reads it as committable stock to promise to a customer. The auditor reads it as on-hand stock to validate the balance sheet. The number cannot be all three at once, because Reserved units, Damaged units, plus In-Transit units behave differently from genuinely Available units. The system collapses them all into one figure plus everybody works from the wrong picture.

The cost shows up as overcommitments plus stockouts that should never have happened. A salesperson promises 200 units from a SKU showing 240 on hand, not knowing 80 are reserved against a previous order plus 35 are damaged stock awaiting vendor pickup. The order ships short. Procurement sees 240 on hand plus declines to reorder, then the next customer order arrives plus there is nothing to fulfill from. The auditor at quarter-end finds inventory the books say is worth full value but physically sits in the Damaged corner of the warehouse, plus the controller has to explain why the write-down was not booked earlier.

Inventory Control fixes this by treating status as first-class data, not a comment field. Every unit of inventory carries a status flag: Available, Reserved, Damaged, In Transit, plus Obsolete. The dashboard shows each status separately so procurement reads Available, sales reads Available minus Reserved, plus the controller reads the full breakdown for financial reporting. The same underlying ledger answers different questions cleanly for different teams. No collapsed single number lying to everybody.

Freeze locks a SKU, a location, or a category against any further transactions for the duration of a physical count, an investigation, or a controlled adjustment. While the freeze is active, the ledger remembers exactly what the system thought was there. Counters can do their work without races against live orders. When the count completes, the reconciliation tool compares system quantities against counted quantities, flags variances for review, plus posts the adjustments only after the controller approves them. The freeze releases when the reconciliation closes.

Lock differs from freeze in scope. Lock applies to a single transaction record (say, an in-progress receipt or a half-completed transfer) to prevent two users from editing it simultaneously. Optimistic locking lets multiple users read the record at the same time but prevents conflicting writes. The user whose change posts second sees a conflict warning plus the chance to merge or refresh before retrying. The ledger never loses an event to a race condition between two well-meaning users.

Reconciliation tools cover the rest of the variance resolution workflow. The bulk-adjustment screen handles the post-count corrections with reason codes plus authorized approvers. The investigation queue holds variances that require deeper review before adjustment posts. Every adjustment runs through the audit trail with its source (count session, investigation, manual correction) plus the linked Physical Inventory record when applicable. The whole reconciliation cycle stays inside Inventory Control instead of fragmenting across separate spreadsheets.