Configurix

Live product pricing guide

Every price, explained from product choice to approved quote.

A product configurator pricing engine turns valid dimensions, materials, options and quantities into the correct commercial result for a customer, dealer, market and date. The result should be immediate, reproducible and traceable—not a number detached from the configured product.

Clear definition

Live pricing is a calculation contract.

A connected pricing engine receives an accepted configuration: the exact product family and revision, stable option IDs, dimensions, quantities and derived values. It combines that product state with commercial context such as price list, account, channel, country, currency, date, discount permissions, services and tax treatment.

It returns a structured result. That result can include base price, option and quantity lines, surcharges, services, discounts, net value, tax, gross value, currency, messages, approval status and the calculation revision. The visible total is only the last line of a much more important record.

Configurix can connect 3D product configuration to formula, matrix, unit, dimension, account and market pricing. The exact source of truth and calculation responsibilities are defined for each implementation so the website, salesperson, quote and receiving system do not invent separate answers.

Interactive pricing lab

Change the product. See every price decision.

This worked example exposes the calculation order for a bioclimatic pergola. Its sample values demonstrate the method; they are not a Configurix subscription price or a customer quotation.

Configuration inputs

Bioclimatic pergola

Valid product
Roof system
Compatible options
Customer context
Market and currency

Price result · PR-1042

Dealer account · European Union · EUR

€13,954

Gross · 21% example tax

Bioclimatic frame

BASE-BIO

€2,450

14.7 m² configured area

AREA-ROOF

€5,072

Louvered roof package

ROOF-LOUVERED

€2,450

Integrated zip screen

SCREEN-ZIP

€1,280

Dimmable LED package

LED-DIM

€430

Installation package

INSTALL

€853

Configured subtotal€12,535
Dealer account adjustment · 8%−€1,003
Net price€11,532
Example tax · 21%€2,422

Validation

Accepted

Discount policy

Within policy

Price revision

EU-2026.08

Reproducible result

Configuration revision, stable item codes, commercial context and ordered price lines can travel together to the quote or receiving system.

Pricing method library

Ten building blocks for configurable-product prices.

Most real catalogues combine several methods. The important work is defining units, precedence, boundaries, fallbacks, revisions and evidence for every method used.

Fixed amount

A stable amount for a product, package or service.

Control hub: €420

Per unit

Quantity multiplied by an accepted unit price.

Heaters: 2 × €310

Length or perimeter

Profiles, screens, rails or finishing priced from calculated length.

Front screen: 4.2 m × €185

Area or volume

Roofing, glazing, fabric, panels or capacity priced from geometry.

Roof: 14.7 m² × €345

Band or block

A controlled price applies when a quantity or dimension enters a range.

Width 4.01–5.00 m: band B

Matrix lookup

Two or more inputs select an approved price cell or table row.

Width band × projection band

Formula

A documented expression uses dimensions, quantities or derived values.

Base + area rate + post count

Percentage

Margin, uplift, discount, commission, tax or another controlled adjustment.

Dealer adjustment: −8%

Conditional surcharge

A valid selection, site condition or combination activates an amount.

Reinforced beam when span exceeds 5 m

Minimum or maximum

A price floor, cap or minimum service charge controls the result.

Installation minimum: €850

Calculation order

A pricing waterfall people can audit.

Order matters. A discount applied before a surcharge can produce a different result from the same discount applied after it. The calculation sequence should be explicit, versioned and repeated consistently.

1

Accepted product state

Product family, model revision, stable selections, dimensions, quantities and derived values pass validation first.

2

Base and configuration price

Apply base product, size, material, component, package, option and dependency-driven amounts.

3

Commercial context

Resolve price list, account, channel, market, currency, quantity tier and effective date.

4

Services and project charges

Add survey, installation, delivery, engineering or other scoped project-level charges.

5

Discount and approval controls

Apply allowed promotions and user adjustments, then enforce margin, floor and approval rules.

6

Tax, rounding and result

Use the agreed tax owner, currency precision and rounding policy before returning a versioned result.

Source-of-truth design

One owner for every pricing responsibility.

Configurix does not require every business to move pricing into one new database. It can calculate, synchronize or call an existing authority. The important decision is who owns each field and what the customer journey does when that owner changes or becomes unavailable.

Product validity

Configuration model

Only an accepted product state can request a sellable price.

Product and option identity

Catalogue, PIM or ERP

Stable IDs identify every priced family, option, component and service.

Price lists and conditions

ERP, CPQ or pricing service

Name the authoritative list, condition record, date and synchronization policy.

Account and opportunity

CRM, B2B portal or commerce

Pass the correct account, segment, channel and authorization context.

Tax

ERP, commerce or tax service

Define whether displayed prices are net or gross and which system calculates liability.

Issued quote

CPQ or document workflow

Lock configuration, price result, currency, terms and revision at issue time.

Price result contract

Store enough evidence to reproduce the answer.

A price result is a versioned business record. It should identify what was priced, which commercial context applied, how every adjustment was calculated and whether the result can be quoted, approved, ordered or only reviewed.

Identity

Result ID, configuration ID and revision, product-model revision and status.

Context

Account, channel, market, currency, quantity, effective date and price-list revision.

Calculation

Stable line codes, quantities, units, rates, formulas, adjustments, net, tax and gross.

Governance

Messages, approval state, user changes, expiry, destination and audit timestamps.

{
  "priceResultId": "price_1042_r3",
  "configuration": { "id": "cfg_7X4P2", "revision": 3, "state": "valid" },
  "context": { "accountId": "dealer_18", "market": "EU", "currency": "EUR" },
  "source": { "priceList": "DEALER-EU", "revision": "2026.08", "effectiveAt": "2026-08-19" },
  "lines": [
    { "code": "BASE-BIO", "quantity": 1, "unit": "each", "amount": 2450 },
    { "code": "AREA-ROOF", "quantity": 14.7, "unit": "m2", "amount": 5072 },
    { "code": "ROOF-LOUVERED", "quantity": 1, "unit": "each", "amount": 2450 },
    { "code": "SCREEN-ZIP", "quantity": 1, "unit": "each", "amount": 1280 },
    { "code": "LED-DIM", "quantity": 1, "unit": "package", "amount": 430 },
    { "code": "INSTALL", "quantity": 1, "unit": "project", "amount": 850 }
  ],
  "adjustments": [{ "code": "DEALER", "type": "percent", "value": -8, "amount": -1003 }],
  "net": 11529,
  "tax": { "status": "calculated", "rate": 21, "amount": 2421 },
  "gross": 13950,
  "approval": "within_policy"
}

Markets, currencies and channels

The same product can have several correct prices.

Product validity and commercial result are related but different. An anthracite pergola can be valid in several countries while using a retail price in one market, a dealer list in another and a negotiated account price for a specific business customer. Language alone does not choose the price.

A market context can control catalogue availability, price list, fixed overrides, currency, tax display, units, freight, services, promotion eligibility and legal terms. A B2B context can additionally control company location, buy price, sell price, margin visibility, payment terms and approval permissions.

Treat currency conversion, market pricing and accounting settlement as separate concerns. Explicitly test minor units, rounding, fixed local prices and the amount received by ecommerce, payment and ERP systems. Do not recalculate a market's price from a displayed base amount when another system owns the contextual answer.

Quote and revision lifecycle

Live price now. Historical truth later.

A live calculation can update with every choice. An issued quote needs a stable record of what the customer received. Design both behaviors before launch.

1

Working configuration

Recalculate when price-relevant product or context fields change. Clearly show incomplete, estimate, review and final states.

2

Saved project

Store the configuration and price reference. On reopen, preserve, warn or reprice according to an explicit policy.

3

Issued quote

Lock the accepted configuration revision, result, terms, currency and expiry. Changes create a new quote revision.

4

Accepted order

Carry the exact approved commercial lines and product identity forward; reconcile later changes through controlled amendments.

Permanent regression pack

Eight tests before anyone calls the price accurate.

Use approved source calculations and keep the cases after launch. Re-run them when product rules, price data, currencies, tax, integrations or calculation code change.

Known-price configuration

Calculate a representative product whose expected line items and total were approved independently. Match every amount, not only the grand total.

Invalid product state

Create an incompatible combination. The interface must not present an apparently final price for a product that cannot be supplied.

Boundary dimensions

Test just below, on and just above every important band, increment, minimum, maximum and formula threshold.

Account and market context

Price the same valid product for retail, dealer and distributor audiences in every priority market and currency.

Discount permissions

Attempt allowed, approval-required and prohibited discounts. Verify price floor, margin visibility and audit ownership.

Effective-date change

Price before and after a controlled list change. New work uses the correct version while an issued quote keeps its accepted history.

Save, resume and reprice

Reopen a configuration after a price change. Follow the agreed policy to preserve, flag or reprice instead of silently changing the result.

Destination reconciliation

Send the accepted result to quote, cart, CRM or ERP and reconcile IDs, quantities, currency, tax, line amounts and total.

Failure patterns

A fast price is not automatically a dependable price.

Price without validity

A number appears while required choices are missing or the product violates a compatibility rule.

Better: Gate sellable pricing on an explicit validation state and surface review states separately.

Labels used as price keys

A translated or renamed option breaks a formula, list lookup or integration.

Better: Use stable IDs for calculation and localize only the displayed explanation.

Hidden waterfall

A total is visible but nobody can explain the base, surcharge, discount, service or tax contribution.

Better: Return a structured price ledger with rule, source and revision references.

Two calculation paths

The website estimates one amount while sales rebuilds another amount in a spreadsheet or ERP.

Better: Choose an authority, reuse one calculation contract and reconcile every destination.

Silent historical repricing

An old saved project or issued proposal changes when the current price list is edited.

Better: Version price inputs and define preserve, warn, reprice or migrate behavior for each lifecycle state.

Currency and tax ambiguity

A figure lacks market, currency, net/gross status, tax source, date or rounding policy.

Better: Make commercial context part of the request, result, quote and acceptance evidence.

Pricing engine FAQs

Detailed answers for buyers, product owners and technical teams.