A warehouse shift is underway, and pickers are working through the afternoon picking wave, which must be completed before the shipping cutoff. Then a picker reaches a bin expected to contain 24 units and finds it empty.
The shift supervisor starts fielding questions: “Where did we move this?” “Did it go to overflow?” and “Is it on hold?” While the team searches, orders begin queuing at packing stations and the cutoff gets closer.
So what went wrong? The inventory record, whether it lives in a spreadsheet, an ERP, or a warehouse management system (WMS), said the stock was there. But stock on paper isn’t always stock your team can pick, pack, and ship in time. This article explains the difference, walks through five signs that your warehouse has an inventory availability problem, and shows how to fix each one.
Key Takeaways:
- On-hand stock can fill a new order only when it is unrestricted, uncommitted elsewhere, accurately located, in the right unit, and reachable before the cutoff.
- Allocated stock is unavailable to new orders but remains available to the order it is allocated to.
- Scan-to-move procedures keep location records accurate only when supervisors check compliance and handle exceptions.
- Short shipments can start at allocation, in the record, at picking, or at packing, and each source needs a different fix.
- Recurring cycle count variances persist until you trace each adjustment through movement history to a root cause.
- Forward-pick locations can run empty despite full reserve stock when replenishment starts only after a picker reports a gap.
- Set targets for inventory availability metrics only after measuring a baseline for a few weeks.
What does inventory availability mean in warehouse operations?
Inventory on hand tells you how much stock is recorded at a location. Available inventory is the part of that quantity you can still commit to an order: on-hand stock minus quantities already reserved, restricted, or tied up in pending transactions. Oracle’s inventory documentation, for example, calculates the quantity available to reserve as on-hand quantity minus reserved quantity and pending transactions. Ready-to-pick inventory narrows it further: stock that is free for the order in question and sits in a forward-pick location (also called the pick face: the location that holds a small, easily reached quantity for picking), in the unit of measure the order needs.
Here is how 100 units on hand can turn into far fewer units a picker can use for a new order:
| Quantity | What it means | Example |
|---|---|---|
| On hand | Physical quantity recorded in the warehouse | 100 units |
| Restricted | On quality hold, damaged, or awaiting returns inspection | 20 units |
| Allocated to other orders | Committed to existing orders (available to those orders, not to a new one) | 30 units |
| Available to commit | On hand minus restricted and allocated stock | 50 units |
| Ready to pick now | Available stock already in the forward-pick location | 12 units (the other 38 are in reserve storage awaiting replenishment) |
The system can show 100 units on hand, but you can pick only 12 for a new order without replenishment. Stock not ready to pick now can still be ready in time if you replenish it before the cutoff. To know whether stock will be ready for a specific order, check four conditions:
- Location: The record matches where the stock physically is, confirmed by its last recorded movement. Stock fails this test when putaway (moving received stock into its assigned storage location and recording the move) was never completed, or when it was moved to an overflow area without a record. Stock split across several bins is fine, as long as the record shows each location and its quantity.
- Restrictions and allocation: Nothing restricts the stock, such as a quality hold, damage, an uninspected return, or a compliance hold, and it is not allocated to a different order. Allocated stock remains available to the order it is allocated to.
- Quantity and unit of measure: There is enough stock in the form the order needs. A case of 12 is not the same as 12 eaches (individual units) if the order calls for single units and nobody can break the case before the cutoff.
- Accessibility: The stock sits in a forward-pick location, or you can replenish it from reserve storage before the cutoff.
If the system shows enough stock on hand but the location, restriction, unit-of-measure, or accessibility condition fails, you don’t have a stock problem; you have an availability problem.
5 signs your warehouse has an inventory availability problem
These signs can appear individually or together. Each one points to a different breakdown, so each gets its own fix, with a named owner and measure.
1. Pickers spend too much time searching for stock
Pickers move between bins and storage areas searching for SKUs whose recorded location doesn’t match the shelf. Inaccurate location records also extend onboarding, because new hires rely on experienced coworkers who know where stock actually ends up.
Consider this illustrative scenario: a new warehouse associate is sent to Aisle 5, Shelf B3 to pick Item A because the inventory system shows it there. The shelf is empty. During a busy shift, someone moved the item to an overflow pallet near the loading dock, and nobody recorded the move. The associate spends 10 to 15 minutes searching and asking coworkers before finding it.
Why stock goes missing from its recorded location
- Location naming isn’t standardized across zones such as receiving, reserve storage, forward picking, and quarantine. For example, Zone A uses bin labels, Zone B uses shelf labels, and Zone C uses unmarked floor storage.
- The system doesn’t record moves into overflow or staging areas, so it shows the last official location instead of the current one.
- Putaway is marked complete before the stock is placed in its assigned location.
How to make location records reliable
- Standardize locations: use one naming convention across all zones, and add sub-locations such as aisle, rack, shelf, and bin where pickers need them. EZO’s guide to organizing inventory covers the basics.
- Make scan-to-move a standard operating procedure: every move, including a temporary move into overflow or staging, is scanned at the destination. A mobile scanning app records the move, but the procedure works only if supervisors verify compliance and handle exceptions.
- Investigate recurring unrecorded moves, and address the causes through clearer procedures and accountability.
- Keep cycle counting. Counts find location errors that already exist; scan-confirmed moves reduce new ones.
Owner and measure: The inventory control lead owns location standards, and shift supervisors enforce scan-to-move. Track location accuracy and search time per missing-stock exception.
2. Meeting shipping cutoffs requires constant overtime and last-minute fixes
On paper, shipments leave on time. In practice, the team is in firefighting mode. Overtime spikes around cutoffs and peak days, supervisors pull stock together by hand, and administrative staff chase confirmations so orders can ship.
Why problems surface at pick time
Availability problems are discovered when a picker reaches the shelf, not when the order is accepted. Orders are promised against unverified inventory records, and replenishment of forward-pick locations doesn’t follow the picking schedule, so shortages appear with little time left to fix them.
How to confirm availability before committing to orders
- Before releasing a picking wave, confirm that each order’s stock is in a verified location, has no restrictions, and is ready to pick or can be replenished before the cutoff.
- Allocate only verified quantities that are eligible for the intended order, excluding stock restricted by damage or quality holds.
- Review a short readiness report before each wave: orders at risk, quantities ready to pick, and replenishment needed before the cutoff.
Owner and measure: The operations or shift manager owns the pre-wave check. Track overtime hours on cutoff and peak days; the metrics table later in this article shows how.
3. Orders are frequently short-shipped despite stock on record
A short shipment delivers fewer units than the customer ordered. Whether the order is for replacement equipment at a main office or spare parts for a facility, partial shipments become more frequent, and complaints about them become the norm, leading to rework and second deliveries. A single short shipment can look like a one-off mistake. A pattern points to a gap between recorded stock and stock that is ready to ship.
Where short shipments start
- At allocation: The order was allocated against stock that was restricted or already committed to another order.
- In the record: Phantom stock, quantities the system shows but that aren’t physically there, inflates the on-hand figure. Common causes are unrecorded moves, unrecorded damage or loss, and returns posted back to available stock before inspection.
- At picking: The picker took the wrong item or quantity, or picked a case where the order needed eaches.
- At packing or shipment verification: Items were picked but not packed, or the shipment was not checked against the order.
- In supply: There was not enough stock to begin with.
How to fix short shipments at the source
- Restricted stock: Keep stock on quality hold, damaged stock, and returns awaiting inspection in physical on-hand counts, but exclude them from available quantities until they are released.
- Phantom stock: Count the locations with repeated variances, and require a recorded move for every relocation. Follow standardized location management practices so stock is scanned and recorded the same way everywhere.
- Picking and packing errors: Scan to confirm the item and quantity at picking and again at packing.
- Unit-of-measure errors: Record each SKU’s base unit and case quantity, label case packs clearly, and update the system when a case is broken into eaches. GS1, the global barcode standards body, requires a separate identifier for each packaging level above the base unit, so cases and eaches must be tracked as distinct quantities.
- True shortages: Set minimum stock levels per location so replenishment or purchasing starts before stock runs out.
Owner and measure: The inventory control lead owns the fixes. Track the short-shipment rate and classify each short shipment by its origin.
4. Cycle counts keep finding the same discrepancies
Counts take a long time to reconcile, and the same SKUs and locations show variances count after count. The cycle counts are doing their job by finding errors. The problem is that the causes aren’t fixed, so the errors keep returning.
Why the same discrepancies return
- The system corrects variances without anyone investigating why they occurred.
- Moves, damage, and returns are not recorded when they happen. For example, returned stock is received without a quality inspection, or its quantity is posted back to available inventory before approval.
How to stop recurring discrepancies
Prioritize counts by risk: high-velocity SKUs, high-value items, locations with frequent relocations, and SKUs that showed variances before. Then run every variance through a defined workflow:
- Identify the variance between the recorded and counted quantity.
- Verify it with a recount, and check for open transactions such as picks, transfers, or receipts still in progress.
- Review the movement history for the SKU and location.
- Classify the root cause: unrecorded move, picking error, unit-of-measure error, damage, receiving error, or returns processing.
- Approve the correction. A supervisor approves adjustments above a set threshold, and every adjustment carries a reason code.
- Monitor recurrence, and fix the process behind any cause that keeps appearing.
Owner and measure: The inventory control lead owns the workflow. Track inventory record accuracy and the repeat-variance rate.
5. Forward-pick locations run empty while reserve stock sits elsewhere
Pickers reach an empty forward-pick location while full pallets of the same SKU sit in reserve storage. Picking stalls until someone moves stock forward, and orders can miss the cutoff even though the warehouse holds enough stock.
Why replenishment falls behind picking
- Replenishment starts only when a picker reports an empty location, instead of when the quantity reaches a set minimum.
- Forward-pick location minimums and capacities do not reflect current demand, so fast-moving SKUs run out mid-wave.
- No one clearly owns replenishment during a shift, or replenishment competes with putaway for the same people and equipment.
- Replenishment moves are not recorded, so the forward-pick quantity in the system drifts from what is on the shelf.
How to keep forward-pick locations stocked
- Set minimum and maximum quantities for each forward-pick location, and trigger replenishment at the minimum.
- Schedule replenishment ahead of each picking wave based on that wave’s orders.
- Assign replenishment ownership for every shift.
- Record each replenishment move to keep forward-pick quantities accurate.
- Check that the equipment used to move stock, such as forklifts and pallet jacks, is serviced and available, because replenishment depends on it.
Owner and measure: The shift supervisor owns replenishment tasks. Track replenishment completed before cutoff.
Diagnose your warehouse: signs, causes, and metrics
Use this table to match what you are seeing to its likely cause and first fix:
| Sign | Likely root cause | First fix | Owner | Metric to track |
|---|---|---|---|---|
| Pickers search for stock | Unrecorded moves; inconsistent location names | Standardize locations; scan every move | Inventory control lead | Location accuracy |
| Cutoffs need overtime | Orders promised against unverified records | Pre-wave availability check | Operations or shift manager | Overtime hours on cutoff and peak days |
| Short shipments | Restricted, phantom, or mispicked stock | Fix at the source (allocation, record, pick, pack) | Inventory control lead | Short-shipment rate |
| Repeat count variances | Adjustments without root-cause analysis | Six-step discrepancy workflow | Inventory control lead | Repeat-variance rate |
| Empty forward-pick locations | Reactive replenishment | Min/max triggers ahead of each wave | Shift supervisor | Replenishment completed before cutoff |
To set a readiness strategy, track a small set of metrics weekly, by shift where possible:
| Metric | How to calculate it | What it tells you |
|---|---|---|
| Inventory record accuracy | Counted SKU-locations matching the record ÷ total SKU-locations counted | Whether your records can be trusted |
| Location accuracy | Pick attempts where stock was in its recorded location ÷ total pick attempts | Whether location records match the shelf |
| Replenishment completed before cutoff | Replenishment tasks finished before the shipping cutoff ÷ replenishment tasks required | Whether forward-pick locations will hold enough stock |
| Short-shipment rate | Orders shipped incomplete ÷ orders shipped | How often availability gaps reach customers |
| Search time per missing-stock exception | Total minutes spent searching ÷ number of missing-stock exceptions | How much labor inaccurate records cost |
| Overtime hours on cutoff and peak days | Overtime hours logged on cutoff and peak days, compared with other days | Whether cutoffs depend on firefighting |
| Repeat-variance rate | Variances at an SKU-location that also had a variance in its previous count ÷ total variances | Whether root causes are being fixed |
Measure a baseline for a few weeks before setting targets, then track the trend.
Why counting alone doesn’t fix availability
Many warehouse teams track inventory diligently and still struggle. A common reason is timing: records update after stock moves rather than when it moves, so delays, unrecorded moves, and floor errors reach the record late or not at all. When tracking relies on manual updates like this, the routine follows a familiar loop: Count → List → Update → React to discrepancies.
Count
- Cycle counts: Scheduled counts of specific SKUs, locations, or zones, spread across the week.
- Wall-to-wall counts: Full physical counts of every item in the warehouse.
- Spot checks: Quick verification counts triggered by a suspected problem.
List
- Spreadsheets: Often used to note temporary information, such as overflow locations, pallets waiting for putaway, or items moved during busy shifts.
- Bin maps: Diagrams of the warehouse layout showing racks, aisle numbers, and storage zones.
- Printed reports: Used during picking, counting, or auditing.
- Exception logs: Records of known issues, such as missing items, damaged stock, or unresolved discrepancies.
Update
Under pressure, teams “fix it in the system”: they adjust the recorded quantity to keep operations moving instead of investigating why it was wrong.
React to discrepancies
Teams investigate discrepancies only after a short shipment, a customer complaint, or an unexpected count variance.
None of these activities is wrong on its own. Counts find errors, and lists fill gaps. The weakness is that problems surface during picking. If system records and physical stock don’t match, the warehouse runs on staff knowledge, with pickers asking each other who moved what. That is coping, not control.
How to move from reactive inventory updates to proactive warehouse controls
Transaction-driven inventory control means recording every stock change, from receiving to shipping, as it happens so the record stays current between counts. Build the controls around the stock lifecycle:
Receive → Put away → Verify → Allocate → Replenish → Pick and ship → Reconcile
- Receive: Record the quantity and unit of measure at the dock. Inspect returns before they re-enter available stock.
- Put away: Scan stock into its assigned location, and record temporary overflow as its own location.
- Verify: Keep each SKU’s location, condition, and allocation current, and flag any hold as soon as it is placed.
- Allocate: Commit only eligible quantities. A reservation should block conflicting orders, not the order it belongs to.
- Replenish: Use minimum and maximum triggers, and replenish ahead of each picking wave.
- Pick and ship: Scan to confirm items and quantities at picking and again at packing.
- Reconcile: Run risk-based cycle counts and the discrepancy workflow described in sign 4.
Two activities run across every step. Proactive planning uses upcoming orders, seasonal peaks, and demand trends to set stock levels and forward-pick location minimums. Periodic inventory audits check that each control is being followed and feed corrective actions back into the process.
Where to start
- Verify your records. Start with your highest-risk locations, and fix location names as you go.
- Introduce movement controls. Make scan-to-move the rule for every relocation, including overflow and staging.
- Separate restricted stock. Exclude held, damaged, and uninspected stock from available quantities.
- Set up the discrepancy workflow. Require a root cause and a reason code for every adjustment.
- Measure. Establish baselines for the metrics above and review them weekly.
Where EZO EAM fits in warehouse inventory control
First, a note on scope: EZO EAM is not a warehouse management system. A WMS directs picking, packing, and order fulfillment. EZO EAM manages the operational equipment that supports those activities, such as forklifts, pallet jacks, and dock equipment, and warehouses can use it alongside a WMS. Its inventory tracking also covers stock quantities by location across sites. For teams that track stock such as spare parts, consumables, or displays outside a WMS, or that need location-level visibility, EZO EAM supports several of the controls in this article:
| Control from this article | EZO EAM capability | Plan availability |
|---|---|---|
| Reliable locations (sign 1) | Parent and child locations down to the shelf level; location records can be imported in bulk | Location management on all plans |
| Recorded moves (signs 1 and 4) | Mobile apps that scan barcodes and QR codes; stock transfers between locations | Mobile apps on all plans; stock transfers and handheld scanner support on Advanced and above |
| Restricted stock (signs 2 and 3) | Custom substates to mark stages such as on hold or awaiting inspection, for Assets and Asset Stock (not standard Inventory items) | Premium and Enterprise |
| Avoiding conflicting commitments (sign 2) | Reservations with an availability calendar | All plans |
| Low stock and empty locations (signs 3 and 5) | Location-based stock thresholds with low-stock email alerts, for Asset Stock and Inventory | See pricing |
| Recurring discrepancies (sign 4) | Audits, including location audits | Audits on Advanced and above; location audits on Premium and Enterprise |
| Replenishment equipment readiness (sign 5) | Equipment location, custody, and maintenance records | Maintenance management (CMMS) is available as an add-on |
Here is how that looks in practice for a team managing spare parts across a main warehouse and two sites. Parts are recorded as Asset Stock in named locations down to the shelf. When a technician moves 20 filters from reserve storage to the forward-pick location, they scan the item in the mobile app and record the transfer. When the forward-pick location drops below its location threshold, the inventory lead receives an email alert and schedules replenishment. Each week, an audit of the locations with the most variances confirms the counts.
Customer results show what this can look like. Foster Display Group moved its inventory into Asset Stock and manages roughly 2,000 active SKUs in EZO EAM, with generated labels and carts that give warehouse teams order details for picking. The company reports that a 10-item fulfillment order that previously took 1.5 to 2 hours can now be completed in about 20 minutes. Results depend on each team’s workflow, but the case shows how structured stock records, labels, and carts can shorten fulfillment.
Build inventory control into daily warehouse workflows
Use this readiness checklist to see where your warehouse stands:
- Give every location one name, and scan every move.
- Exclude restricted stock from available quantities.
- Allocate orders only from verified, eligible stock.
- Replenish forward-pick locations before each wave.
- Assign a root cause to every variance, not just an adjustment.
Counting still matters: it tells you whether these controls are working. The goal is to make availability a figure your team can act on, not an unreliable number in a spreadsheet.
