If stock already fails to reconcile, find the cause first: why stock levels never match.
The main decision: which warehouse level you need
Business Central does not have a single "warehouse module". It has several levels of warehouse process, and the choice between them is made once, per location, before implementation. Getting it wrong is the most expensive warehouse mistake, because moving between levels later means reconfiguring live processes.
There are three practical levels: single-step, two-step and three-step handling. They differ in how many documents stand between an order and the goods physically moving.
| Level | How it works | Who it suits |
|---|---|---|
| Single-step | Posting the sales or purchase order itself moves the stock. No separate warehouse documents | Small warehouses where one person both sells and ships |
| Two-step | Separate receipt and shipment documents. Warehouse staff work with their own paperwork, not with the order | Warehouses with dedicated staff and a few hundred lines a day |
| Three-step | Adds picks and put-aways with bin-level directions | Large warehouses with bins, zones and several teams working in parallel |
The rule that saves money. Start at the lowest level that covers your process today, not the one that looks most advanced. Every extra step is an extra document somebody has to create, and warehouses reject processes that slow them down.
What each additional level buys you
Moving to two-step separates commercial and physical work. Sales enters the order; the warehouse sees a shipment task. This matters as soon as different people do those two jobs, because it removes the situation where a salesperson accidentally posts a shipment that never left the building.
Moving to three-step adds directed movement. The system tells the picker which bin to take from and the put-away worker where to place goods. This only pays off when you genuinely have bins and enough volume that walking routes matter.
A common and sensible pattern: the main distribution centre runs three-step, while a small regional store runs single-step. Business Central allows different levels per location within the same company.
Storage structure: from location to bin
The storage hierarchy has three tiers, and each one should be introduced only when there is a reason.
- Location — a physical warehouse or store. Always required.
- Zone — an area within a location: receiving, bulk storage, picking, dispatch. Useful once the warehouse is large enough that areas have different rules.
- Bin — a specific shelf or position. This is where directed picking becomes possible.
Bins are frequently introduced too early. If a warehouse has 200 SKUs and two staff who know where everything is, bin-level tracking adds work without adding accuracy. The threshold is usually somewhere around the point where a new employee cannot find an item without asking.
Cross-docking and distribution warehouses
Cross-docking means goods arriving for a known outbound order bypass storage entirely and move straight from receiving to dispatch. Business Central can flag such lines at receipt.
It pays off in two situations: distribution businesses where a large share of inbound stock is already sold before it arrives, and any operation where storage space is the binding constraint. It does not pay off when inbound and outbound timing rarely align — the setup effort then exceeds the saving.
Replenishment planning: stockkeeping units
Once you have more than one location, item-level planning stops being enough. The same product can need different reorder points in Kyiv and in Lviv.
Stockkeeping units solve this: they hold planning parameters per item per location — reorder point, safety stock, lead time, replenishment method. The planning worksheet then produces suggestions per location rather than a single company-wide number.
Without them, one of two failures is guaranteed: either the central warehouse holds stock the regions need, or the regions over-order because nobody sees the group picture.
What to decide before implementation
- The process level for each location. Single, two or three-step — decided per site, not per company.
- Whether you need bins, and if so, the naming convention. Renaming bins later is painful.
- Who posts what. Which role creates receipts, which confirms picks, who is allowed to correct.
- How stock counts will run. Full counts, cycle counting by zone, or both.
- Lot and serial requirements. Driven by regulation or by warranty obligations — this cannot be retrofitted cheaply.
- Barcode scanning. Whether warehouse staff work from screens or handheld devices changes the interface design.
These six answers determine most of the implementation timeline for the warehouse area. Getting them written down before the project starts is the single most effective thing a client can do.
Warehouse processes in distribution.
Frequently asked questions
What is the difference between single-step and two-step warehouse handling?
With single-step handling, posting the sales or purchase order moves the stock directly. Two-step handling adds separate receipt and shipment documents, so warehouse staff work with their own paperwork instead of the commercial order.
When do we actually need bins?
When a new employee cannot find an item without asking a colleague. Below that threshold, bin-level tracking adds administrative work without improving accuracy.
What is cross-docking and when is it worth it?
Goods arriving against a known outbound order move straight from receiving to dispatch without being stored. It pays off in distribution businesses where much of the inbound stock is already sold, and wherever storage space is the binding constraint.
Can different warehouses run at different levels?
Yes. The process level is set per location, so a central distribution centre can run three-step handling while a small regional store stays on single-step.
How do we plan replenishment across several locations?
Through stockkeeping units, which hold planning parameters per item per location: reorder point, safety stock, lead time and replenishment method. The planning worksheet then produces suggestions per site.
How long does a warehouse implementation take?
The warehouse area typically adds several weeks to a project. The duration depends mostly on six decisions: process level, bin structure, roles, counting method, lot and serial requirements, and whether barcode scanning is used.