Business Central Warehouse Management Explained

What Business Central warehouse management actually is

Business Central warehouse management is the set of features that turns basic inventory into a structured warehouse operation. Microsoft’s design overview describes it as adding bins, warehouse shipments, inventory picks, and movement worksheets to inventory management so that businesses get an overview of inventory levels and item placement, plus fast and accurate receive, pick, and ship processes.

It is integrated, not standalone. The same warehouse documents post to the item ledger, update availability, link to purchase orders on the inbound side and sales orders on the outbound side, and feed the general ledger through posting groups. That integration is the main reason a distribution or light-manufacturing SME uses Business Central warehousing rather than a bolted-on WMS: one source of truth for stock, cost, and order fulfillment.

Warehouse features are included in the Essentials tier at $80/user/month (paid yearly). Premium at $110/user/month adds Manufacturing and Service Management but does not change the warehouse module itself. A Device license at about $45/device/month covers a shared shop-floor workstation or scanner for shift-based teams, and Team Members at $8/user/month suits light warehouse lookups.

From basic to advanced: Business Central warehouse complexity

Business Central deliberately does not force one warehousing model. Microsoft’s design overview uses two denominations—Basic and Advanced Warehousing—to cover several complexity levels, each enabled by toggles on the Location Card, so an SME can start simple and graduate as volumes grow. The most advanced level, directed put-away and pick, is what Microsoft calls a WMS installation.

In practice, partners map those toggles to four practical configurations. Level 1 has no dedicated warehouse activity: receipts, picks, and shipments post directly from orders or journals, with Bin Code is Mandatory as an optional setting. Level 2 is basic order-by-order handling using the Require Put-away and Require Pick toggles, served by Inventory Put-away and Inventory Pick documents tied to a single order. Level 3 is basic consolidated handling, enabled by Require Receipt and Require Shipment, which introduces the Warehouse Receipt and Warehouse Shipment documents that consolidate multiple orders. Level 4 is advanced warehousing with Directed Put-away and Pick, where bins become mandatory and the system generates directed put-aways and picks using bin ranking, templates, and capacities.

Microsoft’s own configuration table also shows a common intermediate: Require Receipt + Require Put-away (and Require Ship + Require Pick) without directed put-away—consolidated multi-order documents with optional bins. The jump from Level 2 to Level 4 is still the single biggest configuration decision in a Business Central warehouse rollout. You cannot set up the warehouse to use bins when the location has open item ledger entries, so the choice should be deliberate and made before transactions exist against the location.

Bins, zones, and locations: the physical model

Locations and bins answer different questions. A location is typically a geographic or organizational warehouse (or a distinct operational area with its own calendar, posting setup, and warehouse features). Bins are the smallest addressable storage unit inside a location—a shelf, a rack position, a floor spot. Microsoft notes locations are preferred when operations are distributed across areas or need separate planning parameters; bins model placement so the system can suggest put-aways and picks.

Zones group bins to direct workflow: a receiving zone, a bulk stocking zone, a pick face zone, a shipping zone. In advanced warehousing, bins created within a zone inherit several properties from it, which keeps a large warehouse manageable and helps new or temporary staff orient themselves. Shelf No. on the Item Card is informational only—it does not drive warehouse activities or availability calculations the way bins do.

Each bin carries a bin type that controls what can happen there. Microsoft defines six bin types: RECEIVE (items received but not yet put away), SHIP (picked but not yet shipped), PUT AWAY (bulk storage not used for picking), PICK (picking only, replenished by movements), PUTPICK (suggested for both put-aways and picks), and QC (used for inventory adjustments when set as the adjustment bin, plus defective or inspection items). Microsoft notes a warehouse can operate with just RECEIVE, PUTPICK, SHIP, and QC—those four enable the suggestions that support item flow and inventory discrepancy recording.

Warehouse class codes add a second layer of control by restricting where items can be stored—for example, frozen, hazardous, or high-value class codes assigned to product groups, items, zones, and bins. The system uses class codes when suggesting item placement in bins, so mismatched conditions are caught at put-away rather than after the fact. Bin contents can also be Fixed, Dedicated, or Default (or floating when none of those apply); directed put-away and pick does not use the default bin property the way simpler bin setups do.

• →Locations: geographic/org warehouses with separate calendars, posting, and warehouse toggles.
• →Bins: smallest addressable storage unit (shelf, rack, floor spot); drive suggestions and capacity.
• →Zones: group bins by workflow; bins inherit zone properties in advanced warehousing.
• →Six bin types: RECEIVE, SHIP, PUT AWAY, PICK, PUTPICK, QC — minimum viable set is RECEIVE, PUTPICK, SHIP, QC.
• →Warehouse class codes (frozen, hazardous) restrict item-to-bin placement via product groups and zones.
• →Bins become mandatory once Directed Put-away and Pick is enabled.

Directed put-away and pick: the advanced level

Directed put-away and pick is the most sophisticated level Business Central offers. It is turned on with a single toggle on the Location Card and, once enabled, makes bins mandatory and activates system-directed suggestions using bin ranking, put-away templates, bin types, capacities, and First-Expired-First-Out (FEFO) for items with expiration tracking.

Bin ranking automates and optimizes both directions: for put-aways the system suggests higher-ranking bins before lower-ranking ones, and for picks it takes the highest-ranked bin content first. Replenishment suggests lower-ranking bins first, so bulk-to-pick-face movements flow downhill. Microsoft recommends setting bulk PUT AWAY bins with lower rankings than ordinary pick bins or forward-picking-area bins so fast-moving stock lands in the pick face.

Put-away templates add prioritized rules—for example, place items in a bin with the same unit of measure, and if no similar bin has enough capacity, place them in an empty bin. Capacity is modelled per bin as Quantity, Total cubage, and Weight, which lets the system refuse an over-capacity put-away rather than silently overflowing a location. Multiple units of measure at bins are only available at locations that use directed put-away and pick; in all other configurations, bin contents use the base UOM and larger quantities convert down.

• →Enabled by the Directed Put-away and Pick toggle on the Location Card; bins become mandatory.
• →Bin ranking drives suggested put-aways (high-rank first) and picks (highest-ranked content first); replenishment flows low-to-high.
• →Put-away templates: prioritized rules such as same-UOM bin, then empty bin with capacity.
• →Per-bin capacity as Quantity, Total cubage, and Weight prevents over-capacity put-aways.
• →Multiple UOMs at bins are a directed-warehousing-only feature.
• →FEFO applies on directed pick for items with expiration dates.

Inbound and outbound warehouse flows (receipt → put-away → pick → shipment)

Business Central warehouse management organizes every transaction into three flows. Inbound covers items moving into the location—purchases, inbound transfers, and sales returns—handled by an inventory put-away in the basic order-by-order flow or a warehouse receipt (then optionally a warehouse put-away) in the consolidated or advanced flow. Outbound covers picking and shipping to customers or other locations—sales, outbound transfers, purchase returns, and service orders—handled by an inventory pick in the basic flow or a warehouse pick against a warehouse shipment in the advanced flow. Internal flow covers movements within the location: components to production, physical inventory counts, and bin-to-bin replenishment.

Microsoft documents four inbound methods (A–D) and four outbound methods that mirror the same complexity ladder. Methods A–C combine receive-and-put-away (or pick-and-ship) into one post. Method D splits them: post the warehouse receipt first so inventory is available, then register a separate warehouse put-away so items become pickable; on outbound, register the warehouse pick first, then post the warehouse shipment later. Inventory put-aways and picks post the source document; warehouse put-aways and picks only register warehouse activity and require the receipt/shipment documents.

The worksheets are the dispatch surface where a supervisor batches and releases work to the floor. In advanced setups, the Put-away Worksheet and Pick Worksheet pull pending work from posted receipts and released warehouse shipments; fully assigned lines leave the worksheet when warehouse put-aways and picks are generated. Because every warehouse document posts back to the item ledger and the general ledger, a single receive–pick–ship cycle updates availability, cost of goods sold, and the sales or purchase order status in one motion.

Mobile barcode workflows—and when AppSource WMS is needed

Built-in Business Central warehouse management is document-centric: inventory picks, warehouse receipts, and warehouse shipments work from the browser or the Business Central mobile client, and partners routinely drive those documents with barcodes on items, bins, and documents. Microsoft’s Q&A guidance (2026) confirms scan-based receiving, put-away, picking, and consumption are supported on basic and advanced configurations without a separate WMS product—devices scan codes and post against the configured warehouse documents.

What the standard client does not give you out of the box is a rugged, offline-first, forklift-optimized execution layer: dead-zone store-and-forward, license-plate (pallet) scans that put away an entire LP in one step, GS1 parsing, multi-view UIs for handheld vs tablet vs ring scanner, or wave/labor management. That is where AppSource mobile WMS extensions sit. Insight Works Warehouse Insight and similar ISV apps keep rules and posting inside Business Central while workers scan on the floor; partner and community threads in 2025–2026 repeatedly point teams with existing Zebra scanners toward purpose-built mobile WMS rather than customizing the generic BC mobile client alone.

Choose built-in when volumes are moderate, Wi-Fi is reliable, supervisors can work from worksheets, and accuracy is already high with paper or light scanning. Add AppSource mobile WMS when scan-first accuracy is the goal, when dock or rack dead zones drop connections mid-pick, or when directed put-away logic must be executed entirely on a handheld without desktop touch. For extreme 3PL velocity, wave planning, and labor standards, evaluate a best-of-breed WMS or Dynamics 365 Supply Chain Management warehouse-management-only mode integrated to Business Central via APIs—not more Location Card toggles.

• →Built-in: scan items/bins/documents against inventory pick, warehouse receipt, put-away, pick, and shipment documents.
• →AppSource mobile WMS: handheld-first UX, store-and-forward, LP/pallet scans, configurable worker views, label/GS1 support.
• →Still one ledger: quality ISV apps post into BC warehouse and item entries—do not dual-system invent inventory.
• →Step up beyond BC WMS when you need labor standards, wave planning, or multi-client 3PL orchestration.

Business Central warehouse setup before go-live

A clean warehouse rollout in Business Central follows a predictable sequence. First, decide the complexity level per location and set the Location Card toggles before any item ledger entries exist against that location—directed put-away and pick cannot be enabled against a location with open entries. Second, define zones (if you operate zones) and bins, assigning bin types and bin rankings that match the physical layout and the flow you want. Third, configure warehouse class codes on product groups, items, zones, and bins where storage conditions matter. Fourth, set up put-away templates and bin capacity (Quantity, Cubage, Weight) for directed locations.

Fifth, populate item master data with the warehouse fields—default bins, bin types, UOM dimensions for cubage and weight, and reorder policies. Sixth, decide the barcode and device strategy: item/bin labels, Device licenses for shared scanners, and whether AppSource mobile WMS is in scope for day-one go-live or a phase-two accuracy program. Seventh, run a counted, reconciled physical inventory as the opening balance so the first put-aways and picks start from truth. Finally, pilot the inbound and outbound flows with a single SKU set and a single shift before rolling out to the full floor.

The most common go-live failure is enabling directed put-away and pick on a location that already has transaction history and then trying to retrofit bins. The second most common is underestimating the data discipline required for bin rankings and put-away templates to produce useful suggestions. The third is shipping scanners without a labeled bin map and trained FEFO/class-code exceptions.

What Business Central warehouse management costs an SME

Warehouse management is included with every Essentials seat—there is no separate Microsoft WMS license for the built-in module. Microsoft list pricing (paid yearly) remains Essentials at $80/user/month and Premium at $110/user/month as of August 2026. Most distribution SMEs run the full warehouse module on Essentials; Premium only matters if you also need Manufacturing or Service Management.

For shop-floor and shift-based teams, two additional license types reduce cost. Partner pricing guides updated after Microsoft’s October 2025 increase list the Device license at about $45/device/month (up from $40), letting multiple named users share a single licensed workstation or scanner. Team Members remain $8/user/month for light users who look up stock, post a limited movement, or approve a pick without full transactional work. You cannot mix Essentials and Premium full users in the same tenant—standardize the full-user tier, then layer Device and Team Member seats.

A realistic 10-user Essentials distribution team with two shared scanner devices lands near $890/month in Microsoft licensing before implementation (10 × $80 + 2 × $45). AppSource mobile WMS, label printers, and rugged scanners are additive. Implementation scope—bin layout design, location configuration, data migration, mobile pilot, and cutover—is the variable cost and is set during an ERP Readiness Call.

Honest limitations before you commit to Business Central warehousing

Directed put-away and pick is effectively a one-way door. Microsoft documents that you cannot set up a location to use bins when it has open item ledger entries, so once a location is live with directed warehousing, unwinding it means a new location and a migration. Choose the level deliberately.

Capacity planning in Business Central is finite per bin (Quantity, Cubage, Weight) but the broader replenishment and planning logic is not a full warehouse-labor-management engine. It will not calculate wave planning, labor standards, or travel-time optimization the way a dedicated WMS will. For most SME distributors that gap is acceptable; for high-velocity 3PL operations it is not—and AppSource mobile layers improve execution accuracy without filling that WMS gap.

Advanced warehousing is configuration-heavy. Bin rankings, put-away templates, zone and bin types, and class codes all interact, and a poorly ranked bin structure produces worse suggestions than no suggestions. The module rewards a partner who designs the physical-to-logical mapping—and the scan path—before configuration rather than after.

How a platform-neutral partner keeps Business Central warehouse management honest

Flectic implements both Dynamics 365 and Odoo for SMEs across Canada, the UK, and the US, so a warehouse recommendation starts from your operation, not from a single vendor’s menu. For a distributor whose complexity sits at Level 2 or 3, Essentials with the right Location Card configuration is often the most cost-effective answer. For a 3PL-adjacent operation that needs wave picking and labor management, the honest answer is sometimes that Business Central’s built-in module is not the right fit—and an Odoo warehouse rollout, an AppSource mobile WMS on BC, or a best-of-breed WMS integration is.

Our AI-Accelerated Delivery approach is designed to deliver up to 3x faster than a traditional waterfall ERP rollout, applied to bin layout design, location configuration, data migration mapping, mobile pilot scripts, and test-script generation. The 3x is a target conditioned on scope clarity, data readiness, and standard configuration—never an unconditional promise. A scoping call establishes whether your project fits the profile.

Because we work on both platforms, the recommendation is not predetermined. A Business Central warehouse rollout, an Odoo warehouse rollout, or a hybrid gets weighed on total cost of ownership, fit, and the team you already have.

Frequently asked questions