What is Dynamics 365 Supply Chain Management?

Dynamics 365 Supply Chain Management (SCM) is Microsoft's enterprise-grade application for procurement, manufacturing, inventory, warehousing, transportation, and master planning. Like Dynamics 365 Finance, it descends from Dynamics AX, and is built for organisations whose operational complexity has outgrown Business Central — multi-site manufacturers, large distributors, retailers, and process industries.

Where it fits

SCM is the operations half of what Microsoft calls the Finance and Operations apps (F&O). Finance and SCM share a single application core, a single database, and a single object model — they are effectively one product sold as two. A deployment that runs both gets a unified back office with no integration between finance and operations; a deployment that runs only Finance is skipping the operational modules but sitting on the same platform, ready to add them later.

The target customer is a manufacturer, distributor, or asset-heavy operator with revenues from a few hundred million upwards. Below that scale, Business Central is usually the right fit, and its light-manufacturing capabilities cover simpler assembly workflows. Above it — global groups running across dozens of legal entities with heavy shop-floor operations — SCM competes directly with SAP S/4HANA and Oracle NetSuite / Fusion.

Inventory and warehouse

Item master with sophisticated product dimensions (size, colour, style, configuration) and tracking dimensions (batch, serial, owner), multi-site warehousing, and full Warehouse Management (WMS) with handheld scanning, wave and load management, configurable mobile device menus, license plate tracking, cluster picking, and slotting. Directed put-away and picking are the norm, not the exception. Inventory classification and periodic inventory closing are what keep that inventory model reconciled to the GL.

The WMS is deep enough that it replaces many standalone WMS products, and it can be advanced-warehouse-enabled on some warehouses while others operate in the simpler basic warehousing mode — useful for phased rollouts. Consignment inventory, vendor-owned stock, and split-ownership scenarios are all supported.

Procurement

Vendor catalogues, sourcing, purchase requisitions with configurable approval workflows, RFQs with sealed-bid evaluation, purchase agreements (blanket orders), a vendor collaboration portal for suppliers who don't have EDI, and three-way matching between purchase order, receipt, and invoice. Freight, duty, and insurance charges on those purchase orders allocate into inventory value through the Landed Cost module.

For process-heavy industries, category management structures the spend hierarchy, and integration to Microsoft Cloud for Sustainability — and its Sustainability Manager component specifically — and to third-party spend-analytics tools brings emissions and category insight into the buying process.

Manufacturing

SCM's manufacturing coverage is broad. Discrete manufacturing uses production BOMs and routings; process manufacturing uses formulas and co/by-products with catch weight; lean manufacturing supports kanban and takt-based flow. All three modes can coexist on the same site.

Beyond the modes, the shop-floor toolkit is comprehensive: work centres and resources with capabilities and calendars, finite scheduling, subcontracting, engineering change management, batch attributes (viscosity, potency, purity) for regulated industries, and shop floor control with clock-in and job registration. Product Configuration Model (PCM) supports engineer-to-order and configure-to-order flows. Process manufacturers producing more than one output from a single run rely on co-products and by-products allocation on top of the formula.

Manufacturing execution below that layer typically integrates through the Manufacturing Execution System (MES) integration hooks or through partner products; SCM is deliberately not an MES.

Master planning

Planning Optimization is a high-performance, in-memory service that replaced the older MRP engine in the last few years. It runs net-change or full regenerative plans in minutes instead of hours, scales across hundreds of sites, and separates planning from the transactional database so long plans don't lock the system.

On top of Planning Optimization sit demand forecasting (statistical baseline forecasts) and the more recent demand planning module (collaborative planning workflows), which increasingly incorporates machine learning forecasting rather than pure statistical models. Together they close the loop from statistical forecast to consensus plan to net requirement to purchase or production order.

Transportation and asset management

Transportation management covers inbound and outbound transportation with rate shopping across carriers, route planning, load building, freight reconciliation, and shipping-carrier integration (parcel and LTL). Not a full TMS replacement for the largest 3PL operators, but adequate for most in-house transportation needs.

Asset Management covers work orders, preventive maintenance, condition-based monitoring, fault management, and IoT signal integration for industrial equipment — increasingly important for asset-heavy operators such as utilities, mining, and manufacturing plants that want the maintenance system on the same platform as inventory and procurement, and it shows up again for asset-heavy telecommunications network operators and energy producers running the same equipment-maintenance discipline.

Adjacent products

Two products sit around SCM and are commonly deployed with it. Intelligent Order Management (sold separately) orchestrates orders across sales channels and fulfilment locations — useful for omnichannel retailers where the "where does this order ship from" decision is non-trivial. Dynamics 365 Commerce is the retail store solution (POS, e-commerce, clienteling); it uses SCM as its inventory and pricing back end.

For the CRM side of the business, SCM shares Dataverse via Dual-write, so a Sales opportunity in the Sales app or a case in Customer Service can flow through to a sales order or a return in SCM without custom integration.

Licensing and implementation

SCM is licensed per user, typically alongside Finance under the F&O bundle. Full users, Activity users, and Team Members provide different price points depending on access needs. Device licenses cover shop-floor terminals and warehouse handhelds.

Implementations are large — six months at the very fast end, more commonly a year and up — and are almost always led by a global system integrator. The functional footprint is wide (finance, procurement, warehouse, manufacturing, transportation) and every area has depth, so consulting effort dominates the total cost of ownership in the first two years.

When Supply Chain Management is the wrong fit

Below a few hundred million in revenue with simple assembly or light manufacturing, Business Central's Premium tier and its production BOMs, routings, and capacity planning cover the workload at a fraction of the licence and implementation cost — SCM's finite scheduling, advanced warehousing, and multi-site planning are overkill for a single-site operation. Above the enterprise tier, at the very largest, most process-heavy multinationals with deep formula management and regulatory batch records across dozens of countries, SAP S/4HANA remains the incumbent default that most large system integrators are staffed to deliver at scale — SCM is the credible, faster-moving challenger, not yet the safe default for that segment. And organisations expecting a manufacturing execution system out of the box will be disappointed: SCM's shop-floor tools stop at job registration and finite scheduling, and true machine-level execution needs an MES integration or a partner product on top.

First-time buyer checklist

• Scale check. Confirm revenue, site count, and legal-entity count actually sit in SCM's target band — a single-site operation with light assembly is usually cheaper and faster on Business Central.
• Manufacturing mode. Decide whether the operation is discrete, process, lean, or a mix — all three can coexist on one site, but the fit-gap workshop should map your actual production flow against them before configuration starts.
• Warehouse depth. Decide which sites need advanced-warehouse-enabled WMS (directed put-away, wave/load management, handheld scanning) versus simpler basic warehousing — mixing both across sites is supported and often the right phased approach.
• Planning cadence. Model whether Planning Optimization's net-change or full regenerative runs fit your replenishment rhythm, and whether demand forecasting or the newer demand planning module is the right layer on top.
• MES boundary. If shop-floor execution needs machine-level detail, scope the MES integration or a partner product alongside SCM rather than expecting SCM alone to cover it.
• Dual-write scope. If Sales, Customer Service, or Field Service are in play, decide which entities sync through dual-write before go-live — retrofitting the integration later is more disruptive than scoping it up front.
• System integrator. SCM implementations are large and consulting-effort-dominated; choosing the right partner matters more here than almost anywhere else in the portfolio.

Where to go next

The planning engine is covered in master planning runs and Planning Optimization; the warehouse in warehouse mobile workflows; the three manufacturing modes in discrete vs process vs lean. The bridge to the CRM apps is dual-write. Current list prices are on the Finance and Operations pricing page.