Inventory sync in Shopify means every place that changes stock writes to the same count for each variant at each location. Sales, refunds, adjustments, transfers, imports and apps all change that one number. Things go wrong when two of them disagree about what the number should be: an app and a spreadsheet both "setting" the quantity, or a CSV import that overwrites sales made since the export. The fix is to decide one owner for each kind of change, and to use changes that add or subtract rather than overwrite.
The short version
- Shopify holds one count per variant per location. Everything else is a copy.
- Changes that add or subtract (a sale, an "Adjust by", a received transfer) are safe to run together.
- Changes that overwrite ("Set to", the bulk editor, an "Available" CSV import) are where counts get lost.
- Export inventory CSVs in the "All states" format. It keeps the current on-hand beside the new one, so Shopify can warn you when something changed in between.
- Give each job one owner: Shopify for sales, your production app for batches, your counts for corrections.
What changes a Shopify count
| Change | Adds or overwrites |
|---|---|
| Online or POS sale, fulfillment, refund with restock | Adds or subtracts |
| Adjust by, with a reason | Adds or subtracts |
| Transfer shipped and received | Adds or subtracts at each end |
| Set to, after a count | Overwrites |
| Approved stock count | Overwrites the counted items |
| Bulk editor | Overwrites, without the usual history detail |
| Inventory CSV import | Overwrites, safely if "All states" with current on hand |
| Apps | Either, depending on how the app is built |
Shopify's help center notes that the bulk editor changes absolute quantities with no origin or destination, so it doesn't keep the same trail as an adjustment. Keep it for big resets.
A made-up example of a lost count
Pali Pottery exports its inventory CSV on Monday morning, with 30 mugs on hand. By Monday afternoon, after packing, it has made 12 more and sold 5. The owner types 42 into the old file and imports. Shopify now says 42, but the true count is 37, because the 5 sales made since the export were overwritten. In the "All states" format, Shopify compares the file's current on hand with the live number and flags the difference before importing.
Keeping apps from fighting
When an app writes stock to Shopify, ask:
- Does it add or set? An app that sets absolute numbers on a timer can undo a sale made a minute ago.
- Which locations does it write to? It should write only where it owns the stock.
- What happens when Shopify and the app disagree? A good app shows you the difference instead of silently overwriting either side.
Shopify inventory not updating covers the common causes when a count won't move at all, and Shopify overselling covers what happens when it moves too late.
Where this stops working
Sync keeps one number right per finished product. It can't tell you whether that number is correct in the first place: if a batch of 48 is entered as 84, every system agrees on the wrong count. And it only covers what Shopify holds. The ingredients behind the product aren't synced anywhere unless you keep them somewhere. That's covered in Shopify raw materials inventory.
How TaroStack does it
TaroStack for Shopify runs inside your Shopify admin and owns one job: what you make, receive and count. When a batch finishes, it adds the finished products to the right Shopify location instead of setting a number, so sales made in the meantime stay counted. A daily check compares TaroStack with your store and shows you any difference, rather than overwriting either side. Behind each count, it keeps the ingredients, the recipe and the lot. Free for 14 days.
