What Dynamics 365 Warehouse Slotting Actually Does (And What It Doesn't)

Here is how Microsoft describes the feature, verbatim:

Read the three order statuses. Ordered. Reserved. Released. Every one of them is an open order, sitting in front of the warehouse right now.

That tells you what the feature looks at. It looks at the work in front of you. It does not look at your order history. There is no year of past orders feeding into it, no analysis of what tends to get picked together, no seasonality, no velocity trend. It reads the demand you have not yet fulfilled and it plans how to stage inventory to fulfil it.

The criteria it uses to assign a location confirm this. They are Assume empty, Consider qty, and Consider on-hand. Those are questions about capacity and occupancy. Does the location have room. How much is there already. They are not questions about distance, or about how often the item is picked, or about what else it ships alongside.

What the feature produces is a replenishment plan. It gets the right quantity of the right item into the pick faces you defined, ahead of the wave. That is genuinely useful.

If you know the product well, you are already forming the objection, so let me put it on the table before you do.

You can, in fact, steer slotting toward faster movers. The slotting template lines carry a query over your locations, and location directives carry their own queries. So if you maintain an ABC classification or a velocity field on your products, you can filter on it and push your A items forward. People do this, and it works.

Here is the honest distinction, and it is the whole point. Dynamics will neither compute that ranking for you nor decide the assignment. It executes a policy that a human derived somewhere else. In practice, that somewhere else is a spreadsheet. Someone exports order lines, builds a pivot table, ranks the SKUs, decides the moves, and types the result back into the system as a fixed policy.

That is real work, and it produces real results. But it is a point in time. Order profiles drift. The classification you loaded in March is describing a warehouse that no longer exists by September, and nobody has time to redo it monthly by hand.

Microsoft has been investing here, and it is worth being precise about what has arrived, because the marketing language and the feature detail say different things and you should read both.

There is a preview capability called warehouse spatial location. It lets you assign X, Y and Z coordinates to your locations, and it can sequence picking work by actual travel distance. That is a real advance. But read what it does: it sequences the trip between locations you already chose. It makes the walk shorter. It does not decide where the item lives, and it is still in preview, which Microsoft labels as not for production use. Coordinates are also entered by hand, location by location.

There is also a feature called dynamic item placement. Microsoft's business value paragraph says the system "intelligently balances inventory during inbound processes, ensuring optimal placement," and the release overview mentions "AI-driven inventory rebalancing." That sounds like the gap being closed. Then read the feature detail paragraph directly below it: "Define preferred storage locations and target quantities for each item, either by editing directly or importing data at scale."

Read the verb. Define. By editing, or by importing. Both paragraphs are accurate. They answer different questions. The first tells you what the outcome feels like. The second tells you who decides. Somebody still works out what the preferred locations should be.

Put it together and the shape is clear. Dynamics 365 will stage inventory to meet open demand, sequence a picker's trip, and faithfully hold a placement policy you give it. What it will not do is read your order history and work out, on its own and on a schedule, where each item should live so that the orders you actually ship are cheapest to fill.

You will have heard that travel is roughly half of a picker's time. It is a fair rule of thumb and I use it too. It is worth knowing where it comes from, though, because the whole industry repeats it as if it were a study. It traces to Edward Frazelle's book World-Class Warehousing, published in 1996 through his own consultancy. There is no disclosed sample or methodology behind the figure. It is directionally right, and it is a consultant's estimate, not a measurement. If you are going to build a business case on a number, it is worth knowing which kind of number it is.

Where the travel statistic comes from, traced to its source

If you are planning slotting work on Dynamics 365, the useful conclusion is this. The platform will execute placement well. It will not derive placement for you. So the first question is not which feature to turn on. It is who is deciding where your inventory lives, how often they revisit it, and whether the answer is still a spreadsheet from two quarters ago.

That is a question you can answer this week, with data you already have.