Warehouse Topology in Business Central, Explained

“Warehouse management” in Microsoft Dynamics 365 Business Central isn’t one feature you turn on. It’s a ladder of increasingly strict configurations, and where a given location sits on that ladder decides what a scanning app on the floor can — and can’t — do there. Most first conversations about warehouse scanning start from the wrong assumption: that a Business Central location is either “in warehouse mode” or not. It isn’t a switch. It’s a small set of rungs, each one trading setup effort for a specific capability, and every rung is a legitimate place for a real business to sit permanently.

Five rungs, not two

Business Central’s own documentation lays out the ladder as a table of configuration levels, distinguished mainly by which documents drive receiving and shipping, and by how much of the physical floor is directed by the system versus by a worker’s judgment. Compressed into plain language, from the ground up:

Rung 1 — no dedicated warehouse activity. You post receipts and shipments straight from purchase and sales orders, or from item journals. There’s no separate receiving or put-away step at all; whatever a purchase order says arrived, arrives, and whatever a sales order says shipped, ships. A one-truck-a-day distributor with a single small storeroom, or a service business that just needs to know it has stock, often runs exactly like this — and there’s nothing unsophisticated about it if that’s genuinely all the operation needs. Bin codes are optional here (a location-level toggle decides whether bins are mandatory at all), and internal movement, when it happens, goes through a plain item journal.

Rung 2 — basic warehousing, order by order. A separate receiving or shipping step now exists for each source document individually: an inventory put-away records what physically arrived before it becomes available to sell, and an inventory pick records what’s being pulled before it ships. Nothing is consolidated across multiple orders yet — one purchase order gets one put-away, one sales order gets one pick. This is where a lot of small-to-mid distributors land: enough structure to check what actually arrived on the dock before it’s sellable, without asking anyone to manage a wave of picks across a shift.

Rung 3 — basic warehousing, consolidated. The same order-by-order documents now get bundled: a warehouse receipt can gather several purchase or transfer orders into one receiving pass, and a warehouse shipment can gather several sales or transfer orders into one shipping pass. Nothing about the physical floor changed — bins can still be optional — but the paperwork now matches how a real receiving dock or shipping dock actually works, where the truck that just backed in usually isn’t carrying only one order’s freight.

Rung 4 — advanced warehousing. Receiving and shipping consolidation continue, and now pick and put-away work is generated from worksheets rather than created and worked one document at a time: a put-away worksheet turns a pile of open receipts into put-away tasks, a pick worksheet turns a pile of open shipments into pick tasks. A multi-zone distribution center running dozens of orders a wave typically needs at least this much structure just to sequence the work across several people on the floor at once, instead of everyone independently deciding what to do next.

Rung 5 — advanced warehousing with directed put-away and pick. The system, not the worker, now decides which specific bin a put-away lands in and which specific bin a pick draws from — using bin capacity, bin ranking, and, for items that need it, expiration date. Bin codes stop being optional and become mandatory the moment this toggle is on. This is the rung with the most automation and, honestly, the most setup discipline demanded in return; it gets its own full treatment in directed put-away and pick, explained.

None of this is a maturity score, and it’s worth resisting the urge to read it as one. A single-bin location running rung 1 or rung 2 correctly, with accurate stock and a worker who knows the floor, comfortably beats a rung-5 setup nobody kept the bin rankings current for. The useful question isn’t “how advanced is our warehouse” — it’s “which rung does our actual receiving-to-shipping process already run at,” because that’s the rung any scanning app has to meet a business on, not the rung a vendor wishes every customer had already climbed to.

What actually changes between rungs

It helps to be concrete about what a rung is, mechanically, rather than treating the ladder as a vague maturity label. Two things move together as you climb it:

Which documents exist. At the bottom, there’s no separate warehouse document at all — a purchase or sales order posts directly. Climbing the ladder introduces, in order: an inventory put-away or inventory pick (order-by-order), then a warehouse receipt or warehouse shipment (consolidated across orders), then put-away and pick worksheets that generate warehouse put-aways and warehouse picks from a pool of open demand. Internal movement follows the same shape — a plain item journal at the bottom, a movement worksheet generating warehouse movements further up.

Whether a bin is a suggestion or a requirement. Below directed put-away and pick, a bin code is either not used at all or optional — useful information, not something the system insists on. At the top rung, bin codes become mandatory, and a set of features that only exist there switch on: bin capacity and weight limits, bin ranking (which bins fill and drain first), bin types (receiving bins, shipping bins, pick bins, and more), zones (groups of bins that share workflow rules), and warehouse classes (keeping frozen or hazardous items in the bins built for them).

A bin itself, in Business Central’s own terms, is simply the smallest storage unit the system tracks — it can be as coarse as “the whole warehouse” or as fine as a single numbered shelf slot. Whether bins are required at all is a location-level setting, independent of which rung a location is otherwise running at.

How to tell which rung a location is actually on

This isn’t guesswork — it’s a handful of yes/no settings on the location card itself, and reading them tells you exactly which rung a given location sits at without having to interview anyone about how the warehouse “feels” to work in. The settings that matter, by flow:

• Inbound: whether Require Receive and Require Put-away are turned on, separately, for purchase, sales-return, service, and transfer documents.
• Outbound: the mirror pair, Require Ship and Require Pick.
• Internal (production, assembly, projects): whether inventory picks, inventory movements, and inventory put-aways are in play at all, or whether the location relies on plain journals.
• The one toggle that changes everything else: Directed Put-away and Pick on the location card’s Warehouse tab. Turning it on doesn’t just add a feature — it makes bin codes mandatory, and a cluster of dependent settings (bin capacity checks, bin ranking, mandatory put-away templates) turn on automatically alongside it, because none of them mean anything on a location where a bin is merely optional information.

A location with none of the Require toggles on and bins optional is rung 1. Turn on Require Put-away and Require Pick alone, still order-by-order, and it’s rung 2. Layer consolidated warehouse receipts and shipments on top, still without worksheets, and it’s rung 3. Introduce put-away and pick worksheets and it’s rung 4. Flip Directed Put-away and Pick, and every dependent setting that switches on with it, and it’s rung 5. Reading these settings directly off a location card is the honest way to answer “which rung are we on” — a much better source than either a vendor’s assumption or a warehouse manager’s sense of how sophisticated the operation feels day to day.

Why a location’s rung matters more than its size

Two businesses can be the same size and legitimately sit on different rungs, because the rung tracks process structure, not headcount. Picture a boutique food importer receiving pallets from a handful of vendors, storing everything in one warehouse with a handful of fixed bins, and shipping whole cases to a short customer list. That operation can run comfortably at rung 1 or 2 for years — there’s no benefit to a directed pick when one experienced worker already knows exactly where everything sits, and the setup cost of bin ranking and capacity data would be pure overhead with no payoff. Now picture a contract packager with the same headcount, juggling dozens of SKUs across a mezzanine, running several pickers through the same wave simultaneously. That operation starts needing rung 4 or 5 just to keep two pickers from colliding on the same bin, and to make sure a new hire doesn’t have to memorize the floor before they can be productive.

Complexity, in Business Central’s own framing, tracks organizational size and process involvement — how many departments and people touch a single transaction, and how many steps a document passes through before it’s done. A process can be as simple as one person creating and posting a document alone; it can also involve an order processor creating a document, a warehouse manager generating pick instructions, and a warehouse worker finishing the flow by posting — three people, three steps, one transaction. Which of those shapes actually describes your floor is the honest input to “which rung are we on,” not a vendor’s sense of what’s impressive.

Why this matters when you’re choosing a scanning app

A scanning app that only knows how to talk to rung 5 — directed put-away, directed pick, bin rankings and all — is implicitly asking a rung-1 or rung-2 warehouse to take on a directed-warehouse project just to scan a receipt. That’s a real cost: item dimensions have to be defined for every unit of measure, every bin needs a rank, put-away rules need to be written and kept current as the floor’s real layout changes. None of that happens automatically just because a location’s directed-warehouse toggle gets flipped on, and a business that doesn’t need the automation shouldn’t have to pay for the setup.

The honest question to ask any vendor, including us, is whether the app actually reads a location’s existing setup and only offers the operations that setup genuinely supports — or whether it assumes, silently, that every customer has already climbed to the top rung. A tool built around the second assumption will either fail confusingly on a rung-1 location, or quietly demand a directed-warehouse migration before anyone can scan a single box.

Where this goes next

Rung 5 — directed put-away and pick — is different enough from the rest of the ladder that it earns its own full explanation: what “directed” actually means day to day, and what it costs to set up. See directed put-away and pick, explained. It’s also the rung where Business Central can enforce shipping by expiration date automatically, covered in FEFO vs. FIFO, explained. And for the Business-Central-specific side of this question — what BC’s own scanning tools assume about which rung a location is on — see does Business Central have a mobile scanner?

Key terms

New to the vocabulary? Bin, basic warehousing, directed put-away and pick, zone, and bin ranking are defined in the glossary.

Further reading — Microsoft Learn

For the authoritative, continuously updated version of the complexity table this article is based on, see Microsoft’s own documentation: Manage Warehouse Activities and Configure Warehouse Processes.