← Back to Blogs/Multi-Zone Directed Put-Away in Business Central
Orca Warehouse Management Guide

How to Set Up Multi-Zone Directed Put-Away in Business Central for Batch-Tracked Stock

A practical look at zones, bins, put-away templates, and lot tracking—and how to prevent common configuration bottlenecks across your wholesale warehouse.

Explore Orca Warehouse
Organise storageMake warehouse zones and bin rules reflect real operations
Keep lots traceableCapture batch information as stock moves through the warehouse
Test exceptionsPrepare for full bins, incompatible classes and receiving changes
For UK wholesalers, distributors, and warehouse teams•Approx. 9 minute read

One Delivery, Three Zones—And a Put-Away That Doesn't Make Sense

A food or pharmaceutical wholesaler receives a delivery containing multiple batches of the same product. The operations team expects the inventory to route cleanly into suitable chilled bins, but Microsoft Dynamics 365 Business Central suggests an ambient location that makes no physical sense—or worse, refuses to generate a put-away line at all. Is the root cause a misconfigured lot number, an incorrect warehouse class, or an unassigned template priority?

When troubleshooting advanced warehousing issues, the fastest route to a solution is separating storage eligibility from bin preference and lot traceability. While these systems function simultaneously during receiving, they are governed by entirely separate logic tables within Business Central.

To build a reliable warehouse workflow, you must understand how these settings interact out of the box and where standard configurations routinely cause floor disruptions.

What Does Directed Put-Away and Pick (DIRMAP) Actually Do?

Directed Put-Away and Pick is Business Central's highest tier of advanced warehouse functionality, enabled directly on the Location Card. Once toggled, it shifts your facility from a paper-guided setup to a rigid, system-driven environment.

Instead of warehouse operators arbitrarily choosing where to drop received items, Business Central runs an algorithmic priority check to calculate optimal placement. It evaluates storage destinations using a strict sequence of conditions:

01

Step 1: Storage Eligibility (Warehouse Classes)

Matches the environmental and handling restrictions of the item (e.g., CHILLED, HAZARDOUS) against candidate bins. If a bin lacks a matching class code, it is instantly disqualified, regardless of how much physical space it has.

02

Step 2: Put-Away Templates

A user-defined sequence matrix that tells Business Central which types of eligible bins to check first (e.g., look for an identical item in a fixed bin before checking empty floating bins).

03

Step 3: Bin Rankings and Preference

If multiple eligible bins are available, the system evaluates the Bin Ranking score. Bins closer to shipping lanes or receiving docks are given higher ranks to optimize walking paths.

04

Step 4: Volumetric Capacity Check

The engine verifies the item’s dimensions and weight against the maximum cubage restrictions defined on the target Bin Content card.

Worked Example: Tracking Arriving Batches in a Multi-Zone Warehouse

GOODS IN80 cases · 2 lots
ZONE CHCH-01 · CH-02
ZONE AMAmbient bins

To see how these rules play out, consider a UK food distributor receiving 80 cases of a temperature-sensitive product across two distinct manufacturer lots:

  • check_circleLot A: 50 cases • Expiry: 18 December • Assigned Class: CHILLED
  • check_circleLot B: 30 cases • Expiry: 4 January • Assigned Class: CHILLED
  • check_circleZone CH (Chilled): Contains physical bins CH-01 and CH-02, both assigned the CHILLED Warehouse Class Code.
  • check_circleZone AM (Ambient): Configured for shelf-stable items; contains bins without the CHILLED class code.

The System Outcome vs. Floor Realities

When the warehouse receipt is posted and a put-away document is generated, the expected result is that both lots are directed strictly into Zone CH based on class compatibility.

However, a critical system distinction must be understood: Standard Business Central lot tracking does not act as an automatic slotting policy. The put-away engine is blind to expiration dates; it will not automatically prioritize placing Lot A in a faster picking bin simply because it expires before Lot B. Lot tracking exists to maintain compliance and traceability; First-Expired, First-Out (FEFO) rules apply to picking documents, not inbound storage.

The System Matrix: Step-by-Step Configuration Architecture

To successfully deploy multi-zone directed put-away for tracked inventory, avoid generic out-of-the-box templates. Use this structural configuration blueprint:

Implementation StepBusiness Central Native SetupCommon Wholesale Friction PointThe Orca Optimization
1. Enforce Absolute Stock SegregationDefine strict Warehouse Class Codes (e.g., CHILLED, FROZEN) on specific Bins and Item Cards / SKUs.Relying on alphabetical Zone names alone. BC ignores zone text fields during its algorithmic eligibility filtering.Orca Warehouse instantly flags and locks out bin drops on the handheld device if an operator attempts a class-mismatched put-away.
2. Capture Inbound Batch IdentityEnable Lot Warehouse Tracking alongside Lot Specific Tracking on the Item Tracking Code card.Forgetting to capture lot data at the Warehouse Receipt line, which breaks the downstream directed put-away routing.Operators scan manufacturer GS1 barcodes at goods-in, automatically populating tracking lines via mobile rugged scanners.
3. Establish Put-Away PrioritiesConstruct a multi-line hierarchy matrix inside the Put-away Templates page.Leaving templates too broad, causing empty suggestions or system validation blocks if a preferred bin fills up.Real-time mobile exception tracking lets operators mark a full bin and instantly receive an optimized alternative path on the fly.

Troubleshooting: Why is Business Central Suggesting the Wrong Bin?

If your system begins producing unexpected put-away movements or fails to generate lines altogether, trace the issue using this logic path before altering global location settings:

Symptom: Item routed to the wrong physical zone.

Likely Cause: The target bin is missing its Warehouse Class Code, or the Item Card lacks an explicit restriction code. If the class field is blank on both sides, the engine assumes open compatibility.

Next Action: Re-verify the relationship between your SKU records and physical Bin Content tables.

Symptom: No suggested bin generated on the put-away document.

Likely Cause: The Put-away Template has run out of fallback lines, or your maximum cubage/weight restrictions are set too tightly, leaving no eligible space.

Next Action: Check if "Allow Floating Bins" is toggled on, or audit recorded physical dimensions.

Symptom: Lot numbers are dropped or missing on the put-away lines.

Likely Cause: The Item Tracking Code is misconfigured, allowing the inbound document to post without validating warehouse tracking fields.

Next Action: Correct the inbound capture workflow before allowing warehouse operators to register physical stock movements.

Six Operational Scenarios to Test Before Go-Live

Never push an advanced warehouse configuration live without executing these physical sandbox validation scripts:

  1. 01

    The Multi-Lot Delivery

    Receive two distinct lot numbers of the same item on a single inbound order and confirm that both lot identities map perfectly to separate put-away tracking lines.

  2. 02

    The Segregation Block

    Attempt to manually register a put-away of a chilled item into an ambient zone bin to verify that the system correctly restricts and triggers an error block.

  3. 03

    The Overflow Fallback

    Completely fill a preferred, high-ranking fixed bin in the system and verify that the put-away template dynamically routes or splits the remaining balance into an eligible floating bin.

  4. 04

    The Mobile Bin Deviation

    Change a suggested system destination directly on the floor using a supported warehouse split-line process, then verify that the final registered item ledger matches physical placement.

  5. 05

    The Ledger Reconciliation

    Register a complex put-away document and run an immediate physical count audit on the bins to ensure Business Central’s inventory tables perfectly match real-world counts.

  6. 06

    The Downstream FEFO Pick

    Perform an outbound sales order pick for an expiry-controlled item to confirm that your picking configurations accurately pull the oldest lot, independent of how it was originally put away.

Where Standard Business Central Ends—And Where Orca Warehouse Begins

Microsoft Dynamics 365 Business Central provides a highly dependable architectural framework for advanced warehousing. However, executing multi-zone rules and lot tracking via printed paper sheets or clunky desktop browser terminals introduces immediate data latency and human error to a busy warehouse floor.

If your warehouse configuration is fundamentally sound but your distribution teams are struggling with data delays, paper instructions, or exception handling, you need an operational execution layer built for fast-moving environments.

At Orca Business Solutions, we bridge this operational gap by deploying hardware-native mobile barcode workflows designed specifically for mid-market UK wholesalers. Our Orca Warehouse WMS module extends standard Business Central logic straight onto rugged handheld scanning units, giving you:

barcode_scannerInstant GS1 Barcode Scanning

Capture item numbers, quantities, lot variations, and expiration dates simultaneously at goods-in, eliminating manual keyboard errors.

alt_routeReal-Time Exception Rerouting

If an operator finds a directed bin is physically blocked or full, they can declare an immediate exception on their scanning gun. Orca recalibrates your put-away template rules instantly, serving a valid alternative path without forcing the user to log into a desktop terminal.

syncUnified Multi-Channel Syncing

By unifying Business Central, Orca Warehouse, and Orca Commerce, your live available inventory counts update across your B2B trade portals the second a put-away is registered, entirely removing backorder friction.

Frequently Asked Questions

Need help with complex warehouse operations in Business Central?

Orca helps wholesalers and distributors review warehouse configuration, improve processes and explore additional WMS capabilities where needed.