Warehouse Management in Business Central

Warehouse management is the part of Business Central where people either fall in love with the system or start quietly cursing it, and the deciding factor is almost never the software. It is whether the warehouse level they configured matches the way their warehouse actually runs. Business Central offers a spectrum of warehousing that stretches from a single field on a stock movement all the way up to fully directed, document-driven, zone-and-bin operations with handheld scanning. That spectrum is a strength, because it lets a two-person stockroom and a multi-shift distribution centre run on the same product. It is also a trap, because the same flexibility means you can easily configure a warehouse that is far heavier or far lighter than your operation needs. This guide walks the whole spectrum and gives you the judgement to place yourself correctly on it.

The message up front: basic versus advanced warehousing is not a maturity ladder you climb. It is a matching exercise. Advanced warehousing gives you control, traceability and directed workflows, at the cost of more documents, more discipline and more training. Basic warehousing gives you speed and simplicity, at the cost of less control. The right answer is the level that fits your volume, your accuracy requirements and your team, and for most companies that is lighter than the software will happily let you configure.

1. Basic versus advanced warehousing: the decision that shapes everything

Everything else in this guide flows from one setup decision, so it belongs first. In Business Central, a location can operate at several distinct levels of warehousing sophistication, and the level is controlled by a handful of settings on the location card. At the simplest end, inventory just moves in and out with the posting of purchase and sales documents, with no separate warehouse activity at all. One step up, you enable order-by-order warehouse handling, where a receipt or a shipment becomes its own warehouse document that a warehouse worker processes separately from the purchasing or sales clerk. At the top end, you enable what Business Central calls required receive, require ship, require put-away, require pick, and bin mandatory together, which turns the location into a fully directed advanced warehouse where nothing moves without a system-generated instruction.

The practical way to think about it is this. Basic warehousing means the inventory document and the warehouse document are the same event, or close to it. When you post a purchase receipt, the stock is in. When you post a sales shipment, the stock is out. You might use inventory put-away and inventory pick documents to add a light warehouse step, but the warehouse activity is tied directly to the source order. Advanced warehousing separates the two worlds. The purchasing and sales side deals in orders, while the warehouse side deals in its own receipts, put-aways, picks and shipments, connected through an internal document called the warehouse receipt or warehouse shipment. That separation is the single biggest conceptual jump in Business Central warehousing, and it is what people mean when they say basic versus advanced.

Why does getting this wrong cost so much? Because the level is set per location and it is woven through every warehouse transaction. If you launch a location as a simple basic warehouse and later discover you genuinely need directed put-away and pick, you cannot just tick a box and carry on. You have to drain the location, reconfigure the warehouse settings, define zones and bins, re-profile the item and bin data, retrain the team, and re-cut every process document. Conversely, if you over-configure a low-volume stockroom as a full advanced warehouse, you saddle a two-person team with a document flow designed for a distribution centre, and they will either drown in steps or quietly work around the system, which corrupts your inventory accuracy anyway. Warehousing is only as accurate as it is usable. For how this warehouse layer sits on top of the item and costing foundations, it is worth reading the companion piece on inventory management in Business Central alongside this one, because warehouse structure and inventory valuation are two views of the same stock.

The rule I use with clients: choose the lightest warehousing level that still meets your accuracy and traceability requirements, and only step up when a concrete operational pain forces you to. Advanced warehousing should be a decision you can defend with volume figures and error rates, not a default you reached for because it sounded more professional.

2. Locations and the warehouse setup that controls behavior

A location in Business Central represents a physical place where you hold inventory: a warehouse, a stockroom, a van, a consignment site, a production floor buffer. On the surface it is just a code and an address, but the location card is where the warehousing behaviour of that place is defined, and almost every warehouse question I get asked traces back to a checkbox on this card being set differently from what the person assumed.

The Warehouse fast tab on the location card holds the settings that decide which level of warehousing that location runs. The important ones, in the order they escalate the complexity, are roughly these. Require Receive and Require Put-away control the inbound side: whether an incoming purchase order needs a separate warehouse receipt and a separate put-away instruction before the stock is considered handled. Require Ship and Require Pick control the outbound side in the same way, for sales and transfer orders. Bin Mandatory decides whether the location tracks inventory down to individual bins rather than treating the location as one undivided space. Directed Put-away and Pick is the master switch that turns on the full advanced warehouse, and enabling it forces bins, zones and the directed workflows on together as a package.

These settings combine into a few recognisable profiles. A location with all of them off is a pure basic location where posting the order posts the inventory. A location with Require Put-away and Require Pick on, but Directed Put-away and Pick off, uses inventory put-away and inventory pick documents, which is a middle ground that gives you a warehouse step without the full zone-and-bin machinery. A location with Require Receive, Require Ship, Require Put-away, Require Pick and Directed Put-away and Pick all on is a full advanced warehouse. Business Central even provides a guided setup that will apply a coherent bundle of these settings for you, which is safer than toggling them individually, because certain combinations are contradictory and the system will stop you.

Two further points matter here. First, these settings are per location, so a single company can and often should run different locations at different levels: a high-throughput central warehouse on advanced, a small regional stockroom on basic, and a service van as a simple bin-less location. That mixed model is completely normal and usually correct. Second, changing these settings on a location that already holds stock and history is deliberately restricted, because you cannot cleanly reinterpret existing quantities under a new set of rules. This is why the level decision belongs at design time, and why I treat it as one of the most consequential choices in a Business Central rollout rather than a setting to revisit casually later.

3. Zones and bins

Once a location uses bins, the physical warehouse stops being a single bucket of stock and becomes a map. A bin is the smallest addressable storage location: a specific shelf, a floor position, a pallet slot. A zone is a grouping of bins that share characteristics, for example a bulk storage zone, a pick face zone, a receiving zone, a shipping zone, or a quarantine zone. Zones exist only in advanced warehousing; a bin-mandatory but non-directed location has bins without the zone layer above them. This distinction trips people up, so it is worth stating plainly: bins can exist without zones, but zones only exist where directed put-away and pick is switched on.

Bins carry properties that drive warehouse behaviour, and this is where advanced warehousing earns part of its keep. A bin can have a bin type that defines what warehouse activities it participates in, for example whether it is a receiving bin, a shipping bin, a put-away bin, a pick bin, or a bin that supports both. A bin can have a ranking that influences the order in which the system suggests it for put-away or pick, so that faster-moving goods land in more accessible positions. Bins can carry capacity constraints, maximum quantity or cubage, so the system avoids directing stock into a bin that physically cannot hold it. Bin content records track which items, in which units of measure, are allowed or currently present in each bin.

The reason all this structure exists is to let the system make placement and retrieval decisions that a human would otherwise make from memory and habit. In a basic or bin-mandatory-only location, a worker decides where to put things and where to find them, and the system merely records the bin they typed in. In a directed location, the system proposes the bin, using zone, bin type, ranking, capacity and existing content to optimise the flow. That is powerful in a large warehouse with many SKUs and shared staff, because it removes the reliance on individual knowledge. It is overhead with no payoff in a small stockroom where two people know exactly where everything lives. The value of zones and bins is directly proportional to the size, turnover and staff rotation of the warehouse, and inversely proportional to how well your team already knows the space in their heads.

The honest caution on bins: bins are only as accurate as the discipline that maintains them. The moment a worker puts stock in a different bin than the system directed and does not correct it, the warehouse map diverges from reality, and directed pick starts sending people to empty bins. Bin-level tracking multiplies the number of places your data can be wrong. It pays for itself only where the team will consistently honour the bin the system records. Without that discipline, bins add precision to your errors rather than removing them.

4. Inbound: receipts and put-aways

The inbound flow is where the difference between basic and advanced becomes concrete. Follow a delivery arriving against a purchase order through each level and the trade-off shows itself clearly.

In a basic location, the purchasing clerk posts the purchase order receipt and the stock is in inventory, in the location, immediately. There is no separate warehouse step. This is fast and simple, and for many small operations it is entirely sufficient, because the person receiving the goods and the person posting the order are the same person or sit next to each other. The weakness is that inventory shows as available the instant the order is posted, even though the goods might still be sitting on the receiving dock, unchecked and unstored.

Add Require Put-away to a location and you introduce the inventory put-away document. Now, receiving the goods and telling the system where they were stored become two acts. The purchase order is received, and a warehouse worker processes an inventory put-away that records which bin the goods went into. This is the light middle ground: a real warehouse step, tied directly to the source order, without the full warehouse receipt machinery. It suits operations that need to track put-away and bin placement but do not consolidate multiple orders into single warehouse handling runs.

In a full advanced location with Require Receive on, the flow splits into two documents. First, a warehouse receipt is created from one or more inbound source orders. Crucially, a single warehouse receipt can pull lines from several purchase orders or inbound transfers arriving together, which is exactly what a busy dock needs, because goods arrive by truck and pallet, not by purchase order. The warehouse worker posts the warehouse receipt to register that the goods physically arrived, which places them in the receiving bin or zone. Then the system generates a put-away document, often automatically, that directs the worker to move the received goods from the receiving zone into their proper storage bins, using bin ranking, capacity and zone rules to choose the destinations. The stock is only considered fully handled once the put-away is registered.

The payoff of the advanced inbound flow is control and consolidation. You can receive many orders in one dock operation, you get a clean separation between goods that have physically arrived and goods that are properly stored, and the system directs placement so that you do not depend on the receiver knowing the warehouse. The cost is documents and steps. Every receipt is now two posting actions and a directed movement rather than one, and the team has to work through the system in real time rather than catching up on paperwork later. For a high-volume dock this is a gift; for a stockroom that takes three deliveries a week it is friction with no return. The purchasing side of this inbound flow, the orders that feed these receipts, is covered in depth in the companion guide on purchasing management in Business Central.

5. Outbound: picks and shipments

The outbound flow mirrors the inbound one, and the same escalation of complexity applies. In a basic location, the sales clerk posts the sales order shipment and the stock leaves inventory immediately. No separate warehouse activity, no pick document. Fast, simple, and adequate when the person shipping is the person posting.

Add Require Pick and you get the inventory pick document. Shipping now separates into two acts: the system tells a warehouse worker which items to pick from which bins, the worker registers the pick, and then the shipment is posted. This gives you a picking instruction and bin-level accuracy without the full warehouse shipment layer. It is the outbound equivalent of the inventory put-away middle ground, and it suits operations that want directed picking discipline but handle each order individually.

In a full advanced location with Require Ship on, outbound splits into a warehouse shipment and a pick. A warehouse shipment is created from one or more sales orders or outbound transfers, and like the warehouse receipt it can consolidate multiple source orders into a single warehouse operation, which is how you pick several orders in one efficient walk through the warehouse rather than one trip per order. From the warehouse shipment, the system generates a pick document that directs the worker to specific bins in an efficient sequence, respecting zone layout and bin ranking so the pick path is sensible. The worker registers the pick, moving goods from storage bins to the shipping zone, and then the warehouse shipment is posted to complete the outbound and update the source sales orders.

The advanced outbound flow is where a warehouse of any real size gets its throughput. Consolidated picking, directed pick paths, and the separation between picking and shipping mean a small team can move a large volume accurately. The system can also apply the picking rules that matter for regulated or perishable goods, choosing which units to pick according to the item's tracking and rotation requirements, rather than leaving it to the worker to remember. The cost, again, is document overhead and the requirement that the team works the system live. If your outbound volume does not justify consolidated, directed picking, this machinery slows you down. If it does, nothing else in Business Central will keep up with it.

6. Warehouse movements and internal picks and put-aways

Not all warehouse activity is triggered by a purchase or a sale. Stock has to move around inside the warehouse too: replenishing a pick face from bulk storage, consolidating partial pallets, clearing a receiving bin, relocating goods after a layout change. Business Central handles these internal flows with a few distinct instruments, and understanding them rounds out the picture beyond the order-driven inbound and outbound flows.

In a directed advanced warehouse, the movement document is the tool for relocating stock from one bin to another without any source order involved. You create a movement, the system or the worker specifies the from-bin and the to-bin, and registering the movement updates the bin content accordingly. Movements are how you keep the pick face stocked from bulk, how you empty a receiving zone that a put-away missed, and how you reorganise storage. Business Central can also generate movements as part of bin replenishment, calculating which pick bins are running low against their defined minimums and proposing the moves from bulk to refill them, so that pickers rarely arrive at an empty pick bin.

Alongside order-driven put-aways and picks, Business Central offers internal put-aways and internal picks, which let you drive a put-away or a pick from an internal need rather than from a purchase or sales order. An internal put-away might store goods that came from production or from an adjustment. An internal pick might stage goods for a production consumption or for an internal requirement that is not a customer shipment. These bridge the gap between the manufacturing and inventory sides of the system and the warehouse, so that goods flowing to and from production still pass through the same directed warehouse discipline as goods flowing to and from customers.

In a basic or bin-mandatory-only location, the equivalent internal moves are handled more simply. You can reclassify stock between bins with a reclassification journal, which is a direct data entry of a from-bin and to-bin move rather than a document-driven, registered warehouse activity. This is faster but less controlled: it is a bookkeeping move rather than a directed physical instruction. The pattern here is the same trade-off that runs through the whole subject. Advanced warehousing turns internal moves into tracked, instruction-driven activities that build an audit trail and keep the bin map honest. Basic warehousing turns them into quick journal entries that trust the operator. Which you want depends entirely on whether the traceability is worth the extra handling.

7. Directed put-away and pick (advanced warehousing)

Directed put-away and pick is the full expression of advanced warehousing, and it deserves a section of its own because it changes the character of the warehouse rather than just adding documents. When Directed Put-away and Pick is enabled on a location, the system stops recording where the worker chose to put or take things and starts telling the worker where to put and take them. The human executes; the system decides. That inversion is the whole point, and it is either liberating or infuriating depending on whether your operation genuinely benefits from it.

Under directed operation, the system uses the full set of bin and zone attributes to make its decisions. For put-away, it looks at the item, the zone and bin types that are valid for that item, the bin ranking, the remaining capacity of candidate bins, and the existing bin content, then proposes destination bins that keep fast movers accessible and respect physical limits. For pick, it looks at where the item is stored, the pick bin rankings, the zone layout and the item's tracking and rotation rules, then proposes a pick sequence that is efficient to walk and correct for rotation. The worker can be constrained to follow these instructions closely, which is what delivers the accuracy, or given some latitude, which trades a little control for flexibility.

This is where the traceability of advanced warehousing becomes complete. Every physical handling of stock, receipt, put-away, movement, replenishment, pick and shipment, is a registered warehouse activity with a document behind it, so you can reconstruct exactly how any quantity moved through the building. Combined with item tracking by lot or serial number, directed warehousing gives you the kind of end-to-end traceability that regulated industries and quality-sensitive operations require, and that a basic location simply cannot produce because it never captured the intermediate moves.

The honest counterweight is that directed warehousing demands real discipline and real training. Workers must process activities in the system as they do them, not from a clipboard at the end of the shift, because the whole model depends on the system's picture matching the floor in real time. The bin data, the zone design, the item and bin rankings all have to be set up thoughtfully and maintained as the warehouse changes. When that investment is made, a directed warehouse runs with an accuracy and a resilience to staff turnover that no manual system matches. When it is not, directed warehousing becomes an elaborate way to generate discrepancies, and the team's trust in the system erodes fast. Directed put-away and pick rewards operations that commit to it fully and punishes those that adopt it halfway.

8. Cycle counting and physical inventory

No warehouse stays accurate on its own. Miscounts, mispicks, damage, unrecorded moves and simple human error erode inventory accuracy continuously, and the only remedy is systematic counting. Business Central supports two broad approaches: periodic physical inventory, where you count everything at once, typically at a financial period end, and cycle counting, where you count a rolling subset of items continuously so that the whole warehouse is covered over time without ever stopping operations for a full stock take.

In a basic or non-directed location, physical inventory is driven through the physical inventory journal. You calculate the expected inventory into the journal, print count sheets, count the physical stock, enter the actual counted quantities, and post the journal so that any differences become positive or negative inventory adjustments. Cycle counting in this model is a matter of policy and item setup: you can define counting periods on items so the system knows how frequently each should be counted, and use that to select which items fall due for counting in a given cycle, rather than counting the whole warehouse at once.

In a directed advanced warehouse, counting is bin-aware and uses warehouse-specific journals. Because inventory is tracked to the bin, counting has to reconcile the physical count in each bin against the bin content the system believes is there, not just the total location quantity. The warehouse physical inventory process calculates the expected quantity per bin, the worker counts each bin, and the differences are posted so that both the bin content and the overall inventory come back into line. This is more granular and more work than counting a location as a single total, but it is also far more diagnostic, because it tells you not just that you are short of an item but which bin the discrepancy is in, which usually points at the process failure that caused it.

The strategic point about counting is that it is where you discover whether your chosen warehouse level is actually being honoured. A directed warehouse with clean cycle counts is proof that the discipline is holding: the system's map matches the floor. A directed warehouse with persistent bin discrepancies is telling you that the team is not working the system as designed, and no amount of extra configuration fixes that; it is a process and training problem. Cycle counting, done honestly, is the health check on the entire warehouse model. I treat a rising discrepancy rate as the earliest warning that a warehouse has been configured heavier than the team can sustain, and it is often the trigger for the conversation about whether the level was set correctly in the first place. For the wider set of operational metrics that this feeds into, the FM KPI framework gives a useful frame.

9. Handheld scanning and warehouse mobility

A directed warehouse reaches its full potential when the workers are not tied to a desktop. If every put-away, pick, movement and count has to be registered at a fixed terminal, the real-time discipline that advanced warehousing depends on becomes a bottleneck, because workers batch their entries rather than record as they go. Handheld scanning closes that gap by putting the warehouse instructions and the confirmation of each action into the worker's hand, at the point and moment of the physical activity.

Business Central itself is a web-based application, and its warehouse activity pages can be operated from a browser on a mobile device, but most serious scanning operations use a dedicated warehouse mobility layer built for barcode scanners and rugged handhelds. These solutions, whether Microsoft's own mobile warehousing capabilities or third-party scanning apps from the Business Central partner ecosystem, present the put-away, pick, movement and count instructions in a stripped-down, scan-driven interface. The worker scans the bin to confirm they are in the right place, scans the item to confirm they picked the right thing, and enters or scans the quantity, and the system validates each step against the directed instruction in real time.

The value of scanning is not just speed, though it is faster than keying. It is validation at the point of action. When the worker has to scan the actual bin and the actual item barcode, the system catches the wrong-bin and wrong-item errors at the moment they would occur, rather than discovering them later at a cycle count. That closed feedback loop is what makes a high-volume directed warehouse both fast and accurate at the same time, which manual entry struggles to achieve, because manual entry lets the worker key what they meant to do rather than what they actually did.

The caution on mobility: handheld scanning multiplies the benefit of a well-run directed warehouse, but it does nothing to rescue a badly designed one. If the bin structure is wrong, the zones are illogical, or the item data is dirty, scanning simply lets the workers hit the wrong instructions faster. Scanning is a force multiplier on the warehouse model beneath it, and force multipliers amplify whatever they are pointed at. Get the warehouse design right first, then add scanning to make it fly. Adding scanning to a broken design just industrialises the errors.

10. When to enable advanced warehousing, and when it is too much

This is the section that should shape the project plan, because it is the decision the rest of the guide has been building toward. Advanced warehousing in Business Central is genuinely powerful, and it is genuinely too much for a large share of the companies that talk themselves into it. Here is the honest guidance I give when someone asks whether they should turn it on.

Advanced warehousing earns its place when several of these are true. You have high transaction volume, enough inbound and outbound movements that consolidating orders into single warehouse operations saves real labour. You have a large number of SKUs and a physically large or complex warehouse, where nobody can hold the whole map in their head and directed placement genuinely helps. You have staff rotation or multiple shifts, so you cannot depend on individual knowledge of where things live. You have traceability requirements, regulated goods, lot or serial tracking, quality holds, that demand a complete audit trail of every physical move. And critically, you have the operational discipline and the training budget to work the system live, because advanced warehousing that is not honoured in real time is worse than no advanced warehousing at all.

Advanced warehousing is too much when the opposite conditions hold. Your volume is modest, a handful of receipts and shipments a day that one or two people handle comfortably. Your warehouse is small and your team knows it intimately, so directed placement solves a problem you do not have. Your traceability needs are satisfied by location and lot tracking without bin-level detail. Or your team is small enough that the extra document steps and the real-time entry discipline would consume more time than the control is worth. In these cases, basic warehousing, perhaps with the lighter inventory put-away and pick documents where you want a bin step, delivers the accuracy you need without the overhead you do not.

There is also a valuable middle path that people forget exists, because the conversation is so often framed as basic versus advanced with nothing in between. A bin-mandatory location that stops short of directed put-away and pick gives you bin-level tracking, inventory put-away and inventory pick documents, and reclassification-based internal moves, without the full zones, warehouse receipts, warehouse shipments and directed instructions. For a lot of mid-sized operations that is the sweet spot: enough structure to track stock to a shelf and drive a put-away and pick step, without the full machinery of a directed distribution centre. Do not let the binary framing hide this middle ground, because it is where a surprising number of companies actually belong.

The test I apply: can you name a specific, recurring operational pain that advanced warehousing solves, and can you commit the discipline to work it live? If you can name the pain and make the commitment, enable it and do it properly. If you are reaching for advanced warehousing because it sounds more capable, or because a demo looked impressive, stop. The most expensive warehouse configurations I have seen were not the ones that were too simple. They were the ones that were too complex for the team running them, configured because advanced sounded better than basic, and quietly worked around until the inventory accuracy collapsed.

One last practical note on sequencing. Because moving a live location between warehouse levels is genuinely hard, the safest strategy is to model your real operation carefully before go-live, choose the lightest level that meets your requirements, and design in the ability to run different locations at different levels so you are not forced into one answer for the whole company. It is far easier to start a specific high-volume location on advanced from day one than to convert a busy basic location later, and it is far easier to leave a small stockroom on basic than to unwind an advanced configuration it never needed. Get the level right per location at design time and warehousing in Business Central becomes a strength. Get it wrong and it becomes the thing everyone blames the system for. Where warehousing sits within the wider platform is laid out in the complete guide to Business Central features, which is worth reading to see how the warehouse module connects to inventory, purchasing, sales and manufacturing.

Final thoughts

Warehouse management in Business Central is not really a technical subject. The mechanics of receipts, put-aways, zones, bins, picks and shipments are well documented and, once you have set them up a few times, entirely learnable. The hard part, the part that decides whether a warehouse implementation succeeds or becomes a running complaint, is judgement: matching the level of warehousing to the operation that has to live inside it every day. Basic versus advanced is the decision that shapes everything downstream, and the honest answer for most companies is lighter than the software will let them configure and lighter than their ambition suggests.

If you take one thing from this guide, let it be that advanced warehousing is a commitment, not an upgrade. It rewards operations with the volume, the complexity, the traceability needs and above all the discipline to work it in real time, and it punishes operations that adopt it because it sounded more serious. Choose the level you can actually sustain, design your locations so different places can run at different levels, and treat rising count discrepancies as the early warning that you may have configured heavier than your team can carry. Do that, and Business Central will run a warehouse of almost any scale. Skip that judgement, and no amount of configuration will save you from a warehouse model that never fit the people running it.

Related reading: Inventory management in Business Central, Purchasing management in Business Central, The complete guide to Business Central features, FM KPI framework.