Dynamics 365 SCM 2026: Single-Scan ASN Transfer Receipts in Warehouse-Only Mode

For enterprise IT administrators and supply chain architects running hybrid ERP stacks, this update closes an important workflow gap. Warehouse-only mode is designed for organizations that run Dynamics 365 Supply Chain Management as a dedicated warehouse execution system connected to external ERPs or order-management platforms. Bringing single-scan, ASN-backed transfer order receiving into WOM means inter-warehouse replenishment in integrated environments can rely on pre-defined packing structures instead of repetitive dockside data entry.

What Changed in Dynamics 365 Supply Chain Management​

At the core of the update is how Dynamics 365 Supply Chain Management consumes and acts on advance shipping notices during transfer order receipts in warehouse-only mode. An ASN provides advance information about an arriving delivery, carrying the shipment's packing structure—including the license plate identifier, cases, items, and quantities—before the physical pallets cross the threshold.

With this capability enabled, the receiving workflow shifts from manual item verification to structural confirmation:

• Single License Plate Scan: Warehouse personnel scan a single license plate barcode associated with an inbound ASN to receive the transfer order in warehouse-only mode.
• ASN-Based Packing Structures: Because the packing hierarchy is already defined within the ASN, the system uses that pre-populated structure to register the receipt rather than forcing the operator to enter individual lines manually.
• Admin-Controlled Enablement: Microsoft notes that the capability is enabled for end users by administrators, makers, or marketers/analysts, and runs on the web platform within Worldwide (Standard Multi-Tenant) cloud instances.
• Release Timeline: Following a preview phase that began in April 2026, the feature reached general availability in June 2026 and is now officially marked as launched on the Microsoft roadmap.

While Microsoft states that the feature speeds up inbound shipment processing, reduces manual steps, and improves accuracy, the roadmap entry does not publish specific benchmark numbers or percentage time savings. In practice, the operational payoff depends on whether upstream shipping sites or external systems transmit clean, accurate ASN packing structures before the truck arrives.

Section Summary: Dynamics 365 Supply Chain Management now supports single-scan license plate receiving for transfer orders in warehouse-only mode by reading the packing structure embedded in an advance shipping notice.

How Warehouse-Only Mode and ASN Receiving Fit Together​

Why does this specific combination—transfer orders, ASNs, and warehouse-only mode—matter so much to enterprise IT teams? In a standard, monolithic Dynamics 365 deployment, when one warehouse Management (WMS)-enabled site ships a transfer order to another, the system automatically generates an ASN. When the receiving worker scans the incoming license plate ID on the Warehouse Management mobile app, the contents tied to that ASN are physically registered at the inbound dock.

However, many large enterprises do not run a single ERP across every subsidiary, acquisition, or regional distribution center. Microsoft introduced Warehouse management only mode so companies could deploy Dynamics 365's warehouse module as a standalone WMS while keeping financial ledgers, purchasing, or legacy order management in an external system.

Core Prerequisites for Warehouse-Only Mode​

According to Microsoft Learn documentation on enabling and configuring Warehouse management only mode, organizations must meet specific system baselines before they can run WOM workflows:

1. Application Version: The environment must run Microsoft Dynamics 365 Supply Chain Management version 10.0.36 or later. The feature is turned on in Feature Management, and starting with version 10.0.47, Warehouse management only mode is mandatory and cannot be turned off.
2. Source System Records: Administrators must configure at least one external system under Warehouse management > Setup > Warehouse management integration > Source systems. Every incoming integration message from the external platform must include a source system name that exactly matches the configured record.In Fact, WOM-related menu items cannot even be searched or accessed until at least one source system record exists in the user's default company.
3. Number Sequences and Master Data: If external order numbers do not match internal numbering, admins must configure dedicated WOM number sequences under Warehouse management > Setup > Warehouse management parameters > Number sequences (such as Inbound shipment order, Outbound shipment order, and Shipment receipt). Master data—including released products and item model groups—along with business events and optional inventory owner or status mappings must also be synchronized.
4. Automated Background Jobs: Creating a source system automatically provisions background processes, including message processors for product master data and shipment orders (running every minute by default) and inventory update log publishers (running every 10 minutes by default).

Importing Structured ASN Data​

When an external system or vendor sends shipment data into Dynamics 365 Supply Chain Management, Microsoft Learn documentation explains that inbound ASNs are consumed using composite data entities—specifically Inbound ASN V3 or Inbound ASN V5—commonly via asynchronous XML file imports.

These composite entities assemble the shipment hierarchy across six child entities:

• Inbound load header (WHSInboundLoadHeaderEntity)
• Inbound shipment header (WHSInboundShipmentHeaderEntity)
• Inbound load packing structures (WHSInboundLoadPackingStructureEntity)
• Inbound load packing structure cases (WHSInboundLoadPackingStructureCaseEntity)
• Inbound load packing structure case lines (WHSInboundPackingStructureCaseLineV3Entity)
• Inbound load packing structure lines (WHSInboundLoadPackingStructureLineV3Entity or V5Entity)

Microsoft Learn notes two critical rules for ASN imports: the items must be enabled for warehouse management processes (WMS), and the corresponding purchase order or inbound shipment order must already be registered in the system before the ASN can be received. Furthermore, only the Inbound ASN V5 entity supports inbound shipment orders via the MODULE="InboundShipmentOrder" attribute, where the ORDERNUMBER value must match the external source system's order number.

After importing an ASN file, warehouse administrators can verify the structure in the web client by navigating to Warehouse management > Loads > All loads, opening the created load, and selecting Packing structure in the Receive group on the Ship and receive tab of the Action Pane. From there, the Pallets, Cases, and Items FastTabs reveal the exact license plates and quantities parsed from the XML payload.

Section Summary: Warehouse-only mode relies on synchronized source systems, version 10.0.36+ (mandatory from 10.0.47), and structured composite data entities to translate external shipment notices into scannable license plate hierarchies.

Critical Configuration Settings: Splitting Receipts and ASN Cleanup​

Getting a barcode scan to register on a mobile device is only half the battle; what happens in the background determines whether dock workers stay productive or get stuck staring at a spinning loading icon. Microsoft Learn's configuration guide for the transfer order receiving process highlights two parameters under Warehouse management > Setup > Warehouse management parameters (located on the General tab's Receiving FastTab) that directly govern how transfer order receipts and ASN records behave.

Why ASN Cleanup Timing Can Make or Break Partial Receipts​

The Transfer order receiving ASN cleanup parameter deserves special attention from systems administrators when rolling out ASN-based transfer order receiving. Under the Default setting, Supply Chain Management deletes associated ASN data when any of the following events occur:

• Putaway work is created or canceled.
• Mobile application receiving completes (when the work policy is set not to create work).
• Transfer order line registration occurs from the web client.
• A transfer order receipt is posted.

What happens if a shipment arrives with multiple license plates on a single transfer order, and your team processes a partial receipt using both the Warehouse Management mobile app and the web client? Under the default rules, registering a line in the web client or posting a partial receipt can prematurely wipe out the remaining ASN data before the rest of the pallets are scanned. Switching the parameter to On transfer order status received ensures the ASN data is only deleted upon putaway work creation/cancellation, no-work mobile receiving, or when the overall transfer order status updates to Received.

Mobile Device Menu Item Nuances​

Administrators also need to keep their mobile device menu items straight under Warehouse management > Setup > Mobile device > Mobile device menu items. Microsoft Learn documentation distinguishes between several inbound work creation processes:

• License plate receiving (and put away): Receives (and optionally puts away) an inbound ASN using the license plate ID. In WOM setup, Microsoft notes that mobile inbound shipment registration processes require an inbound load.
• Transfer order item receiving (and put away): Microsoft Learn explicitly warns that these older item-receiving menu items should only be used when goods were shipped from a warehouse that is not enabled for WMS.

Confusing legacy item-by-item transfer receiving menu items with ASN-driven license plate receiving is a common configuration trap during warehouse rollouts.

Section Summary: Tuning the Transfer order receiving process and Transfer order receiving ASN cleanup parameters prevents mobile app lag during financial posting and protects ASN records from premature deletion during split or partial receipts.

Practical Verification Checklist for IT and Warehouse Admins​

If your organization is adopting the new WOM transfer order ASN receiving workflow in Dynamics 365 Supply Chain Management, use this step-by-step verification plan in a sandbox environment before enabling it on the warehouse floor:

1. Verify Environment Version and Feature State: Confirm your Dynamics 365 Supply Chain Management environment is updated (10.0.36+ required for WOM; 10.0.44+ required for ASN cleanup controls; 10.0.47+ makes WOM mandatory) and ensure the WOM ASN transfer order receiving update is enabled for users by your administrators.
2. Audit Source System and Load Generation: In Warehouse management > Setup > Warehouse management integration > Source systems, verify that your external ERP or shipping warehouse system is properly mapped and generating inbound loads with valid ASN packing structures.
3. Inspect the Packing Structure Before Scanning: Open Warehouse management > Loads > All loads, select an inbound test transfer load, and click Packing structure on the Ship and receive tab. Confirm that the target license plate numbers, cases, and item quantities populate accurately.
4. Review Receiving FastTab Parameters: Go to Warehouse management > Setup > Warehouse management parameters, open the General tab, and check the Receiving FastTab. Consider setting Transfer order receiving process to Split the registration and receiving for all flows so dock workers aren't delayed by background cost updates, and set Transfer order receiving ASN cleanup to On transfer order status received if your operations involve partial receipts across web and mobile clients.
5. Test the Handheld Scan: Log into the Warehouse Management mobile app using a worker account assigned to the appropriate license plate receiving menu item, scan the test license plate barcode, and confirm that registration and putaway work creation proceed according to your warehouse work templates.

By bridging ASN packing structures with single-scan license plate receiving in warehouse-only mode, Microsoft has removed an unnecessary layer of manual dock work for multi-system enterprises. If you are managing Dynamics 365 Supply Chain Management integrations or tuning mobile device menu items across distributed warehouses, head over to our Enterprise IT and Dynamics 365 discussion boards on WindowsForum.com to share how your receiving workflows are holding up.