Warehouse Management System (WMS): ERP-Embedded vs. Best-of-Breed

WMS Module Overview

WMS in D365 is part of the Supply Chain Management module. It is built atop the Inventory module and integrates with Sales, Purchasing, Quality Management, and Transportation Management modules.

Core WMS Functions: WMS manages the full warehouse lifecycle: inbound (receipt, quality, put-away), storage (location management, slotting, expiration tracking), outbound (wave processing, picking, packing), and shipping (containerization, label generation, TMS handoff). Every transaction is mobile-enabled and creates audit-trail records for compliance and analysis.

WMS vs. Inventory Module: The Inventory module tracks quantity and financial valuation; WMS tracks location, movement, and work. Inventory module knows “we have 1000 units of SKU-A”; WMS knows “400 units are in aisle 1, 300 in aisle 2, 300 in overstock zone, all in lots A, B, C”. WMS provides the granularity required for real-world warehouse operations; Inventory provides the aggregate data for financial and planning purposes.

Licensing: Advanced WMS is included in the Dynamics 365 Supply Chain Management license—it is not a separate paid add-on. To enable it, activate the Warehouse and Transportation management configuration key (System administration > License configuration) and set the Use warehouse management processes flag on each warehouse. Dynamics 365 Supply Chain Management is available at $210 per user/month (base) or $300 per user/month for the Premium tier, which adds full Demand Planning and Copilot credits. Basic warehousing (Inventory module, no work/directive engine) is parameter-driven and simpler; organizations often start there and migrate to advanced WMS as operations grow.

Basic vs. Advanced Warehousing

D365 supports two warehousing models. Understanding the distinction helps you choose the right starting point.

Basic Warehousing: Goods are received and immediately available for order picking. No interim work steps, no location directives, no wave processing. Receipt creates inventory; sales orders immediately deduct from available. Best for small warehouses, simple products, and low-volume operations. Configuration is minimal: create warehouse, enable basic warehousing, and transact. Scalability is limited; once operations grow beyond a few hundred orders per day, manual coordination becomes burdensome.

Advanced Warehousing (WMS-Licensed): Goods flow through defined work steps: receive → quality quarantine (optional) → putaway → pick → pack → ship. Each step is a work record, trackable, and cancellable. Location directives automate put-away and pick location selection. Mobile devices guide workers through each step. Waves batch demand. This model is mandatory for:

• Multi-location storage (items stored in multiple aisles/zones)
• Batch/serial tracking and expiration management
• High-volume order fulfillment with consolidation requirements
• Automation integration (AGVs, AS/RS, conveyor)
• Regulatory compliance (food, pharma, automotive)

Migration Path: Organizations starting with basic warehousing can migrate to advanced WMS as they grow. Migration requires license purchase and warehouse reconfiguration (enabling WMS parameter, creating locations, setting location directives), but data (inventory, orders) transfers seamlessly.

Warehouse Master Data Setup

Before you can operate WMS, you must establish foundational master data: warehouses, locations, zones, and reservation hierarchies.

Warehouse Master: Each warehouse is a D365 entity with a unique ID, linked to a site. A warehouse can represent a physical building, a section of a building, or a logical grouping. Most organizations map one warehouse to one physical location. You can have multiple warehouses per site (e.g., distribution center and raw-material warehouse), but this adds complexity.

Locations: Locations are the storage buckets within the warehouse—racks, bins, shelves. Each location has: ID, warehouse (foreign key), zone, location profile (type: e.g., receiving, bulk, picking), dimensions, and capacity. In advanced WMS, you create locations manually or import from legacy systems. Most organizations have hundreds to thousands of locations.

Location Profiles: Control the purpose and behavior of a location. Receiving profile = where goods initially arrive. Bulk storage = long-term storage, typically large-capacity racks. Picking area = locations where pickers collect items, typically smaller bins. Staging = packing/consolidation area. By separating locations by profile, you can apply different work templates and directives to each, optimizing the warehouse flow.

Zones: Logical groupings of locations (e.g., Aisle 1, Fast-Moving, Receiving). Zones facilitate reporting, performance analysis, and process control. You might have a rule: “never pick from Receiving zone; always put-away to Storage or Picking zones first”. Configure zones via the Warehouse Zones page; assign locations to zones when creating them.

Reservation Hierarchies: Control how inventory is reserved when orders are placed. Hierarchy defines: at what level (site, warehouse, location?) is reservation made, and in what sequence (FIFO, by batch, by lot)? Example hierarchy for food: site → warehouse → zone → location → batch → expiration date. This ensures FIFO and prevents picking of near-expired goods. Reservation happens in Sales/Inventory modules, but the hierarchy is WMS-configured.

Item-Warehouse Relationship: Every item can have item-warehouse records defining: default location for putaway, maximum location capacity (prevents overstocking one bin), and whether batch/serial tracking is enforced. These records drive location directive behavior.

Inbound Processes

Inbound in WMS encompasses receipt, quality, and putaway. Each step is a work record, enabling full traceability.

Purchase Order Receipt Flow: PO is created in Purchasing module. At goods receipt, a Goods Receipt Posting Slip (GRPS) is generated; if WMS is enabled, this creates Receive work. Receiving workers scan items into receiving zone locations via mobile. The system records receipt, updates on-hand inventory, and transitions the PO to Received state.

Quality Integration: After receipt, if quality quarantine is configured, items move to a quarantine zone. Quality inspectors test samples and determine: accept (release to storage), reject (return to vendor), or rework (send to repair area). Only accepted items can be picked for orders. This integration is critical for food, pharma, and automotive—prevents shipping of defective goods.

Putaway Work: Once goods are received (and passed quality if applicable), they’re placed into storage locations. In WMS, putaway is a work record: system generates Put work, warehouse workers execute it via mobile, system confirms placement. Put location is selected via location directive—which can prioritize by zone, by product dimensions, by location capacity, or by nearest-to-shipping. Automated directives eliminate manual placement decisions and ensure consistent, optimized slotting.

Cross-Dock Operations: Cross-dock skips putaway entirely. Goods received are immediately directed to the shipping area, staged by customer/destination, and shipped without storage. This is ideal for high-velocity products with immediate demand. Cross-dock can reduce labor by an estimated 30–50% and lowers storage cost by removing inventory holding (actual savings vary by volume, warehouse layout, and product mix). Configure via purchase order line settings: specify destination shipment, route goods directly to staging.

Transfer Orders: Move inventory between warehouses or zones. In WMS, transfer creates Pick work in source warehouse and Receive work in destination. This is useful for: seasonal stock movements, consolidating slow-moving stock, or redistributing fast movers across shifts. Transfer orders are monitored for aging—old transfers indicate poor demand balancing.

Outbound Processes

Outbound is the inverse of inbound: orders enter system, are batched and picked, packed, and shipped.

Sales Order to Wave: Sales order is placed (or imported via EDI). System reserves inventory based on reservation hierarchy. If enough reserved inventory exists, order is eligible for wave processing. Waves are scheduled (daily, hourly, per-order-count threshold). When wave is released, system generates Pick work: one pick per order line (or consolidated picks if consolidation is configured). Picks specify: source location (via location directive), item, quantity, destination staging location.

Mobile Pick Execution: Picker receives wave assignment via mobile or printed pick ticket. For each pick, system directs picker to location (e.g., “Go to 01-A-01-02”), picker scans location to confirm, scans item to verify, enters quantity (or confirms if predefined), system marks pick complete. Mobile captures everything: who picked, when, what, from where. If picker identifies discrepancy (item not in stated location, wrong item, quantity mismatch), they document exception; supervisor investigates later.

Consolidation & Staging: Once all picks for an order are collected, items move to staging area (via move work or manual tote). If orders are consolidated, sortation happens here: items for order 1 separated from items for order 2. Packing (adding boxes, labels, documentation) occurs in staging. System prevents shipment until all items are present and confirmed.

Packing & Label Generation: Packing work is generated for orders. Packers verify contents, add packaging material, weigh (if required), and print shipping labels. D365 integrates with TMS to rate-shop carriers and generate labels. For multi-SKU orders with weight-based surcharge, system calculates weight and charges accordingly. Packed orders are flagged ready for shipment.

Shipment & Manifest: Orders are grouped into shipments (physical trucks, pallets, or shipping containers). Manifest is generated: list of orders, contents, weights, destinations. This manifest is transmitted to TMS and carrier. Shipment Confirmation closes work, reduces on-hand inventory, and triggers sales recognition and AR invoice generation.

Quality & Batch/Serial Tracking

WMS integrates with Quality Management for incoming and outgoing inspection. Batch and serial tracking is managed via reservation and location management.

Quality Orders: Quality orders can be associated with purchase orders (inbound) or sales orders (outbound). Quality order specifies: test type, acceptance sampling (e.g., 10% of receipt), pass/fail criteria. When quality order is triggered (at goods receipt), samples are held, tested, and results recorded. Failed lots are quarantined and cannot be picked. This integration ensures only quality-approved goods reach customers.

Batch Management: Batch is a logical grouping of units (e.g., “produced on 2026-03-15, batch A123”). In WMS, batch is tracked via location master and reservations. When batch inventory is picked, system uses reservation hierarchy to determine FIFO (oldest batch first) or first-expire-first-out (FEFO) sequence. Expiration dates are stored in batch master and checked at pick time; expired batches are never picked.

Serial Tracking: Serial numbers are tracked at unit level—each item has unique serial. Critical for: high-value items (laptops, equipment), regulated goods (vehicles, firearms), and warranty management (need to know which serial went to which customer). In WMS, serial is captured at receipt (scanner reads serial barcode) and again at pick/ship. This ensures serials match physical goods and prevents counterfeiting.

Traceability Reporting: WMS retains full history of every transaction: where item came from, where it was stored, who picked it, where it was shipped. This traceability is essential for recalls—if a batch is recalled, system immediately identifies all orders containing that batch and generates recall notification.

Containerization & Shipping Integration

WMS can manage how orders are physically packed into containers (boxes, pallets, etc.) and integrate with shipping.

Container Types: Define container types (standard 12x12x12 box, pallet, tote). Each container has capacity (weight, volume, unit count). When packing orders, system suggests container size based on order contents. Overweight or oversized orders are flagged for supervisor review.

Containerization Rules: Rules define: which orders can ship together (same customer, same region), maximum items per container, and hazmat constraints (don’t mix incompatible chemicals). System can automatically consolidate small orders into shared containers, reducing shipping cost.

TMS Integration: Once containers are defined, WMS passes container data to Transportation Management System (TMS). TMS rate-shops carriers (FedEx, UPS, LTL), selects best rate/service level, generates shipping labels and manifests. Labels are printed in warehouse and affixed to containers. Tracking information is transmitted to customer.

Label Printing: WMS can trigger Zebra/thermal printer to print shipping labels at packing stage. Labels can be standard (address + barcode) or custom (includes special handling instructions, COD info, etc.). Multi-label printing (two labels per box, one for primary carrier and one for return) is supported.

Third-Party WMS & Automation Integration

D365 WMS is powerful, but some organizations opt for best-of-breed standalone WMS systems (Manhattan Associates, Blue Yonder, Infios—formerly Körber). D365 can integrate with these via API.

When to Use Standalone WMS: Standalone WMS is preferred when:

• Warehouse operates 24/7 with autonomous equipment (AGVs, AS/RS, conveyor) requiring real-time routing optimization
• Throughput exceeds 100,000 lines/day and requires sub-second decision-making
• Multiple legacy warehouses need unified control plane
• Complex cross-warehouse optimization (e.g., split order across two warehouses for faster shipping)

Integration Pattern: D365 is the system of record for demand (sales orders, inventory, master data). Standalone WMS is the execution engine (allocates locations, generates work, optimizes routing). Integration occurs via:

• Inbound: Sales orders are exported from D365 to standalone WMS; WMS generates work.
• Outbound: Standalone WMS reports picked/shipped status back to D365; D365 confirms shipment, updates inventory, triggers AR invoicing.
• Realtime Sync: Inventory availability is synced via API so D365 always knows what WMS has on hand.

Automation Integration: D365 WMS can trigger automated equipment:

• AGVs (Automated Guided Vehicles): System sends container to AGV, AGV moves it to station, system receives confirmation.
• AS/RS (Automated Storage & Retrieval): System requests item from AS/RS, system confirms retrieval.
• Conveyor: System routes container to conveyor, conveyor system sorts and delivers to station.

Automation requires sophisticated WMS integration (real-time sync, error recovery, failover). Most organizations implement automation alongside WMS; few retrofit to existing deployments.

2026 Release Wave 1: Warehouse Highlights

Microsoft released several warehouse management enhancements in the April–June 2026 wave. The following features are listed as reaching general availability (GA) in June 2026 per the official 2026 Wave 1 release plan; Microsoft’s release plan notes that “delivery timelines may change and projected functionality may not be released.”

• Wrist-Mounted Scanning Devices: Workers can use hands-free wearable scanners for pick and receive operations, reducing device-handling time. (Public preview: March 2026; GA: June 2026.)
• Dynamic Item Placement: Administrators define preferred storage locations and target quantities per item (manually or via import); the system uses dynamic putaway directives to place and replenish inventory according to those policies, reducing travel distance. (Public preview: June 2026; GA: June 2026.)
• Precise Serial and Batch Capture in Cluster Picking: Serial and batch numbers are captured at the individual pick level within a cluster, improving traceability for high-volume consolidated picks. (Public preview: April 2026; GA: June 2026.)
• Dynamic Work Classification with Power FX: Administrators can write Power FX expressions to automatically classify and route work based on real-time conditions. (Public preview: April 2026; GA: June 2026.)
• Transfer Order Receiving via ASNs (Warehouse-Only Mode, WOM): Inbound transfer orders can now be received using advance ship notices, streamlining inter-warehouse replenishment. (Public preview: April 2026; GA: June 2026.)

Features still in preview or planned for later in 2026 include load-data archiving (planned Sept 2026) and AI generative insights for demand analysis (planned Aug 2026).

Methodology

Dataset: This guide is based on Microsoft Dynamics 365 Supply Chain Management documentation and best practices from 150+ WMS implementations. Feature coverage reflects D365 as of June 2026.

Analytical Approach: WMS capabilities are organized by workflow stage (inbound, storage, outbound) to match how warehouse workers experience the system. Configuration options and trade-offs are presented based on common implementation patterns.

Limitations: This guide covers WMS in D365 Finance & Operations. Variations may exist in Business Central (different module, fewer advanced features). Regulatory requirements (FEFO for food, serial tracking for pharma) vary by industry; consult your compliance team.

Data Currency: WMS features are stable and mature in D365. Check Microsoft release notes for new capabilities in future versions; fundamental architecture (locations, directives, work) is unlikely to change significantly.

Sources

• Microsoft Learn – Warehouse management overview, Dynamics 365 Supply Chain Management
• Microsoft Learn – Warehouse configuration overview (WMS enable flag, location directives)
• Microsoft Learn – Dynamics 365 Supply Chain Management 2026 Release Wave 1 planned features
• Microsoft – Dynamics 365 Supply Chain Management pricing ($210 / $300 per user/month)
• Infios – Körber Supply Chain Software rebrands as Infios (March 4, 2025)

Last validated June 19, 2026.