Manufacturing and Production in Business Central

Most people who meet Business Central meet it as a finance and distribution system. They see the general ledger, the sales and purchase side, maybe inventory, and they assume that is the whole product. Then a manufacturing client asks whether it can run their shop floor, and the answer surprises people on both sides: yes, Business Central has a genuine, complete manufacturing module, with bills of material, routings, work centers, production orders, capacity planning and material requirements planning. It is not a bolt-on or a partner add-on. It is native functionality that ships with the product, and for a large band of discrete manufacturers it is more than enough. The catch is that it lives behind the Premium licence, it is built for discrete rather than process manufacturing, and it stops well short of a dedicated manufacturing execution system. This guide walks the whole engine, part by part, so you can judge where it fits your operation and where it does not.

The message up front: Business Central manufacturing is a real, well-integrated discrete-manufacturing engine that shares one database with your finance, inventory and sales. For make-to-stock and make-to-order discrete production, it is capable and cost-effective. It is not a process manufacturer's system, not a high-volume MES, and not a substitute for a shop-floor scheduling platform when your scheduling is genuinely complex. Knowing which of those you are is the whole decision.

1. Manufacturing in Business Central: what you get and the Premium licence requirement

Start with the commercial fact that shapes everything else, because it trips up more evaluations than any technical detail. Business Central is licensed in two tiers, Essentials and Premium. Everything most companies think of as core Business Central, finance, sales, purchasing, inventory, projects, warehousing, lives in Essentials. The full manufacturing suite, and the service management module, live only in Premium. If you intend to run production orders, routings and capacity planning, every full user who touches those areas needs a Premium licence, not an Essentials one. That is a per-user cost decision, and it needs to be on the table from the first conversation, because retrofitting Premium across a user base after the fact is an unpleasant surprise.

What you get for that Premium tier is a coherent, mature manufacturing module that has been part of the Dynamics NAV and now Business Central lineage for a very long time. The functional footprint covers production bills of material, routings with work centers and machine centers, production orders across their full lifecycle, capacity requirements planning, consumption and output posting, standard and actual costing of manufactured items, subcontracting, and the planning engine that ties supply to demand. Alongside it sits assembly management, which is lighter and, importantly, available in Essentials as well. That split between assembly and full manufacturing is one of the most useful design decisions in the product, and I will come back to it in detail.

The single biggest advantage of manufacturing in Business Central is not any individual feature. It is that all of it runs inside one system and one database with your finance, inventory, purchasing and sales. A production order consuming components posts inventory movements and cost entries in the same ledger your accountants close each month. There is no interface to build, no nightly synchronisation to reconcile, no second source of truth for stock. For a mid-sized discrete manufacturer, that integration is worth more than a longer feature list in a disconnected best-of-breed tool. For the wider context of what the platform covers beyond manufacturing, the complete features guide maps the full module set.

2. Production bills of material (BOMs)

Everything in manufacturing starts with the bill of material, and Business Central has two distinct kinds that people frequently confuse. There is the assembly BOM, used by assembly management, and the production BOM, used by the full manufacturing engine. They are separate objects with separate purposes, and choosing the wrong one is a common early mistake. This section is about the production BOM.

A production BOM is the recipe for a manufactured item: the list of component items and the quantities of each required to make one unit of the parent. In Business Central the production BOM is a versioned master record with its own status field, typically moving from New to Certified before it can be used, and Under Development or Closed when it is being revised or retired. The Certified status is a deliberate control: you cannot release a production order against an uncertified BOM, which stops half-finished recipes from reaching the shop floor. That certification gate is a small feature that prevents a large class of errors.

Production BOMs support multiple lines per component, unit-of-measure conversion so you can define a component in a different unit from how it is stocked, and scrap percentages so the BOM reflects that you actually consume more than the theoretical quantity because some is lost in production. Crucially, a production BOM line can itself point to another item that has its own production BOM, which is how Business Central represents multi-level manufacturing: subassemblies made in-house, each with their own recipe, feeding a higher-level parent. The system understands that hierarchy when it plans and when it costs, which matters enormously for anything more complex than a single-stage build.

Versioning deserves a specific mention. Production BOMs and routings both support version control with effective dates, so you can define that version two of a recipe takes effect from a given date while version one remains the record for everything produced before it. For a manufacturer whose products evolve, this is not a nicety, it is the difference between a traceable engineering-change history and a mess of overwritten masters. Set up versioning discipline early, because retrofitting it after a year of undated changes is painful.

3. Routings, work centers and machine centers

If the production BOM answers "what goes into the product", the routing answers "how it is made and where". A routing is the ordered sequence of operations required to manufacture an item, and each operation is performed at a work center or a machine center. The BOM and the routing are the two halves of a manufactured item's definition, and the full manufacturing engine needs both.

Business Central models capacity at two levels. A work center is the broader unit, often a department, a team or a group of interchangeable resources, with a defined capacity, a shop calendar, and cost rates. A machine center is a more granular resource that belongs to a work center, representing an individual machine or workstation with its own capacity and its own rates. You do not have to use machine centers; many implementations model capacity at the work center level alone and find that sufficient. You add machine centers when you need to schedule and cost at the individual-machine level. The choice is a modelling decision about how much granularity your scheduling genuinely needs, and more granularity is not automatically better because it adds maintenance overhead.

Each routing operation carries the times that drive both scheduling and cost: setup time, run time per unit, and often wait and move times between operations. Setup time is fixed per operation regardless of quantity, while run time scales with the number of units. Business Central uses these times against the work or machine center calendar to calculate how long a production order will take and when each operation should start and finish. The same times, multiplied by the center's cost rates, feed the labour and overhead portion of the manufactured cost. Getting these times reasonably accurate is where routing setup earns its keep, because they drive both your schedule and your product cost.

Practitioner's note: routings support both serial and parallel operation sequencing through the next-operation and routing-link fields. Most implementations only ever need serial routings, one operation after another. Reach for parallel routing only when you genuinely have concurrent operations, because it complicates scheduling and troubleshooting for a benefit that many shops do not actually realise on the floor.

4. Production orders and their lifecycle (planned, firm planned, released, finished)

The production order is the central working document of the manufacturing engine. It represents a specific instruction to make a specific quantity of a specific item, and it moves through a defined lifecycle of statuses that mirror the real progress of the job from a plan to a completed build. Understanding those statuses is understanding how the whole module behaves.

• Planned: a suggestion generated by the planning engine, not yet committed. Planned production orders are the raw output of MRP and can be regenerated, changed or deleted freely by the next planning run. They are proposals, and the planning system owns them.
• Firm Planned: a plan you have accepted enough to protect from the next planning run, but not yet released to the floor. Firm planned orders hold their place, keep their number, and let a planner lock a schedule while still fine-tuning it. This is the staging status where human judgement overrides the raw plan.
• Released: the order is live on the shop floor. Releasing a production order is what makes components available to consume and operations available to post output against. Warehouse and inventory activity happens against released orders. This is the status where real material and real time get recorded.
• Finished: the job is complete. Finishing a production order closes it, stops further posting, and triggers the final cost calculations that settle the actual cost of what was made. A finished order is a historical record and, in normal operation, is not reopened.

The flow from planned to firm planned to released to finished is not merely administrative. Each transition changes what the system allows and what it posts. You can create production orders manually at any status, or let the planning engine create them as planned orders that you then carry forward. In practice a healthy shop uses both: the planning engine proposes the bulk of the schedule, and planners create or adjust orders by hand for the exceptions. The status model gives you a clean separation between what is proposed, what is committed, what is in progress, and what is done, which is exactly the control a production environment needs.

5. Capacity planning

Having defined routings against work centers and machine centers with real times and calendars, Business Central can tell you whether you actually have the capacity to make what you have planned. This is capacity requirements planning, and it is one of the areas where people expect either too much or too little from the product.

The mechanism is straightforward in principle. Every routing operation on a released or firm planned production order consumes capacity at its work or machine center, measured in time against that center's available calendar. Business Central rolls those loads up so you can see the total demand on each center over a period and compare it against available capacity. The load bars and capacity views make it visible when a center is overloaded, so a planner can move work, add a shift, or push a due date. For the operations backlog view, this is genuinely useful and it comes with the module at no extra cost.

The honest boundary is around scheduling sophistication. Business Central performs finite and infinite capacity calculations and will schedule operations forward or backward against the calendar, but it is not a finite-capacity scheduling optimiser in the sense a dedicated advanced planning and scheduling tool is. It will not automatically sequence hundreds of jobs across constrained machines to minimise changeovers and hit every date. It gives you visibility of load and a competent forward and backward scheduler, and it expects a planner to make the real sequencing decisions. For many discrete shops that is precisely the right amount of automation. For a high-mix, high-constraint environment where scheduling is the core competitive problem, it is a signal that you may need a specialised scheduling layer alongside it.

6. Consumption and output posting

A production order does two fundamental things to inventory: it consumes components and it produces output. Consumption reduces the stock of raw materials and subassemblies, and output increases the stock of the finished item. Both are recorded through journals, and understanding how they post is understanding how manufacturing touches your inventory and your ledger.

Consumption is posted through the consumption journal, which records that the components listed on the production BOM were drawn from stock to make the item. Business Central supports two philosophies here. Manual consumption means someone explicitly records what was consumed, which gives accuracy at the cost of shop-floor effort. Automatic consumption, driven by the flushing method on each component, means the system posts consumption for you based on either the release of the order (forward flushing) or the reporting of output (backward flushing). Backward flushing is the common choice: when you report that you produced ten units, the system automatically consumes the components those ten units required, according to the BOM. Flushing is a powerful labour saver, but it assumes the BOM is accurate, because the system consumes what the BOM says rather than what physically happened.

The honest limitation: automatic flushing is only as truthful as your BOM and your scrap factors. If the BOM says a unit needs two of a component but the floor really uses two and a half because of scrap you never captured, backward flushing will silently under-consume, and your inventory will drift out of line with reality over time. Flushing does not remove the need for accurate BOMs and periodic physical counts. It moves the discipline upstream into the master data rather than eliminating it.

Output is posted through the output journal, which records the quantity of finished item produced and the time spent on operations. Reporting output at an operation both adds the finished quantity to inventory (when it is the last operation) and posts the capacity time consumed, which is what feeds the labour cost. You can report output progressively as each operation completes, or in one posting at the end, depending on how much shop-floor granularity you want. The output posting is also where scrap and reject quantities are captured, so the difference between what you started and what you finished is recorded rather than lost.

7. Costing of manufactured items

The cost of a manufactured item is not a single number you type in. It is built up from the cost of the components consumed plus the cost of the capacity used to make them, and Business Central assembles it automatically from the BOM, the routing and the postings against the production order. How that cost is calculated depends on the item's costing method, and this is where manufacturing costing connects directly to the broader inventory-valuation picture covered in the inventory management guide.

For manufactured items, two costing methods dominate. Standard costing sets a predetermined cost for the item, its components and its routing operations, and measures actual production against that standard, throwing the difference into variance accounts. Standard costing is the traditional manufacturing choice because it gives stable product costs and makes variances visible, which is exactly what a cost accountant wants to analyse. The alternative is an actual-cost method such as average or FIFO, where the manufactured cost reflects what the inputs actually cost at the time. Average costing is simpler to run and avoids variance accounting, but it gives you a moving cost rather than a stable standard to measure against.

The cost build-up itself has a recognisable structure. Material cost comes from the components on the production BOM, valued by their own costing method. Capacity cost comes from the routing times multiplied by the work and machine center rates, split into direct labour and overhead. Business Central also supports subcontractor cost as a distinct element and manufacturing overhead applied as a percentage or a fixed charge. The rolled-up standard cost of a manufactured item is calculated from all of these across every level of the BOM, so a multi-level product correctly inherits the cost of its subassemblies. When a production order finishes, the system settles the actual cost and posts any variance against the standard, which is what closes the loop between the planned cost and what the job really consumed.

The practical advice I give is to decide the costing method deliberately and early, because changing an item's costing method after it has transactions is disruptive. Standard costing rewards manufacturers who have the discipline to maintain standards and genuinely want variance analysis. Average costing suits those who want simplicity and can live with a cost that moves. Neither is wrong; they answer different management questions, and the wrong choice creates months of confusing numbers before anyone diagnoses it.

8. Assembly management: assemble-to-order versus full manufacturing (the merged assembly topic)

This is the section that saves the most implementations from over-engineering themselves, so it is worth reading slowly. Business Central has a second, lighter build capability called assembly management, and it is genuinely different from the full manufacturing engine. It exists precisely because not every "made" item needs routings, work centers, capacity planning and production orders. Many products are simply a kit of parts put together, and for those the full manufacturing machinery is overkill.

Assembly management uses an assembly BOM rather than a production BOM, and it works through assembly orders rather than production orders. An assembly BOM lists the components and, optionally, resources needed to build an item, but it has no routing, no work centers, and no capacity scheduling. You assemble the item, the components are consumed and the assembled item is added to stock, and that is the whole cycle. It is deliberately simple. And critically, assembly management is available in the Essentials licence, not just Premium, which makes it the right tool for a large number of companies that assemble but do not truly manufacture.

The standout capability of assembly is assemble-to-order. Business Central lets you link an assembly directly to a sales order line, so that when you sell the item, an assembly order is created and fulfilled as part of the sale, potentially with customer-specific configuration of the components on that line. This is powerful for kit and bundle sellers, for light configure-to-order products, and for anyone who assembles finished goods only when there is an order to fulfil. The contrast is assemble-to-stock, where you build assemblies to replenish inventory ahead of demand, exactly as you would make-to-stock in full manufacturing. Both patterns are supported, and the assemble-to-order link to the sales line is one of the neatest pieces of design in the product.

The distinction that matters: use assembly when the build is essentially "gather these parts and combine them", with no meaningful operation sequence, no machine scheduling and no multi-stage in-house subassembly you need to plan and cost. Use full manufacturing when the build has real operations at real work centers, needs capacity planning, involves multi-level production, or requires routing-based cost. A surprising number of companies that assume they need the full Premium manufacturing engine are actually assemblers who would be better served, and better licensed, by assembly management in Essentials. Test that assumption before you commit to Premium across the user base.

The honest limitation of assembly is the flip side of its simplicity. Because there is no routing, there is no operation-level scheduling, no capacity planning, and no routing-based labour costing beyond the resources you attach to the assembly BOM. If you need to know that operation two on machine three is the bottleneck next Tuesday, assembly will not tell you, and you need full manufacturing. The two are not competitors; they are two points on a spectrum, and mature Business Central shops use both, assembly for the kits and simple builds, full manufacturing for the genuinely produced items.

9. Subcontracting

Few manufacturers do every operation in house. Plating, heat treatment, painting, specialist machining and similar operations are routinely sent out to a subcontractor and returned for the next in-house step. Business Central handles this through subcontracting, which is modelled cleanly as a special kind of work center rather than as a bolt-on.

The mechanism is elegant. You define a work center as a subcontractor and link it to a vendor. A routing operation performed at that subcontractor work center is then flagged as a subcontracted operation. When the planning engine sees demand for that operation, it can generate a purchase order to the subcontractor for the service, tied to the production order, through the subcontracting worksheet. The component material flows to the subcontractor, the service is purchased, and when the item comes back the operation is received and the subcontractor cost is captured against the production order as part of the manufactured cost. Because the subcontracted step is just an operation in the routing, it sits in the correct sequence and the schedule accounts for it.

What makes this worth the setup effort is that the subcontractor cost lands in the right place automatically. It becomes part of the rolled-up cost of the manufactured item alongside material and in-house capacity, rather than sitting as a disconnected purchase you have to manually associate. For manufacturers with a meaningful outsourced-operation content, subcontracting is one of the genuinely strong pieces of the module. The main thing to get right is the material handling, tracking what you sent out and what came back, because that is where subcontracting processes most often go loose in practice.

10. Supply planning: MRP, MPS and the planning worksheet

The planning engine is what turns demand into a coordinated set of supply suggestions across purchasing and production, and it is the piece that ties the whole module together. Business Central provides both master production scheduling and material requirements planning, and it surfaces their output through planning worksheets.

The distinction between the two is worth being clear on. Master production scheduling (MPS) plans the items that carry independent demand, typically the finished goods and saleable items whose demand comes from sales orders and forecasts. Material requirements planning (MRP) then plans the dependent-demand items, the components and subassemblies whose demand is derived from the production BOMs of the items MPS planned. In Business Central you can run them together or separately, and the calculation walks down through the BOM levels, netting demand against available supply and existing orders at each level, and proposing new supply where there is a shortfall.

The output lands in the planning worksheet as action messages: create a new production order, create a purchase order, change a quantity, reschedule a date, or cancel an order that is no longer needed. The planner reviews these suggestions and accepts the ones that make sense, at which point Business Central creates the planned production orders and requisition-worksheet purchase orders. What drives the suggestions is the reordering policy and planning parameters on each item: reorder point, safety stock, lot-for-lot or fixed reorder quantity, lead times and order modifiers. These parameters are where planning quality is actually determined. A planning run is only as good as the item-level parameters feeding it, and the most common cause of a planning engine "not working" is not the engine, it is missing or wrong lead times, reorder policies and safety stocks on the items.

A caution on planning parameters: teams frequently switch on MRP with default or blank planning parameters, get a flood of nonsensical suggestions, lose trust in the engine, and revert to spreadsheets. The engine is not at fault. Planning is a data-quality discipline before it is a software feature. Budget real time to set reordering policies, lead times, safety stocks and lot sizes item by item, and to keep them current, or the planning worksheet will produce noise rather than signal. This is unglamorous master-data work, and it is the difference between MRP that a planner relies on and MRP that gets ignored.

11. When Business Central manufacturing is enough, and when you need a dedicated MES or a bigger ERP

This is the section that vendors selling Business Central would rather skip and that a manufacturer evaluating it most needs. The module is capable, but it has a defined envelope, and pretending otherwise leads to painful implementations. Here is the honest map of where it fits and where it does not.

Business Central manufacturing is a strong fit when you are a discrete manufacturer, meaning you make countable, assembled or machined units rather than blending continuous batches. It fits make-to-stock, make-to-order and light configure-to-order production. It fits multi-level BOMs with in-house subassemblies. It fits shops where a planner makes the sequencing decisions and the system provides visibility rather than autonomous optimisation. It fits companies that value having production, finance, inventory and sales in one integrated system over having the deepest possible manufacturing feature set. For a very large band of small and mid-sized discrete manufacturers, that description fits well, and Business Central will serve them for years.

It is the wrong fit, or an incomplete one, in several identifiable cases. Process and formula-based manufacturing, chemicals, food and beverage, pharmaceuticals, where you work in recipes with yield variability, co-products and by-products, catch weights and potency, is not what the native module is built for. Business Central models discrete BOMs, not process formulas, and while partner add-ons extend it toward process manufacturing, that is a signal you are outside the core design. Heavy shop-floor execution, real-time machine data capture, operator terminals, detailed quality workflows and traceability at MES depth, is beyond the native module and points to a dedicated manufacturing execution system integrated alongside Business Central rather than replacing it. And genuinely complex finite-capacity scheduling, high-mix low-volume shops where optimal sequencing across constrained machines is the core competitive problem, exceeds the built-in scheduler and calls for an advanced planning and scheduling layer.

The larger-ERP question sits above all of this. If your manufacturing complexity, plant scale, or regulatory and traceability demands are genuinely at the tier of a large multinational running many plants with deep process control, you are in the territory of a heavier ERP built for that scale, and Business Central will feel like it is stretching. The honest test is not "can Business Central technically do this", because with enough customisation and add-ons it often can, but "am I fighting the product or flowing with it". When you find yourself bolting on module after module to reach process manufacturing, MES-depth execution and optimising schedulers, the accumulated cost and fragility usually argue for either a purpose-built system integrated with Business Central for finance, or a different ERP altogether. For a structured way to run that fit decision across the whole platform, the is Business Central right for your organisation guide works through it, including the manufacturer's angle specifically.

Final thoughts

Business Central manufacturing is one of the most under-appreciated parts of the product, precisely because so many people never see past finance and distribution. For a discrete manufacturer that fits its envelope, it delivers a complete, integrated engine, production BOMs, routings, work and machine centers, the full production-order lifecycle, capacity planning, consumption and output posting, standard and actual costing, subcontracting and a real MRP and MPS planning engine, all sharing one database with the accounts. That integration is the quiet advantage that outweighs a longer feature list in a disconnected best-of-breed tool. And the assembly module beneath it means the many companies that assemble rather than truly manufacture can get their build capability, and assemble-to-order, without paying for Premium or wrestling with routings they do not need.

The discipline that makes it work is the same discipline that makes any manufacturing system work, and it is unglamorous: certified BOMs, honest routing times, deliberate costing-method choices, and above all clean, current planning parameters on every item. The engine rewards good master data and punishes bad master data, loudly. Get the data right and Business Central manufacturing quietly runs a real shop. Get it wrong and no amount of the module's capability will save you. And when your operation is genuinely process-based, MES-deep or scheduling-heavy, the honest move is to recognise the edge of the envelope and integrate the right specialist system rather than bend Business Central past what it was built for. Knowing where the product is enough, and where it is not, is the practitioner's judgement that keeps a manufacturing implementation honest.

Related reading: Business Central features: the complete guide, Inventory management in Business Central, Is Business Central right for your organisation?.