Stock Counts and Negative Inventory: A Fix-It Guide

Negative inventory is the system believing you sold more than you had, and it is the sneakiest error in multichannel selling: the item sits on the shelf while every channel says "sold out", or the reverse happens and you sell something you do not have. The lasting fix has two parts: regular stock counts that pull the record back to reality, and closing the source of the negative figure. This guide covers causes, count types, how to push count corrections to your channels, and a practical procedure.

Where negative inventory comes from

Negative stock is a symptom, not the disease. Resetting it to zero without finding the cause means the same problem returns a week later. The most common causes:

• Late goods receipt. Stock arrived, was shelved and sold, but the receipt was entered the next day. Units sold in between go negative.
• Returns not booked in. A return was accepted and shelved, but never recorded. The next sale finds "nothing".
• Overselling. The same last unit sold on two channels at the same time. Stock synchronisation and overselling explains the mechanism.
• Wrong barcode. The warehouse scanned black 40, the system deducted black 38. One goes negative, the other looks overstocked.
• Bundle and component confusion. A bundle sold and components were deducted twice, or not at all.
• Manual overrides. Someone typed a stock figure into the marketplace panel that contradicts the ERP.
• Shrinkage and damage. Broken or lost items were never written off and stayed "available" until the next count.

What negative inventory does to your channels

On a single store, a negative figure means one customer complaint. Across channels the effect multiplies. A single stock pool pushes a negative value to every channel as zero, and the product disappears from sale everywhere. If the item is really on the shelf, you lose sales; if it is not, you get cancellations and negative reviews. Some marketplaces lower seller ratings for repeated cancellations; N11 store score and order performance describes that effect.

There is also the ERP side. Negative stock can block invoicing or distort cost calculations. Finance ends up at month-end with a list of "minus stock" lines, each needing a manual explanation.

Count types: full, cycle and targeted

There are three types of count, and they are used together.

Full count

The entire warehouse counted in one go, usually at year end or after a move. Accurate but expensive: selling stops and the whole team is involved. It is never enough on its own; a week later the record starts drifting again.

Cycle count

A small section of the warehouse counted every day or week, so the whole warehouse is covered once per period. Fast-moving and high-return products are counted more often, slow movers less. For multichannel sellers this is the healthiest method.

Targeted count

Triggered by an event: a product going negative, dropping below its low-stock threshold, or showing a rising return rate. Counting the products that appear in the low stock and days-of-cover report catches variances before the product actually sells out.

Step-by-step count procedure

This list is written for cycle counts; for a full count the same steps apply to the whole warehouse.

1. Define the area and products. Zone, shelf or category. Products in negative stock join the list automatically.
2. Record the start time and system quantity. Freeze the pre-count figure; movements during the count are listed separately.
3. Count by scanning, not by eye. Scan every unit; never type quantities. Put unreadable barcodes on a separate list.
4. List the variances. System quantity, counted quantity, difference. Close lines with zero variance.
5. Have a second person recount large variances. A big difference counted by one person may be a counting error.
6. Write the cause of each variance. Late receipt, unbooked return, damage, wrong barcode. A variance without a cause repeats next month.
7. Correct in the ERP, not on the channel. The ERP is the source of truth; channels update from there.
8. Verify that the new stock reached every channel. After the correction, check that each channel shows the right quantity.
9. Close the source. If the cause was goods receipt, fix the receipt process; if it was returns, fix the returns step.

A variance is not a number, it is a question: "how did this happen?" Every variance left unanswered hides a gap in the procedure.

Pushing count corrections to your channels

Stock changed after the count; now that change has to reach the channels correctly. The frequent mistake is typing the variance straight into the marketplace panel. A week later the ERP and the channel disagree again, because the ERP still holds the old value.

The correct sequence: an adjustment document is posted in the ERP, the single stock pool reads the new value, and the channels receive it. If you run several warehouses, correct per warehouse; multi-warehouse stock management covers warehouse-level sync.

Products whose stock went up after the count return to sale; those that went down should trigger a low-stock alert. In both cases, do not call the count "done" until you have seen the update land on every channel.

Preventing negative inventory in the first place

Counting cures; prevention is cheaper. A few rules remove most negative stock:

• Goods are booked in before they are shelved. Shelving is the result of the record, not the other way round.
• Returns are accepted by barcode scan and only go back to the shelf after the entry is posted.
• Bundle-to-component relationships are defined in the ERP so a bundle sale deducts components automatically.
• Stock entry through marketplace panels is off limits; everyone works through the ERP or the integration panel.
• Shrinkage and damage are written off daily, not at month end.
• Any product that goes negative is added to a targeted count the same day.

How it works with Bulutegra

Bulutegra reads the single stock pool from your ERP and pushes it to more than 24 marketplaces. Products that go negative appear on the system health screen and in the low-stock alert, so you can add them to the count list. Users in the Warehouse role accept returns and run counts by scanning; a returned item does not re-enter sellable stock until it is recorded. After a count, the correction is made in the ERP, the panel reads the new value and sends it to every channel; channel monitoring runs continuously, so a channel that goes quiet raises an alert and a push notification on your phone.

The shadow mode phase of setup is especially useful here: for a week or two the system only reads and writes nothing, so you see the stock differences between ERP and channels before any write permission is granted. The ownership flag shows which system manages which channel, so manual overrides from an external system are caught at the source.

To see where negative inventory originates in your own warehouse, request a demo.