Stock across multiple locations: do you still know which order shipped from where?

Short answer. Stock across multiple locations only adds up once a single source per location tracks the count and decides which location reserves and ships an order. ERP systems like AFAS support multi-location stock, but the reservation logic (which location ships which order, and in what order) is a decision that follows your situation. A stock buffer per channel mutes the symptom, but it does not solve the cause.

With one warehouse, stock is a number. With multiple locations it is a question: how much is where, and who ships this order?

If you do not answer that question in your system, you answer it in your head. And then it never quite adds up.

Why multiple locations break your stock

Every location has its own stock position. ERP systems like AFAS support that, with stock per branch. But adding those positions up into one reliable picture, and assigning an order to the right location, is where it goes wrong.

An order comes in. Which location ships it? The nearest one, the location with the most stock, or the location that already has a shipment heading to that region? That is a decision, and without a rule it comes out differently every time.

The buffer per channel is a band-aid

The common solution is a stock buffer per channel, so your webshop shows less than what is physically there. That mutes overselling, but it costs you sales, because you are hiding stock that does exist. And it does not solve the core: you still do not know which location reserves what.

Which order shipped from where?

If you have to reconstruct that after the fact, your system is missing the reservation logic. You want to know at the moment of ordering which location reserves, so the stock there drops right away and no second order claims the same item.

This touches your purchasing and your margin too. An order shipped from the wrong location costs extra freight. If you do not trace that back, it disappears into a general cost pot instead of into the margin of that order.

What this requires

The goal is control over your stock across locations, with less manual work and figures that add up. That is why I first go through your stock and order process, because some location rules have just grown that way and can be smarter. What remains, one source that brings the counts per location together and the reservation logic that follows your rules, I build. This has to be sorted one way or another. The question is whether it can be done smarter today than with separate counts and a buffer.