Product configurator pricing: base prices, dimensions and quote approvals
A live total is useful only when the business can explain how it was calculated and which terms apply. Product dimensions, options and customer agreements need a controlled calculation path, with explicit treatment of exceptions.
In this guide
Inventory the price inputs
List the base product, dimensions, materials, accessories, quantity, customer list, currency and applicable charges. Identify which system owns each value and who may change it. Keep the product-rule approval separate from the commercial decision about the amount offered.
For a fictional custom-panel manufacturer, an area-based component may coexist with a fixed setup charge and selected accessories. The commercial team needs to state the approved units and formula. A developer should not have to infer whether a rate is per panel, per order or per square metre from a sample invoice.
Specify the calculation order
Write the sequence for base price, additions, discounts and other applicable amounts. Decide which values are inputs and which are derived. A discount applied to the entire total can produce a different result from one applied only to selected components.
Salesforce’s price-rule considerations show that calculation stages and downstream fields matter in a particular CPQ implementation. Use the broader lesson in procurement: ask the supplier to explain the actual calculation order rather than accepting a final number without its inputs.
Use an independent worked example
In a hypothetical example, a panel has a €100 setup charge, an area of two square metres at an invented rate of €50 per square metre and a €20 accessory. The subtotal is €220. If the fictional commercial rule discounts only the €100 area component by 10%, the result is €210 before any other applicable charges.
Discounting the entire €220 instead would produce €198. Neither is the right business rule until the commercial owner defines it. These figures are illustrative, not a vendor quote or tax calculation. Keep a hand-calculated reference case so the software’s result can be checked independently.
Define customer terms and exceptions
| Rule | Owner to confirm | Test to retain |
|---|---|---|
| Dimension formula | Commercial and product owner | Approved units and boundary values |
| Customer list | Account or dealer owner | Correct list for the signed-in context |
| Discount | Authorised approver | Scope, order and exception route |
| Price revision | Commercial administrator | Effect on new and saved quotes |
Record what happens when a price is missing or outside the intended range. The system should have a defined unresolved state or review route. Do not let an empty value become a plausible-looking zero-price quote without an approved policy.
Connect the total to the saved specification
Configurix’s pergola page describes pricing linked to the configured product. For a proposed implementation, ask the supplier to change dimensions and options, then show the price breakdown and saved quotation using the same revision.
For the panel manufacturer, the reviewer should be able to identify which size, finish and accessory produced the total. If the visual preview and price use different records, a customer can approve one specification while receiving another quote. Use a stable configuration reference and an understandable revision process.
Test price changes and reopened quotes
Change an approved test price table and reopen an earlier quotation. Inspect whether the original terms remain fixed, a new revision is created or the user is asked to recalculate. Agree the intended behaviour before release. A supplier’s default may not match the business’s quoting policy.
Test a manual exception and an unavailable price source. Check permissions for entering overrides and the information an approver receives. Record the outcome in the quote rather than relying on a separate private message. Include the receiving order system in the test if the implementation sends commercial data downstream.
Maintain a commercial regression set
Keep ordinary orders, boundary dimensions, customer-specific terms and exception cases with expected outcomes. Run that set when prices or rules change. Retain the effective date and owner of the released pricing configuration. Independent review helps catch a correct formula applied to the wrong scope.
Use the CPQ comparison guide and product-rule guide. The Configurix profile provides vendor context. Treat pricing maintenance as an ongoing commercial responsibility, with software supporting an agreed calculation rather than defining the agreement by accident.
Frequently asked questions
Why does pricing calculation order matter?
Discounts, additions and derived fields can produce different totals depending on their scope and sequence. Define the commercial rule explicitly.
Should old quotes change when the price list changes?
Agree the intended revision policy. Test whether saved terms remain fixed or a deliberate recalculation creates a new quote version.
How should a missing price be handled?
Use an explicit unresolved or review state under the business’s policy. Do not assume an empty input should become a zero-price offer.
Put the guide into practice
Explore product configurator tools, then compare your shortlist.
Explore the category →