Multi-warehouse stock and inventory management: how to stop selling what you don't have

There's a very specific moment in the life of many businesses that starts to genuinely hurt: the day you open a physical store on top of your online one, or add a second warehouse because the first one has become too small, or start selling on Amazon as well as your own website. On that day, the question that a simple spreadsheet used to answer ("do I have this in stock, yes or no?") becomes much more complicated: which warehouse is it in, how much is in each one, what happens if it's in Madrid but the customer wants urgent delivery to Barcelona?

Multi-warehouse inventory management isn't a luxury reserved for big chains. It's the problem that naturally shows up as soon as a business grows a bit beyond "one single place where everything is kept," and getting it wrong has a very concrete cost: selling something you don't have, promising a delivery you won't meet, or having money tied up in one warehouse while the other runs out of your best-selling product.

Why a single "stock" number stops being enough

When all your inventory lives in one place, your online store only needs to know one thing: how many units are left. As soon as a second warehouse, a physical store or a marketplace fulfilment centre enters the picture, that single number turns into several numbers that need to be added, subtracted and synced in real time. If your website keeps showing "in stock" by cheerfully adding up inventory from both locations with no further logic, you'll end up selling units that are physically sitting in a warehouse that can't fulfil that order in time, or worse, selling the same unit twice because one item shows as "available" in two systems that don't talk to each other.

The three common models for splitting stock

There's no single correct way to split inventory across warehouses; it depends on the size of the business and where the customers are.

• A single central warehouse serving all online orders. The simplest to manage: all ecommerce stock lives in one place, and the physical store (if there is one) has its own separate inventory, with no overlap. Easy to control, but it means you can't use physical-store stock to fulfil an urgent online order, or the other way round.
• Geographic distribution. Several warehouses in different areas, each fulfilling the closest orders to cut delivery times and shipping costs. It makes sense once order volume in a specific region (Catalonia or the Levante, for instance) justifies holding stock there instead of always shipping from a single point.
• Unified inventory ("stock pool") with priority rules. The most advanced model: all warehouses are treated as a single stock pool, and a system automatically decides which location should fulfil each order based on proximity, availability and shipping cost. It requires dedicated software, but makes the best use of total inventory without duplicating purchases.

The real problem: overselling

The most expensive and most common mistake in a business with multiple stock points is overselling: selling online a unit that was actually sold ten minutes ago in the physical store, or that's reserved for an order on another channel. The customer gets the purchase confirmation, the payment goes through, and two days later the most uncomfortable email in all of ecommerce lands in their inbox: "we're sorry to inform you that your order isn't available." That email doesn't just cost a refund, it costs the customer's trust and, very likely, a negative review that the next potential customer will read.

Overselling almost always has the same root cause: systems don't update each other in real time. A sale in the physical store takes an hour to show up on the website, or the marketplace doesn't receive the stock deduction until end of day. The faster that sync cycle is, the less overselling happens; below a few minutes of delay the risk drops sharply, while manual once-a-day syncs guarantee it will happen sooner or later.

What to look for in inventory management software

You don't need an industrial-grade ERP to solve this if the business is small or medium-sized; there are mid-tier tools (some built directly into platforms like Shopify or WooCommerce via plugins, others as standalone systems that connect via API) that cover the essentials:

• Real-time or near-real-time syncing across all sales channels (website, physical store, marketplaces), not once a day.
• Minimum stock alerts per warehouse, not just a global alert, so you know exactly where to restock and when.
• Traceability of transfers between warehouses, so you always know exactly where each unit is physically and who moved it.
• Order routing rules that automatically decide which warehouse should fulfil an order based on proximity to the customer or availability, without someone having to decide it manually every time.

A practical case: the two-store chain that was losing sales to a spreadsheet

A homeware client with a physical store in Tres Cantos and another in Alcobendas, plus their online store, managed combined stock with a spreadsheet someone updated by hand every evening. The outcome was predictable: several times a month, a product would sell online that was actually out of stock in the warehouse meant to fulfil it, leading to refunds and frustrated customers. After switching to a centralised inventory system syncing every few minutes across both physical stores and the website, overselling nearly disappeared entirely, and along the way it revealed a problem nobody had spotted: one of the two warehouses was carrying double the stock of the catalogue's slowest-moving product while the other ran out of the best-seller every two weeks. Rebalancing that split freed up capital that had been sitting idle for months for no reason.

The hidden cost of "just in case" excess stock

Overselling grabs all the attention because it generates visible complaints, but the opposite problem (holding too much stock "just in case" spread across every warehouse) is just as costly, only quietly. Every unit sitting on a shelf is money that isn't generating revenue, and in businesses with tight margins, the cost of carrying idle inventory (space, insurance, capital you can't use for anything else) can eat up a large share of a product's profit. A good multi-warehouse management system doesn't just stop you selling what you don't have, it also flags when you have too much of something in the wrong place, so you can redistribute or discount it before it turns into dead stock.

How to start if you're still managing everything by hand

If today you track stock with a spreadsheet and one or two warehouses, you don't need to jump straight to the most sophisticated system on the market. The sensible path is: first, make sure there's a single source of truth for stock (even if it's manual) that gets updated immediately after every sale, on any channel. Second, set minimum stock thresholds per product and per warehouse that trigger an alert before you hit zero. Third, and only once order volume justifies it, move to a tool that automatically syncs channels, so you stop depending on someone manually updating everything without making a mistake.

The cost of a bad initial count

Before implementing any automatic inventory system, there's a prior step many businesses skip out of haste: doing a rigorous physical count of real stock at each location. If the starting number is already wrong (because it had been carrying small uncorrected discrepancies for months), the automatic system will simply perpetuate that error faster and with apparent precision, giving a false sense of control. A full physical count, even if it's a tedious weekend task, is the foundation any later automation rests on; without that reliable starting point, not even the best software can fix a problem that was already broken at the source.

Team training: the piece that gets forgotten

An inventory system, however good, depends on the people using it day to day feeding it correctly: logging every transfer between warehouses, every loss, every return, the moment it happens rather than "whenever there's a spare minute." The temptation to implement the tool and assume the team will use it well with no further training is one of the most common reasons an inventory management project that looked promising on paper ends up failing in practice. Dedicating a clear training session at the start, and revisiting the process a few weeks later to correct bad habits, makes a noticeable difference to how reliable the data the system ends up showing actually is.

Inventory and cash flow: a connection that gets overlooked

Every unit of stock purchased is cash leaving the business before it turns into sales revenue, and in businesses with several warehouses that relationship becomes harder to see at a glance, because the capital invested in inventory is spread across different locations with different turnover speeds. A business can have healthy accounting profit on paper and, at the same time, real liquidity problems because too large a share of that capital is tied up on shelves instead of circulating. Periodically reviewing what percentage of the business's total capital is trapped in inventory, and comparing it against that inventory's real turnover speed, helps catch this problem before it turns into a cash crisis alongside apparent profit in the books.

Built-in platform module or external system: how to decide

When the moment comes to leave the spreadsheet behind, a decision shows up that isn't always obvious: stick with the inventory module already built into Shopify or WooCommerce, or hire a specialised external system that connects via API. The built-in module has the advantage of simplicity: everything lives in one dashboard, with no need to maintain a second subscription or sync two separate systems, and for a business with a single warehouse and one sales channel it's usually more than enough. The problem shows up once several warehouses, a physical store and marketplaces all combine at once: that's where built-in modules start showing their limits (inflexible routing rules, alerts only at the global level, poor transfer traceability) that a specialised system handles better, in exchange for a longer learning curve and an extra monthly fee.

The most honest way to decide is to list the specific features the business needs today, not in two years, and check how many of them the built-in module already covers at no extra cost. If the list of gaps is short (one or two minor features), it almost always pays to stick with the built-in option and wait for the business to grow further. If the list includes several core pieces (automatic routing between locations, full transfer traceability, demand forecasting), the cost of an external system pays for itself quickly compared to the time lost trying to force the built-in module to do something it wasn't designed for.

Frequently asked questions