Why Multi-Channel Sellers Still Oversell
Five reasons sellers oversell across channels even with software in place, what one oversell costs, and five questions to ask your tool.
Multi-channel sellers oversell for five reasons, and having an integration doesn't rule out any of them: stock that syncs on a timer, retailers that take inventory once a day, updates that fail without anyone noticing, returns that restock one channel and not the others, and marketplaces that process a correct update late. Each one sells a unit you no longer have. Each one ends the same way: an unhappy buyer, someone on your team hunting for stock, and eventually a cancellation that counts against your account.
What does one oversell actually cost?
Mostly time, and it's hard to put a number on. Someone has to notice the order can't ship, try to find the unit somewhere else, contact the buyer, and if nothing turns up, cancel. The buyer is unhappy either way.
The cancellation is the part with a hard number. Amazon asks sellers to keep the cancellation rate on seller-fulfilled orders under 2.5% over any 7 days, and says a rate above that can get seller-fulfilled offers deactivated. Walmart's seller performance standards set the cancel rate below 2%. On a slow week, a handful of oversells is enough to cross the line.
The five reasons sellers oversell
| Cause | What happens | What to check |
|---|---|---|
| Sync on a timer | Stock goes out every few minutes or hours. A unit that sells in the gap is still for sale everywhere else. | How long between a sale and every other channel updating? |
| Once-a-day EDI feeds | Retail drop-ship programs often take inventory through an EDI 846 file on a fixed schedule. Between files, the retailer is selling yesterday's count. | How often does each retailer get a new inventory file? |
| Failed updates nobody sees | An update is rejected, times out, or hits the marketplace's rate limit. The old quantity stays live and nothing tells you. | Does a failed update alert anyone, or just sit in a log? |
| Returns and cancellations | A return or cancellation puts a unit back on the channel it came from, and the other channels never hear about it, or hear about it wrong. | Does a return update every channel, or just one? |
| The marketplace is late | Your software sends the right number on time, and the marketplace takes a while to apply it. The listing stays buyable in the meantime. | Can your software show what it sent, and when? |
"The marketplace processed it late" is an explanation, not a fix
When an order oversells, it's tempting to blame the fifth reason: Amazon was slow, the retailer was slow, nothing anyone could do. Marketplaces do apply updates late sometimes. But that's a known condition, not bad luck, and software that sells on marketplaces all day has to be built around it. If the answer to every oversell is "the marketplace was late," the integration isn't handling the one condition it should expect most.
How to tell if your setup is exposed
Five questions to put to whatever runs your inventory today:
- When an order comes in on one channel, how long until every other channel shows the new quantity?
- How often does each retailer on EDI get a new inventory file?
- When an update fails, who finds out, and how fast?
- When a return is restocked, which channels get the new count?
- For an order that oversold, can you see exactly what quantity was sent to that marketplace, and when?
If the answer to the last one is no, every oversell becomes an argument between you and your software, with no record to settle it.
How Rilk handles it
Rilk keeps one stock count per product, not a separate count per channel. When an order lands from any connected channel, that count drops and the new quantity goes out to every other listing of the product. The same happens when you receive stock, ship, move stock between bins or process a return. Every stock update Rilk queues for a marketplace is logged: the quantity, the time and what triggered it, so an oversell can be traced to the minute.
We don't publish the mechanics, but Rilk is designed around marketplaces that apply updates late, instead of treating a late update as bad luck. The simplest way to judge it is on your own channels. More on how the sync works: multi-channel inventory sync. If you sell on Amazon, the Amazon inventory guide covers the Amazon side in more detail.
Start free at rilk.ai — no credit card required. Inventory sync across channels is on Pro and Ultimate, and every account gets one 14-day Pro trial to run it on your own orders. See plans.
About the author
Nouri Shaaya
CEO, Rilk
Nouri Shaaya is the CEO of Rilk. He has been selling online since 2013, running a multi-channel operation across Amazon, Walmart, eBay and retail drop-ship, with sales approaching $40 million a year.
More from NouriReady to simplify your operations?
See how Rilk replaces your spreadsheets and duct-taped tool stack with one platform built by sellers, for sellers.
