When you only have one location, sheet design is relatively simple. Listing SKU and quantity will get you through most cases. The moment you add a second warehouse, a third store, or an external 3PL, though, the question of "how do we represent this in the sheet?" suddenly becomes much harder.
This article compares design patterns for keeping a multi-location inventory master in Google Sheets. Let's get the conclusion out of the way first: there's no single right answer. But there are clear points to look at when picking a design. Get those right and you dramatically lower the risk of your operations breaking down later.
Accidents that tend to happen with multiple locations
A few failure patterns we hear about often with multiple locations: "We overwrote the Osaka warehouse's inventory with the Tokyo warehouse's numbers by mistake." "We moved stock from the warehouse to a store, but didn't update the sheet, and the next day's sync rolled it back." "For some reason, this SKU only syncs at some of our locations." Every one of these is the kind of thing that proper sheet design could have prevented.
At the root of these accidents is almost always the same problem: it's unclear, in the sheet's own structure, which cell holds which warehouse's number. The team may understand it intuitively, but the sync app can't read that unspoken understanding. What matters is that location information is explicitly expressed in the column structure of the sheet itself.
Designing your columns
There are broadly two ways to express multi-location inventory in a sheet: the horizontal layout and the vertical layout. Both are common in actual operations, so let's look at the strengths and weaknesses of each.
Horizontal layout
In the horizontal layout, one row corresponds to one SKU, and locations are spread across columns. For example, to the right of the SKU you'd have four columns — Tokyo warehouse, Osaka warehouse, Shibuya store, Umeda store — each holding a quantity. It's a format many stores have used since the Excel days and looks visually clean.
- Pro: one SKU per row is easy to read; total inventory is a simple row sum
- Pro: lays out nicely if you print it as a stock-count sheet
- Con: adding a new location means adding a new column
- Con: awkward when you want to update only one location at a different time
Vertical layout
In the vertical layout, each row corresponds to a SKU × location combination. The same SKU at three locations becomes three rows. It's closer to a database mindset, and the column structure doesn't need to change when you add a location.
- Pro: adding a location just means adding rows
- Pro: partial sync by location and filter-based narrowing are easy
- Con: seeing total inventory for one SKU needs a SUM or pivot
- Con: row count balloons with the number of locations, hurting at-a-glance readability
Which is easier to operate?
So which is better, horizontal or vertical? The answer depends on what stage your store is at.
If you have two or three locations and a few hundred SKUs at most, the horizontal layout is far easier to live with. You see the whole picture the moment you open the sheet, and it's well suited to writing in stock-count results directly. It also makes it easy to build a shared mental model of "the inventory table" inside your team — another quiet strength of this pattern.
Once you cross into five or more locations and over a thousand SKUs, however, horizontal slowly becomes painful. There are so many columns that scrolling is a chore, and when you want to update only one location at a separate time, you tend to drag unrelated columns along with you. This is the point at which it's worth thinking about moving to the vertical layout.
If you're unsure, the realistic approach is a two-stage one: start horizontal and switch to vertical when operations get painful. Sync Master is designed to handle both patterns, so the timing of the migration can be decided flexibly on the operations side.
What the sync side can take care of
However careful your sheet design, in real operations things will always change — a location gets renamed, a new store is added, a particular warehouse needs to be paused temporarily. Operations become much safer when the sync app provides a few protections for these situations.
- Location name pre-mapping: ties sheet-side names to the official Shopify names
- Targeted runs by location: enables partial syncs like "only the Tokyo warehouse today"
- Ignore non-existent locations: avoids cascading errors when unregistered location names sneak into the sheet
Sync Master ships with configuration options for these multi-location situations. You don't have to think about them at first, but as your locations grow, you'll find yourself thinking "ah, I'm glad this feature was here."
Next time we'll take on a long-standing Shopify staple: CSV upload workflows. We'll look concretely at why switching to sheet sync is safer and walk through the pitfalls of CSV-based operations.