Is Dynamics 365 WMS fast enough for a high-volume distribution centre?

Is Dynamics 365 WMS fast enough for a high-volume distribution centre?

Microsoft has answered this in public, repeatedly, without publishing a benchmark. Its deprecation register deprecates warehouse surfaces, names performance as the reason, and ships replacements it describes as significantly faster. The question is not whether the product is fast enough — it is whether you still run the pages it deprecated.

The answer is in the deprecation notices, and it is Microsoft's own word three times

Removed or deprecated features in Dynamics 365 Supply Chain Management (ms.date 2026-06-24) is not marketing. It is a dated register of what stops working, and its warehouse entries give the same reason three times, in the Reason for deprecation or removal field:

• Load planning workbench [DEPR] — "The Load planning workbench page has performance issues."
• Release to warehouse page [DEPR] — "The Release to warehouse page has performance problems."
• Inventory transactions support for internal warehouse operations [DEPR] — "Using inventory transactions to track on-hand inventory for internal warehouse operations has well-known performance problems."

A vendor writing "well-known performance problems" about its own shipped behaviour is stronger evidence than any benchmark — the slow parts were identified and replaced.

The replacements are in the same register. The load planning workbench "has been split into two new workbench pages, which together provide equivalent functionality with significantly improved performance", and the release page likewise "split into two new release to warehouse pages".

So if your DC is slow on those screens, the first question is which version and which page — not whether the platform scales.

Deprecated and removed are different words, and the page defines both

• Removed — "A removed feature is no longer available in the product."
• Deprecated — "A deprecated feature isn't in active development and might be removed in a future update."

Deprecated means two things at once: no new development, and no guarantee about when it goes. Neither definition says anything about it being switched off today — the assumption that turns a deprecation notice into a panic.

The warehouse register, with each entry's exact status wording

The artefact worth keeping. The removal language is not uniform, which is the whole reason to read the field rather than the heading.

• Load planning workbench — Release: 10.0.39 · What the Status field actually says: "Deprecated." Now "hidden in the app", re-enablable via Support, and "will be completely removed from the product one year after the release of Supply Chain Management version 10.0.39"
• Scale unit capability — Release: 10.0.40 · What the Status field actually says: "paused for new customers since July 2022", "formally deprecated as of Supply Chain Management version 10.0.40 and will be completely removed for all customers one year after the release of that version"
• Release to warehouse page — Release: 10.0.41 · What the Status field actually says: "Deprecated." Now "hidden in the app", re-enablable via Support, and "removed from the product one year after the release of Supply Chain Management version 10.0.41"
• Inventory transactions for internal warehouse operations — Release: 10.0.41 · What the Status field actually says: "Supported until version 10.0.40." Deprecated as of 10.0.41; "Approximately one year after the release of version 10.0.41, support for this scenario is removed and all customers are required to move to" warehouse-specific inventory transactions
• Adjustment out must use process guide — Release: 10.0.43 · What the Status field actually says: The setting "is mandatory starting in Supply Chain Management version 10.0.45. Approximately one year after the release of version 10.0.45, the non-process guide implementation is no longer supported and might eventually be removed from the product"
• Spot cycle counting must use process guide — Release: 10.0.43 · What the Status field actually says: Default in 10.0.45, "mandatory in version 10.0.47", and one year after 10.0.47 the old implementation "is no longer supported and might eventually be removed from the product"
• Work creation number number sequence — Release: 10.0.43 · What the Status field actually says: Replaced by Work creation ID; "it's no longer used by the system and production data doesn't include the Work creation number number sequence"
• Service-based authentication for the Warehouse Management mobile app — Release: 10.0.37 · What the Status field actually says: "Removed. As of July 15, 2024, Microsoft discontinued support for using service-based authentication methods (certificate and shared secret) to connect the Warehouse Management mobile app to Supply Chain Management"

Read the two process-guide rows against the rest. Sort the eight by what the Status field commits to and there are four classes, not two:

• Already removed, flatly: service-based authentication — "Removed.", with a date in the past.
• Commits to removal: load planning workbench and scale units ("will be completely removed"), the release to warehouse page ("removed from the product one year after"), and inventory transactions ("support for this scenario is removed").
• Commits only to unsupported: both process-guide rows say the old implementation "might eventually be removed" — materially weaker, and the honest thing to quote when someone asks whether it is gone.
• Neither: the work creation number sequence — a replacement note, not a removal.

What this table is and is not. Every warehouse-area entry on that page as fetched on its ms.date of 24 June 2026 — not the full history. The page links an archive of previous releases, which this article did not open, so nothing here claims what was removed before 10.0.15.

Hidden is not removed, and Support can turn two of them back on

Both workbench-style pages carry the same arrangement, easy to miss:

"The Release to warehouse page is now hidden in the app, but you can enable it if necessary by contacting Microsoft Support."

The same sentence appears for the load planning workbench — a middle state between shipped and gone: present, hidden, re-enablable through a support case.

Useful, and a trap: a site can run a deprecated page because someone asked for it back, and an upgrade can quietly remove it again. If either was re-enabled for you, the register's removal date is still your date.

Microsoft is direct: "We strongly recommend that you instead use the new pages … because they provide equivalent functionality with significantly improved performance."

The one that is a data-model change rather than a screen change

Two of those rows are pages — the load planning workbench and the release to warehouse page. The row a high-volume site should read twice is neither.

Inventory transactions support for internal warehouse operations is deprecated in favour of warehouse-specific inventory transactions, which "have been available since version 10.0.32". The status is staged:

"Supported until version 10.0.40. As of version 10.0.41, inventory transactions are deprecated for tracking on-hand inventory for internal warehouse operations. Existing customers can continue using this scenario after that version, but new features and bug fixes for this scenario are only implemented for warehouse-specific inventory transactions."

Then: "Approximately one year after the release of version 10.0.41, support for this scenario is removed and all customers are required to move to warehouse-specific inventory transactions."

Two consequences bear on scale. New features and fixes stopped arriving for the old mechanism at 10.0.41, so a fix you are waiting for may be shipping only to the other. And "all customers are required to move" is not a recommendation.

The scale-unit row points the same way. Its replacement is warehouse management only mode, which "replaces some of the functionality planned for scale units and adds many new architectural and integration possibilities."

Note some — Microsoft's word. Chapter 12 tests that mode properly.

How we optimize on top of this, and where we would draw the line

Pick-Path & Slotting Optimizer decides which orders travel together and which item earns which slot, writing the answer back into the wave, cluster and slotting objects Dynamics 365 executes, behind an approval step. Dynamics is the system of record; the optimization above it is a modelling problem.

A working demo exists; it is not off the shelf. We build it against your systems and your constraints on request, and we have no delivered warehouse engagements — so this is a capability, not a report on somebody's building.

One measurable thing you can get without us, from chapter 6: the Locations evaluated figure on a location directive acceptance test.

Microsoft writes: "For efficient warehouse operations, you should try to have as few locations as possible evaluated."

We would not answer a scale objection with a benchmark. We have no delivered warehouse engagements, any throughput figure would be invented, and this audience has run these buildings for years.

We would also not propose an optimizer as the fix for a deprecated page. If you release to warehouse through a page Microsoft deprecated for performance, the upgrade is the work; no model above it changes what that screen costs.

What to do this week

1. Find your version, then read the register from that version forward. Microsoft's steps: "after the dashboard loads, select the gear symbol at the upper right of the page and then select About" — update model versions in the automated build. Every row above is keyed to a release, so your version decides which are history and which are calendar.
2. Check whether anyone asked Support to re-enable a hidden page. If the load planning workbench or the old release page is visible, someone did — and the removal date applies.
3. Establish which inventory-transaction mechanism you run. The only row that is a data-model change rather than a screen — and fixes stopped arriving for the old one.
4. Run one location directive acceptance test and read Locations evaluated. The closest thing to a throughput number that comes from your configuration rather than a vendor claim.

About Cognilium Cognilium is the AI optimization layer for Dynamics 365 — complementary apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Built on Power Platform, Dataverse and Azure. https://cognilium.ai · https://www.linkedin.com/company/37180269/

If a scale objection is holding up a warehouse decision, book a fifteen-minute call and we will read the register against your version with you. No deck. https://cognilium.ai

Sources

• Removed or deprecated features in Dynamics 365 Supply Chain Management
• Warehouse-specific inventory transactions
• Warehouse management only mode overview
• Test location directives with acceptance tests
• Update model versions in the automated build — the gear symbol → About navigation

Sources

• learn.microsoft.com — removed deprecated features scm updates
• learn.microsoft.com — warehouse transactions
• learn.microsoft.com — wms only mode overview
• learn.microsoft.com — location directive acceptance tests
• learn.microsoft.com — version models build