Inbound and outbound settings

These settings decide what a connected store is allowed to change in Yessort, and what Yessort derives when it pushes out. They are set per channel, on the channel's catalogue settings, and need organisation-admin access.

The defaults are deliberately uneven. Read the reason column before changing one — each default is the way it is for a specific reason, not by oversight.

Inbound — what the store may change

Setting	Default	What it does
Stage new Shopify products for review	On	A product the store has and Yessort does not is staged into the review queue. It is never created automatically. Turn off for a store that sits downstream of another system and should never propose anything.
Accept SKU changes from Shopify	Off	Lets a store edit write the SKU onto an already-linked variant.
Accept barcodes from Shopify	Off	The same, for barcode.
Accept price changes from Shopify	Off	The same, for price.
Mirror presentation fields	Off	Mirrors the store's product name, product description and variant title onto already-linked rows.
Sync vendor → brand	On	When importing a product, matches the store's vendor to a Yessort brand by name, creating one if there is no match. Turn off if you use the vendor field for something else.

Why staging is on but the field settings are off. They answer different questions. Staging governs whether the store may propose a product Yessort has never seen, and a proposal costs nothing — a person still decides. The field settings govern whether the store may overwrite a record Yessort already owns, which is not reversible in the same way. Yessort stays the sole authority on a linked variant unless you opt out, per field.

Turning on sync presentation changes behaviour immediately for a live channel. It governs only already-linked rows; unlinked products keep feeding the review queue regardless, because that is a separate path governed by staging.

The product image is not covered by any of these. When a newly linked product has no image in Yessort, the store's is copied across. That copy only fills an empty field and never replaces one, so it carries none of the overwrite risk these settings guard against. Gating it would mean newly linked products never picked up their cover image.

Outbound — what Yessort derives when pushing

Setting	Default	What it does
Derive taxable from tax category	Off	Sets the store's taxable switch from the variant's Yessort tax category — a rate above zero makes it taxable, zero-rated or out-of-scope makes it not — instead of sending the variant's own taxable field. Nothing flows back; the store's taxable value is never read.
Notify customer on fulfilment	Off	A dispatch from Yessort asks the store to email the customer its shipping confirmation, with the tracking numbers. Off means the fulfilment still posts, quietly. Applies only to dispatches Yessort initiates.

Why derive taxable is off when the other outbound behaviour is not. Turning it on re-asserts Yessort's tax categorisation across your whole catalogue at once. It is only safe once the categorisation it propagates is known to be right, so it is something you opt into after checking, not something you inherit.

Publishing

Setting	Default	What it does
Publish mode	Manual select	Whether a newly created variant is listed on this channel automatically (auto all) or only when you choose it (manual select).

A channel starts in manual select and stays there until you change it. Connecting a store does not alter it: onboarding decides which of the store's existing products you keep, which is a different question from what happens to variants you create later.

A choice you make for a single variant always outranks this setting. Unlisting a variant from a channel set to auto all keeps it unlisted — see how catalogue linking works.