Turn the item-by-site costing matrix into D365 inventory model groups, storage granularity and a defensible opening inventory position — the design that blocks manufacturing and cutover until it is approved.
There is one sentence in the gap register that determines how this domain runs: CloudSuite Industrial can combine standard, average, and FIFO costing behaviors across the item and site matrix.
The matrix arrives from the Product and Item Modelling module as a grid of item-site combinations with a cost method in each populated cell. The design work is classifying what each pattern implies.
An inventory model group is more than a costing method, and treating it as one produces a group design that has to be reworked when the other attributes turn out to matter.
Standard-cost items behave differently enough from actual-cost items that the design splits here, and the split runs all the way through to the posting design and the manufacturing close.
For average and FIFO items, the target's behaviour differs from most source systems in one way that reliably surprises people, and it is worth explaining before the first month-end rather than during it.
The concept mapping records warehouse and storage location as a composite mapping with medium confidence, and asks a specific question: confirm whether source warehouse granularity should remain warehouse-level or collapse into site defaults.
The transfer decision belongs to topology, but it lands in inventory, so it appears in both modules by design.
The target inventory position is established, not migrated. That distinction is the same one the whole path applies to history, and it is particularly important here because inventory value is a control-account balance that an auditor will test.
CloudSuite Industrial let costing method vary across the item and site matrix. D365 governs costing through inventory model groups attached to the released product, which exists once per legal entity.