Track Stock Across Multiple Locations

A wholesale distributor expanded from one warehouse to three in two years. Their inventory system — a shared Google Sheet — didn't survive the expansion. When a customer asked if a product was available, the answer depended on which warehouse you called. Nobody had a complete picture. Inter-warehouse transfers were tracked via WhatsApp messages. Products "in transit" between locations existed in a void — out of one spreadsheet, not yet in another. Multi-location inventory management is one of those problems that seems simple ("just add another column for location") until you actually try to solve it. The complexity isn't in tracking quantities — it's in managing the movement and allocation of stock across locations. <h2>The Core Challenge</h2> Single-location inventory answers one question: "How much do we have?" Multi-location inventory needs to answer several more: <ul> <li>How much do we have at each location?</li> <li>How much is in transit between locations?</li> <li>How much is allocated to orders at each location?</li> <li>Which location should fulfill this order?</li> <li>When should we transfer stock between locations?</li> <li>What's the total across all locations?</li> </ul> Each question seems straightforward. The difficulty is answering them all simultaneously, in real time, with accurate data. <h2>Building the Unified View</h2> The foundation of multi-location tracking is a single system that knows about all locations. Not separate spreadsheets, not separate software instances — one system with a location dimension on every inventory record. <h3>Location Hierarchy</h3> Define your locations in a way that matches your operations: <ul> <li>Level 1: Sites — each physical location (Main Warehouse, Distribution Center East, Retail Store Utrecht)</li> <li>Level 2: Zones — areas within a site (Receiving, Bulk Storage, Pick Area, Cold Storage)</li> <li>Level 3: Positions — specific storage positions (Aisle 3, Shelf B, Bin 12)</li> </ul> You don't need all three levels from day one. Start with sites. Add zones and positions as your operations require more precision. <h3>Transfer Management</h3> When stock moves between locations, it needs to be tracked through three states: <ol> <li>Transfer created: Stock is earmarked for transfer (still physically at origin, but allocated for transfer)</li> <li>In transit: Stock has left the origin but hasn't arrived at the destination. The system shows it as "in transit" — deducted from origin, not yet added to destination.</li> <li>Transfer received: Stock has arrived and been confirmed at the destination. Now it's available for sale or use at the new location.</li> </ol> The "in transit" state is where most simple systems fail. Stock in a delivery truck isn't at either warehouse. If your system doesn't handle this state, you either double-count (stock appears at both locations) or lose track (stock appears at neither). <h3>Fulfillment Logic</h3> When an order comes in, which location fulfills it? Common strategies: Proximity-based: Ship from the location closest to the customer. Minimizes delivery time and shipping cost. Inventory-based: Ship from the location with the most stock. Balances inventory across locations. Priority-based: Always ship from the primary warehouse unless stock is unavailable, then fall back to secondary locations. The right strategy depends on your business. Many companies use a combination: proximity-based for standard orders, fallback to any available location for urgent orders. <h2>Rebalancing Stock</h2> Over time, inventory imbalances develop. One location runs low while another has excess. Without proactive rebalancing, you end up with stockouts at one location and dead stock at another — even though you have enough inventory in total. Effective rebalancing uses data: <ul> <li>Sales velocity by location: How fast does each product sell at each location? This tells you where demand is and how much to stock there.</li> <li>Lead time between locations: How long does a transfer take? This determines when to trigger a rebalancing transfer.</li> <li>Minimum and maximum levels per location: When stock at Location A drops below the minimum, trigger a transfer from Location B (if B is above its minimum).</li> </ul> Automated rebalancing suggestions — "Location A is running low on Product X, Location B has excess, recommend transferring 50 units" — turn inventory management from reactive firefighting to proactive optimization. <h2>The Reporting Layer</h2> Multi-location inventory requires multi-dimensional reporting: Aggregate view: Total stock across all locations. This is what your finance team needs for valuation and what your purchasing team needs for reorder decisions. Location view: Stock levels per location. This is what each warehouse manager needs for their daily operations. Product view: Where is this specific product across all locations? This is what your sales team needs when a customer asks about availability. Movement view: What's been transferred between locations, received, shipped, and adjusted? This is your audit trail and the basis for identifying inefficiencies. <h2>Starting Multi-Location Tracking</h2> If you're expanding from one location to two, implement multi-location tracking before the second location opens. Adding location tracking after the fact — with inventory already scattered and untracked — is significantly harder than setting it up proactively. Start with simple location-level tracking (no zones or positions). Get accurate opening balances at each location. Implement transfer management so inter-location movements are tracked from day one. Add fulfillment logic and rebalancing as your operations mature. The goal is a single question with a single answer: "Do we have this product available?" The answer should include where, how much, and whether more is on the way — regardless of how many locations you operate.