As soon as you try to manage inventory for several warehouses or stores in Shopify, you run into one unavoidable question: which real warehouse corresponds to which Shopify location? A Shopify location is a place that stocks, fulfills, and sells inventory. If you have three physical warehouses, you generally need three locations in Shopify to represent them.
If you leave this matching vague, you will eventually hit a nasty surprise — the numbers for your Tokyo warehouse somehow landing in your Osaka location. In this article we will walk through how to build a mapping table that ties real warehouses to Shopify locations, and how to keep it from breaking over time. This is not about counting stock or laying out spreadsheet columns; it is strictly about the name-to-location correspondence.
Why You Should Build the Mapping Table First
When you start configuring inventory sync, it is tempting to jump straight to how the numbers flow. But before that, capture the correspondence between your real warehouses and your Shopify locations in a single table. We call this the mapping table.
With a mapping table, you can see at a glance where each piece of inventory data is headed. The table tells you which location a given sheet row should feed. Without it, the correspondence lives only in the head of whoever set things up — and the moment that person changes, nobody can reproduce it. In multi-warehouse operations, creating this reproducible state matters more than almost anything else.
Standardize Your Location Naming Convention
The first thing to decide when building the table is a naming convention for your locations. Shopify lets you name locations freely, and that very freedom is what makes them drift apart. One person writes ‟Tokyo”, another writes ‟Tokyo DC”, and a third writes ‟Tokyo Warehouse” for the exact same place.
A good pattern is to lead with a short identifier for the region or site, followed by the role — for example ‟TYO-Main” or ‟OSA-3PL”, so the place and its purpose are obvious at a glance. Keep the warehouse name in your sheet and the location name in Shopify as identical as possible, and matching mistakes drop dramatically.
Inconsistent Spelling and Abbreviations Cause Accidents
Inconsistent spelling deserves special care. If your sheet says ‟Tokyo Warehouse” and Shopify says ‟Tokyo Warehouse” with a double space, a human reads them as the same, but any name-based matching treats them as two different places. Here are the common traps.
- Mixed character widths or accents (treating visually similar characters as identical)
- Extra spaces, or leading and trailing whitespace
- Mixing abbreviations and full names (‟Logistics” versus ‟Logistics Center”)
- Differences in upper and lower case
These tiny differences are exactly what break name-based matching. That is why you should write down the naming convention once and align both the sheet side and the Shopify side to it. It is the shortest road to avoiding accidents.
The Advantage of Binding by Location ID, Not Name
Follow the spelling problem to its conclusion and you reach a single answer: in the end, binding by location ID is safer than binding by name. Every Shopify location is assigned a unique ID. People can change names; the ID does not change.
So even if you later rename a location from ‟Tokyo Warehouse” to ‟East Japan DC”, the binding survives as long as the ID is the same. Match on name alone and the link snaps the instant you rename — inventory then writes nowhere, or worse, into the wrong place. Always record both the human-readable name and the machine-readable location ID in your mapping table.
Document the Mapping and Share It
A mapping table is not done the moment you make it. Record it as a document and share it so anyone on the team reaches the same conclusion. Put it on a dedicated spreadsheet tab, restrict edit access, and keep track of when, who, and why something changed.
If the correspondence lives only in one person’s head, it is not a system — it is a private skill. The moment you write it into a table, it becomes a shared asset for the whole team.
Also remember that to hold inventory in Shopify, a product must be stocked at the location in question. Alongside the mapping table, jot down which products carry stock at which locations, and you will catch missing setup far sooner.
An Update Flow for Adding or Renaming Locations
Warehouses get added, and their names change. Decide in advance how to update the mapping table each time, and you can relax. Here is the flow we recommend.
- 01Add or rename the location in Shopify (check whether a new ID was issued or the existing one stayed)
- 02Record the real warehouse name, the new location name, and the location ID in the mapping table
- 03Fix the warehouse name spelling on the sheet side to match your naming convention
- 04Before the real sync, run a connection test to confirm columns map to the right locations
- 05If all is well, fold it into your scheduled automatic sync and leave a change log
Follow this flow and your mapping will not quietly break, no matter how many locations you add or rename. Multi-warehouse inventory sync may look mundane, but locking down this name-to-location correspondence is the foundation everything rests on. Build one mapping table, align your naming, and record the IDs. That small preparation prevents big accidents down the road.