Design storage and tracking dimensions from a source warehouse and bin model, decide honestly whether advanced warehousing is justified, and rebuild inventory value rather than replaying source history.
Inventory is where this path's optimism runs out. The source material says so directly: finance usually migrates with fewer semantic surprises than warehouse and production.
The target expresses stock location through storage dimensions: site, warehouse, and where enabled, location. Each is a dimension on the inventory transaction, and the dimension group assigned to a product determines which of them the system tracks.
D365 offers warehouse management with work creation, location directives, wave processing, licence plates, mobile device execution and a reservation hierarchy. It is powerful and it is heavy.
Batch and serial tracking is the cleanest mapping in this module. The concept mapping rates it a direct translation into tracking dimension groups, with one instruction: preserve legal and audit traceability, and redesign open balances and open stock state carefully.
Source items carry a valuation method. Target released products carry an item model group, which determines costing method, whether physical and financial updates post to the ledger, whether the item is stocked, and how issues settle against receipts.
The instruction from the source posting rules is firm: historical revaluation detail is legacy evidence, and opening balances must be rebuilt, not replayed.
Stock transfers between warehouses map to transfer orders or inventory transfer journals. There is one case that needs attention early.
The gap register rates warehouse behaviour at medium confidence, and the reasons are worth stating.
Site is a design layer the source usually lacks, and branch context alone does not establish it. Classify every warehouse by what it represents. Ownership constructs — consignment, customer-owned, transit — are not ordinary on-hand.