Inventory and warehouse management in Business Central

Business Central can run as a basic inventory system for an online retailer or as a fully-bin-managed warehouse for a multi-site distributor. The same underlying objects scale up and down — what changes is how much warehouse complexity you turn on. The most important implementation decision in this area is honest self-assessment: turning on more warehouse than the operation needs creates daily friction for no benefit, and turning on less than it needs creates inventory records nobody trusts.

Items and inventory

Each item card carries a costing method (FIFO, LIFO, Average, Standard, Specific), unit of measure conversions, item tracking (serial / lot numbers), assembly or production BOMs, and reordering policy (Lot-for-Lot, Maximum Qty, Fixed Reorder Qty). Items can be non-inventory (consumed services), service (no stock), or inventory (physical). The item ledger records every inbound, outbound, and adjustment with quantity, while the value entry table records the cost — these are deliberately separate so cost adjustments can flow without touching quantity. Related items and lookalike substitutes are covered in item substitutes and cross-references, grouping and search live in item categories, and the master-data discipline that keeps all of this consistent across thousands of item cards is master data management in Business Central.

The costing method is effectively permanent per item, so choose it before go-live: FIFO or Average for most distribution businesses, Standard where manufacturing wants variance analysis, Specific only for serialized high-value goods. The trade-offs are covered in costing methods compared.

Locations

Inventory is held at locations, each of which can be configured for different warehouse levels: simple postings only; bin tracking; receive/ship documents; or full directed put-away and pick with bin policies. The same database can mix simple and complex locations — a central warehouse on full WMS and a service van as a simple location is a normal setup, not a workaround.

The level ladder is worth spelling out, because each rung changes daily work:

• No bins, no documents. Posting a sales shipment moves stock. Right for small stockrooms and virtual locations.
• Bins without warehouse documents. Stock has a bin code, but posting is still done from the order. Right when you want to know where things are without changing who posts.
• Receive/ship documents. Warehouse staff post receipts and shipments separately from the back office. This is the first rung that separates duties.
• Directed put-away and pick. The system suggests bins by zone, capacity, and policy; work is driven by put-away, pick, and movement documents. Right for real warehouses with real pickers — and overkill for everyone else.

Moving a location up the ladder mid-flight is possible but disruptive; it is much cheaper to pick the right rung per location at design time.

Warehouse documents

In a full WMS setup, inbound flow is purchase order → warehouse receipt → put-away, and outbound flow is sales order → warehouse shipment → pick → post shipment. Bins are constrained by capacity, item, and zone policies. Movement worksheets and replenishment between bulk and pick bins are standard, and pick and put-away strategies covers the configuration detail. Barcode scanning on the shop floor comes either from Microsoft's warehouse scanning add-on or from established ISV apps; running a directed warehouse on paper defeats the point.

Item tracking

Lot and serial numbers are configurable per item, with optional expiration date tracking and warranty dates. Both can be required at receipt, shipment, or both, and feed into recall/traceability reports. Decide tracking requirements early: switching an item to lot tracking after thousands of untracked entries is genuinely awkward, while carrying tracking you never use taxes every posting with an extra dialog. Item tracking with lots and serials covers the setup and traceability reporting in depth.

Counting

Physical inventory journals support whole-warehouse counts and cycle counts; counted differences post to inventory adjustments with cost and quantity reconciled automatically. Cycle counting by ABC classification — count the fast movers often, the slow movers rarely — keeps accuracy high without shutting the warehouse down; the ABC analysis guide shows the setup, cycle counting and physical inventory covers the counting workflow itself, and for full-warehouse counts with sign-off discipline, see physical inventory orders.

Costing and valuation

Adjust Cost — Item Entries is the routine that propagates landed cost from inbound transactions into outbound cost of goods sold; running it before period-end is standard practice (most systems now run it automatically on posting). The Inventory Valuation report ties cost back to the GL, and the interim accounts for received-not-invoiced stock are part of the month-end reconciliation. When inventory value and GL disagree, the cause is almost always a skipped adjust-cost run or direct GL postings to inventory accounts — lock those accounts against manual posting and the problem disappears.

What to take away

Match warehouse complexity to the physical operation location by location, fix costing methods and tracking policies before go-live, and let the item ledger be the single truth for quantity. Business Central's inventory machinery is deep enough for serious distribution — the failures are almost never missing features, they are complexity switched on without the discipline to operate it.

Decision matrix — warehouse level per location

Signal	No bins / no docs	Bins, no docs	Receive/ship docs	Directed put-away + pick
Physical size	A shelf or a closet	A room, one picker	A warehouse with a small team	A warehouse with a picking crew
Who posts stock moves	Back office	Back office	Warehouse staff	Warehouse staff, scanner-driven
Bin discipline	None	Lookup only	Lookup, some enforcement	Fully policy-driven
Serial/lot capture	Optional	Optional	Frequently required	Required
Barcode scanning	Not needed	Rare	Sometimes	Effectively required
Daily overhead	Near zero	Low	Meaningful	Substantial — pays back in accuracy

Pick the rightmost column that matches the operation and nothing further. Locations can be mixed within one company.

A worked example: sizing the warehouse for a distributor

A 40-person distributor with one 2,000 m² warehouse and a small returns bench sits comfortably at "directed put-away and pick" for the main location and "receive/ship documents" for the returns bench. Bins are grouped into a receiving zone, three pick zones (fast, medium, slow), a bulk-reserve zone, and a shipping zone. Fast-movers auto-replenish from bulk to pick when a pick bin drops below a min quantity. ABC cycle counting counts A items monthly, B quarterly, C annually, and the whole warehouse is only fully counted once a year.

Skipping the zoning, replenishment, and cycle-count design at go-live is the number-one reason a directed warehouse fails after a few months — not the software, the operating model around it.

Wrong-fit signals

• 3PL billing based on bins, weights, or licence plates — that is a Supply Chain Management problem.
• Wave and cluster picking across dozens of orders per wave — again, Supply Chain Management territory.
• The operation is a shed with a whiteboard, and BC is being asked to model it as a full WMS — implement one rung down and rise with the operation.