Behind marketplace overselling: where stock data usually breaks

The platform says 40 are available, a dozen orders come in, and the warehouse finds only 25 on the shelf. The remaining orders have to be cancelled. The first reaction is often "the platform synced too slowly", so people keep editing the stock figure by hand, and the overselling returns. Overselling is rarely a single fault. It almost always means one link in the chain of stock data has broken. Following the chain link by link works far better than changing the number again.

First, how does the number reach the platform?

A sellable quantity travels from the shelf to the product page through several stops:

1. How many pieces are physically on the shelf.
2. How many the books (1C, Excel or an ERP) show, minus anything already reserved.
3. How many the platform back office shows, and whether that figure is typed in, uploaded from a spreadsheet or synced automatically.
4. Whether the same stock is also being sold elsewhere, such as in a Telegram group or at a market counter.

If any stop holds a figure that is more optimistic than the one before, you oversell. Platforms update in different ways, so find out which one you use and how often it refreshes before digging further.

If the platform quantity is updated by uploading a stock sheet, each upload is only a snapshot. Between one upload and the next, sales you make through other channels are invisible to the platform. The longer the interval, the wider the window for overselling.

Six common break points

• Returns counted before they are shelved. The parcel arrives and the quantity goes straight back to sellable, though nobody has inspected it.
• Duplicate codes. One product has two SKUs, the stock sits under one, and the other listing keeps taking orders.
• Transfers not booked. For goods sent to a marketplace warehouse, some businesses book the receiving side at dispatch and others at acceptance. During the days in transit, both sides are wrong.
• Picked but not dispatched. The goods have left the shelf, the order has not been shipped, and the books still show them as available.
• Offline channels not recorded. Sales closed in Telegram or at a market counter are not deducted from the same stock.
• Bundles and single items. A set made of three single items is sold, and the stock of the three is not reduced.

The order of investigation

Start where it hurts rather than checking every product:

1. List the 20 SKUs with the most cancellations in the last month.
2. Give each SKU one row with four columns: shelf count, books, platform figure, in transit.
3. Against the six break points, mark the most likely cause on each row.
4. Group the rows by cause and fix each group together.

Suppose a Bluetooth earbud shows 40 on the platform and 40 in the books, but 25 on the shelf. Checking the missing 15 shows that 9 were sold in a Telegram group and noted only in the chat, 4 sit in the returns area uninspected, and 2 belong to a bundle that was sold without reducing its components. Three causes need three different fixes. Simply changing the platform figure to 25 would bring the same problem back next week.

Add a buffer first, repair slowly

While the causes are being traced, you can set a temporary buffer on the fastest sellers, so the platform shows the sellable quantity minus 2 or 3 pieces. This is a stopgap, not a cure. It buys time to repair each break point, and the buffer should shrink as the data improves.

Keeping it from coming back

• Give returns clear statuses, and add to sellable stock only at "ready to shelve".
• One code per SKU, with duplicates merged first.
• Open a transfer document at dispatch and record goods in transit separately.
• Register orders from every channel against the same stock, even ones agreed in a chat.
• Each week, compare shelf count and platform quantity for the 20 best-selling SKUs.
• Name one person who owns "platform quantity matches the shelf" and leads the search for causes, so the problem does not bounce between customer service, the warehouse and operations.

Overselling is a symptom of stock data quality, and it is cured with data, not with the platform. InventoryHub's e-commerce SKU reconciliation puts back-office stock, ERP records and physical stock in one table, to find SKUs with an oversell risk, returns not yet shelved and items sitting in the wrong bin.