
Bins, zones and bin types
Bins are the smallest container unit. Zones group them. Bin types (RECEIVE, PICK, PUTPICK, PUTAWAY, SHIP, QC) control which activities a bin allows.
Business Central runs a warehouse with bins, zones and directed put-away and pick. Finance & Operations adds a slotting engine that plans picking locations from open order demand before work is released. If you need that engine, Business Central does not have it.
But neither product decides which item belongs in which location, and that is the decision that determines how far your pickers walk.
11
capabilities compared, row by row
2
Microsoft docs every claim is read from
1
row where both products say no

Microsoft describes four levels of warehouse complexity in Business Central, from posting straight off orders up to directed put-away and pick, which is the most advanced configuration and the one that makes bin codes mandatory. At that level you get real warehouse machinery.

Bins are the smallest container unit. Zones group them. Bin types (RECEIVE, PICK, PUTPICK, PUTAWAY, SHIP, QC) control which activities a bin allows.

Put-away suggests higher-ranking bins first, picking takes from the highest-ranking bin content first, and replenishment works the other way. This is the closest thing Business Central has to a placement preference.

An item can have one or more fixed bins, so its content survives the bin being emptied. Put-away templates hold prioritised rules applied when put-aways are created.

Quantity, total cubage and weight limits per bin, plus warehouse class codes on items, bins and zones to control where something may be stored. FEFO picking is available for tracked items.
“In advanced warehousing, you can automate and optimize how to collect items in put-away and pick worksheets by ranking bins. Items are suggested for picks and put-aways based on the bin ranks.”
One detail worth knowing before you plan around it. The Shelf No. field on the item card looks like a placement field and is not one. Microsoft is explicit that its value “is only informational” and “isn’t used in warehouse activities or availability calculations”. Teams do sometimes discover this after building a process on it.
Supply Chain Management has everything above and then a feature Business Central has no equivalent for: Warehouse slotting. It plans picking locations before orders are released and creates the replenishment work to fill them.
“The Warehouse slotting feature lets you consolidate demand by item and unit of measure from orders that have a status of Ordered, Reserved, or Released. You can apply generated demand to locations used for picking, based on quantity, unit, physical dimensions, fixed locations, and more.”

Generate demand, then Locate demand to produce a slotting plan, then Run replenishment to create the work. It can be scheduled on a recurrence.

Per warehouse, with unit-of-measure tiers, min and max demand quantities, directive codes and an overflow location. Demand that cannot be slotted is flagged in the plan.

Assume empty, Consider qty, or Consider on-hand. The last one reduces the planned quantity by what is already sitting in the target location.

Slot only to fixed locations for the product, only to fixed locations for the variant, or to fixed and non-fixed locations alike.
| Capability | Business Central | Finance & Operations |
|---|---|---|
| Bins, zones, bin types | Yes | Yes |
| Directed put-away and pick | Yes, most advanced level | Yes |
| Bin ranking | Yes | Yes, via location directives |
| Fixed bins / fixed locations | Yes | Yes |
| Put-away templates | Yes | Yes, location directives |
| Capacity limits (qty, cubage, weight) | Yes | Yes |
| FEFO picking | Yes | Yes |
| Demand consolidation from open orders | No | Yes, Warehouse slotting |
| Slotting plan before work release | No | Yes |
| Scheduled, recurring slotting run | No | Yes |
| Derives which item should live where | No | No |
Compiled from Microsoft’s documentation for both products, read 28 July 2026. Feature availability changes; check the current docs before making a licensing decision.
Read the slotting documentation closely and you can see what it takes as given. Slotting consolidates demand and applies it to picking locations based on fixed locations, quantity, unit and physical dimensions. Every one of those is an input you supply. The fixed location for an item is a setting someone chose. Slotting executes that policy well. It does not tell you the policy was right.
Both products execute a placement policy reliably. Neither derives one.
So the question “which item should sit in which location, given how we actually get ordered” stays where it has always been: in somebody’s judgement, usually assisted by a spreadsheet, usually reviewed far less often than the order profile changes. That matters because travel is roughly half of order-picking time, and order picking is the largest single component of warehouse labour cost. Both figures come from the standard reference on the subject, Edward Frazelle’s World-Class Warehousing (1996).


This is a licensing and scale question more than a warehouse one, and your implementation partner is better placed to answer it than we are. Two things are worth saying plainly.
Do not move to Finance & Operations to get slotting. Slotting executes a placement policy; it does not produce one. If your placement policy is a spreadsheet somebody updates twice a year, migrating platforms gives you a better engine running the same unexamined policy. Fix the policy first, on the platform you already have.
You have already paid for it. Setting it up is real configuration work, unit of measure tiers, directive codes, slotting templates and location directives, but it is configuration rather than development. Worth doing before anyone builds anything custom.
Dynamics is your system of record. It manages the warehouse, and it manages it properly. What it does not do, on either platform, is compute the optimal placement from your own order history. That is the last mile, and it is what we build: an optimization app that runs in tandem with the ERP you already have, on your governed stack, without touching the ERP core. A working demo exists and we build these on request.

Which platform carries which capability, what the licence covers, and what each release wave changes.

Dynamics 365 is an umbrella over two different ERPs with two different admin planes. Choosing between Business Central and finance and operations apps sets your admin portal, your update cadence, your developer language, how you obtain environments and who releases production. Every claim here is quoted from Microsoft's own pages.
Read more12 min read
Seven reference architectures for AI that optimizes decisions on Dynamics 365 — the Azure services, the D365 read and write surfaces, the cost shape, and where each pattern stops working.
Read more12 min read
No. Microsoft describes Dynamics 365 as a set of applications you choose one, some, or all of. The useful part is what the umbrella contains — two ERPs, a family of customer engagement apps, and Power Platform underneath — and where the seams between them fall.
Read more6 min read
Through the surfaces each ERP publishes for exactly that purpose — and the two ERPs under the Dynamics 365 umbrella publish different ones. Business Central names four built-in ways into Dataverse plus three web-service types. Finance & Operations names virtual entities, dual-write and data entities. On two of those surfaces Microsoft states that no copy of your data is made.
Read more8 min read
Microsoft publishes the app prices and the attach prices, but not the two user-licence prices most quotes actually turn on. Base plus attach, the seat minimums that differ by edition, and the four numbers you have to go and measure yourself.
Read more9 min read
Dataverse and Operations storage became one pooled entitlement in December 2025. Here is what the published entitlements are now, and the four different things Microsoft says happen when you exceed them — because storage, Business Central, Copilot Credits and platform requests each enforce differently.
Read more11 min read
Microsoft's standard cloud offer for finance and operations apps includes two environments — one production instance and one Tier-2 Standard Acceptance Testing instance. Everything past those two is bought as an add-on, run in your own Azure subscription, or provisioned against capacity you already hold, depending on which admin plane you are on. There are now two tier vocabularies in the documentation, the availability commitment covers production only, and a project that mixes the vocabularies buys the wrong thing.
Read more9 min read
Microsoft's deprecation register states that Lifecycle Services is being replaced by the Power Platform admin center. New project creation froze on 16 February 2026; self-service migration tooling is a mid-2026 preview. No page we found publishes a full retirement date. Microsoft names a destination for every retired capability — the question is whether each destination is actually there, and for three of them the answer is more complicated than the table suggests.
Read more9 min read
FAQ
No. Business Central has bins, zones, bin types, bin ranking, fixed bins, put-away templates and directed put-away and pick, but it has no equivalent of the Warehouse slotting feature in Finance & Operations, which consolidates demand from open orders and produces a slotting plan before work is released.
No. Microsoft's documentation states its value is only informational and is not used in warehouse activities or availability calculations. It is copied to document lines and reports, and nothing else acts on it.
Not on its own. Slotting executes a placement policy rather than producing one, so migrating gives you a better engine running whatever policy you already had. The placement decision is worth fixing first, and it can be fixed on either platform.
Demand by item and unit of measure from orders with a status of Ordered, Reserved or Released, applied to picking locations based on quantity, unit, physical dimensions and fixed locations. Every one of those location inputs is a setting somebody configured.
Usually a licensing and scale question rather than a warehouse one, and your implementation partner is the right person to answer it. On the warehouse question specifically, Business Central covers a great deal more than teams expect once directed put-away and pick is switched on.