Once your store runs several warehouses or shops and you start syncing inventory, a whole new class of trouble appears that never showed up with a single location. The numbers themselves are right, yet ‟somehow it lands in the wrong place” or ‟stock exists but can’t be sold” — these are location-specific stumbles.
This article rounds up the mistakes teams most often make with multi-location sync, each paired with its cause and a fix. Rather than a generic checklist, it sticks to the concrete pitfalls that actually crop up in practice, so work through whichever ones ring a bell.
Mistake 1: Writing to the Wrong Location
The most common one is writing inventory to a location other than the one you intended. A Shopify location is a place that stocks, fulfills, and sells inventory, and even for the same SKU, warehouse A and store B are tracked separately. If your sheet’s ‟column for warehouse A” is mapped to store B on the Shopify side, the figure is correct but the destination is wrong — one ends up overstocked, the other stocked out.
The fix is simple: manage the column-to-location mapping by a reliable link rather than by name alone, and always test once before a real sync. Location names are often similar, so they are easy to mix up by eye — build a correct mapping table first and lock it down for peace of mind.
Mistake 2: Assigning Quantity Before Stocking the Location
In Shopify, you can only assign a quantity at a location after you have set the product to ‟stock inventory” at that location. If you add a new warehouse but forget to enable that location on the product, a sync will fail to write the quantity, or error out. This crops up especially when adding new products or standing up a new warehouse.
- After adding a new location, enable it as a stocking location on the relevant products
- After creating a new product, confirm it can hold stock at every location you need
- If a SKU won’t take a quantity on sync, suspect a missed location enablement first
- Use bulk editing to enable the target locations in one pass
Mistake 3: Mixing Up Inventory States and How You Count
Inventory is recorded per location as states (available, committed, on hand, and so on). Sync while that distinction stays fuzzy and you create unexpected shortfalls or surpluses. Let’s look at the headline cases in three parts.
Confusing Committed and On Hand
On hand is what physically sits in the warehouse; available is on hand minus committed (ordered but not yet shipped). If your sheet tracks on hand but you compare it directly against Shopify’s available and jump to ‟they don’t match,” you will make needless adjustments. When you sync, the rule is to line up like with like between sheet and Shopify. In most cases the safe approach is to write the sheet’s on hand into Shopify’s on hand and leave committed to Shopify’s order processing.
Double-Counting Across Columns
If you keep per-location columns but also hand-type a separate ‟total stock” column, the total and the per-location figures drift apart before you notice. Pour that total into some location as well and you end up counting the same stock twice. Decide that the total is always computed by a formula, and that the only thing you ever type in is the per-location quantity.
Mistake 4: Syncing the Total
Writing ‟100 across all locations” into a single location in one lump is another classic. Shopify routes orders and decides where to fulfill from based on each location’s inventory. Pile the total into one spot and fulfillment gets distorted — it may try to ship from a store that has none, or pick a far warehouse when a near one was available.
The fix is to hold the sheet as per-location quantities and sync to Shopify at that same granularity. Sync Master treats Google Sheets as the single source of truth and writes the sheet’s per-location on hand straight into each Shopify location, so there is no need to consolidate a total anywhere. Keeping the granularity intact is, in the end, the approach with the fewest accidents.
Mistake 5: Leaving Stale Location IDs and Settings in Place
If you recreate a location after a warehouse move or a store swap but leave the mapping to the old location in place, the sync keeps writing to a place you no longer use. On screen it looks like a success, yet the real store’s stock never updates. Whenever you add or remove a location, be sure to revisit the mapping table and the schedule settings.
- 01After adding, removing, or deactivating a location, update the column-to-location mapping
- 02Run the connection test again afterward to confirm it lands in the right place
- 03If you use scheduled sync, check that the target locations match the current setup
- 04Tidy up columns for retired locations early to avoid confusion
Each multi-location sync mistake is simple on its own, but stacked together the cause gets hard to see. Nail down these five points — destination, stocking, the state distinction, granularity, and ID freshness — and build the habit of confirming with a connection test after every change, and you will head off most stockouts and oversells. Start with whichever item rings a bell and check them off one by one.