Skip to main content
Where to find it: Main → Integrations → Sales Channels — Open in OTO ↗
Every storefront you sell on quotes a stock number. Sync is how those numbers come from one place instead of five, and it is the difference between a catalog that is roughly right and one that is right.

​
What it does

When stock changes for any reason — a sale on one channel, a return, a receipt, a count correction — OTO calculates the new availability and pushes it out to every connected channel. The merchant does not update anything anywhere. Synchronization is available for Salla, Zid, Shopify, WooCommerce and Magento.
The oversell that sync prevents is the expensive oneA stockout costs you a sale you never knew you had. An oversell costs you a sale you already took: a cancellation email, a refund, a marketplace metric, and a customer who now knows your stock numbers cannot be trusted. Multi-channel sellers do not oversell because they are careless — they oversell because the same unit was on sale in four places at once.

​
Setting it up

Sync is configured per channel, at Integrations → Sales Channels → the channel’s ⋯ menu → Inventory Sync Settings.
The Inventory Sync Settings form

Fig. 1 — One form per channel: what number to send, how often to send it, whether to send it at all, and which of your locations maps to which of theirs.

Inventory Sync is a per-channel switch, not a global oneThat matters during onboarding and during trouble. A new channel can be connected, configured and left with sync off until the catalog is aligned; a channel behaving badly can be isolated without touching the other four.It also means an unexplained stale stock figure has an obvious first thing to check.

​
Inventory Calculate Method — what number to send

The Inventory Calculate Method options

Fig. 2 — Two methods, each with a Magento-specific variant.

Min Inventory is where the figure from inventory tracking earns its keep: the buffer you set per SKU is held back from what the storefront sees, so the last few units exist only for you.
Why Magento has its own entriesMagento models stock differently from the other platforms, so the same intention — send everything, or hold back the safety buffer — has to be expressed to it in its own terms. The choice you are making is still one of the two; the Magento rows simply exist so that the integration does not have to guess.

​
Inventory Update Method — how often to send it

The Inventory Update Method options

Fig. 3 — Push each change as it happens, or batch them.

​
Multi-location and pickup locations

If you hold stock in more than one warehouse or branch, enable Multi-Location and fill in the Pickup Locations table beneath it. One row per location, added with Add New Row: This mapping is what makes a location-aware storefront work properly. Without it, a channel that offers pickup or per-store availability has no way to know which of your buildings its stock figure refers to — so it either shows a single pooled number, or it shows the wrong one per store.
Map the locations before you go live, not afterTurning multi-location on with the mapping half-finished is worse than leaving it off: the channel starts attributing stock to locations that do not correspond to yours, and the resulting discrepancies look like sync failures rather than configuration.

​
Checking that it worked

Sync activity is logged at Settings → Logs → System Logs, on the Inventory Sync Logs tab — one of six log tabs alongside shipment errors, webhook errors, pickup requests, product sync and route automation.
The Inventory Sync Logs tab

Fig. 4 — Every column filters, which is what makes this usable as an investigation tool rather than a wall of entries.

A failed sync is a silent problem — the channel keeps selling against the last number it was given — so this log is worth a scheduled look rather than a look when something goes wrong.
Filter on quantity, not on statusStatus tells you what failed. The QTY range tells you something more useful: filter to a maximum of zero and you have every SKU that was pushed out as unavailable. Some of those will be genuine; the ones that are not are your stockouts that never were, and they will not appear as errors anywhere.

​
Catalog comparison

Stock sync only works for products the two systems agree exist. Synchronize Products, on the Products page, pulls product information from your connected channels so that SKUs, names and prices line up on both sides. This is the unglamorous prerequisite for everything else on this page. A SKU that is listed on a channel but absent from OTO gets no stock updates at all, and it will go on selling from whatever number it had when it was set up. Comparing the catalogs is how you find those before a customer does.
Run the comparison after every channel changeNew listings, renamed SKUs and merged variants all break the link quietly. The listings that stop syncing are rarely the ones anyone is watching — which is precisely why they are the ones that oversell.