TL;DR
Dynamics 365 warehouse spatial location adds X, Y, Z coordinates and can sequence picking by travel distance. That is real, and it is routing, not slotting. Here is the difference.
Answer first
No, Dynamics 365 warehouse spatial location does not do slotting. It is a genuine and useful advance, but it solves routing, not placement. It lets you assign X, Y, and Z coordinates to your locations and then sequence a picker's work by actual travel distance. That shortens the trip between locations you already chose. It does not decide where inventory should live, and it is currently a preview capability, which Microsoft labels as not for production use.
What spatial location actually adds
For most of the history of ERP-based warehouse systems, the system knew what inventory existed and which location it was in, but it had no sense of the warehouse as a physical space. It could not tell that location A-01 and location A-02 are next to each other while A-01 and Z-40 are a long walk apart. Location codes are labels, not coordinates.
Spatial location changes that. By assigning coordinates to each location, Dynamics can calculate the real distance between them and sequence picking work to reduce walking. That is a real step forward, and it is fair to call it one of the more meaningful additions to Dynamics warehouse management in a while.
Why it is routing, not slotting
The distinction is precise and worth getting right. Spatial location works on the sequence of a trip. Given that a picker must visit a set of locations, it orders those visits to minimize travel. That is the definition of routing.
Slotting is the upstream question: which locations should hold which items in the first place. Spatial location does not touch that. It takes your placement as given and makes the walk through it more efficient. If your fast movers are badly placed, spatial location will route you between them more cleverly, but they are still badly placed.
Put simply: routing shortens the trip, slotting removes it. Spatial location is a routing feature, and a good one.
The current limits, stated plainly
Because this comes up, and because being exact is the point: as it stands, spatial location is a preview capability. Microsoft's own documentation notes it is not meant for production use. Coordinates are also entered by hand, location by location, which for a facility with thousands of locations is a real data-entry effort. And it sequences picking work, rather than deciding placement.
None of this is a criticism of the feature. It is doing what it was designed to do, and doing it well. It is simply solving a different problem from the one that determines where your inventory should live.
The takeaway
If you are evaluating spatial location, evaluate it as what it is: a way to make picker trips shorter over your existing layout. That is worth having. Just do not expect it to answer the placement question. The decision of where each item should live, derived from your order history and kept current, sits above the routing layer, and it is still the larger lever.
Share this article
The mechanism behind these articles, applied to the warehouse you already run.
Mudassir Marwat
Founder & CEO, Cognilium AI
Mudassir Marwat
Founder & CEO, Cognilium AI
Mudassir Marwat's argument is that ERP systems record decisions they never optimise.


