E-commerce & webshops

You sold the same last unit twice, and that is an integration problem

Stock that does not match across bol, Amazon and your own shop leads to overselling. Why manual inventory management breaks at the second channel, and what a real solution requires.

By Ricardo TheijsMarch 4, 20264 min read

Short answer. Stock does not match across multiple channels because each channel keeps its own count and those counts do not communicate with each other in real time. The solution is one central inventory source that updates every channel at the same time with each sale. A CSV export or a manual adjustment is not synchronisation, and it breaks the moment you sell on two channels at once.

A customer orders a product on bol. Your own shop already sold that same last unit an hour ago. Now you have two customers and one product, and you have to disappoint one of them.

This is called overselling. It feels like bad luck, but it is not. It is a missing connection between your channels.

Why your stock never matches

Every sales channel keeps its own stock count. Your own shop, bol, Amazon, the till in the store. As long as those counts do not talk to each other in real time, each channel sells as if it were the only one.

One business owner put it like this: "Manual inventory management falls short the moment you sell on two or more channels at the same time." And in Excel it is even sharper: "Online orders from platforms do not lower your stock automatically in Excel, every update requires manual work."

That is the core of it. One forgotten update and your inventory records are off for the rest of the week.

Why Excel and CSV are not enough

Stock in Excel works fine, until the second channel. After that you are updating all day, and every time you forget, a gap appears.

A CSV export that you run a few times a day is not synchronisation. Between two exports, each channel keeps selling on outdated numbers. With fast-moving products that is exactly long enough to sell the same unit twice.

What a real solution requires

One central source that holds the truth, and that updates every channel in real time with each sale. When bol sells a unit, the count on your own shop and in the store drops along with it immediately.

For most webshops a standard inventory synchronisation tool covers this. If you sell on a few channels with simple products, pick a tool like that and build nothing yourself.

It becomes different the moment your situation deviates:

  • Stock across multiple locations, where you want to know which order ships from where.
  • Bundles and sets, where selling one product affects the stock of another.
  • Purchasing that arrives just in time, where you want to match what is on its way to what a customer has ordered.

Then these are decisions, not simple counts. Which stock do you reserve, for which channel, in what order. Those rules are yours, and a standard tool does not know them.

Frequently asked questions

How do I sync my stock between bol and my webshop?

With one central inventory source that updates all channels with each sale. Sync tools like ChannelDock or Channable usually do this every 5 to 15 minutes. With multiple locations or bundles you often need more than a standard tool.

Do I get a penalty for overselling on bol?

Yes. With overselling you have to cancel orders, and bol counts that as cancellations. Repeated overselling can lead to a lower performance score and even suspension of your seller account. That is why reliable synchronisation is not a luxury.

Which inventory management software works with bol, Shopify and multiple channels?

Tools like ChannelDock, Picqer and Stockitup sync stock across bol, Shopify, WooCommerce and Amazon from one central count. For standard products a tool like that is enough. With multiple locations, bundles or just-in-time purchasing you run into the limits and a tailored process is often needed.

Further reading


I am Ricardo Theijs of RNT Projects. I ran cross-border e-commerce myself for years and I build inventory and order systems where standard tools fall short.

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