UMUBARTAS.MEDIA

UM Multistore Sync

Keeps inventory in step across your Shopify stores and explains every number the app sets.

Coming soon to the Shopify App StoreThe app's privacy policy

← Back to help

Notices and what to do

Every notice the app shows, what it means and what you can do, even when the answer is nothing.

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.

"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.

"One problem has lasted more than 30 minutes"

A store can't be reached, real-time sync is paused, 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.
  • More variants than your plan includes: real-time sync that is already on keeps running. You can only turn it on again with the plan named there. Click "View … 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.
  • … 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 on the "Locations" page 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.
  • The sync stopped responding: it probably stopped because of a restart. Start it again.

Other notices

  • Matching needed (on "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 (on "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".