Shopify Inventory Sync History: Check What Changed, Store by Store

You open your second store and a product’s stock looks wrong. Maybe a price moved. Maybe a product you didn’t touch has a different description. The sync app says everything succeeded, but “success” doesn’t tell you what it wrote, where, or when.

If you run two or more Shopify stores with a sync app, this is a common place to end up: something changed on the other store, nobody remembers approving it, and there is no record you can read. This guide shows how to piece together what a sync changed, one store at a time, and check it against Shopify. The checks work on any setup.

Why “sync succeeded” is not an answer

A green status only says the app finished its job. It doesn’t say:

• which products and variants it touched,
• what the value was before and after,
• whether the run was started by hand or by a schedule,
• whether Shopify really holds that value now.

Without those four facts, you can’t tell a correct sync from a quiet mistake. A useful inventory sync history answers them per store, so you can go from “something looks off” to “this run changed this field on this store”.

Step 1: Write down what you expected

Before you read any log, note what should have happened:

1. Which store holds the stock count, and which stores follow it?
2. Which fields are meant to sync: title, description, price, compare-at price, stock?
3. Is a price rule set for a store (for example, a different price on the second store)?

This gives you something to compare against. A history without expectations is just a list.

Step 2: Gather the record, one store at a time

Work through one store at a time. For each store, collect what you can find about the changes in the window you care about:

• Your sync app’s own log or status page, if it has one: when it ran, and whether someone started it or a schedule did.
• Shopify’s adjustment history for stock. Open the product, and in the Inventory section click View adjustment history. It shows when a quantity changed and which staff member, app or sales channel changed it, for one variant at a time.
• Your team’s notes on who changed sync settings or price rules, and when.

Start with the most recent changes and work backwards to the time you first noticed the problem. For each change, note which store it hit and which field it touched, then compare that with your list from Step 1. Anything outside that list needs a closer look.

Step 3: Check the change against Shopify

A log entry is a record of what was sent. Shopify is the source of truth for what the store holds. For anything important, check by hand:

1. Open the product in that store’s Shopify admin.
2. Compare the current stock, price or description with what you expected and with what the record says was written.
3. If they match, the change did what was reported. If they don’t, you’ve found the store and the change to look into.

A later sale or return can also change a stock count, so check the timing in the adjustment history before you call a sync wrong.

Step 4: Decide per store: keep, fix or roll back

Once you know what changed, act on each store separately:

• Correct change: nothing to do.
• Wrong value: fix it on that store, or roll the change back. A synced change in StoreFleet can be rolled back for its store where Shopify allows. Not every change can be undone, so check before you rely on it.
• Unexpected field or product: review your sync setup and price rules before the next run.

Each change belongs to one store, and so does each rollback. There is no single action that undoes a change across several stores at once, which keeps a fix on one store from creating a new problem on another.

Step 5: Put an approval step in front of the next sync

Piecing together history tells you what already happened. To avoid the next surprise, make sure changes wait for a person first. In StoreFleet, every synced change is filed in its own store and waits for that store’s approval by default. Pending changes from all your stores appear in one Approvals list, so you review them in one place, and you approve each change for the store it belongs to. There is no single approval that applies to several stores. After a change is written, StoreFleet reads it back from Shopify to check it landed.

A simple routine:

1. Start a sync, or let a scheduled product sync run.
2. Open Approvals and preview what each store would receive.
3. Approve what is right for each store.
4. Spot-check the product in each store’s Shopify admin to confirm it matches what you approved.

On the Standard and Pro plans, live stock sync lets one store hold the stock count while the others follow it, and product sync can run on a schedule. Syncing products by hand (title, description, price and compare-at price, with a price rule per store) is on every plan. Either way, it is sync between your Shopify stores that you set up and approve store by store. It is not a promise that your stores stay identical without your review.

For a wider routine on keeping stock safe across stores, see how to manage multiple Shopify stores’ inventory without risky bulk changes. To check a single stock change end to end, see how to check a stock change really landed.

A quick audit checklist

• Do I know which store holds the stock count?
• Can I find out when each sync ran and who or what started it?
• Can I tell which store each change landed in?
• Was the written value read back from Shopify?
• Can I roll back a wrong change for that store?
• Did anyone approve it for that store before it was written?

If you answered “no” to several of these, your current sync setup is asking you to trust it rather than letting you check it.