Notices and what to do

The basics

• A notice appears where the problem happened and names the cause and the next step.
• If it says "Nothing to do", the app handles it by itself, for example when Shopify briefly slows down requests or can't be reached for a moment.
• If the app can't make sense of a message, it shows you the technical message too. If the error keeps happening, send it to support.
• Notices that only inform you can be dismissed. They come back only when there's a new reason. Notices about an ongoing problem stay until the problem is fixed.

"… can't be reached"

The app couldn't write to this store. The other stores still get their changes, this one doesn't until access is restored. The app retries whatever didn't arrive.

• No access anymore: usually the app was uninstalled in that store. Open the store and the app there. Note: after an uninstall, the store starts from scratch when you reinstall the app and has to be connected again (see "Uninstalling and your data").
• Shopify briefly slowed down requests or couldn't be reached: nothing to do, the app tries again by itself.

"Real-time sync paused for …"

More than 20 inventory levels in this store dropped to 0 within 10 minutes. That looks like an import or an empty store, not like sales. To keep the other stores from being emptied, the app sends nothing from this store for now. The other stores keep running.

1. Click "View in activity log" and check which inventory levels dropped.
2. Check in the store whether an import or bulk change ran and whether the numbers are right.
3. Click "Checked, resume".
4. Then check that inventory is right in all stores. A sync with "Sync now" on the "Sync" page brings them in line using your rule.

"Real-time sync paused for …: someone else is writing too"

Don't rely on this notice alone. It only shows up once the change has already been counted one to three times too often. The app doesn't detect a second app that writes different amounts every time. In a test on October 6, 2026 it showed up after the first round. By then, inventory was at 140 instead of 35 in both stores. So if you don't see the notice, that doesn't mean no second app is writing. The only safe way is to turn the other app off before you turn on real-time sync.

This notice names a SKU, not a store. Within 15 minutes, the same change kept coming back, shortly after the app had transferred it, and there was never an order behind it. That was in two stores, or three times in the same one. The notice tells you where. That's what it looks like when a second app syncs inventory between the same stores: each app passes on what the other one wrote, and inventory runs away in every store.

So the app transfers nothing for this SKU anymore, and syncs leave it out too. All other SKUs keep running. The notice shows the quantity in each store, the transfers from the minutes before, and a link to Shopify's adjustment history for each store. For every change, that history lists the app or staff member behind it.

1. Check the adjustment history to see who made the changes. If it's another sync app, turn it off.
2. Count your stock and set the right quantity in every store while the SKU is still paused. The app doesn't transfer these corrections. After a loop like this, it can no longer tell which quantity is correct.
3. Click "Checked, resume". From then on, every new change moves to the other stores again.

Good to know:

• If you resume while the other app is still running, the app pauses the SKU again as soon as the next duplicate arrives.
• If three SKUs are paused within 30 minutes, the app pauses real-time sync for the whole group. Each store then shows "Real-time sync paused for …" with that reason, and you resume store by store. The individual SKUs stay paused until you resume them too.
• Changes that weren't transferred while the SKU was paused are in the activity log with the result "Paused".
• No second app running? Then the same amount was entered several times in a row with no order behind it: four times in the same store, for example four returns of the same variant, or three times alternating between two stores. The app didn't transfer the last of these. In that case steps 2 and 3 are enough.

"Needs your attention"

This lists items that have used up all retries. The app tried for twelve hours, with growing gaps between attempts. None of them will retry on their own.

• A transfer to a store: the row shows the SKU, target store, change and cause. Fix the cause and click "Try again".
• An inventory update from a store: Shopify sent an update that couldn't be processed. Fix the cause and click "Process again". If the update came in a format the app doesn't recognize, contact support.

An inventory update stays here for 30 days. After that the app deletes it, even if you haven't processed it again. Anything still out of step by then is brought back in line by the next sync. A transfer stays until you try it again.

"One problem has lasted more than 30 minutes"

A store can't be reached, real-time sync is paused for a store or a SKU, or an item needs your attention, and it has been that way for over 30 minutes. Until it's fixed, inventory drifts apart. The individual notices above tell you what to do.

"Missed real-time changes"

A sync found differences even though real-time sync was on. Real-time sync missed these changes, and the sync has already caught them up. There's nothing to do. "View in activity log" shows which SKUs were affected.

"You're close to your plan's limit" and "More variants than your plan includes"

• You're close to your plan's limit: at least 80% of your plan's variants are in use. If more are added, you'll need the next plan. On the highest plan, it says "There is no higher plan." and "For more, contact us." instead.
• More variants than your plan includes: a connected store has more matched SKUs than its plan includes. The notice names the store and appears in every store of the group. Real-time sync that is already on keeps running. You can only turn it on again once that store is on the plan named there. Click "View … plan".
• If a store has more matched SKUs than the highest plan includes, the same notice doesn't name a plan. It says how many SKUs the highest plan includes, followed by "For more, contact us." The button then reads "View plans". You can only turn real-time sync on again once the number fits a plan.

"Skipped today because the linked location doesn't stock the item"

A target store doesn't track inventory for this item at the linked location. The app never activates a location by itself. "Which ones?" shows the affected rows in the activity log. If you want that location synced, turn on inventory tracking for it in the store, on the product under "Inventory".

Notices after a sync

• Stopped by the safety brake: too many SKUs would have dropped to 0 even though there's stock elsewhere. Nothing was written. Check whether one of the stores is empty or incomplete right now.
• … SKUs left out: real-time sync is paused: real-time sync is paused for these SKUs because the same change kept arriving with no order behind it (see above). The sync doesn't touch them until you've resumed them on the Overview page.
• … changes held back: these SKUs would have dropped to 0 even though another store has stock. The brake didn't write them. Check the SKUs listed.
• Stock is at locations that aren't connected: the other side is missing in the location link, but the stock exists at a location that isn't in any link. Link that location under "Settings" → "Locations" if it belongs.
• Inventory not tracked: in these stores, "Track quantity" is off for the SKU. Without tracked inventory there's no number to sync, not even 0. Turn on inventory tracking on the product under "Inventory" and set a quantity.
• … SKUs can't be synced: only one store tracks active inventory here. A sync needs two sides. Usually inventory tracking is off in the other store.
• Last sync failed: the message names the cause. If location links are missing, "Connect locations" takes you straight there. If Shopify just couldn't be reached or slowed down requests, the app retries a scheduled sync on its own and tells you when. A sync you started manually, you start again yourself (see "Real-time sync, syncs and the activity log", section "When a scheduled sync fails").
• The sync stopped responding: it probably stopped because of a restart. Start it again.

Other notices

• Matching needed (under "Settings" → "Locations"): a store has several locations. Decide which one belongs where.
• Real-time sync wasn't turned on (in "Settings"): the sync that runs before switching on failed or was stopped by the brake. The reason is shown with it.
• A code is still active (under "Settings" → "Stores"): this store already created an invite code. If you no longer have it, create a new one.
• No shared SKU found and The run stopped responding (on "Matching"): see "Matching variants".