When you start syncing inventory in Shopify, one early decision keeps paying you back — or keeps costing you — for a long time: how many locations to create. It looks like you should simply line up one per warehouse or store, but the number of locations sets the size of the whole sync. Too many or too few, and your daily inventory updates slowly get heavier.
This article deals only with that design decision — how many to split into in the first place — before you get into column mapping and sync settings. We’ll cover when to split, when to keep things together, and how to decide when you’re unsure. Do read it with your own shelves and warehouses in mind.
Why the location count decides how heavy your sync is
A location is the unit for a place that stores, ships, and sells inventory. Shopify keeps quantities separately for each location, so the more locations you have, the more finely you can see your stock. But from the sync side, that fineness comes straight back to you as more data to maintain and more work to do. Let’s make that structure explicit first. What a Shopify location actually is sets out what a location really represents.
Rows and columns multiply, they don’t add
The scale of an inventory sync isn’t set by your SKU count alone. The quantities you actually have to maintain are the combinations of SKU and location. With 500 SKUs at one location you’re managing 500 numbers; at four locations that becomes 2,000. There’s a big gap between how “just two more warehouses” feels and how the data volume actually grows.
When you use a spreadsheet as the single source of truth for stock, the basic shape is to hold each location’s on-hand quantity in its own column. So adding one location adds one column to the sheet. Adding the column is the easy part; whether you can keep filling it in correctly, every time, is what determines your sync accuracy.
- 500 SKUs × 1 location = 500 quantities to maintain
- 500 SKUs × 4 locations = 2,000 quantities to maintain
- Every location you add adds one more column to the sheet
- Blanks and values that stopped being updated are still treated as “the number” on every sync
What gets overlooked here is the column nobody quite finishes filling in. A column no one updates either carries a stale number into every sync or lingers as a blank you have to think about. Not creating columns you can’t sustain is, in the end, the most reliable accuracy measure you have.
Every location needs somebody who actually counts it
Creating a location in the Shopify admin takes a few minutes. But the numbers that go into it only exist if someone actually counts them. Someone to run the stock take, someone to record what comes in and out, someone to investigate when there’s a discrepancy. Creating one more location means adding one more set of these roles.
Location designs that stop working share a pattern: somewhere in the mix is a location with no one assigned to count it. Numbers from a place nobody counts quietly stop being trusted, and eventually get dropped from the sync altogether. When you’re unsure whether to add one, ask yourself first: who is going to count this? If you can’t answer with a specific name, it isn’t time to split yet.
More places means more sources of drift
Inventory drift is usually born in the moment something moves but doesn’t get recorded. Transfers between stores, re-shelving inside a warehouse, samples going out, returns coming back in. The more locations you have, the more of these movement paths exist — and the more chances there are to miss one.
What makes cross-location movement especially awkward is that the total stays the same, so nothing looks wrong. The overall figure matches while the breakdown quietly drifts. That state only surfaces the day you can’t ship from a place that was supposed to have stock. So when you add locations, decide on the rules for recording movement at the same time.
Three conditions that justify splitting a location
So when should you split? Rather than distance or the number of buildings, look at these three angles and your judgment stays steady. If even one of them clearly applies, the split is worth it.
When the stock is physically separate
The clearest condition is that the stock sits in physically separate places and you can’t use one side’s stock for the other side’s orders. Ten units in the Tokyo warehouse and three in the Osaka store add up to thirteen, but only three are immediately usable for an Osaka order. Try to express that difference as a single number and it will contradict reality somewhere.
Split the locations and you can express exactly that state for one product: in stock in Tokyo, sold out in Osaka. On the sheet side, it’s simply a Tokyo column and an Osaka column. Keep things that are physically separate separate in the data too — that’s the most straightforward design, and the one that leaves the fewest doubts later.
When it ships from a different origin
The second condition is whether you actually ship orders from there. A different shipping origin means different shipping costs, different delivery times, and a different sender on the label. Shopify can only decide which location to assign and ship an order from if the locations are separate to begin with.
Put the other way round: a storage-only space you never ship from doesn’t necessarily need to be its own location. That said, if you plan to ship from it in future, splitting early makes the transition easier. Consider both questions — do you ship from it now, and are you likely to ship from it soon?
When it is counted independently
The third is the unit you count in. If different people count it at different times, those numbers already exist separately. Adding them together before entering them into Shopify not only adds arithmetic every single time, it also makes it impossible to tell which of the two figures is the stale one.
Match the unit you count in to the unit you sync in. It sounds unglamorous, but this is the single most reliable way to raise sync accuracy. If the stock-take sheets your team already uses are split by place, that split is often the answer to your location design, ready-made.
- 01The stock is physically separate, and one side can’t be used for the other side’s orders
- 02You actually ship orders from there, or plan to in the near future
- 03Different people count that stock at different times
Cases where you don’t need to split
Just as important as the conditions for splitting is being clear about when not to. Add a location in the cases below and the upkeep grows out of all proportion to what you get back. The failures that follow from over-splitting are listed in common multi-location sync mistakes.
When two teams simply touch the same shelf
Even if your online team and your store team each watch the stock, if the shelf it physically sits on is the same, that is one location. Split it for organisational reasons and the same stock on the same shelf exists as two numbers, and nobody can tell which one to trust.
What you need here isn’t a split; it’s a single decision about who updates that shelf’s number. Having several people involved is fine. Having several entry points for the number is the problem. If the sheet is your source of truth, simply deciding who updates the column for that shelf clears up most of the confusion.
When you want to separate states like reserved or damaged
Buckets like reserved, awaiting inspection, or damaged describe the state of stock, not a place. The urge to model them as locations is understandable, but it leaves you with locations that are neither a shipping origin nor a counting unit, and they end up mixed into the pool of candidates orders can be assigned to.
These state distinctions are usually easier to handle as columns in the sheet. For example, keep sellable quantity and awaiting-inspection quantity in separate columns and sync only the sellable column to Shopify. A location represents a place; a sheet column can represent a state. Keep that division of labour in mind and the design gets much cleaner.
When you want a split purely for reporting
Because you want to see sales by region, or track stock by product category — those are usually not good reasons to add locations. Groupings for reporting can be rebuilt later from aggregation. The operational load of an extra location, on the other hand, is paid every single day.
When you’re torn, ask: does anyone decide anything by looking at this distinction? Changing a price, triggering a replenishment, pausing sales. If the distinction doesn’t lead to a concrete action like those, it’s an analytical lens — not something to hold as a location.
You don’t have to get the perfect location structure right on day one. Adding the missing boundaries as you operate is entirely enough.
How to settle on a count that’s just right
With those conditions in hand, how do you actually decide? The approach we’d recommend has three stages: start coarse, try it in the sheet, and review on a fixed cadence. Let’s take them in order.
When unsure, start coarse
Splitting later is relatively easy; merging is not. Combining locations that already hold quantities means re-assigning past figures and pausing operations while you do it. That asymmetry is exactly why, at the point of doubt, not splitting is the safer move.
Concretely, start by creating locations only for the places that genuinely act as shipping origins. For most shops that comes to two or three. Run it for a while, and if you hit real situations where not seeing the breakdown causes trouble, splitting at that point is still perfectly timely. Growing from one is the subject of migrating from a single location to multiple.
Model it in the sheet before you create it in Shopify
Before you add locations, we’d suggest building the shape in your spreadsheet first. Set up one column per intended location and fill in real quantities by hand for about a week. That alone makes it remarkably clear whether the design can survive daily operations.
What you’re checking here isn’t the accuracy of the numbers but whether the columns get filled at all. A column that ends up blank every time is a sign that location is premature. If every column fills without strain, create the Shopify locations to match, confirm the column-to-location pairing with a connection test, and then move on to a real sync. Model it with one sheet, many locations.
- Set up one column per intended location in the sheet
- Fill in real quantities by hand for about a week
- Check whether any column keeps ending up blank
- If all is well, create the locations in Shopify and confirm the pairing with a connection test
- Then move the whole thing onto a scheduled sync
Decide the review cadence up front
Location design isn’t something you settle once and forget. Stores open, fulfilment moves to a third party, seasonal stock goes somewhere else — the business changes first. That’s why deciding up front on a cadence, such as a review every quarter, keeps the design from drifting away from reality.
There isn’t much to look at during that review. Is there a location whose quantities haven’t moved at all in three months? Is there a single column quietly holding stock from more than one place? And is somebody still assigned to count each location? Those three questions are usually enough to tell you whether to add or to trim.