UM Multistore Sync

How matching works

The app reads the catalogs of all stores in the group and compares them by SKU. If a SKU appears in at least two stores, those variants belong together. When inventory later changes for one of them, the app knows where that change needs to go.

• Only the SKU counts. Product IDs, handles and titles play no part.
• Leading and trailing spaces and upper or lower case are ignored. sl-123 and SL-123 are the same SKU.
• Matching writes nothing. You see the result first.

Start matching

1. Open "Matching".
2. Click "Start matching". After the first run, the button reads "Update matching".
3. While the run is going, the page updates on its own and shows how many variants have been read. Depending on your catalog, this can take a few minutes.
4. Afterwards, "Result" shows how many SKUs were matched across how many variants, and how many variants are left without a match.

"Matched" lists the matched SKUs. Click a SKU to see its history in the activity log.

The reasons under "Not matched"

Every variant without a match is listed there with its store and the reason. Above the list you see how often each reason occurs.

• No SKU set. Without a SKU there is nothing to match. Add a SKU in the store and update matching.
• SKU used twice in the same store. Two variants in the same store share a SKU, so it's unclear which one counts. This SKU is deliberately not synced at all, not even in the other stores. Give one of the two variants its own SKU and update matching.
• No counterpart in the other store. This SKU only exists in one store. Either the product is missing in the other store, or the SKU is spelled differently there. If that's intended, there's nothing to do.

"No shared SKU found"

Both stores were read, but no SKU appears in both. The most common causes: the stores carry different items, the SKUs are spelled differently, or they aren't filled in at all. The "Not matched" table shows the reason for each variant.

If a run gets stuck or fails

• The run stopped responding. There has been no sign of life for several minutes, probably because of a restart. Nothing was written. Just start matching again.
• Last run failed. The message names the cause and, where needed, the next step. If Shopify couldn't deliver the full catalog, start again later.
• Matching is already running. Two runs can't happen at the same time. Wait for the current one to finish.

"Previous runs" shows the latest runs with their result and duration.

When to run matching again

Matching only runs when you start it. Run it again when:

• you've added new products or variants,
• you've changed or added SKUs,
• you've fixed one of the reasons under "Not matched".

Until then, real-time sync does nothing for a new SKU.

What matching means for your plan

Each matched SKU counts once, no matter how many stores it appears in. Unmatched variants don't count. There's more in the article "Plans and billing".