Dynamics 365 ships no native CPQ. AltoLeap builds custom product configuration that feeds Business Central with validated configurations, BOMs and routing operations.
★★★★★5.0 across verified Clutch reviews · proven with manufacturers ↗Dynamics 365 Sales handles catalog quoting well enough: price lists, line items, pricing rules, discounts, taxes, and a PDF quote off a Word template. What it has no answer for is configuration. Nothing in it checks that a combination of options can actually be built, and nothing works out the parts and operations those choices imply.
So the quote still gets assembled by the person who holds the rules in their head, and that person becomes the constraint on how fast you can sell. Microsoft's 2026 release wave 1 plan for Sales lists 31 features, and not one of them touches quoting, pricing or configuration. This gap is not closing.
An option combination gets through that engineering then has to unpick. The customer has already seen a price, so the cost of the correction lands on you rather than on them.
When pricing lives in a spreadsheet beside the ERP rather than in the rules, the small misses do not show up as errors. They show up as a gross margin nobody can quite explain.
Configuration knowledge that lives with two senior estimators is a bottleneck on a good week and a stoppage on a bad one.
Every option, dependency and exclusion encoded once, so invalid combinations cannot be selected rather than being caught downstream.
Not a finished-goods SKU with options bolted on, but resolution all the way to the materials and components the selections actually imply.
The configurator resolves choices into the objects an ERP consumes, instead of leaving someone to translate a quote into a works order by hand.
Cost, margin, channel and regional logic resolved against the configuration as it is built, not applied to it afterwards.
The quote document, supporting drawings and specification generated together from one configuration.
Review and handoff steps modelled as your process actually runs, which is usually where packaged tools force the worst compromises.
The configuration flows to the systems that need it rather than being re-entered into each one.
A configurator handling a product where the valid combinations outgrew what any spreadsheet could hold, in daily production use.
Configurable parameters driving the drawings themselves, so the documents come out of the configuration rather than being redrawn per order.
Configuration, pricing, documents and handoff to production running as one system rather than four that someone keeps in sync.
Configuration rules should be deterministic. A quote that is right because a model guessed well is not a quote you can build from, so the rules engine stays rules.
Where AI earns its place is around the edges: reading an incoming RFQ or spec sheet and proposing a starting configuration, flagging a quote that looks unlike anything you have sold before, and drafting the narrative parts of a proposal. The configuration itself stays deterministic, auditable, and yours.
Tell us how you quote today; we confirm it's a fit.
A focused session that maps your quoting rules, scope, risks, and a costed Phase 1.
We build Phase 1 around what creates value now, architected to grow.
We support and evolve the system as your products and pricing change.
The configurator holds the option set, the rules connecting them, and the logic that turns a valid selection into a specific product. The output is not a description of what the customer wants. It is a resolved bill of materials and a set of routing operations, which is the difference between a quote your ERP can act on and a quote someone has to interpret.
That resolution is what makes the rest possible. Pricing computes against real parts. Drawings generate from real dimensions. The works order is created from the same configuration the customer approved, not from a second interpretation of it.
AltoLeap's configurator engine already produces what Business Central consumes: derived values, a resolved bill of materials, and routing operations. The integration work is therefore mapping and transport rather than rebuilding logic, because the logic lives in the configurator.
The connector is in development, and the design is direct. When a configuration completes, its resolved BOM and routing map onto Business Central's item, BOM and routing structures through the Business Central API. The sales document is created or updated against that same configuration, so the quote, the order and the production data all trace back to one source instead of being re-keyed between systems.
AltoLeap works alongside a Business Central implementation partner on the ERP side of this work.
Most manufacturers running Dynamics are not short of systems. They are short of agreement between them. The configuration sits in one place, the pricing in another, the drawings in a third, and the ERP receives a summary that someone typed.
A configurator that resolves to structured data removes the retyping, and with it the drift. What the customer approved, what gets priced, what gets drawn and what gets built all come from the same configuration record. See our custom CPQ and quote automation work, our CAD drawing automation, and the CPQ for manufacturers guide.
No. Dynamics 365 Sales quotes from a catalog with price lists, discounts and templates, but it has no configuration rules engine and no check that a product combination is buildable. Business Central handles items, BOMs and routings on the ERP side but has no sales-side configuration engine either. Microsoft's 2026 release wave 1 plan for Sales adds no quoting, pricing or configuration features.
Business Central is one product inside the Dynamics 365 family, the ERP aimed at small and mid-size businesses, formerly Dynamics NAV. Dynamics 365 also covers the CRM applications such as Sales, and the enterprise products Finance and Supply Chain Management. They are different products with different APIs, so an integration with one is not an integration with the others.
Custom, built around your configuration and pricing rules. Several mature CPQ products plug into Dynamics, and where your rules fit what they model, a licensed product is cheaper and faster. We will say so on the call if that is the better answer for you.
No. The configurator sits in front of Dynamics and feeds it. Dynamics stays your system of record. If you are migrating from AX or NAV to Business Central, that is usually the best moment to rebuild configuration properly rather than carry the spreadsheet across, because the item and BOM structures are being touched anyway.
A first phase typically runs $50,000 to $100,000 and delivers a working system against one real quoting process. Cost scales with the number of rules to encode, the systems to integrate, and how much of the current process is undocumented.
AltoLeap builds custom product configurators and quoting systems for made-to-order and engineered-to-order manufacturers, designed to feed an ERP such as Dynamics 365 Business Central with validated configurations, bills of materials and routing operations.
Through a connector, currently in development, that maps the configurator's resolved bill of materials and routing operations onto Business Central's item, BOM and routing structures, and creates or updates the sales document against the same configuration. The engine side already produces those objects today. We work alongside a Business Central implementation partner on the ERP side, and we are happy to walk through exactly where the work stands on a call.
Tell us how configuration and quoting work today. We will tell you straight whether a custom configurator is worth it, or whether a packaged tool fits you better.