What is CPQ?

What is a product configurator (CPQ)?

Configure, price, quote. How a true constraint solver produces error-free quotes and why fill-in order does not matter.

CPQ stands for Configure, Price, Quote. A product configurator lets sales reps, dealers or customers compose a valid product, calculates the price live, and generates the quote and bill of materials. But not all configurators are equal, the difference is in the technology underneath.

From multiplying to adding

Toolbox example: 30 pre-engineered articles versus 10 independent choices that only combine at configuration time
Two things that vary independently are two choices. Never one baked-together article.

The custom-work reflex turns a toolbox with 3 layouts × 5 colours × 2 materials into thirty articles. The modular approach says. These are 3 + 5 + 2 = ten independent choices, and combining happens at configuration time. A new colour is one line in the model, article codes follow automatically.

Constraint solver, not decision tree

A decision tree forces a fixed question order and breaks on whatever its builder did not foresee. A constraint solver considers all rules simultaneously. Fill-in order does not matter, what is impossible is not selectable (with the reason shown), and a valid configuration is complete by definition. Dimensions, BOM and price are all derivable. If a choice conflicts with an earlier one, you get a proposal instead of a dead end.

Why this matters

The system knows the origin of every value. Did the customer choose it, did a rule force it, or did the solver fill it in? So you can explain every value, to the customer and to the auditor.

Frozen versions keep quotes reproducible

A released model is frozen. A March quote keeps calculating with March's model, prices and screens, even after you change things in April. Modules version independently, and the register shows in advance who a change affects. Without this change process the first rush job wrecks your architecture. With it in place, a change is just work.

Prices live apart from the model

Your model builder decides what is possible, your commercial team decides what it costs. Price lists live apart from the product model. A price increase needs no model change, multiple lists (own sales, dealers, customer segments) run side by side with validity dates, and a missing price stands out instead of silently falling back to an old amount.

One model, three sales channels

The same product model serves your own sales team (faster quoting), your dealers (quoting independently at their purchase price, only within valid choices) and your website (visitors configure themselves and leave a lead with the configuration attached). Opening a new channel costs no new system, only a decision.

Start in Excel, end in the tool

Do not start with software. Start with a structured spreadsheet. Modules, variants and rules in plain language, plus the often-forgotten interfaces tab. When the web of cross-dependencies outgrows a human, the spreadsheet becomes your specification, and the configurator the engine. Excel is for thinking, RulePro is for scaling.

Where RulePro fits

Compared with spreadsheets. Rules are visible and explainable, several people work simultaneously without version chaos, and errors cannot arise instead of being spotted. Compared with the big CPQ suites. Configured in weeks rather than quarters, adjustable without consultants, and priced for SME manufacturing.

Frequently asked questions

What does CPQ mean?
CPQ stands for Configure, Price, Quote. It is software with which sales reps or dealers compose a valid product (configure), the price calculates live (price), and the quote plus bill of materials is generated automatically (quote).
What is the difference between a constraint solver and a decision tree?
A decision tree follows a fixed question order and only knows paths thought out in advance. A constraint solver considers all rules at once. Fill-in order is irrelevant, invalid combinations are not selectable, and every valid configuration is complete, including derivable dimensions, BOM and price.
Can a configurator handle price changes?
Yes, provided prices live apart from the product model. In RulePro the commercial team manages price lists with validity dates, per channel or customer segment. A running quote keeps the price level it was created with.
Does a configurator work for dealers and on a website?
The same product model serves three channels. Your own sales, a dealer portal (own purchase prices, only valid combinations) and a public web configurator that delivers leads with the configuration attached instead of an empty contact form.

See the constraint solver at work, on your own product.

In a demo you configure live, the price updates as you go, and you see why an invalid choice simply is not selectable. No decision tree, no dead ends.