One pile of stock. Four places selling it.
The units are in one building. Your own storefront is selling them, and so are two or three marketplaces, each with its own idea of what a quantity means and its own delay before it hears about a sale. The question is not whether to sell on marketplaces. It is what number each one is allowed to see, and who decided.
Four things sellers say once the second channel is live
One channel has no coordination problem. The second one creates it, and every channel after that multiplies it, because each new place to sell is another place to be wrong.
"It oversold again."
Two buyers were told yes for the same unit, on two different channels, inside the window between the first sale and the update reaching the second channel. Nobody did anything wrong.
"The numbers never match."
Four systems, four totals, and no agreement on what is being counted — whether committed units are in, whether stock still on a truck is in, whether a held-back buffer is in.
"Why is that listing showing three?"
Because a per-marketplace cap nobody remembers setting is lower than the stock you have, and the listing is quietly showing the smaller of the two numbers.
"Which channel gets the last one?"
Whichever one happens to sell it first, unless somebody has decided otherwise. On the last unit of a best-seller, "whoever is fastest" is a strategy by default rather than by choice.
What each channel does to the number before a buyer sees it
None of these is a bug. They are documented behaviours, and they are the reason four correct systems can still disagree.
One
"In stock" is several different buckets
Shopify's On hand is the total of Committed, Unavailable and Available, and only Available is "inventory that you can sell". Incoming is excluded until it is received.
Two
A listing may show the lower of two numbers
eBay holds a ship-to-home quantity that is the total "available for sale across all marketplaces", and "the quantity specified on a listing will be the minimum value between this field and the availableQuantity field".
Three
Quantity may be held per location, not per company
Walmart models inventory against ship nodes — "a physical location (for example, a warehouse) where you store inventory or ship orders" — with quantity kept by SKU and ship node.
Four
An update is not instant
Walmart's documentation names lag time directly: "the delay between when an inventory change occurs and when that change is reflected as available for sale".
Platform behaviours quoted from each platform's own published documentation, September 2026. Platforms change these models — verify before you design around them.
Where OmniOrders fits
OmniOrders is an order management system for brands and retailers selling through many channels. Orders from the channels you connect arrive in one place, against one catalogue, so the questions on this page stop being answered separately in four admin panels.
OmniOrders also publishes an API at omniorders.com/api, so external tools can read order data — useful when the reporting you need does not exist in any single channel's dashboard, which is most cross-channel reporting.
And the boundary, honestly stated, because it is the part a demo should cover rather than a web page: what each marketplace will display, how quickly it accepts a change, and what caps it applies are that marketplace's rules. No order system removes them. What a system can do is give you one place to decide what each channel is told, instead of four places to be surprised.
omniorders.com/integrations lists 137 integrations across sales channels, fulfillment, shipping and ERP or accounting — including Shopify, Amazon, eBay and Walmart.
The question no platform answers for you
Every mechanic above is about how a number is stored and displayed. None of them decides how much of a scarce unit each channel should be allowed to sell. That is a commercial decision, and it is yours.
It usually comes down to four things: which channel earns the most on that unit after fees, which one costs the most when you cancel, which one punishes you hardest for being wrong, and which one you are trying to grow this quarter. Those rarely point the same way, which is why "sell everything everywhere and see what happens" survives so long — it avoids the argument rather than settling it.
Write the answer down before you connect anything. A rule you can state is a rule you can change on purpose; a rule that emerged from whichever integration was configured first is one nobody can explain when it costs you a listing.
Three questions this page does not answer
The answers depend on which channels you run and how your stock is held, not on anything we can put on a web page. Bring them to a demo and make us answer them about your setup.
-
How fast does a sale on one channel reach the others?
Ask for the real interval under load, not the best case, and ask what happens to the orders that land inside it.
-
Which buckets does each channel get to see?
Committed, unavailable, incoming and safety stock each have to be in or out per channel. Ask to be shown where that is configured and who can change it.
-
What happens on the last unit?
Not the happy path. The contested one: two channels, one unit, both live. Ask to see that walked through end to end.
What changes when the channels read from one number
A number per channel
- Every channel holds its own number, set by hand or by a different app
- A sale on one channel is visible to the others minutes or hours later
- Nobody can say which channel caused an oversell after the fact
- A per-marketplace cap set once is still silently limiting a listing
- Incoming stock is counted as sellable on some channels and not others
One position behind every channel
- One position per unit, with every channel reading from it
- A sale anywhere changes the number everywhere it is published
- What each channel may sell is a stated rule, not an accident
- Caps and buffers are deliberate, written down and reviewed
- Incoming stock is excluded until it is actually received
Questions about selling the same stock on more than one marketplace
Because some platforms take the lower of two numbers rather than the one you last typed. eBay's documentation is explicit about it: the ship-to-home quantity is the total "available for sale across all marketplaces", and "the quantity specified on a listing will be the minimum value between this field and the availableQuantity field" on the offer. A per-marketplace cap you set months ago can quietly hold a listing down.
Partly because an update is not instant. Walmart's inventory documentation describes lag time as "the delay between when an inventory change occurs and when that change is reflected as available for sale". Between the sale and the update landing on every channel there is a window where more than one buyer can be told yes, and the more channels you run, the more often that window is occupied.
Almost never the raw shelf count. Shopify's model is a useful way to think about it: On hand is the total of Committed, Unavailable and Available, and only Available is "inventory that you can sell" — Incoming is excluded until it is received. Deciding what each channel sees is a policy choice about which of those buckets the channel is entitled to, made before anything is connected.
Not necessarily, but some marketplaces model locations whether you do or not. Walmart works in ship nodes — "a physical location (for example, a warehouse) where you store inventory or ship orders" — and quantity is held per node rather than as one global pool. Whether your own operation mirrors that structure or flattens it is a decision to make deliberately rather than discover.
See it against your own channel list
Connect the channels you already sell on and work from one catalogue and one set of orders. Start with a free trial, or read how multichannel inventory actually breaks and what happens when three channels want the same unit.
Or go straight to inventory management.