What Yessort sends to a channel
Everything here travels one way. Yessort holds the authoritative record and instructs the store — see who owns your product data.
Listings
| Sent | When | Value comes from |
|---|---|---|
| The listing itself | A variant is published to the channel | The Yessort product and variant |
| Price | On publish, and when the price changes | The channel's default price list, at the unit of measure on the link |
| Barcode | On publish | The barcode for that unit of measure |
| Taxable | On publish, only if the channel derives it | The variant's tax category — a rate above zero is taxable |
| Archive | A variant or product is taken off sale | See unlisting and relisting |
Which variants are published at all depends on the channel's publish mode and any per-variant choice — see how catalogue linking works.
Customer-account and customer-group price overrides are not published. They are worked out when an order arrives, not when a price is pushed, so the storefront shows the channel's price list and the order carries the customer's.
Stock
| Sent | When | Value |
|---|---|---|
| Availability, per variant per store location | On a change to the stock behind it, and on a regular sweep | Your stock at the Yessort site mapped to that location, plus supply a counterpart has published to you, floored at zero |
Nothing is sent to a location you marked ignored, to one the store has deactivated, or to one Yessort has discovered but you have not yet mapped.
The figure includes partner supply. Your Available in the app does not — see what "Available" means, where for all three figures side by side.
Because the figure is floored at zero, a shortfall is not visible on the storefront. See how negative stock happens.
Fulfilments
| Sent | When | Notes |
|---|---|---|
| The fulfilment, with per-box tracking numbers | You dispatch in Yessort | Posted whether or not the customer is emailed |
| A request for the store to email the customer | The same, only if the channel is set to notify | Off by default. Applies only to dispatches Yessort initiates |
A dispatch the store reports to Yessort is not pushed back to it.
Catalogue reads
Not a push, but outbound traffic worth knowing about: a catalogue sync asks the store for a full export of its products. A store runs one export at a time, which is why a sync and a weekly drift check can contend for the same slot — see reconcile and drift statuses.