Short answer. Your stock does not match between webshop and warehouse because your ERP (AFAS, Exact, Business Central), your sales channels and your warehouse each maintain their own stock level that does not communicate in real time. Standard connectors and middleware bridge the ordinary case. The goal, a single source of truth with control, calls for a process that resolves conflicts and validates, not yet another interface.
Ask three people in your wholesale business about the stock of one item and you get three answers. The ERP says one thing, the webshop another, and in the warehouse there is yet something else.
That is not sloppiness. It is what happens when every system keeps part of the truth and no single system owns the whole.
Stock does not match between webshop and warehouse
The ERP keeps the administrative stock. The webshop shows what it thinks is there. The warehouse knows what is really on the shelf. As long as those three do not come together in real time, you are selling on figures that are already outdated the moment you see them.
The consequence is concrete. Two channels reserve the same item at the same time, and you sell something twice that you cannot deliver.
Why AFAS and Exact don't talk to your channels on their own
An ERP like AFAS or Exact is built to run your administration and logistics, not to connect automatically to your point of sale, your webshop and your marketplaces. That is why there is middleware in between, tools like StoreLinkr, IntegrationsMonkey or Monta, that shuffle stock back and forth.
That works for the ordinary case. Many wholesalers set a stock buffer per channel as well, so the webshop shows less than is physically there to dampen overselling. That is a patch on the symptom, not a fix for the cause: the source of truth is still fragmented.
False certainty instead of control
This is the treacherous part. You have reports, you have figures, you have screens full of data. It feels like control. But when every system keeps its own version, it is false certainty.
You don't know which source is leading. You don't know which order was shipped from where. And when something is off, the searching begins, not the intervening.
More bookkeeper than entrepreneur
So you retype. Orders from the supplier portal into the ERP. Stock corrections by hand. Bank transactions that you match to purchase invoices, often with a difference in amount that no one flags automatically.
That is how you become more bookkeeper than entrepreneur. Not because you want to, but because the work keeps falling between the systems and you are the only one who bridges it.
Where standard packages stop
The happy path is covered. AFAS, Exact and Business Central run your administration fine, and middleware connects the standard stock flow. The exceptions are not, and in a wholesale business those are the rule:
- The same purchase from multiple sources, at different prices and lead times.
- Stock across multiple locations, where you want to know which order shipped from where.
- Bank reconciliation where a difference between transaction and invoice slips through unnoticed.
This is the build-or-buy line. The question is not which tool, but which goal you want to reach: control and overview, figures that are correct, less manual work. That is why I go through your process thoroughly first, because some steps have grown organically and can be smarter. What remains, bringing your systems together into one source with validation and clear rules on which source wins, I build. That is exactly what a standard package does not do for your situation.
Frequently asked questions
How do I connect AFAS or Exact to my webshop?
Through a standard connector or middleware (such as StoreLinkr, IntegrationsMonkey or Monta) that synchronizes stock and orders between your ERP and your channels. That covers the standard flow. For multiple locations, multiple sources or deviating logic, you run into the limits.
Why doesn't my stock match between webshop and warehouse?
Because your ERP, your webshop and your warehouse each maintain their own stock level that does not come together in real time. Without one leading source you sell on outdated figures, with overselling as the result.
What is middleware and do I need it?
Middleware is a layer between your ERP and your channels that shuffles data back and forth because they do not connect natively. For the standard flow that is enough. It does not resolve which source is leading in a conflict, and that is precisely where control is missing.
When is an ERP connection enough and when do I need custom work?
With one structured flow and one stock location, a standard connector is enough. With multiple locations, multiple purchasing sources and bank reconciliation with differences, a dedicated process with validation is often the cheaper choice.
Further reading
- Tracking purchasing across multiple suppliers
- Matching bank transactions to purchase invoices
- Stock across multiple locations
I am Ricardo Theijs of RNT Projects. I ran cross-border trade for years myself, with purchasing across many suppliers and stock across multiple locations, with a background in enterprise process management. I build the systems where standard packages fall short, and I tell you honestly when that is not needed.
Running into this yourself?
I review your process and build the solution where a standard package falls short. Remote, with visible results in two weeks.
Let's talk