Business Central Quotes and Production BOMs: Why They Don’t Match
There is a version of this story in nearly every Business Central manufacturing business that builds products to customer specification. A salesperson takes a requirement, works through the options with the customer, and produces a quote. The quote goes out. The order comes in. And somewhere between the sales order and the shop floor, the details change.
Sometimes it’s a small thing, a finish that was swapped, a component quantity that doesn’t match what was sold. Sometimes it’s more significant: a production BOM that reflects a standard configuration rather than the one the customer actually ordered. The result is the same either way. Manufacturing builds something. Sales sold something else. Someone has to reconcile the difference, and that someone is usually doing it manually, after the fact, under pressure.
This is the configure-to-order problem. It’s common, it’s costly, and it tends to get worse as product complexity increases.
Why the Gap Exists
The root cause is almost always a broken or missing handoff between the sales process and the production planning process. In businesses where products are straightforward, a fixed catalog, limited variants, predictable configurations, this handoff is easy. The sales order references a standard item. The BOM for that item already exists. Production picks it up and gets to work.
Configure-to-order is different. The customer is selecting from options. The finished product doesn’t exist yet as a standard item. Its BOM and routing need to be assembled from the selections made during the sales process. And in most businesses without a formal configuration tool, that assembly happens manually, either by a salesperson who also knows enough about production to build the BOM themselves, or by an engineer who takes the sales quote and rebuilds it from scratch.
Both approaches work at small scale. Neither scale reliably. As product complexity grows, more options, more combinations, more rules about what can and can’t be ordered together, the manual process becomes a bottleneck and an error source simultaneously.
The specific failure modes tend to cluster around a few recurring patterns:
- The BOM reflects the base item, not the configured item. A production BOM was created from a template and never updated to reflect the specific options on this order. Manufacturing builds the standard product. The customer receives something different from what they ordered.
- The quote and the BOM were built independently. Sales produced a quote. Engineering built a BOM. Both are internally consistent. They don’t match each other because they were created by different people from the same customer conversation, interpreted differently.
- A rule that should have prevented a bad combination didn’t. The salesperson selected options that aren’t physically compatible. Nothing in the system flagged it. The error reaches production.
- Costs on the quote don’t match costs in the system. The quote was built with one set of component costs. The BOM was generated with another. Finance reconciles the difference at month end.
These are not technology failures in the sense that the software broke. They are process failures enabled by the absence of a system that connects the sales configuration directly to the production output.
The Real Cost of Manual Configuration
The visible cost of this problem is re-work. A BOM that must be corrected before production can start. A production order that must be revised mid-run. A customer who receives the wrong product and has to be managed through a correction.
The invisible cost is harder to measure but probably larger. It lives in the time engineers spend rebuilding BOMs from sales quotes that should have generated them automatically. It lives in the caution that builds up around complex orders, the informal rule that certain products need to be reviewed by someone in engineering before they go to production, because experience has taught the team not to trust the handoff. It lives in the quotes that take longer than they should because the salesperson is waiting on confirmation that the configuration they’ve proposed is actually buildable.
None of this shows up as a line item. All of it shows up in capacity, throughput, and margin.
There is also a quoting cost that often goes unexamined. A salesperson who has to rely on an engineer to validate every complex quote is a salesperson whose response time is limited by engineering availability. In competitive markets, quote speed matters. The business that can respond to a complex configuration request in hours rather than days has a structural advantage over the one that can’t.
What a Properly Connected System Does Differently
The configure-to-order problem is solvable. The solution requires connecting three things that are currently disconnected in most businesses that experience it: the option selection process, the BOM generation process, and the rules that govern what combinations are valid.
When these are connected, the sales process and the production process stop being two separate workflows that have to be manually reconciled. They become a single workflow. The salesperson selects options. The system validates the combination against defined rules in real time. The BOM and routing are generated automatically from those selections. The production order is created with the correct configuration already embedded. There is no handoff to manage because the handoff is built into the process.
This changes several things at once.
Quote accuracy improves because the same logic that generates the BOM governs what the salesperson can select. If a combination isn’t valid, it’s excluded at the quoting stage, not discovered in production. The salesperson doesn’t need to know the production implications of every option choice, the rules handle that.
Quote speed improves because the salesperson is no longer waiting on an engineer to validate the configuration or build the BOM. The system does it. Response time is limited by the conversation with the customer, not by the capacity of the engineering department.
Cost accuracy improves because the BOM is generated from the same selections that generated the quote. Component costs flow from the configuration. There is no separate cost build to maintain in parallel.
And perhaps most importantly, the information that manufacturing receives is the information that sales produced, not an approximation of it, not a reconstruction of it, but the actual configured BOM derived from the actual customer selections.
What to Look for in a Configuration Tool
Not every configuration tool is the same, and the differences matter more than vendors typically acknowledge. A few capabilities are worth evaluating carefully before committing to an approach.
Rule enforcement at the point of selection, not after.
The value of rules is that they prevent bad configurations from being created, not that they flag them after the fact. A tool that validates after submission still requires someone to correct the quote and resubmit. A tool that enforces rules during selection prevents the problem from being created at all.
Automatic BOM and routing generation from the selected options.
This is the core capability. The BOM should be a direct output of the configuration, not something that has to be built separately. This includes handling both production BOMs and assembly BOMs, depending on the manufacturing model, and correctly generating routings for production-type items.
Cost calculation from the configuration.
The configured item’s cost should be calculated from the options selected, including component costs, resource costs, and any applicable waste or scrap factors. This cost should be consistent between the quote and the BOM, derived from the same source, not maintained separately.
Support for complex product hierarchies.
Products with sub-assemblies that are themselves configurable require a tool that can manage nested configurations. The cost and attribute logic needs to remain coherent through the hierarchy, parent configuration settings should propagate correctly to sub-configurations, not require manual replication.
Integration with planning.
A configured item that feeds correctly into MPS and MRP is a configured item that can be planned. The tool should connect naturally to Business Central’s planning functions, so that new configured products are visible to the planning engine from the moment the order is created.
Where Product Configurator Fits
Product Configurator from Insight Works is built specifically for Microsoft Dynamics 365 Business Central and addresses the configure-to-order problem within the platform businesses are already running on. It handles both production and assembly BOM types, enforces configuration rules at the point of selection, generates BOMs and routings automatically from the options chosen, and integrates with standard Business Central MPS and MRP.
It is designed to be approachable for businesses of varying size and product complexity, not a full CPQ platform requiring a lengthy implementation, but a focused tool that solves the specific problem of connecting sales configuration to production output within Business Central.
For businesses managing configure-to-order products and experiencing the gap between what sales quotes and what production receives, it is the closest available answer to the problem described in this article.
More information is available at CPQforDynamics.com. Businesses looking to implement can connect with any of Insight Works’ 750+ global Microsoft Partners.