How-toMicrosoft Dynamics 365 Supply Chain ManagementWarehouse management only mode

Dynamics 365 Supply Chain Warehouse Only Mode: What It Is and Its Limits

Question
dynamics 365 supply chain warehouse only mode

Also searched as

  • d365 warehouse management only mode
  • d365 wms only deployment
  • d365 warehouse only mode limitations

Short answer

Warehouse management only mode is a Dynamics 365 Supply Chain Management configuration that lets you run the warehouse management processes while another system, such as a separate ERP, owns orders, pricing and finance. Source documents arrive as inbound and outbound shipment orders instead of sales and purchase orders, and the warehouse executes and reports back.

Applies to: Dynamics 365 Supply Chain Management. This is a feature enabled in Feature management, and its availability and scope depend on your release, so confirm in Microsoft's current documentation before committing.

Evaluate and enable warehouse only mode

  1. 1Decide that a separate system truly owns orders and finance, and that you want only warehouse execution from D365.
  2. 2Check Microsoft's current documentation for your release, including the feature's status and the list of supported and unsupported processes.
  3. 3Enable the Warehouse management only mode feature in Feature management in a sandbox first, and treat enabling as a one-way decision unless documentation says otherwise.
  4. 4Configure the warehouse as usual: warehouses, locations, location profiles, work templates, wave templates, directives and mobile device menus.
  5. 5Build the integration that feeds inbound and outbound shipment orders from the upstream system, plus the return flow of confirmations and inventory changes.
  6. 6Test receiving, picking, packing and shipping end to end, including partial receipts, short picks and cancellations from the upstream side.
  7. 7Plan inventory reconciliation between the two systems.

What changes in this mode

In normal operation a warehouse receives against purchase orders and ships against sales orders in the same database. In warehouse only mode the documents driving the floor are shipment orders created by your integration. Warehouse execution (waves, work, mobile app, license plates, containers) behaves like standard WMS, but pricing, costing and invoicing are not the job of this system.

The integration is therefore the project. Message design, error handling, ordering and idempotency decide whether the warehouse runs smoothly. D365 supports integration through data entities, OData, and the data management framework, and the choice depends on volume and latency.

Limits to plan around

Expect reduced finance and costing functionality, and verify each module you rely on, since not every process works without the full order-to-cash chain. Features that depend on sales orders, such as certain reservations and price-dependent logic, need individual validation.

Compare the alternative: running full Supply Chain Management for order handling and warehouse together. If your ERP is being replaced soon, warehouse only mode can be a bridge. If not, weigh the cost of maintaining the integration long term.

Integration patterns

Common patterns are a scheduled import of shipment orders through the data management framework, or event-driven calls from middleware to OData endpoints. Keep a clear mapping between upstream order IDs and shipment order IDs for reconciliation. See our page on the Supply Chain Management APIs for authentication and endpoint options.

Try it here, free

D365 Finance and Supply Chain License Cost Calculator

Open full tool

Estimate monthly, annual and term cost for D365 Finance and Supply Chain users, including attach licenses, team members and discount.

Common pitfalls

  • !Enabling the mode in production without confirming it is reversible for your release.
  • !Assuming every sales order dependent feature still works without sales orders.
  • !Underestimating the integration work, which is usually larger than the warehouse configuration.
  • !No agreed owner for inventory truth, leading to two systems with different on-hand.

How an ERP-grounded AI assistant handles this

Where two systems share a warehouse process, most pain is reconciliation. A grounded assistant can compare shipment confirmations against the upstream order status and surface mismatches for people to resolve. Netray builds such read-only reconciliation views, including on-prem next to the upstream ERP.

See ERPray

Frequently asked questions

What is warehouse only mode in D365 Supply Chain Management?

It is a deployment configuration that uses the warehouse management processes while an external system handles orders, pricing and finance. Work comes in as inbound and outbound shipment orders created by an integration.

Who should use warehouse only mode?

Companies that want D365's warehouse execution but keep another ERP for orders and finance, often during a phased migration or in a multi-ERP group. It is not for companies that want one integrated system.

Can I switch back to the full mode later?

Do not assume so. Treat enabling as a significant decision and verify reversibility in Microsoft's current documentation for your release before using it in production.

How does the upstream system send orders?

Through an integration, commonly data entities loaded with the data management framework or calls to OData endpoints, creating inbound and outbound shipment orders in D365.

Related

How-to

Dynamics 365 Supply Chain Wave Planning and Inventory Journals

In Dynamics 365 Supply Chain Management, a wave is a batch of shipment lines released to the warehouse together. A wave template defines which wave steps run (for example reserve, replenish, create work), and work templates plus location directives then turn the wave into pick work. Inventory journals are a separate tool: they post stock adjustments, movements, transfers and counts directly against on-hand without a sales or purchase order.

Advanced

Dynamics 365 Supply Chain Management API: OData, Custom Services and Data Packages

Dynamics 365 Supply Chain Management exposes three main integration routes: OData endpoints over data entities for record-level reads and writes, JSON custom services for X++ logic you expose as operations, and the data management package API for bulk import and export. All use OAuth 2.0 with a Microsoft Entra ID app registration.

How-to

D365 Recurring Integration: Enqueue, Dequeue and Ack Explained

Create a recurring data job on a data project, register an Entra ID application and authorize it in D365, then POST files to api/connector/enqueue/{activityId} to import, or GET api/connector/dequeue/{activityId} followed by an ack call to export. The job's activity ID in the URL ties your calls to the data project.

Error fix

Fixing "Cannot create a record in (table). The record already exists" in D365 F&SCM data entity imports

This is the standard kernel duplicate-key exception, thrown when the Data Management Framework tries to insert a staging row into a target table whose unique or alternate key already matches an existing record. It almost always means the entity's insert-vs-update logic did not recognize the target row as an update, not that you have a true accidental duplicate in your source file.

Error fix

Fixing "There are currently no batch servers available for processing" in D365 F&SCM

This message means the batch framework cannot find any AOS instance flagged as a batch server and available for the batch group the job is assigned to. The fix is almost always in server configuration (System administration > Servers) or batch group assignment, not in the batch job itself.

Error fix

Fixing "You do not have the following permissions on TableData (table): (permission)" in Business Central AL

This runtime error means the current user's assigned permission sets do not grant the required Insert, Modify, Delete, Read, or Execute right on that specific table. It is most common right after installing or updating a custom AL extension, because Business Central checks object-level permissions even for tables an extension owns.

AI for ERP

AI for Dynamics 365 Finance and Supply Chain beyond Copilot

AI for D365 Finance and Supply Chain beyond Microsoft Copilot: private LLM grounded on data entities and OData, on-prem-capable via Local Business Data.

Stuck on Microsoft Dynamics 365 Supply Chain Management?

Talk to engineers who work inside Microsoft Dynamics 365 Supply Chain Management every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software

TermsDynamics 365 Financial DimensionsWarehouse Management System (WMS)Dynamics 365 Business Central