How the review queue works
When a Shopify store has a product Yessort does not, that product is proposed, not created. It lands in the channel review queue and waits for a person.
This follows directly from who owns your product data. Letting a store create catalogue records on its own would make it a second source of truth, and duplicate variants are difficult to unpick once stock and orders have attached to them.
What puts something in the queue
A product created or updated in the store that Yessort has no link for. This is on by default, per channel; turn it off for a store that should never propose anything.
A catalogue sync, which re-reads the whole store and stages everything it finds that is not already linked.
Products you have already linked do not appear. The queue is about things Yessort does not yet recognise.
Where to find it
The queue has two entrances onto the same work. Under Catalogue in the workspace it shows every channel at once, which is how most people clear it. On a connection's own page under Integrations it shows just that store. Same rows, same decisions, different scope.
The decisions
Each staged variant gets one of these.
| Decision | What it does |
|---|---|
| Create | Makes a new Yessort product and variant, and links it to the listing |
| Link to existing | Attaches the listing to a variant you already have — no new record |
| Skip | Leaves it alone. Nothing is created and nothing is linked |
| Pending | No decision yet. Where every row starts |
Link to existing is the one that saves trouble. If the store lists something you already sell — usually visible because the SKU matches — linking joins the two rather than leaving you with the same product twice.
Yessort guesses, you decide
Yessort proposes a decision for rows it can judge confidently, mostly by matching SKUs and barcodes. These are guesses, and Yessort keeps them fresh: when the store edits a product, or you run a full sync, it re-examines its own suggestions and updates them.
It never touches a decision a person made. That distinction is load-bearing. Without it, a row you dismissed would come back the next time someone edited the product in Shopify, and re-syncing a catalogue would discard a whole channel's review work.
Conflicts are a separate queue
If the store sends an edit carrying a SKU or barcode that already belongs to a different Yessort variant, the edit is skipped and recorded as a conflict. It is not a proposal to accept or reject — it is a clash between two records that both claim one identifier.
There is deliberately no way to apply it anyway: identifiers are how Yessort matches stock and orders, so quietly moving one off the variant that holds it would break matching elsewhere. See resolve a SKU or barcode conflict.
Stock when a row is applied
Applying a create or link decision gives Yessort a link where it had none, so it checks the store's stock figure against its own. A small difference is booked automatically; a large one is held for review. What counts as small, and why the automatic booking exists at all, is in keeping stock in step.