Can't See Multi-Location Stock? Fix It [2026]

The call that exposes the problem

A customer wants an item today. Your sales team checks the system and sees 18 units available.

The warehouse manager checks the main warehouse. Nothing.

Someone calls the second site. They have 12, but those units are already picked for another order. The remaining six are split between a retail store and a third-party packing area. Nobody is quite sure whether they are sellable, reserved, or simply missing from the count.

This is what multi-location inventory blindness feels like. You technically have more than one location, but you don't have one reliable picture of your stock.

The result isn't just inconvenience. You delay an order, promise stock you can't ship, transfer goods too late, or buy more inventory while perfectly usable units sit somewhere else.

A 2026 study of inventory record accuracy looked at around 24,000 SKUs across 11 stores, using roughly 150,000 stock-count records and 22 million sales records. The researchers found that correcting inaccurate inventory records led to an 11% store-wide sales lift, with the effect concentrated in items where the system showed more stock than was physically available. (Source: Journal of Business Logistics)

The exact result came from grocery retail, not every product business. But the operational lesson carries over: when the system says stock exists and the location cannot find it, the problem is already costing you sales.

Why multi-location stock goes blind

The root cause is usually not that anyone is careless. It is that stock movements happen in many places, while the record of those movements is spread across too many tools.

A warehouse receives a shipment. A store sells a unit. Someone takes samples to a trade show. A customer return sits on a desk. A team member moves cartons from one site to another and sends a message in Slack. At the end of the week, the inventory spreadsheet gets updated from memory.

Each individual action seems small. Together, they create drift.

There is a second problem: people think in total stock, while orders happen at specific locations. You may have 40 units across three sites, but that doesn't mean you can fulfill an order from the location nearest the customer. Total inventory can look healthy while one warehouse is empty of the exact SKU you need.

That is why a single company-wide number isn't enough. You need both:

• The total quantity for each SKU
• The quantity available at each location

You also need the movement history that explains how the numbers got there.

The warning signs you're already there

You don't need ten warehouses for this problem to appear. Two locations are enough if the process is informal.

Here are the symptoms I would take seriously:

Your team asks "which warehouse?" after every stock question

If the stock number doesn't include a location, someone has to open another screen, call another person, or make an assumption. That slows down sales and makes urgent orders more expensive.

Transfers are recorded after the fact

A box leaves Location A on Tuesday but doesn't get added to Location B until Friday. During those three days, the stock is wrong in both places. The source location may still look full, while the receiving location cannot promise the product.

Stocktakes produce arguments instead of answers

A count difference is useful only if you can trace it. If the system doesn't show which location owns the quantity and which movements affected it, every variance becomes a debate about whose spreadsheet is current.

Our guide to inventory accuracy and what bad stock data costs covers the broader issue. With multiple sites, the risk compounds because each handoff is another point where the record can drift.

You buy more while another location has stock

This is the expensive version of blindness. The purchasing team sees a shortage at one site and places a new purchase order, without knowing that another site has excess units. You pay for new stock, freight, and storage while your existing inventory is in the wrong place.

Customers hear "we thought we had it"

That sentence damages trust quickly. It is also a sign that your sales team is looking at an aggregate number that doesn't reflect the actual fulfillment decision.

From the Founder

I ran a family product company for 13 years, from 2008 to 2021. We grew from occasional container shipments to more than 75 containers a year, and every stage of that growth introduced another layer of operational complexity.

One warehouse can hide a surprising number of mistakes. You can walk over, look at the shelves, and resolve a question. Once stock is spread across warehouses, stores, or fulfillment points, that physical shortcut disappears. The quality of your decisions becomes dependent on the quality of your records.

That is one of the reasons I built VNDLY around location-aware inventory. A growing product business should not need a detective to answer a basic question like, "How many do we have, and where are they?"

How VNDLY gives every location its own stock picture

VNDLY's Locations area lets you create and manage the places where your inventory lives. Locations can have a code, name, type, address, country, and contact details. The list also shows a Stock qty total for each location, and you can search by location name or code.

Open a location and VNDLY shows its Stock summary, including total quantity and unique SKUs. The Inventory at this location table lists the SKU, product, variant, and quantity. You can export that location's inventory as CSV or Excel, which is useful when a warehouse manager needs a working list for a physical check.

The main Inventory screen adds the wider view. VNDLY groups stock by variant and location, then calculates the total per variant by summing the location-level quantities. That means you can answer two questions without building a manual reconciliation:

1. How much of this SKU exists across the business?
2. How much is at each specific location?

The difference matters. If you have 40 units total but only three at the location fulfilling today's order, the second answer is the one that protects the customer promise.

For a deeper overview of the broader use case, see multi-warehouse inventory management software and VNDLY's warehouse inventory software for growing businesses.

Transfers should be visible, not remembered

When stock moves between sites, VNDLY records a Transfer as an inventory movement with a From location and a To location.

The workflow is intentionally concrete:

1. Go to Inventory movements.
2. Choose Transfer in the Type field.
3. Select the SKU in Product (SKU).
4. Select the From location.
5. Select the To location.
6. Enter the Quantity.
7. Add an optional note, such as PO-1234 received or Urgent customer allocation.
8. Select Post movement.

The recent movements table then displays the transfer as a location pair, such as WH1 → STORE2, alongside the SKU, quantity, reference, and note. The movement is not hidden in a spreadsheet tab. It becomes part of the inventory history.

That history is important for more than investigation. It gives the next person context. If someone asks why a location's stock changed, the movement record provides the event type, time, SKU, quantity, and note instead of forcing the team to reconstruct the story from messages.

Stocktakes close the loop

A location-aware system still needs accurate inputs. Physical counting is how you check the record against reality.

VNDLY's stocktake workflow assigns a stocktake to a location and keeps the location name in the count sheet and variance report. That gives the count a defined boundary. The team is not vaguely counting "the inventory". They are counting the stock held at a specific place.

When a variance appears, you can investigate it alongside the location's movement history. Maybe a receipt was posted to the wrong site. Maybe a transfer was never recorded. Maybe a damaged unit was removed without an adjustment. You may still need to correct the process, but the search starts with evidence.

For routine corrections, VNDLY supports inventory movements such as Adjustment (+/-) and Cycle count. If you need to make a manual correction, our VNDLY stock adjustment guide explains the workflow and audit trail.

The goal is not to pretend inventory will never be wrong. The goal is to make wrong numbers easier to find, explain, and fix.

What changes in the daily workflow

Before a location-aware process, a typical stock question looks like this:

• Sales asks whether an SKU is available.
• Someone checks the total in a system.
• Someone else checks a warehouse sheet.
• A third person confirms what is reserved or already moving.
• The customer waits while the business investigates its own data.

After the process is in place, the question becomes more direct:

• Open Inventory.
• Find the SKU.
• Read the total and per-location quantities.
• Check recent movements if the number looks unusual.
• Transfer stock or adjust the record when the physical situation requires it.

That is a modest change in clicks, but a large change in confidence. Your team stops treating location information as a side note and starts using it as part of the stock record.

It also improves purchasing. Instead of reacting to a shortage at one site with a new order, you can first ask whether a transfer solves the problem. That reduces unnecessary buying and helps you use the inventory you already paid for.

The practical starting point

You don't need to redesign your entire operation in one weekend. Start with the SKUs and locations that create the most customer or cash-flow risk.

1. Create every active warehouse, store, or fulfillment point in Locations.
2. Give each one a short, unambiguous code.
3. Review the stock table for the SKUs your team sells most often.
4. Post transfers when goods move instead of waiting for a weekly update.
5. Run a stocktake at the locations where variances happen most often.
6. Review recent movements when a quantity seems surprising.
7. Give warehouse and operations staff clear responsibility for posting receipts, shipments, adjustments, and transfers.

VNDLY's plan limits include locations, so choose the plan that fits the number of places you operate. Starter includes two locations, Professional includes five, and Enterprise includes unlimited locations. All three plans include the location-aware inventory workflow; the limits are part of the subscription capacity, not a separate per-location surcharge.

Frequently Asked Questions

How does multi-location inventory management work?

It records stock against a specific location instead of treating the business as one undifferentiated pool. You can then view both the total quantity for a SKU and the quantity held at each location.

Can VNDLY transfer stock between warehouses?

Yes. In Inventory movements, choose Transfer, select the From location and To location, choose the SKU, enter the quantity, and select Post movement. The transfer appears in the recent movement history.

Can I see stock for only one location?

Yes. Open a location from the Locations page to see its stock summary and the Inventory at this location table, including SKU, product, variant, and quantity. That inventory can also be exported as CSV or Excel.

What should I do when a stocktake doesn't match the system?

Keep the count tied to the correct location, review the movement history, and post an Adjustment (+/-) or Cycle count movement when the physical quantity has been verified. The important thing is to correct the record with a documented movement instead of silently overwriting a number.

How many locations does VNDLY support?

Starter supports two locations, Professional supports five, and Enterprise supports unlimited locations. The plans also differ by users, connected stores, and monthly order capacity, so check the full VNDLY pricing details before choosing one.