A product configurator for Business Central lets a salesperson pick options on a sales line. Microsoft Dynamics 365 Business Central then creates the item, its Production BOM, its Routing, and its price from those choices. The result is ordinary Business Central master data, not a record in a separate CPQ system. This article explains what configure-to-order looks like in standard Business Central and why a separate CPQ tool creates a second product master. It then covers what Product Configurator from Insight Works does and does not do.
What does configure-to-order look like in standard Business Central?
Standard Business Central handles product variation in two ways, and neither one is a configurator. Item variants cover a fixed list of colors, sizes, or materials against a single item number. Assemble-to-order lets someone edit the component list of an assembly item on a sales order line. Microsoft Learn documents that feature under the title “Sell Items Assembled to Order” (assemble-to-order on a sales line).
Both approaches work when the number of combinations is small. They stop working when a product is defined by dimensions, dependent choices, or rules. “A shelving unit ten feet or longer needs a third upright” is a rule. A cabinet shop selling 4 widths, 6 finishes, 3 door styles, and 2 hinge options already has 144 combinations. Nobody wants 144 item cards, 144 Production BOMs, and 144 Routings maintained by hand.
The standard alternative is manual. Sales sends a description to engineering. Engineering creates the item and the Production BOM, then copies and edits a Routing, and then someone prices it. The quote goes out days later, and the work repeats for the next similar order.
Why does a separate CPQ system create a second product master?
An external CPQ system solves the selection problem and creates a data problem. The product structure now lives in two places. The CPQ tool knows the options, rules, and prices; Business Central knows items, BOMs, Routings, and costs. Every engineering change has to be made twice. Every order needs an integration to turn the configured result into something planning, production, and finance can post against.
In practice, that integration is where projects slow down. A configured product has to become a real item before a production order can exist for it. If the CPQ tool only passes a description and a price, someone in Business Central still builds the BOM and Routing by hand. If it passes a structure, the field mapping between the two product models has to be maintained forever.
A configurator that runs inside Business Central removes the second master. Options, rules, and prices are set up against Business Central item categories. The output is a standard item with a standard Production BOM and Routing. Planning, MRP, costing, and the production order behave exactly as they would for any other item.
How does a product configurator for Business Central build the item, BOM and Routing?
Product Configurator from Insight Works uses a three-level model. Configurator Item Categories hold Configurator Options, and each option holds Configurator Option Choices. An item category becomes configurable by being listed; there is no separate attribute or option-group object to maintain. The product configurator for Business Central is launched from a sales quote or sales order line, or from the menu.
The sequence on a sales line runs like this:
- The salesperson opens the configurator on the quote or order line and answers the options. Mandatory options render bold green when answered and bold italic red when still open. An incomplete configuration is therefore visible before anyone saves it.
- Each choice carries a unit price, so the price builds as choices are made. The Configurator BOM Price Sheet shows the per-option breakdown.
- On completion, the app creates one item per unique configuration. If the same configuration has been ordered before, it finds the existing item instead.
- Depending on the BOM Type on the item category, the app builds a Production BOM plus an item-specific Routing, or an assembly BOM. Routing run times come from configuration values, and an operation attached to a chosen option overwrites the matching base operation.
- Cost and weight are calculated from the selected options, including labor, and a standard cost is set on the generated item.
Quantities inside the BOM can be formula driven. A Child Qty. Calculation Formula such as Length * 1.1 derives a component quantity from a typed dimension, and a Scrap % can be set on item choices. Sub-configurations reach parent values with a Parent prefix, so a drawer inside a cabinet can size itself from ParentLength. Anyone comfortable with Excel formulas will recognize the expression evaluator, which covers trigonometry, rounding, minimum and maximum, powers, and conditional logic.
For a fuller walkthrough of the sales side, see quote generation with a configurator in Business Central.
How is a configured item priced?
Pricing is per choice. Each Configurator Option Choice carries a unit price, and the configured item’s price is the sum of the choices selected. Rules do not price; they enforce. The calculated figure is best understood as a list price built from the option sheet. Interaction with Business Central sales price lists, customer price groups, or line discounts is not documented. A company that relies on customer-specific pricing should test that flow first.
What do the rules do?
The Rule Builder is configuration, not code. A rule groups conditions with one of four group types: match all, match any, match none, or evaluate everything. It compares values with one of eleven operators. It then fires one of nine actions: continue, error, message, hide option, hide choice, show option, show choice, set value, or run another rule. A user prompt action offers a yes or no branch. Choice Combinations handle simple include and exclude behavior without a rule at all.
This is how “if it is ten feet or longer, you need these shelves” becomes an enforced constraint instead of tribal knowledge. The knowledge base documents rule definitions for configured products with examples.
Where does a Business Central product configurator stop?
Being clear about limits saves an implementation. Product Configurator launches from sales quotes and sales orders. It does not create item variants for the configured product; it creates items. Changing a choice’s price or component later does not update configurations already used. Routing run time is configurable, but changing an operation’s setup time requires an extension.
There is no customer-facing web configurator out of the box. A webshop or e-commerce front end is a separate development project, and the knowledge base carries the current extensibility options for a partner taking that on. There is no CAD integration. Highly variable configured products also forecast poorly, because each unique configuration is its own item with little sales history.
Setup effort is the honest caveat. Configurators are hard, and this one is setup-heavy and front-loaded on whoever owns the product data. Insight Works trains and supports but does not build configurations for customers. The related article on orders and quotes with a configurator for Business Central covers the order-to-production handoff in more detail.
Standard Business Central vs a product configurator for Business Central
| Need | Standard Business Central | Product Configurator |
|---|---|---|
| Fixed variations (color, size) | Item variants | Option choices; variants not created |
| Editable components on a sales line | Assemble-to-order components | Options drive BOM and Routing generation |
| Dimensional products (typed length or width) | Manual item, BOM and Routing per order | Formula-driven quantities and run times |
| Dependent choices and constraints | None; relies on people | Rule Builder and Choice Combinations |
| Pricing of the configured product | Manual or price list per item | Sum of option choice prices |
| Item creation | Manual | One item per unique configuration, reused on repeat |
| Production BOM and Routing | Created and versioned by hand (routings) | Generated from the configuration |
| Quoting without creating items | Not possible for new configurations | Quoting items store detail against a Configuration ID |
| Business Central license types | Per Business Central licensing | Essential, Premium, and Team Member listed as compatible on the app page |
How much setup does a Business Central product configurator take?
The setup lives on the configurator item category. The work is proportional to how many options and rules a product family has. A practical order of attack:
- Pick one product family with real variation and known BOM logic. Do not start with the hardest product.
- Separate options from components. A finish such as birch is not a component; it is a value that drives which components appear.
- Define option choices with unit prices, then the BOM lines and quantity formulas per choice.
- Copy and adjust the base Routing so operations attached to choices overwrite the right base operations.
- Add rules last, once the structure is stable, and run Check Configuration to catch common missing setup.
Commercially, Product Configurator is licensed per company on a subscription, and the app page lists Essential, Premium, and Team Member as compatible Business Central license types. Quoting items store detail against a Configuration ID and convert to a real item on order. As a result, a company that quotes a thousand configurations a month and closes ten does not create a thousand item numbers.
Frequently asked questions about a product configurator for Business Central
Does it auto-create the item, BOM and routing? Yes. Completing a configuration creates the item, its Production BOM (or assembly BOM, per the item category), and an item-specific Routing. A repeat configuration reuses the existing item.
How is a configured item priced? Each option choice carries a unit price and the configured price is the sum of the selected choices. Rules do not change price.
Can it work with a webshop? Not out of the box. A customer-facing front end is a separate development project; confirm the integration approach with your partner before scoping it.
Does the configurator create item variants? No. It creates one item per unique configuration. Variants remain a standard Business Central feature for fixed lists such as color or size.
Can a Team Member license user quote a configured product? The app page lists Team Member among the compatible Business Central license types, and the app itself is licensed per company. Microsoft defines what a Team Member can do on sales documents, so confirm the quoting flow for that license with your partner.
Does Business Central have its own CPQ? No. Standard Business Central offers item variants and assemble-to-order, which cover small fixed variation but not rule-driven or dimensional configuration.