Why is my stock count always wrong, and how does an ERP fix it?
Stock counts drift because movements go unrecorded. Learn the usual causes in D2C warehouses and how an ERP and simple routines keep counts accurate.
Anadoris Digital · · 4 min read

When the system says forty units and the shelf holds thirty-two, the gap rarely comes from theft or a single big error. It builds up from many small movements that nobody recorded. A free sample for an influencer, a damaged bottle thrown away, a return that is still in its courier bag, a receipt from the manufacturer typed in two days late.
Software alone does not close that gap. What closes it is a rule that stock only moves with a transaction, and a system that makes recording the transaction quicker than skipping it.
The usual causes of stock drift
- Returns and RTO parcels received but not inspected and added back.
- Damaged, leaking or expired units discarded without a write-off entry.
- Samples, gifting and influencer units taken from saleable stock.
- Goods received from the manufacturer entered late, or entered as ordered rather than as counted.
- Wrong SKU picked for an order because two products look alike.
- Combo packs assembled by hand without the system reducing component stock.
- Stock edited directly on a channel and never reflected in the main record.
How an ERP changes the picture
In an ERP every change to stock is a document: a goods receipt, a delivery, a return, a transfer, an adjustment. Each one carries a date, a user and a reason. That gives you an audit trail, so when a count is off you can see which movements happened since the last good count and narrow the search.
Good ERPs also stop the most common errors at the source. Goods can only be received against a purchase order, so the quantity is checked against what was ordered. Adjustments need a reason code and, above a set size, an approval. Kits reduce components automatically. Picking by barcode scan blocks the wrong SKU from being packed.
Cycle counting instead of yearly stock-takes
A full stock-take once a year tells you how wrong you were, not why. Cycle counting means counting a small set of SKUs every day or week so that every item is counted several times a year. Fast movers and high-value items are counted more often.
Because each count is small, differences are found while the cause is still fresh. Someone can remember the damaged carton from last Tuesday. That memory is gone by year end.
A stock accuracy checklist
- Every SKU and every shelf location has a barcode label.
- No goods leave the warehouse without a scanned order, transfer or issue note.
- Returns are processed within a fixed time and graded as resaleable, refurbish or scrap.
- Samples and gifting come from a separate location, not saleable stock.
- Write-offs need a reason code and a photo.
- Receipts are entered on the day goods arrive, against the purchase order.
- A short cycle count runs on a set schedule, with variances investigated the same day.
Measure accuracy so you know it is improving
Track the share of counted SKUs whose system quantity matched the shelf, and the value of adjustments each month. Watch the trend rather than a single month. If adjustments keep coming from the same cause, such as returns, fix that process rather than counting harder.
A sudden large variance on one SKU often points to a mapping or unit-of-measure error, for example a case of twelve entered as one unit, rather than physical loss. Check the transaction history before assuming shrinkage.
Make the right action the easy action
Warehouse staff skip recording steps when those steps are slow. If logging a damaged unit means walking to a desktop, finding a menu and typing a reason, it will not happen during a busy dispatch window. Put the most common actions on a phone or handheld scanner: scan item, choose reason, take photo, done.
Set up the ERP so that the shortest path is also the correct one. Pre-filled reason codes, default locations for returns and one-tap receipt against an open purchase order all reduce the temptation to fix it later. Later usually means never.
Share accuracy results with the warehouse team every week. People take more care with counts they know will be checked and discussed, and they often spot process problems that the founder cannot see from the dashboard.
Finally, treat the opening balance as a one-time event done properly. A rushed opening count on go-live day carries every existing error into the new system, and the team will blame the ERP for numbers it inherited.
Where to start
- Do one full physical count and load it as the opening balance on a fixed date.
- Create separate locations for returns awaiting inspection, damaged stock and samples.
- Introduce reason codes for every adjustment.
- Start a weekly cycle count of your top-selling SKUs.
- Review variances every week for the first two months and fix the process behind each one.
If you need help designing these routines inside an ERP, Anadoris Digital can set up the locations, reason codes and scanning flow around how your warehouse already works.
Related service: ERP Solutions · More on this topic: ERP Solutions articles
