Everyone feels the same anxiety the first time they use a sync app: "What if I mapped the sheet to Shopify wrong and zero out every product's inventory?" That fear is not unfounded. Stories of misconfigured syncs that nuked live inventory show up in the Shopify community on a regular basis. That is why there is one ritual you should always perform before any live sync: the connection test.
A connection test is a feature that, instead of writing to Shopify, previews what would happen if you ran the sync with the current settings. Sync Master ships with one out of the box. In this article we walk through that high-leverage habit—seconds of effort that all but eliminate nighttime firefighting.
What does a connection test actually do?
A connection test is essentially a read-only dress rehearsal. It writes nothing to Shopify; it compares the contents of the sheet with the current state of Shopify and returns a report.
Concretely, it works like this. First it opens the Google sheet and reads the configured sync key column. Next it uses those values to find the matching variants on the Shopify side. Each match counts as a success, each miss counts as a failure. Finally it compares the inventory numbers on both sides and highlights rows where they differ.
What you can verify
There is more to learn from a connection test report than you might expect. Here are the most important things to check.
Matching results: success of the linking
The most important figure is the match rate. Of 100 rows in the sheet, how many were correctly linked to a Shopify variant? In an ideal world it is 100%, but in practice you tend to land around 95% and discover things like "five SKUs were actually blank" or "three barcodes had extra whitespace."
Diff preview: which values would change
The other big thing is the diff: which rows would change, and how, if you ran the live sync. You will see lines like "SKU TX-001: 50 today, would become 48 after sync," with the change shown per row. Scan it for any unexpectedly large swings (such as a drop of 1,000 units).
Warnings: signs of trouble
Warning messages are not to be skimmed past. "Location name does not match Shopify," "Numeric column contains text," "The same key appears in multiple rows"—these are often the early signal of incidents that will hit you later. It is well worth clearing each warning before running a live sync.
Pre-flight checklist
To get the most out of your connection test, here are the items to check before you run it. When test results look bad, the most common reason is that the sheet was not ready.
- 01Make sure no rows have a blank sync key column (SKU or barcode)
- 02Make sure numeric columns do not contain unit text such as "pcs" or "pieces"
- 03Confirm location names match the Shopify admin spelling exactly
- 04Check that the header row has no stray formatting
- 05Make sure no other user with edit access is working in the sheet
- 06Confirm no large product import or export is in progress on the Shopify side
Clear these six items before running the connection test and your results will be stable. Skip them and you will keep hitting "the test passed 100% but live failed," the most frustrating kind of surprise.
Common issues and fixes
Here is a quick summary of common issues you will see in connection test results and how to handle them. Most of them are minor and can be recovered in a few minutes.
- Match rate lower than expected → check the sync key column for whitespace or mixed full-width/half-width characters
- Location-related warnings → align the location names in the sheet exactly with those in the Shopify admin
- Errors in numeric columns → remove thousands separators and unit text
- Extreme diffs → re-check that the inventory column is not pointing at the wrong column
- Test never completes → Shopify may be under heavy load; wait and retry
Location-related warnings are overwhelmingly caused by inconsistent naming. "Tokyo Warehouse" versus "東京倉庫" being different from what Shopify has is enough to break the link. They are just strings, but exact matches matter.
If multiple issues show up at once, prioritize and tackle them one at a time. Match-rate issues first, then locations, then formatting. Fixing other items while match rate is broken will not get you into a state ready for a live sync.
Wrap-up: treat the connection test as a ritual, not an option
As long as you treat the connection test as a "just-in-case" extra, you will keep skipping it. Build it in as a ritual before every sync, however, and incidents drop dramatically. Before your weekly scheduled sync, before bulk-loading a seasonal collection, immediately after adding a new location—always run the connection test. That alone makes you far less likely to get woken up by a midnight phone call.
Inventory data is one of those things where a mistake costs more than the numbers themselves; it costs trust. A connection test takes seconds, but those seconds protect the trust between you and your customers. Starting today, make running it before every live sync a non-negotiable habit.