Dynamics 365 for Manufacturing: Cost, SKU Fit & Comparison (2026)

The Manufacturer's Buy-Decision Guide to Dynamics 365

Updated July 2026. Microsoft does not sell a product called 'Dynamics 365 for Manufacturing'. It sells three overlapping SKUs — Business Central, Finance, and Supply Chain Management — and partners bundle two or three of them into something they call a manufacturing solution. Getting that bundle wrong is the single most expensive mistake in a Microsoft ERP evaluation, because the migration path between tiers is a re-implementation, not an upgrade. This page tells you which SKU fits your plant profile, what the whole thing actually costs, and when a different vendor is the better answer.

For the full module feature list — BOMs, routings, MRP, finite scheduling, shop-floor control, quality — see our manufacturing module guide. This page is the buy-decision guide: SKU fit, budget bands, partner economics, and head-to-head vendor comparison. Read that one to understand what the software does; read this one to decide whether to sign.

Get Dynamics 365 Pricing Find a Dynamics 365 Partner Compare Dynamics 365

This is independent, vendor-neutral research. No vendor pays for placement or ranking here, and we do not resell any of the systems on this page.

That deployment split matters to the Dynamics decision more than it looks. Dynamics 365 Supply Chain Management is cloud-first, with on-premise available only through a constrained 'cloud and edge' scale unit model. If your plants sit in the on-premise or hybrid share above — because of WAN reliability at a rural site, machine-controller latency, or a customer contract that constrains where data may reside — that is a design constraint you have to price in on day one, not discover in the middle of a rollout.

Where Generic ERP Breaks Down in Manufacturing

Before comparing SKUs it is worth naming the specific failure modes that push manufacturers into an ERP replacement. Almost every dissatisfied manufacturer we speak to selected a system that was competent at finance and distribution and assumed the plant would be a manageable extension of it. The plant is never a manageable extension.

Costed BOMs Drift Away From Reality

A manufacturer's margin lives in the standard cost of a finished good, and that cost is only as accurate as the BOM, the routing, and the burden rates behind it. Generic ERP systems track item cost as an average or a last-purchase price, with no concept of a multi-level explosion that rolls sub-assembly labour and machine burden up into the parent. When engineering swaps a component, when a routing operation moves to a slower machine, or when scrap rates on an operation drift from 2% to 7%, the standard cost stays frozen and the variance shows up as a mystery number at month-end. Manufacturing ERP has to recost on demand, keep a costing version history, and explain variance by operation — not just by nominal account.

Planning Runs on Spreadsheets Outside the System

The most common symptom of a bad manufacturing ERP fit is a planner running MRP in Excel. It happens when the system's planning engine cannot model the things that actually constrain the plant: alternate work centres, tooling availability, minimum batch sizes, sequence-dependent changeovers, or supplier lead-time variability. The planner exports demand, plans in a spreadsheet, and keys production orders back in. That workflow hides every planning assumption in one person's file and makes capacity commitments unauditable. Our guide to MRP software covers what a planning engine needs to model before it can replace the spreadsheet.

The Shop Floor Never Gets Data Back

Operators are asked to key job registrations, scrap, and downtime into a system that gives them nothing in return — no schedule for their own work centre, no visibility of what is coming next, no confirmation their entry landed. Compliance collapses within a quarter, the data becomes unreliable, and the plant reverts to whiteboards. The fix is not more training; it is a shop-floor interface that is genuinely useful to the person standing at the machine, on hardware that survives a factory environment.

Traceability Is Reconstructed, Not Recorded

When a customer raises a containment request, a manufacturer needs to answer within hours: which finished lots contain the suspect raw batch, where did they ship, and what did the inspection record say at the time. Systems that record batch numbers as a text field on a transaction rather than as a linked genealogy force the quality team to reconstruct the chain by hand from paper travellers. In automotive, aerospace, medical device, and food that reconstruction time is itself an audit finding.

Engineering Change Escapes the Process

An engineering change order approved in a PLM system but not reflected in the ERP BOM means the plant keeps building the old revision, buying the old component, and quoting the old cost. Without effective-date control on BOM and routing versions, and without a workflow that ties an ECO to the production orders it affects, change management becomes an email chain. The gap between engineering release and shop-floor reality is one of the most reliable predictors of scrap cost.

Multi-Plant Consolidation Is a Month-End Project

Manufacturers that have grown by acquisition typically run three to six different systems, each with its own item master and its own definition of a work centre. Consolidated stock valuation, group-level demand planning, and inter-company transfer pricing all become manual month-end exercises. This is usually the trigger for a mid-market manufacturer to move up from a single-plant system to a multi-entity platform — and it is the point where the Business Central versus Supply Chain Management decision gets forced.

Quotes Are Built Outside the System and Never Reconciled

Configure-to-order manufacturers quote in a CPQ tool, a spreadsheet, or an estimator's head. If the configured product structure that wins the order does not become the BOM and routing the plant builds to, every configured order is a manual re-entry with a fresh chance to mis-price. The link between configuration, quoted cost, and as-built cost is where configure-to-order manufacturers lose margin quietly and continuously.

Choosing Between Business Central, Finance, and Supply Chain Management

The SKU decision is the most expensive question to get wrong, so start here before you look at features. The short version:

Business Central Premium is the minimum SKU that includes the manufacturing module. The Essentials tier does not have BOMs, routings, or production orders. Buyers regularly start scoping on Essentials and discover the gap mid-implementation — budget Premium from day one if you manufacture anything. Our detailed walkthrough of Business Central production and manufacturing covers exactly where the Premium tier's ceiling sits.

At the enterprise end, the equivalent trap is assuming Finance alone covers the plant. It does not. Production orders, MRP, finite scheduling, warehouse management, and asset maintenance all live in Supply Chain Management, which is a separately licensed application; our breakdown of the Supply Chain Management module sets out what sits on each side of that line. Almost every enterprise manufacturing deal is Finance plus Supply Chain Management together, and any quote showing only one of them is either scoped for a distribution business or incomplete.

UK and Irish buyers should also confirm the statutory layer explicitly during scoping. Microsoft maintains the UK localisation, including Making Tax Digital-compliant VAT submission, CIS handling where a manufacturer also does site installation work, and Republic of Ireland VAT if you operate across both jurisdictions. That is one of the quieter advantages of the Microsoft stack over vendors whose UK compliance is delivered by a partner add-on: the localisation follows the standard update cadence rather than a third party's release schedule.

Discrete vs Process vs Engineer-to-Order: Where Dynamics Actually Lands

Discrete manufacturing (assembled units — pumps, machinery, electronics, automotive components). Supply Chain Management is genuinely strong here. Native multi-level BOMs, engineering versions and engineering change orders, finite scheduling with capacity reservations, kanban, lean manufacturing, and a mature shop-floor terminal experience. Mixed-mode operations — some make-to-stock, some make-to-order, some configure-to-order — are well handled through the product configurator, which is one reason Microsoft does well with UK industrial-equipment OEMs.

Process manufacturing (formulated products — food, chemicals, cosmetics, light pharma). This is where vanilla Dynamics has real gaps. The platform supports formulas, batch attributes, catch weights, and co-products and by-products, but the depth is shallower than S/4HANA, Infor CloudSuite Industrial, or Sage X3. Most successful process-manufacturing Dynamics deals layer in ProcessForce by NeoVision or a Merit Solutions life-sciences accelerator. Expect this to add roughly £25–50 per user per month plus implementation work, and expect the ISV to own a meaningful share of your upgrade risk.

Engineer-to-order. Supply Chain Management has a project-based manufacturing capability and integrates with Project Operations, which is genuinely useful for industrial-equipment manufacturers running 6–18 month builds. For true engineer-to-order with heavy serialisation, multi-thousand-line BOMs, and contract revenue recognition — defence, aerospace, shipbuilding — IFS Cloud and S/4HANA remain the safer bets, and the gap is in project accounting depth rather than in production control.

Best Fit for SMB Manufacturers (£8M–£200M Revenue)

At this size the decision is rarely 'which module is deepest'. It is 'which platform can my team run without a permanent consultant on retainer'. Here is how the realistic shortlist compares for a manufacturer in this band.

Dynamics 365 Business Central Premium

Best for: Single-site and two-site discrete manufacturers, job shops, and contract manufacturers between roughly £8M and £160M revenue whose office already runs on Microsoft 365 and who want one system for finance, stock, and production without enterprise implementation overhead.

Business Central Premium is a complete manufacturing back office at a mid-market price point. Multi-level BOMs, routings, production orders, capacity planning, and a working MRP engine are all in the base Premium licence, alongside full financials, purchasing, sales, warehousing, and service management. The Microsoft integration is the differentiator competitors cannot copy cheaply: production data lands in Power BI without an integration project, approvals run in Teams, and Power Apps lets a plant build a scrap-capture tablet screen in a few days rather than commissioning custom development. Implementation timelines of four to nine months for a single plant are normal and achievable, which matters enormously to a manufacturer without a dedicated IT function.

The AppSource ecosystem is unusually strong for manufacturing. Insight Works, Cosmo Consult, Netronic, and Continia between them cover shop-floor data collection, graphical scheduling, barcode and warehouse mobility, advanced quality management, and document capture — each installable as an extension rather than a code fork, which keeps the monthly Microsoft update cadence survivable.

Watch out for: Premium's ceiling is real and arrives faster than buyers expect. Finite scheduling is basic — capacity planning is largely infinite unless you add a scheduling ISV. Advanced warehouse features such as wave management, licence plating, and directed put-away are thin compared with Supply Chain Management. Multi-entity consolidation across more than two or three legal entities becomes painful, and there is no native asset-maintenance module. Most importantly, the move from Business Central to Finance and Supply Chain Management is a re-implementation, not an upgrade — if your five-year plan involves five plants and three countries, paying for the enterprise tier now is usually cheaper than paying for two implementations.

Oracle NetSuite Manufacturing

Best for: Growing discrete manufacturers between roughly £20M and £200M revenue who prioritise a single cloud financial system across multiple entities and subsidiaries over deep production control.

NetSuite's strength in this band is the financial and multi-subsidiary backbone. Multi-entity consolidation, multi-currency, and revenue recognition are genuinely enterprise-grade at a mid-market price, and the manufacturing capability — works orders, assembly BOMs, work centres, routing, and the Advanced Manufacturing module for shop-floor execution — is adequate for assemble-to-order and make-to-stock operations with straightforward routings. For a manufacturer whose real complexity is corporate structure rather than the plant, it is often the faster answer. Our head-to-head on the two mid-market platforms works through where each one wins.

Watch out for: Production depth is the weak point. Finite scheduling, engineering change management, and quality management are all noticeably shallower than the Microsoft enterprise tier, and the standard answer for complex scheduling is a third-party bolt-on. Licensing is per-user with module-based uplifts, and the renewal uplift pattern is the most commonly reported cost surprise among manufacturers we hear from. If the plant is the hard part of your business rather than the org chart, this is the wrong end of the trade-off.

Epicor Kinetic

Best for: Make-to-order and engineer-to-order job shops, metal fabricators, and machine shops between roughly £8M and £400M revenue where quoting, estimating, and shop-floor control are the core of the business.

Kinetic's heritage is job-shop manufacturing and it shows. Quote-to-job workflow, estimating, method-of-manufacture management, real-time job costing, and shop-floor data collection are the product's centre of gravity rather than an extension of a financial system. Advanced planning and scheduling is a first-class module, not an afterthought, and the product configurator handles the parametric configure-to-order patterns fabricators live on. For a UK metal fabricator whose main question is 'what did this job actually cost me and can I quote the next one better', it is frequently the strongest functional fit on the shortlist. We cover the platform in detail in a dedicated fit-check for job shops and fabricators.

Watch out for: The financial and reporting layer is less polished than either Microsoft or NetSuite, and the analytics story requires more work to reach the same place Power BI arrives at natively. Multi-country and multi-entity depth is weaker, which limits it for manufacturers with meaningful European operations. Implementation quality is heavily partner-dependent and the UK partner bench is thinner than Microsoft's. The user experience, whilst much improved in recent Kinetic releases, still carries visible legacy in less-used corners of the product.

SAP Business One

Best for: Smaller manufacturers — typically under £60M revenue — and UK subsidiaries of larger European groups that need a lightweight plant system with the option of consolidating into a parent's SAP landscape later.

For manufacturers in this band, Business One offers solid production orders, multi-level BOMs, MRP, and batch and serial traceability, with a large partner-built add-on ecosystem (Boyum, Produmex, Beas Manufacturing) that adds shop-floor execution, advanced planning, and warehouse depth. The strongest structural argument for it is corporate: if a European parent runs S/4HANA, a two-tier landscape with Business One in the subsidiaries is a well-trodden pattern with established consolidation tooling. Our Business One manufacturing assessment covers what the base product does versus what the add-ons carry.

Watch out for: Almost every serious manufacturing deployment depends on a partner add-on, which means managing two vendor relationships, two upgrade cycles, and two support paths. Add-on quality varies widely and some are maintained by very small firms. The platform also runs out of headroom sooner than the alternatives above — past roughly 75–100 users or three plants, most buyers are looking at a migration rather than an expansion.

Best Fit for Enterprise Manufacturers (£200M+ Revenue)

Above £200M revenue the questions change. Multi-country statutory compliance, group consolidation, plant-template rollout methodology, and the depth of the partner bench matter more than any individual feature.

Dynamics 365 Finance + Supply Chain Management

Best for: Discrete and mixed-mode manufacturers from roughly £200M to £1.6B revenue operating 3–25 plants, already standardised on Microsoft 365 and Azure, who want one platform covering finance, planning, production, warehouse, and asset maintenance.

This is the pairing partners mean when they say 'Dynamics 365 for manufacturing'. Supply Chain Management brings a real MRP II engine with finite scheduling against work-centre calendars, alternate resources, and capacity reservations; a genuine warehouse management system with RF support, wave management, licence plates, and zone-based picking; engineering change management with effective-date control; and an asset management module that competes credibly with IFS and Maximo at the mid-enterprise level. Finance carries multi-entity, multi-country statutory reporting with localisations maintained by Microsoft rather than by a partner — which for a UK manufacturer with European subsidiaries removes a category of compliance risk entirely.

The Azure and Power Platform layer is the honest differentiator. Machine telemetry through IoT Hub feeds machine signals into Supply Chain Management for condition-based maintenance and OEE, Power BI removes an entire class of reporting projects, and Power Apps lets each plant build the small tools it needs without a change request. For a manufacturer whose IT strategy is already Microsoft, the marginal cost of these capabilities is close to zero, which is not true of any other platform in this comparison.

Watch out for: The licence is only part of the number. Partner implementation fees typically run 2.5–4x first-year licensing, environment strategy (dev, test, sandbox, production tiers in Lifecycle Services) adds real cost, and master-data migration is almost universally underestimated. Process manufacturing needs an ISV. Full MES is integrated, not replaced. And the release cadence — several service updates a year — means you need a permanent regression-testing capability, which is a running operational cost that rarely appears in the business case.

SAP S/4HANA Manufacturing

Best for: Global manufacturers above roughly £400M revenue, regulated industries, and any organisation running more than about 25 plants on a common template.

S/4HANA remains the deepest manufacturing platform available. Production planning, quality management, plant maintenance, and the extended warehouse system are individually stronger than their Microsoft equivalents, and the process-manufacturing capability — recipe management, batch genealogy, electronic batch records — is a real differentiator for pharma, chemicals, and food. Country localisation coverage is unmatched, the reference-architecture and rollout-template methodology is genuinely mature at scale, and the partner bench is the largest in the industry, which matters when you need experienced people across a dozen European sites at once. Public-cloud editions have narrowed the entry-cost gap considerably; our public-cloud pricing breakdown sets out where the bands land.

Watch out for: Cost and complexity, in both directions. Below roughly £400M revenue and outside regulated industries, most manufacturers are buying capability they will not use and paying for the configuration effort to switch it off. Implementation timelines are the longest in the market. The clean-core discipline required to stay upgradeable in the public-cloud edition constrains the customisation manufacturers with idiosyncratic processes often expect. And whilst the ecosystem is deep, UK day rates are correspondingly high.

Infor CloudSuite Industrial

Best for: Process manufacturers — food and beverage, chemicals, nutraceuticals — and industrial manufacturers between roughly £80M and £800M revenue who want native process capability without an ISV dependency.

The strongest argument for CloudSuite Industrial is that formulation, recipe management, co-product and by-product yield, catch weights, and grade-based pricing are native rather than bolted on. For a UK food or chemicals manufacturer, that removes an entire vendor from the stack and an entire class of upgrade risk, and it makes BRCGS and allergen-management evidence considerably easier to produce. The industry-specific CloudSuite packaging ships with pre-configured process flows, which shortens design workshops noticeably. Multi-site process operations, quality management against formulation specifications, and regulatory reporting are handled to a depth Microsoft reaches only with a partner product.

Watch out for: The consulting talent pool is materially smaller than either Microsoft's or SAP's in the UK, which is a genuine execution risk on a multi-plant rollout — partner availability, not product capability, is the usual failure point. Reporting and analytics require more assembly than the Power BI experience. Multi-country statutory coverage is thinner than SAP's. And the platform's strengths are concentrated in process and industrial verticals; a pure discrete assembler will find less of the packaged content relevant.

Reading the Comparison Table

The decision rules that fall out of the table: choose Supply Chain Management if you are under £1.6B, mostly discrete, and Microsoft is already the office standard. Choose S/4HANA if you are global, regulated, or above roughly 50 plants. Choose NetSuite for £20–200M discrete makers who want lighter implementation overhead and do not need finite scheduling. Choose Kinetic if you are a job shop or make-to-order fabricator where quoting and job costing are the business. Choose Infor for process manufacturing where native recipe management matters more than the Microsoft ecosystem. To widen the field beyond these five, start from our manufacturing ERP hub.

Essential Capabilities to Test During Evaluation

Generic ERP evaluation checklists miss the things that decide a manufacturing implementation. These are the capabilities worth scripting into a scenario-based demo rather than accepting on a feature matrix.

Multi-Level BOM and Routing Management

Test a four-level BOM with a phantom sub-assembly, an alternate component, and a scrap factor at two operations. Ask the vendor to change a component at level three and show you the cost roll-up, the affected open production orders, and the effective-date behaviour. Systems differ enormously in how they handle in-flight orders when a BOM changes, and this is where the difference shows.

Finite Scheduling and Capacity Modelling

Infinite capacity planning is easy and nearly universal. Finite scheduling against real constraints is not. Test sequence-dependent changeovers, tooling as a constrained resource, alternate work centres with different run rates, and what happens when a machine goes down mid-shift. Supply Chain Management handles this natively; Business Central needs a scheduling ISV; several competitors need a separate advanced-planning product.

Engineering Change Management

Ask to see an ECO raised, costed for impact, approved through a workflow, and released with an effective date — then ask what happens to the purchase orders already placed against the superseded component. Manufacturers with active engineering functions lose more money to weak change control than to almost anything else on this list.

Batch and Serial Traceability

Script a mock recall. Give the vendor a raw-material batch number and ask for every finished lot containing it, every customer shipment, and the inspection results recorded at goods receipt — in a single query, on screen, without a report developer. If the answer involves exporting to Excel, that is your recall response time.

Quality Management and Non-Conformance

Inspection plans, sampling, certificates of analysis, non-conformance reports, and CAPA workflow should be part of the transaction flow rather than a separate log. For regulated manufacturers, test electronic signature and audit-trail behaviour specifically — this is where the gap between vanilla Dynamics and purpose-built systems is widest.

Warehouse Execution

If you run RF scanners, test directed put-away, wave picking, licence-plate handling, and cycle counting on the actual devices you intend to buy. Supply Chain Management's advanced warehouse capability is a genuine WMS; Business Central's is stock management with mobility bolted on. Many manufacturers only discover the difference after go-live.

Product Configuration

Configure-to-order manufacturers should test a configurable product end to end: quote, configuration rules, price roll-up, automatic BOM and routing generation, and as-built cost versus quoted cost. The gap between the configurator and production is where configure-to-order margin leaks.

Shop-Floor Data Collection

Put the shop-floor interface in front of an actual operator during the evaluation, not a project manager. Job start and stop, quantity and scrap reporting, downtime coding, and access to the work-centre schedule need to be achievable with gloves on, in under thirty seconds, on hardware that survives coolant and dust.

Dynamics 365 Manufacturing Cost Ranges

Licensing is the visible number and rarely the largest one. Budget in three layers: subscription, implementation, and the running cost of staying current. UK list prices move with Microsoft's periodic currency alignment, so treat the figures below as planning bands and confirm current pricing with your partner.

SMB Manufacturers (£8M–£200M Revenue)

• Software subscription: Business Central Essentials is around £55 per user per month at UK list and does not include manufacturing; Premium is around £80 per user per month and does. A 40-user single-plant manufacturer therefore lands near £38,000 per year before add-ons.
• Manufacturing ISVs: shop-floor data collection, graphical scheduling, and advanced quality typically add £15–40 per user per month each. Two add-ons can increase the subscription line by 40–60%.
• Implementation: typically 1–1.5x first-year subscription for a straightforward single-plant discrete deployment, so roughly £40,000–£120,000. Add 30–50% if you are migrating from a legacy system with poor master data.
• Realistic first-year total: £95,000–£320,000 for a single-plant manufacturer. A £40M maker with clean data and a disciplined scope lands near the bottom of that band; one with 15 years of accumulated item-master debt lands near the top.

Enterprise Manufacturers (£200M+ Revenue)

• Software subscription: Finance and Supply Chain Management are each around £165 per user per month at UK list, commonly discounted toward a combined ~£240 when both are licensed. Operations Activity users (light read/write) run around £40 per user per month and Operations Device licences around £60 per device per month for shared shop-floor terminals — getting this user-mix right is the single biggest lever on the subscription line.
• Implementation: 2.5–4x first-year licensing is the reliable planning ratio. A £320,000 annual licensing footprint implies £800,000–£1.3M in partner fees.
• Integration: MES, PLM or CAD, EDI, and quality systems each carry 6–16 weeks of work. EDI in particular is usually a partner product (TIE Kinetix, SPS Commerce) rather than native, and UK automotive suppliers should confirm Odette and VDA message support explicitly.
• Environments and tooling: Lifecycle Services environment tiers, data migration tooling, and a permanent regression-test capability for the service-update cadence.
• Realistic first-year total: £1.6M–£2.8M for a £240M discrete manufacturer with 3 plants, 200 office users, and 400 shop-floor terminal users.

The Cost Drivers That Surprise Buyers

Five items account for most manufacturing ERP budget overruns, and none of them is licensing. Master-data cleanup — items, BOMs, routings, suppliers, customers — is routinely underestimated by more than half, and it is the single most common cause of a delayed go-live. ISV stacking compounds quietly: three add-ons at £25 per user per month on 200 users is £180,000 a year that no one modelled. Shop-floor licensing is frequently mis-scoped, with buyers assuming operators need full licences (they usually need Activity or Device licences) or assuming the reverse and discovering mid-project that their operators need transaction rights. Integration count matters more than integration complexity — each additional system in scope adds coordination overhead disproportionate to its technical difficulty. And change management on the plant floor is almost never budgeted, despite being the difference between a system that gets used and one that gets worked around. Our full breakdown of Dynamics 365 costs goes deeper on the licensing mechanics across every SKU.

Implementation Timeline and Milestones

Plan for four to nine months for Business Central Premium in a single-plant SMB manufacturer, nine to eighteen months for Finance and Supply Chain Management in a one-to-five-plant mid-enterprise, and eighteen to thirty-six months for multi-country rollouts above ten plants.

Dynamics 365 for Metals: Fabricators, Steel Service Centres, and Foundries

Metals is one of the strongest verticals for Microsoft in manufacturing, and one of the most misunderstood, because 'metals' covers three quite different businesses with three different fits.

Fabricators and machine shops — laser cutting, forming, welding, machining, assembly — are the classic Dynamics sweet spot. The work is discrete and make-to-order, routings are multi-operation with real changeover time, and job-level cost accuracy is the business model. Business Central Premium with a scheduling and shop-floor ISV covers this well up to a few hundred employees; Supply Chain Management's finite scheduling and alternate-resource modelling earns its cost once you are running multiple cells across shifts and need to promise dates you can hit. The one capability to test hard is nesting and remnant tracking: neither Microsoft SKU natively manages sheet remnants or drop stock, and fabricators carrying meaningful remnant stock need either an ISV or an integration to their nesting software.

Steel service centres and stockholders — slitting, cut-to-length, blanking, stocking — look like distribution with a light conversion step, and their requirements are dominated by stock attributes rather than routings. Coil and sheet stock has to be tracked by heat number, gauge, width, grade, and usually mill certificate, with dual units of measure (weight and length, or weight and pieces) that must reconcile through every transaction. Supply Chain Management handles catch weights and batch attributes natively, which covers most of this, but theoretical-versus-actual weight variance handling and mill-certificate document management usually need configuration work or an ISV. Test dual-UOM behaviour on a partial coil consumption before you sign anything.

Foundries, forges, and heat treaters sit closest to process manufacturing and are the weakest Microsoft fit of the three. Alloy chemistry, charge calculation, yield loss, and furnace scheduling as a batch resource are all things vanilla Dynamics models awkwardly. Manufacturers in this segment should shortlist Infor CloudSuite Industrial and S/4HANA alongside Microsoft rather than assuming the Microsoft ecosystem advantage carries the decision.

Across all three, traceability is the common thread. UK automotive and aerospace customers increasingly demand heat-number traceability from mill certificate through to shipped part, plus PPAP documentation and IATF 16949 evidence, and post-Brexit rules-of-origin declarations add a further layer of material-provenance record-keeping for anyone shipping into the EU. Both Microsoft manufacturing SKUs support batch and serial genealogy, but the quality-document side — certificates of analysis, mill certificates, inspection records attached to the batch rather than to a folder — is where you should concentrate the demo script.

Dynamics 365 Apps for Manufacturing Beyond the ERP Core

One reason manufacturers shortlist Microsoft is that the platform does not stop at ERP. Because the Dynamics 365 apps for manufacturing share a tenant, an identity model, and a data platform, the workloads a manufacturer usually buys separately can sit on the same stack — and that changes the total-cost picture even when the ERP itself is not the cheapest line item.

• Field Service. For manufacturers with an installed base to maintain — capital equipment, machinery, HVAC, industrial systems — Field Service handles work-order dispatch, engineer scheduling, van stock, and warranty and contract entitlement, with the service history tied back to the serialised asset the plant built. Aftermarket service is frequently the highest-margin part of an equipment manufacturer's business and is usually run on a disconnected system.
• Sales and Customer Insights. Quote-to-order for configured products, opportunity management for long capital-equipment sales cycles, and account intelligence, with configured quotes flowing into production rather than being re-keyed.
• Project Operations. The right home for engineer-to-order and installation-heavy work: project structures, resourcing, time and expense, and percentage-of-completion revenue recognition alongside the production orders.
• Asset Management (within Supply Chain Management). Preventive maintenance schedules, condition-based triggers from machine telemetry, and maintenance work orders that compete for the same capacity as production — which is the point most standalone CMMS tools miss.
• Power Platform and Copilot. Low-code Power Apps for plant-specific tools such as scrap capture, gauge calibration logs, and safety checklists; Power Automate for cross-system approvals; Power BI for OEE, margin, and on-time-delivery dashboards; and Copilot for drafting supplier communications and summarising exception queues.

For most manufacturers the sequencing is: get the ERP core live first (Business Central Premium, or Finance plus Supply Chain Management), then add Field Service or Project Operations once the production data is trustworthy. Buying the whole suite in wave one is the most reliable way to extend an implementation by six months.

Frequently Asked Questions

Which Dynamics 365 SKU should a manufacturer buy?

For discrete manufacturers under roughly £120M revenue with one to three plants, Business Central Premium is the starting point — it is the only Business Central tier that includes BOMs, routings, and production orders, and Essentials will not work for you at any price. For manufacturers above roughly £120M revenue, or with multiple plants, multiple legal entities, or finite-scheduling requirements, the answer is Finance plus Supply Chain Management together. Finance alone does not include production; Supply Chain Management alone does not include the statutory financial depth. Any partner quote showing only one of the two is either incomplete or scoped for a distributor rather than a manufacturer.

How much does Dynamics 365 cost for a manufacturer?

Budget in three layers. Subscription: Business Central Premium is around £80 per user per month at UK list; Finance and Supply Chain Management are each around £165 per user per month, commonly discounted toward a combined ~£240 when both are taken. Implementation: 1–1.5x first-year subscription for a single-plant Business Central deployment, 2.5–4x for an enterprise Supply Chain Management rollout. Running cost: ISV add-ons, integration maintenance, and regression testing against Microsoft's service-update cadence. Realistic first-year totals are £95,000–£320,000 for a single-plant SMB manufacturer and £1.6M–£2.8M for a £240M manufacturer with three plants and 600 total users.

Which companies integrate CPQ with Dynamics 365 for manufacturing?

Several established CPQ vendors have productised Dynamics integrations, and the right one depends on how your configuration logic works. Tacton is the strongest fit for complex engineered products with constraint-based configuration rules, and is widely used by industrial-equipment and machinery manufacturers running Supply Chain Management. Experlogix has the deepest native integration into both Business Central and Finance and Supply Chain Management, is listed on AppSource, and is the most common choice for mid-market manufacturers because configured quotes generate the production BOM and routing directly. DynamicsPrice and Dynamic Web serve mid-market Business Central customers with simpler pricing-and-options configuration. PROS and Configure One (a Revalize company) appear more often in larger deals where pricing optimisation or deep CAD-driven configuration is the requirement, and In Mind Cloud targets manufacturers wanting a sales platform layered over the ERP. Microsoft's own product configurator inside Supply Chain Management handles dimension-based and rules-based configuration natively and is sufficient for many manufacturers — evaluate it before buying a third-party CPQ, because the integration you avoid is the cheapest integration you will ever have. The key test for any of them is whether a won, configured quote produces a costed BOM and routing without manual re-entry.

Who implements Dynamics 365 Business Central for discrete manufacturing?

Business Central manufacturing work is delivered by Microsoft partners rather than by Microsoft, and the partners who do it well are a subset of the general Business Central bench. The pattern to look for is a partner with a manufacturing practice rather than a manufacturing case study. In the UK and Ireland, firms such as Tecman (Technology Management), TVision Technology, Clever Dynamics, Dynamics Consultants, HSO, Columbus UK, Prodware, and Cosmo Consult all run established Business Central manufacturing practices, with Cosmo and Clever Dynamics publishing their own manufacturing extensions. Several ISVs — notably Insight Works and Netronic — work through implementation partners rather than direct, so the partner you choose determines which shop-floor and scheduling tooling you end up with.

Screen candidates on four things: how many discrete-manufacturing Business Central go-lives they have personally delivered in the last 24 months (three or more is the bar); whether they will name a UK reference in your sub-vertical; which manufacturing ISVs they have implemented and how many times; and whether the consultant running your design workshops is the one who ran those go-lives, or a different, more junior person. Partner quality is the single largest variance in Business Central manufacturing outcomes — larger than any product decision on this page. Our Dynamics partner directory lets you filter by manufacturing specialisation and region.

What's the difference between Business Central and Supply Chain Management for manufacturing?

Business Central is the SMB SKU: one stack, lighter customisation, faster to implement, lower licensing cost, and clean handling of single-plant manufacturers up to roughly £160M revenue. Supply Chain Management (licensed alongside Finance) is the enterprise SKU: substantially deeper finite scheduling, a genuine warehouse management system, native asset management, product configuration, and multi-site, multi-country, multi-entity scale. The practical dividing lines are finite scheduling, advanced warehouse execution, and more than two or three legal entities — if you need any of the three, Business Central will not stretch to it. The migration path between the two exists but is a re-implementation rather than an upgrade, so pick the right tier upfront even if it means paying for headroom.

Does Dynamics 365 support process manufacturing for food, chemicals, and pharma?

Partially, with caveats that matter. Supply Chain Management natively supports formulas, catch weights, batch attributes, and co-products and by-products, which covers straightforward process operations. It is materially shallower than S/4HANA or Infor CloudSuite Industrial for complex recipe management, multi-level by-product yield, grade-based pricing, and regulated batch records. Most successful process deals layer in ProcessForce by NeoVision (around £40 per user per month) or a Merit Solutions life-sciences accelerator for regulated batch-record compliance. UK food manufacturers should additionally test allergen management and BRCGS evidence generation specifically. Budget the ISV from day one, and treat its upgrade cadence and financial stability as part of your platform risk assessment — for a heavily regulated pharma or biotech manufacturer, a purpose-built platform is usually the lower-risk answer.

Is Dynamics 365 a good fit for metals manufacturers and steel service centres?

For fabricators and machine shops, yes — discrete make-to-order work with multi-operation routings and job-level costing is where both Microsoft manufacturing SKUs are strongest, though sheet remnant and drop-stock tracking needs an ISV or a nesting-software integration. For steel service centres and stockholders doing slitting and cut-to-length, it works but requires careful testing of dual units of measure (weight and length), heat-number tracking, and mill-certificate document management against real transactions before you commit. For foundries, forges, and heat treaters, where alloy chemistry, charge calculation, and furnace batch scheduling dominate, Microsoft is the weakest of the three metals segments and Infor CloudSuite Industrial or S/4HANA deserve a place on the shortlist.

How long does a Dynamics 365 manufacturing implementation take?

Four to nine months for Business Central Premium in a single-plant SMB manufacturer. Nine to eighteen months for Finance and Supply Chain Management in a one-to-five-plant mid-enterprise. Eighteen to thirty-six months for multi-country rollouts above ten plants. The largest schedule risk by a wide margin is master-data quality — items, BOMs, routings, customers, and suppliers almost always require more cleanup than buyers estimate, and the cleanup cannot be parallelised indefinitely. The second-largest is partner capability. Neither risk is reduced by choosing a different product.

Can Dynamics 365 integrate with MES, PLM, and CAD systems?

Yes, through documented patterns rather than plug-and-play connectors. On the MES side there are established integration approaches for Aveva (Wonderware), Siemens Opcenter, GE Proficy, and Rockwell FactoryTalk. On the PLM and CAD side, Autodesk Vault, Siemens Teamcenter, PTC Windchill, and SOLIDWORKS PDM are all commonly integrated, frequently via partner products such as Bluestar PLM. Middleware is typically Azure Logic Apps, Dataverse virtual entities, or a partner connector. Plan six to sixteen weeks per integration depending on depth, and be clear during design about which system is the master for item, BOM, and routing data — ambiguity there is the most common cause of integration rework.

Is Dynamics 365 cheaper than SAP S/4HANA for a mid-market manufacturer?

Usually yes, on total first-year cost, for manufacturers under about £400M revenue. The gap comes less from list licensing — the public-cloud S/4HANA editions have narrowed that considerably — and more from implementation effort and UK day rates. A mid-market discrete manufacturer will typically see a Microsoft proposal at 50–70% of an equivalent SAP proposal, with a shorter timeline. That advantage compresses as you add plants, countries, and regulatory requirements, and it inverts above roughly 25 plants or in heavily regulated process industries, where SAP's packaged capability means less configuration rather than more. Compare on five-year total cost including a realistic ISV stack, not on year-one licensing.

What does a Dynamics 365 partner implementation actually cost?

Partner fees typically run 2.5–4x first-year licensing for Supply Chain Management manufacturing deployments, and 1–1.5x for Business Central. On a £320,000 annual licensing footprint, expect £800,000–£1.3M in partner fees across the implementation. Partners with manufacturing-specific accelerators charge more per day but generally deliver faster with fewer scope failures than horizontal generalists, and the difference in total cost usually favours the specialist. The rate to scrutinise is not the headline day rate but the blend — how much of the delivery is senior manufacturing consultants versus offshore configuration resources, and which of the two will run your design workshops.

Which Dynamics 365 apps for manufacturing do buyers add beyond ERP?

The most common additions are Field Service (aftermarket service, warranty, and installed-base maintenance for equipment manufacturers), Sales with Customer Insights (long capital-equipment sales cycles and configured quoting), Project Operations (engineer-to-order and installation projects), and the Power Platform layer — Power BI for OEE and margin dashboards, Power Apps for plant-specific capture tools, and Copilot for exception summarisation. Asset Management sits inside Supply Chain Management rather than being a separate purchase. The sequencing advice is consistent: get the ERP core live and the production data trustworthy first, then add workloads. Buying the full suite in wave one is the most reliable way to add six months to an implementation.

Do shop-floor operators need a full Dynamics 365 licence?

No, and getting this wrong in either direction is one of the biggest swings on the subscription line. Operators who record job start and stop, quantities, scrap, and downtime generally need an Operations Activity licence (around £40 per user per month) rather than a full user licence, or an Operations Device licence (around £60 per device per month) where a terminal is shared across a shift. The Activity licence permits light transactional work but not master-data maintenance or approvals, so supervisors usually need a full licence. Model your user mix by role during evaluation and have the partner confirm the licensing position in writing — the difference between a well-modelled and a badly-modelled shop-floor user mix on 400 operators is easily six figures a year.

How does Dynamics 365 handle IoT and Industry 4.0 use cases?

Azure IoT Hub feeds machine telemetry into Supply Chain Management as machine signals, which drive condition-based asset maintenance, OEE dashboards in Power BI, and predictive quality alerts. The integration story is genuinely strong because Azure is first-party Microsoft rather than a partnership, which is a real differentiator against every other vendor in this comparison. Set expectations correctly, though: you build the IoT data layer in Azure (IoT Hub, Stream Analytics, and Fabric or Time Series Insights) and surface signals into the ERP. Telemetry-to-ERP is not out-of-the-box plug-and-play, but the foundation is solid and the skills to build it are widely available in the UK market.

Build Your Manufacturing ERP Requirements

The manufacturers who get this decision right are the ones who walk into demos with a scripted set of scenarios drawn from their own plant — a four-level BOM change, a mock recall, a configured order, a machine breakdown mid-shift — rather than a feature checklist. The manufacturers who get it wrong are the ones who let each vendor run their own demo script.

Our requirements tool builds a structured, weighted requirements document covering BOM and routing management, planning and scheduling, shop-floor execution, quality and traceability, warehouse, costing, and maintenance — organised so that manufacturing-specific requirements carry appropriate weight rather than being buried in a generic ERP checklist. Involve your operations manager, your planner, your quality lead, and your financial controller in building it; a manufacturing ERP selected by finance and IT alone will miss the requirements that decide whether the plant actually uses the system.

Build Your Manufacturing ERP Requirements Get Dynamics 365 Pricing Find a Manufacturing Partner Compare Manufacturing ERP Systems