The webshop shows three in stock, and the shelf in the warehouse is empty. Or the other way round: the product is sitting right there, but online it shows as sold out. See that happen a few times a month and it is tempting to think the work is sloppy. Usually, that is not what is going on.
The mismatch almost always sits between systems, not between people. Your webshop, your warehouse software and your till or ERP each keep their own stock count. As long as those records do not talk to each other automatically, they drift apart. The question is not whether that happens, but how fast.
Every manual step is a chance for things to diverge
In many organisations, the link between webshop and warehouse is in practice one person with two screens open. They type sales from one system into the other, usually at the end of the day, sometimes not until the next morning. That task is the first thing to slip when it gets busy, and busy is exactly when stock moves fastest.
Input errors pile on top of that. A wrong item number or a transposed quantity only comes to light once a customer orders something that is not actually there. Manual data transfer between systems is therefore not just slow, but a source of errors that hides itself.
A nightly sync is by definition behind
Where systems are linked, they often exchange counts in batches: once a night, or once an hour. That sounds orderly, but between two updates the webshop and the warehouse each live in their own version of reality. Sell the last unit through two channels at once inside that window, and one of your two customers ends up with a problem.
It bites hardest exactly when it matters most. A campaign, a seasonal peak, a product that suddenly takes off: the moments when the batch runs late are the same moments when cancellations cost the most.
Returns and corrections are the quiet disruptors
Beyond sales, there are movements that slip out of view just as easily. A return accepted in the warehouse but never added back to stock online. A damaged item pulled from sale. A delivery booked in while the webshop still knows nothing about it. Each movement is small on its own; together they decide whether your figures add up.
The underlying cause is almost always the same: nobody has decided which system leads. When three systems each keep their own stock count without an agreed source, every difference turns into a discussion and every count is just a snapshot.
How to bring the numbers back in line
The fix rarely means replacing everything with one all-encompassing package. It means making the systems you already have share the same reality. That takes three ingredients:
- One leading system. Decide where the stock level officially lives, usually your warehouse software or ERP. Every other system follows that source.
- A link that passes on movements directly. Through the APIs of your webshop and warehouse software, sales, returns and deliveries are processed within seconds instead of waiting for the night batch.
- Monitoring for differences. An automatic check compares the counts and raises a flag the moment they diverge, so you spot a mistake before your customer does.
What is realistic depends on your software. Most modern webshop platforms and warehouse packages have workable APIs; older systems sometimes need a middle layer to handle the translation. That is worth working out in advance, before you are committed to anything.
If your stock keeps drifting out of step, do not start with the technology but with the overview: which systems keep a count, what movements happen, and where does the mismatch begin. With that laid out, a link can be developed with a clear aim. You can read how we approach that, from first analysis to ongoing management, on our data integrations service page.