Business Central for manufacturing companies: where the standard holds and where it tears

Business Central covers manufacturing solidly: bills of material, routings, multi-level production, make-to-order. But honestly: with high variant diversity, deep configuration or complex detailed planning, the standard tears. Then what counts is where you extend in a targeted way and what it costs, instead of overlooking every gap.

Where does the standard hold?

The Business Central standard carries further in manufacturing than many expect. For a large share of manufacturing companies it is enough without heavy customisation, and that is the cheaper and lower-maintenance basis. Microsoft documents the scope of the production modules openly and in full, from bills of material through routings to production order processing.

Source: Microsoft Learn: Manufacturing

• Multi-level bills of material with a clear structure.
• Operations and capacities via routings.
• Make-to-order for order-based manufacturing.

The practical benefit of this clarity is commercial. What the standard covers costs you configuration rather than development, and it survives every update without rework. So it pays to check your own requirements list against the standard first, before extensions or add-ons are discussed at all.

Where does it tear, and what does that mean?

Limits show up in three places: with genuine variant configuration, with very fine-grained shop-floor control and with complex detailed scheduling. Here you need extensions or specialised add-ons, and that decision belongs made deliberately rather than discovered during the project.

Honesty matters here: a manufacturing add-on closes functional gaps but brings its own cost, update dependency and integration effort. What you buy is not only functionality but a second vendor in your system landscape, whose release cycle you will have to plan around from then on.

That belongs on the table before the purchase, not after. The useful test question is: what share of our orders genuinely needs this capability, and what does the alternative in the standard cost? At ten percent exceptions, an add-on is rarely the cheaper answer.

Source: Microsoft Learn: About production orders

How do you model variant diversity deliberately?

Perhaps the most consequential decision is how you represent variant diversity. It determines master-data upkeep, inventory management and reporting for years to come, and it can only be corrected later at considerable effort. Three routes are available.

• Via item variants, when the differences are manageable.
• Via a configurator, when the combination diversity is high.
• Via separate items, when processes and reporting genuinely require it.

The most common mistake is the third route out of habit: every variant becomes its own item, because that is how it was in the legacy system. With a few dozen variants that works; with several hundred, master-data upkeep becomes a permanent burden. Before you buy an add-on, let us examine your manufacturing requirements: we say up front which ones the standard carries and which mean genuine extension effort.