CPQ is where a configurable product meets the person selling it. For a B2B manufacturer that person is often a dealer, working on a project with hundreds of line items and a deadline tomorrow. CPQ has to make that person fast without letting them sell something the plant can't build.
The three letters
- Configure: walk the option model and its constraints to a valid product.
- Price: list price from a build-up of options, then discounts, dealer multipliers, surcharges and contract pricing.
- Quote: documents, approvals, revisions and, when it's won, a clean order into ERP.
Where CPQ meets everything else
In furniture, many dealers specify in design tools such as CET or pCon before anything reaches the manufacturer's CPQ. That means the same product data has to stay consistent in several places: option codes, price lists and rules. When they drift apart, a quote that looked perfect becomes order fallout at order entry.
Where it goes wrong
- CPQ and ERP rules are maintained separately and disagree.
- Prices are published before the configuration rules for a new option are live.
- Approvals become the place where configuration errors are caught by hand.
Questions people ask
Should rules live in CPQ or in ERP?
Ideally once, with the other system reading them. When that isn't possible, the two rule sets need shared test configurations so drift is caught before dealers find it.
Is CPQ only for complex products?
No, but it pays for itself fastest where options multiply and pricing depends on the configuration.
Updated November 2026. Think I've got something wrong? Tell me.