Manual stock reconciliation across multiple warehouses
Reconciling stock across multiple warehouses is difficult when each site records movements differently and updates at different times. As order volume grows, small timing gaps and data entry errors create persistent mismatches between physical stock and what sales channels show. The result is operational noise that competes with fulfilment work and customer service.
By Sean SaleUpdated
Co-founder of Just Applications Ltd, the team behind Adlixor
The Challenge
Manual reconciliation typically relies on spreadsheets, emailed reports, and periodic stock counts that do not reflect real-time activity. Transfers, returns, and write-offs are often recorded late or inconsistently, so each warehouse appears correct locally while the total position is wrong. These gaps lead to overselling, delayed despatch, excess safety stock, and time lost investigating discrepancies.
The Solution
A systematic approach uses a single stock model with clear rules for how stock moves between states such as on-hand, reserved, in-transit, and unavailable. Automated integrations and controlled workflows record each movement once at the source, then synchronise changes across warehouses and order systems. Reconciliation becomes exception-led, focusing on genuine variances rather than routine re-keying.
Step-by-Step Guide
- 1
Define a consistent set of stock states and movement types to be used across all warehouses.
- 2
Assign a unique SKU and location structure that maps bins, zones, and warehouse identifiers in a standard format.
- 3
Document how orders, picks, despatches, returns, adjustments, and transfers should create stock movements.
- 4
Implement a single source of truth for stock and ensure each warehouse system can send and receive updates reliably.
- 5
Introduce reservation logic so available-to-sell is reduced as soon as an order is confirmed, not when it is picked.
- 6
Track inter-warehouse transfers as two linked events: outbound from the origin and inbound to the destination, with an in-transit state in between.
- 7
Automate ingestion of goods-in and returns using barcode scanning and mandatory reason codes for adjustments.
- 8
Set up scheduled variance reports that compare expected stock to counted stock by SKU and location.
- 9
Create an exception workflow for investigating variances with ownership, timestamps, and auditable outcomes.
Pro Tips
- ✓Treat transfers as their own process with transfer IDs, expected quantities, and a due date for receipt confirmation.
- ✓Require reason codes for all manual adjustments and limit who can post them to reduce noise in the audit trail.
- ✓Separate damaged, quarantined, and expired stock into dedicated locations so it does not inflate available-to-sell.
- ✓Run cycle counts by value and velocity, focusing daily effort on the SKUs most likely to cause customer impact.
- ✓Freeze inventory movements for a short window during full stocktakes, or record movements in a controlled log to replay afterwards.
- ✓Standardise units of measure and pack sizes to prevent silent conversion errors when receiving or transferring.
Frequently Asked Questions
- Why do stock figures differ between warehouses and sales channels?
- Differences usually come from timing and state mismatches, such as orders reserving stock in one system but not another, or transfers not being marked in-transit. Manual entry and delayed posting of returns or write-offs also cause drift.
- What is the minimum data needed to reconcile stock reliably?
- You need a unique SKU, a location identifier, a quantity, a timestamp, and a movement type for every change. For traceability, include a reference such as order number, return ID, or transfer ID.
- How should inter-warehouse transfers be represented?
- Transfers should reduce on-hand at the origin when despatched, increase an in-transit balance, then increase on-hand at the destination when received. This avoids double-counting and makes missing receipts visible.
- How do reservations affect reconciliation?
- If reservations are not applied consistently, a warehouse may show stock on-hand while channels show it as available, leading to overselling. A clear separation between on-hand and available-to-sell makes it easier to explain discrepancies.
- How often should cycle counts be done in a multi-warehouse setup?
- Frequency should be based on SKU value, pick frequency, and error rate, not a single blanket schedule. Many operations count fast-moving or high-value items weekly or daily and slow movers less often.
- What are common root causes of recurring variances?
- Typical causes include mis-picks, unrecorded damage, incorrect receiving quantities, barcode issues, and transfers that were despatched but never receipted. Poor location discipline, such as putting away into the wrong bin, can also create persistent variance.
Related Guides
Further reading from our blog
Ready to simplify your multichannel operations?
Start your 14-day free trial with Adlixor — no credit card required.