Blog

How to Track Stock Across Multiple Warehouses

VORQ Operations · 2026-05-01 · 9 min read · Multi-warehouse · Storage sites · Inventory

Warehouse loading dock with palletised goods ready for multi-site distribution

Teams that track inventory across multiple warehouses usually fail in the same place: one company total that pretends Main DC and a van share a single shelf. Sales promises “we have 80”. The picker at Main DC finds 55. Van 2 holds 25 that nobody can see without a phone call. A Purchase order for 40 is still on the road, and someone has already sold against it twice.

Multi-warehouse tracking works when every quantity is tied to a Storage site, and when on-hand is never confused with incoming. This article shows that split with a small hypothetical: Main DC and Van 2, one SKU, and the views you need before you pick, transfer, or reorder.

Answer first: what “multi-warehouse stock” must show

For each SKU you need at least:

  • On-hand by Storage site (what you can pick or transfer today)
  • In transit between sites (Transfers that have shipped but are not fully received)
  • Incoming by destination site (open Purchase orders still expected at that site)

A company-wide total is fine as a roll-up. It is not fine as the only number on the screen when someone decides where to pick from.

VORQ product analytics already surface multi-warehouse on-hand and incoming Purchase order quantity by destination site. Use those views as the planning layer; use floor workflows (Receive stock, Transfers, Scan to deduct) as the truth that feeds them.

Hypothetical: Main DC and Van 2

SKU FLR-120, flooring cartons. Two Storage sites: Main DC (racking and dock) and Van 2 (mobile stock for same-day jobs).

Location / statusQuantityWhat it means
Main DC on-hand55Pickable at the warehouse
Van 2 on-hand25On the van shelves, not at Main DC
Transfer TR-118 in transit (Main DC → Van 2)10Left Main DC, not yet received on Van 2
Open PO to Main DC40Supplier inbound; not on-hand anywhere yet
Company total if you add everything naively130Misleading: mixes on-hand, in transit, and PO
True pickable company on-hand8055 + 25 only

If a customer needs 30 cartons tomorrow from Main DC, you have 55 on-hand there. You do not “have 80 at Main DC”. You do not “have 120 available” because of the PO. The PO may arrive late, short, or damaged.

On-hand vs incoming at each site

On-hand

On-hand is quantity confirmed at a Storage site after Receive stock, putaway, a completed Transfer receive, or an adjustment from Stock counts. It is what Scan to deduct can burn down. Van 2 on-hand of 25 is real stock; it just is not sitting in aisle A at Main DC.

Incoming Purchase orders

Incoming is quantity still open on Purchase orders for a destination site. In the table, 40 units are expected at Main DC. That number belongs in planning and Low stock context, not in today’s pick face. When the supplier delivers, Receive stock converts incoming into on-hand at that site (full or partial).

In transit on Transfers

Transfers sit between sites. Once Main DC ships 10 cartons toward Van 2, those 10 leave Main DC on-hand and sit in transit until Van 2 receives them. Partial receive on a Transfer is normal: Van 2 might book 8 today and leave 2 outstanding if two cartons are missing from the load. Until receipt posts, neither site should sell those units as local on-hand.

For the floor SOP on shipped, in-transit, and received states, use the warehouse stock transfer SOP and the product guide for Transfers.

How to read the week without double-counting

  1. Planning a pick at Main DC: use Main DC on-hand only (55), minus open commitments if you reserve stock elsewhere.
  2. Planning a same-day job from Van 2: use Van 2 on-hand (25). If the job needs 30, raise a Transfer from Main DC for at least 5, then wait for receive on Van 2 before promising the full 30 from the van.
  3. Reordering: look at on-hand by site plus incoming PO by destination. If Main DC has 55 on-hand and 40 incoming, Low stock logic should not pretend the site is empty. If Van 2 has 25 and no PO of its own, replenish via Transfer, not a second supplier order to the wrong address, unless you truly buy direct to the van.
  4. Company dashboard: show site columns first. Totals second. Never hide site splits behind a single green “in stock” badge.

Workflows that keep multi-site numbers true

  • Receive stock against Purchase orders with the correct destination Storage site selected before labels print.
  • Transfers for every Main DC → Van 2 move. No “just take ten for the van” without a document.
  • Scan to deduct at the site that actually issues the stock. Dispatching from Main DC while the van held the carton creates a discrepancy that Stock counts will find later.
  • Stock counts per Storage site on a cycle. Counting only Main DC while Van 2 drifts is how the company total looks fine and the van is wrong.
  • Low stock thresholds per site when demand patterns differ (van burn rate vs DC bulk).

Batch identity still matters across sites. If you need to ship a specific receipt lot from Main DC, follow how to dispatch stock from a specific batch rather than guessing from carton artwork.

Common multi-warehouse mistakes

  • One spreadsheet tab named “Stock” with no site column. Van 2 becomes folklore.
  • Selling against open POs as if they were on-hand. Incoming is a plan, not a pick.
  • Transfer without receive. Main DC already deducted; Van 2 never booked. Ten units vanish into the gap.
  • Reordering to the wrong site. A PO lands at Main DC while Van 2 is the one starving.
  • Ignoring in-transit. Planners add Main DC + Van 2 + transfer and invent stock that is already counted once in the ship event.

Practical checklist for Monday morning

  • Open analytics (or inventory views) filtered by Storage site for your top movers
  • For each site, note on-hand and incoming PO quantity separately
  • List open Transfers and treat in-transit as neither site’s pickable stock
  • Confirm Low stock alerts are site-aware before you raise Purchase orders
  • If Van 2 needs replenishment, create a Transfer from Main DC instead of a handwritten list

Tracking stock across multiple warehouses is not a harder version of a single total. It is a site-first ledger: on-hand where it sits, incoming where it is headed, and Transfers for everything in between. When Main DC shows 55 and Van 2 shows 25, you can promise with confidence. When you want that model live, start at signup or compare pricing.