Multi-store5 min read

Compare Inventory Across Multiple Shopify Stores Before You Change It

Check one SKU's stock in every Shopify store before you edit anything, then change each store with a preview and its own approval. Sync waits for approval too.

In this guide
  1. Why looking before changing matters
  2. Step 1: Open Stock by SKU
  3. Step 2: Find the SKU
  4. Step 3: Read the numbers before you decide anything
  5. Step 4: Change one store at a time, with a preview
  6. Step 5: Check the result after it’s written
  7. What this doesn’t do
  8. A quick routine you can reuse

You open a product in one store and the stock says 12. In the second store, the same SKU says 0. In the third, you aren’t sure. If a sync app has ever changed or zeroed stock in another store without anyone approving it, you know why this matters. The first step is to see the numbers side by side, before anything gets written.

This guide shows a safer routine to compare inventory across multiple Shopify stores. You look first. You decide second. Then you change each store on its own terms.

Why looking before changing matters

The problem isn’t that the numbers differ between stores. They often should. One store may hold the stock, another may be a wholesale or regional storefront, and a third may be a client’s. The problem is writing to a store before you’ve seen the full picture.

So split the job in two:

  1. Read: see one SKU’s stock in every store.
  2. Write: change a store only after you’ve seen a preview and approved it for that store.

If a sync app has already changed stock behind your back, start with what to do when a sync app changed stock without approval. This post is about the routine that comes before any change.

Step 1: Open Stock by SKU

In the StoreFleet web dashboard, open Inventory & Products → Stock by SKU. Each row is one SKU, with its stock in every connected store side by side. This view is for reading: opening it changes nothing in any store.

Step 2: Find the SKU

Find the row for the SKU you want to check. By default the table shows only SKUs that are mismatched or missing; switch to All SKUs to see everything. Click Read again to read the latest stock from your stores.

The table also marks what to look at:

  • Mismatch: the stores report different quantities for this SKU.
  • Missing: a store does not carry this SKU.
  • Duplicate: the SKU appears more than once in a store.

This is useful when:

  • A customer asks whether an item is available and you run more than one storefront.
  • You suspect a past sync or bulk edit put a store out of line.
  • You’re about to restock and need to know where the stock actually sits.
  • You manage client stores as an agency and want to check before you touch anything.

Step 3: Read the numbers before you decide anything

Before you edit, ask a few questions:

  • Is the gap expected? A store with 0 may be intentionally sold out or reserved for another channel.
  • Which store is right? If you recently received a shipment or did a stock count, you know which number to trust. If you don’t, check that first.
  • Does every store need the same number? Often not. Decide per store.

This is the step a silent sync skips. It copies a number from one store to another with no human judgment. Here, the decision stays with you.

Step 4: Change one store at a time, with a preview

When you’ve decided a store’s stock should change, make the change for that store. To copy another store’s quantity, click the store’s cell for the SKU and choose Match another shop. Either way, StoreFleet shows a preview of what will be written, with the values before and after, and the change waits for approval.

Two rules apply:

  • Each change belongs to one store. There is no single approval that applies to several stores. If three stores need a fix, you review three changes, each approved for its own store.
  • Nothing is written until it’s approved. Pending changes from all your stores appear in one Approvals list, and each item stays tied to the store it belongs to.

This takes a few more clicks than a blind sync. That’s the point. Inventory is the kind of data where a wrong write costs you oversold orders or products showing as out of stock.

Step 5: Check the result after it’s written

After a change is written, StoreFleet reads it back from Shopify to check that the store now shows what you approved. Where Shopify allows it, a change can be rolled back. Not every kind of change can be reversed, so the preview is your main safeguard.

A simple habit: after a round of edits, go back to Stock by SKU, click Read again, and confirm the numbers match what you intended.

What this doesn’t do

To avoid surprises:

  • Comparing doesn’t turn on a sync. Live stock sync, on the Standard and Pro plans, is a separate group you preview and turn on, and each stock change it copies waits for that store’s approval by default.
  • Comparing stock is a read. It doesn’t make any store match another.
  • Match another shop is a one-time change you start, approved like any other. To keep stores in step afterwards, use live stock sync.
  • An approval for one store doesn’t carry over to another store.

If you want stock to change in another store, you decide it, preview it and approve it store by store.

A quick routine you can reuse

  1. Open Inventory & Products → Stock by SKU.
  2. Find the SKU’s row and click Read again.
  3. Compare each store’s number against what you know is true.
  4. Create the change for each store that needs one.
  5. Review the preview and approve it for that store in the Approvals list.
  6. Check the read-back, then look at the SKU’s row again.

For a step-by-step routine for the change itself, see how to manage multiple Shopify stores’ inventory without risky bulk edits.