Short answer: Overselling happens when the same stock is listed on several marketplaces and two of them sell the last unit before the quantities are updated. The fix is one stock record that every channel reads from, a small safety buffer on fast or low-stock items, and a daily routine that catches mismatches before they turn into cancellations.
Why overselling hurts more than one lost sale
When you cannot ship an order, you usually have to cancel it. On Amazon, seller-cancelled orders count towards the cancellation rate in Account Health, and Walmart and Temu also track cancellations and fulfilment performance for their sellers. One cancellation is a lost sale; a pattern of them puts each account at risk separately. Our guide to Amazon account health metrics explains how Amazon measures this. Check each marketplace's own seller help pages for its current targets.
Why it happens
- Separate stock counts per marketplace. Each channel shows its own quantity, and someone updates them by hand from a spreadsheet.
- Delays between a sale and the update. Two orders arrive on two channels in the same window, both for the last unit.
- Stock that is not really available. Units that are damaged, reserved for another order, or still with the supplier are counted as sellable.
- Receiving not recorded. Goods arrive, but counts are not updated, so the next correction is a guess.
- Bundles and variations. A single unit sold inside a bundle or under a different variation is not deducted everywhere.
- Returns put back too early. A returned unit is listed again before anyone has checked that it can be resold.
A process that prevents it
Keep one stock record. Decide on one place that holds the real quantity for every SKU, and make every marketplace listing follow it. Never adjust quantities directly on one channel and forget the others.
Count only sellable stock. Separate units that are available from units that are reserved, damaged, in transit or waiting for inspection.
Use safety buffers. For fast sellers and items with only a few units left, list slightly fewer units than you hold, so that two near-simultaneous orders do not both land on the last one. Remove the buffer for slow items with deep stock.
Record receiving the moment goods arrive. Count against the purchase order, note shortages, then release the stock to sale. Our Amazon FBM fulfilment workflow shows where receiving fits.
Map SKUs carefully. The same product often has a different SKU or listing ID on each marketplace. Keep one mapping table and check it whenever you add a listing, bundle or variation.
Run a short daily check. Compare the stock record with each marketplace's listed quantities, look at yesterday's cancellations and find out why each one happened.
Plan for peaks. During sales events and Q4, increase buffers and check stock more often. See the Amazon FBM Q4 peak checklist.
When the spreadsheet stops working
A spreadsheet can work for a handful of SKUs on one or two channels. Once you have hundreds of SKUs, several marketplaces and more than one person updating stock, manual updates are where overselling starts. Our guide to Amazon FBM operations without spreadsheets covers what to look for in a system.
How ECOMHUTSY helps
HutsyBoard, our operations software, works with Amazon, Walmart and Temu, bringing orders, purchasing, receiving, inventory and shipping into one workspace, so your team works from one stock record instead of separate spreadsheets. If you would rather hand the work over, our Amazon automation and Walmart automation teams run multichannel operations day to day. Every engagement is scoped after a short consultation. Talk to our team.
Each marketplace sets its own performance policies and targets. Follow the current rules in each seller account.
