Skip to main content

Resolve a SKU or barcode conflict

A conflict is raised when a store sends an edit carrying a SKU or barcode that already belongs to a different Yessort variant.

The incoming value is not written. Yessort records the clash and leaves both variants as they were.

Why there is no "apply anyway"​

SKUs and barcodes are how Yessort matches stock and orders. Letting the most recent edit win would move an identifier off the variant legitimately holding it, and quietly break matching for everything already attached to it — stock, open orders, pick work.

So a conflict is not a proposal to accept or reject. It is two records claiming one identifier, and the fix is deciding which should have it.

Steps​

  1. Open the conflicts on the channel's page under Integrations.
  2. For each conflict, look at the incoming value, the listing it came from, and the Yessort variant already holding it.
  3. Work out which is right, using the guide below.
  4. Make the correction in whichever system is wrong.
  5. Mark the conflict resolved, or dismiss it if no action is needed.

Working out which is right​

The store is right, and the Yessort variant should not have this identifier. Someone typed it onto the wrong variant here. Correct the Yessort variant first — freeing the identifier — then let the store's next edit through, or set it yourself.

Yessort is right, and the store's listing is wrong. Someone put an existing SKU onto a new listing in Shopify, often by duplicating a product. Fix it in the store. The conflict stops recurring once the store stops sending it.

Both are meant to be the same product. Two listings for one thing. Decide which listing to keep, and unlist or archive the other in the store.

If the same conflict keeps appearing​

Repeated events refresh the existing record rather than stacking duplicates, so one row with current values is normal. It will keep re-opening until the underlying clash is fixed in one system or the other — dismissing it does not stop the store sending the value again.

Preventing them​

Most conflicts come from duplicating a product in Shopify and forgetting to change its SKU. They also become far more likely when Accept SKU changes from Shopify or Accept barcodes from Shopify are on, since Yessort is then being asked to take identifier edits from the store at all. Both are off by default — see inbound and outbound settings.