Inventory sync apps usually include a feature called full sync that pushes every row of your sheet into Shopify in one shot. It's more deterministic than delta sync and can process thousands of rows at once, which makes it reliable for big moments — initial loads right after a migration, or a clean reset at the start of the month.
But that convenience has a flip side: full sync is also an operation where a single mistake can be enormous. Pointed at the wrong column, or run while your safety-stock formula was broken, and thousands of rows of data are overwritten in an instant. This article gives you a checklist to verify before every full sync — split into sheet-side, Shopify-side, and last-minute final checks.
What 'full sync' actually does
Let's clarify what full sync is. Most sync apps have two modes: delta sync and full sync. Delta sync is a light operation that pushes only the changes since the last run. Full sync writes every row of the sheet into Shopify. If the sheet says '100,' Shopify's inventory for that product gets overwritten to 100 with no questions asked.
Because of this behavior, full sync's biggest precondition is that the sheet is in a correct state. If the sheet contains errors, those errors propagate straight into the store. Conversely, when the sheet is correct, full sync is the most powerful tool for restoring consistency. That's exactly why the pre-flight check matters so much.
Sheet-side checks
Start by inspecting the Google Sheet thoroughly. Doing this carefully prevents most production incidents.
Confirm the required columns
Do you have all the columns the sync needs? Typically three: SKU (or barcode), location, and inventory count. In the app settings, you map which column corresponds to which field — before a full sync, revisit that mapping screen and check that 'no column points somewhere unexpected.' Forgetting that you changed the spec last month and running with the old mapping is a textbook accident.
How empty cells are handled
When the inventory column has empty cells, apps differ on behavior: 'treat as zero,' 'skip,' or 'error out.' If full sync writes empty cells as zero, hundreds of products could suddenly appear out of stock. Before running, filter the inventory column for empty cells and decide whether you really want them to be zero, or whether the data is simply missing.
Verify data formatting
Easier to overlook than you'd think: data format. Is the inventory column mixing in strings ('out of stock,' 'TBD,' etc.)? Are there trailing spaces in SKUs? Does the numeric column contain commas as thousand separators? Any of these leads to sync errors or wrong values being written. Google Sheets' data validation rules let you restrict per-column formats up front — if you'll run this regularly, set them.
Shopify-side checks
Don't forget to confirm the state of the destination — Shopify itself — not just the sheet.
- Is the target location active? (You don't want to write into a deactivated location.)
- Is inventory tracking enabled on the product? (If tracking is off, writes won't be reflected.)
- Are any target products archived? (Archived products are often excluded from sync.)
- Does your Shopify plan fit the number of products and locations you're syncing?
- Are any other inventory apps running at the same time? (Multiple apps writing concurrently causes nasty conflicts.)
The last point — conflicts with other apps — deserves particular care. If a warehouse-management system or another sync tool is running in the background, the value you just wrote with full sync can be overwritten moments later. Pause other inventory writes for the few tens of minutes around your full sync.
Right before you press the button
Sheet checked. Shopify checked. Mapping confirmed. Now you're about to run full sync — give yourself one more pass.
- 01Open the sheet's revision history and review 'who changed what in the last 24 hours' at a glance
- 02Read aloud the inventory numbers for a handful of critical rows (e.g., your top 10 sellers) and confirm they look right
- 03If the app has a 'connection test' or 'dry-run' feature, use it without fail and preview the expected outcome
- 04Pick the day and time of day deliberately (avoid peak order hours and times when you're busy with email)
- 05Decide in advance how you'll verify success (which screen and which numbers will tell you it worked)
The dry-run feature in particular is essential whenever it's offered. It's a mode that 'doesn't actually write but simulates what the result would be.' If hundreds of errors or unexpected changes show up here, cancel the real run, fix the root cause, and try again. Ten minutes of verification prevents hours of recovery work.
Full sync is an operation where convenience and risk go hand in hand. But if you commit to walking through this checklist every time, the risk shrinks dramatically. The more comfortable you get, the more tempting it is to skip checks — yet that's exactly when incidents strike. Keep that in mind and build the habit of pausing for one breath before every run.