Managing Inventory at Multiple Locations in QuickBooks Online
QuickBooks Online keeps one quantity per item, not one per site. We explain the limit and compare locations, sub-items, and inventory apps.

Many QuickBooks Online files reach a point where stock sits in two places: a warehouse and a shop, a main site and a satellite. The question that follows is always the same, and people often suspect their file is simply set up wrong. It usually is not. QuickBooks Online keeps a single quantity on hand for each item, and every workaround trades something away. There are three realistic routes, and one question decides between them.
Does QuickBooks Online know how much stock sits at each site?
No. Each product in your item list carries one quantity on hand and one average cost. The software has no concept of “12 units at the warehouse and 4 at the store”; it only knows 16 units. Multi-site warehousing has long been a feature of QuickBooks Desktop Enterprise, and the online product never inherited it. So the “correct way” your books seem to promise does not exist inside QuickBooks Online alone. That is a real limit of the software, not a mistake on your part.
Does location tracking solve it?
Partly. Location tracking, which sits in the Plus and Advanced plans alongside inventory tracking, tags each transaction with a site. Profit and loss reports then split by location, which answers the question “which site makes money?” What it cannot do is split the balance sheet. The inventory asset stays in one pool, and quantity on hand never divides by site. If your real need is site profitability, locations are enough. If you need to know where units physically sit before promising a delivery, they are not.
Can sub-items stand in for locations?
Yes, and for one or two sites the approach holds up. Create a parent item, then one sub-item per site: for example “Widget, Warehouse” and “Widget, Store”. Sell from the sub-item that shipped the goods, and receive purchases against the site that took them in. Moving stock means a quantity adjustment that lowers one sub-item and raises the other by the same amount.
The costs are real. Your item list can double overnight, and years of inconsistent entries will multiply with it. QuickBooks Online has no transfer transaction for inventory, so adjustments are the only lever, and any cost difference posts to your adjustment account. Low-stock alerts also fire per sub-item rather than for combined stock. We suggest this route only for short item lists and patient bookkeepers.
Should the detail live in an inventory app?
Often, yes. Dedicated apps such as SOS Inventory or Cin7 track quantities by site and bin, handle transfers, and post summarized entries into QuickBooks Online. Your file then keeps the financial view while the app holds the operational truth. Before committing, ask two questions. Does the app support multiple sites and transfers between them? And what does its sync create inside QuickBooks, because some apps mirror each site as its own item and your list grows to match.
Clean the item list before layering anything on top
A file built by many hands over the years usually holds duplicates, dead items, and quantities nobody has verified. Any multi-location scheme will faithfully reproduce that mess at every site. Audit first: merge true duplicates, archive what you no longer sell, and set quantities from a fresh physical count. Merging is permanent, so check twice. Then write the convention down on one page, so the next person follows it instead of inventing a fourth option.
One question decides the route
Do you need quantity per site, or profit per site? Profit alone: turn on locations and stop there. Quantity across one or two small sites: sub-items with disciplined adjustments. Quantity across several sites, bins, or channels: an inventory app for operations, QuickBooks Online for accounting. Pick the smallest option that answers the question, because each step up adds maintenance.
Your next move is small. Export the product list, mark what actually sold this year, and run a full count at one site. That count, set against the books, tells you which of the three routes your file can honestly support.