Customer-Specific Pricing
Acme has a contract rate. Beta gets the distributor tier. Stop quoting list price and fixing it after the customer notices.
Customer pricing · session
Quote line · X-Series Pump
Customer
Compare
Select an account to apply price book
What this controls
By account
Price follows the customer on the quote
Contract rate
Negotiated lists replace public list where agreed
Before send
Account price visible before approval
The challenge
The customer has a contract rate. The quote still shows list price.
Finance signed a framework agreement with a tier-one plant last quarter. Inside sales opens the public price list anyway because the account code is buried in a CRM note. The PDF goes out at list. Procurement sends the contract page back and asks for a revised quote.
Dealers maintain their own spreadsheets of who gets which tier. New reps quote from memory. When the same customer reorders through a different channel, price disagrees with the last deal and margin review starts over.
Dynamic pricing rolls up options on the configuration. Rule-based pricing applies IF/THEN surcharges. Discount management governs exceptions below floor. Customer-specific pricing is different: when you select the account, the agreed price list applies before anyone edits a line.
Inquiry to config to price to approval to order should start from the customer's commercial terms, not from a generic list you fix later.
How it works
How Mercura applies account and contract price lists
Pricing ops link customers, accounts, or segments to price lists in Mercura: contract rates, distributor tiers, and regional agreements. When a rep or dealer selects the customer on a quote, the matching list drives line prices before dynamic roll-up, volume tiers, or discounts layer on. Contract-pricing pages cover long-form agreements; this page is how the right list attaches to the right account at quote time. Customer price books need an owner when agreements renew or segments change.
Price waterfall
How pricing layers combine on a deal
Illustrative stack · each page highlights its own contribution
Compare
Account terms vs discretionary discount
Customer-specific
Agreed price exists before the quote is negotiated
Account price · €10,980
Discount management
Rep requests a discretionary reduction during the deal
Account €10,980 → optional −3%
What's included
What customer-specific pricing covers
Identify
- Account-linked price lists applied when the customer is selected
Map
- Contract rates distinct from public catalog list
- Segment and tier lists for distributors and key accounts
Apply
- Same account logic for inside sales, dealers, and portals
- Visible account price on the quote before approval
- Updates when contract price books are republished
Trace
- Traceability of which list drove the quote total
- Works with dynamic pricing, rules, volume, and discounts
The difference
Account pricing before and after CPQ
List price plus manual fix
- 01 Reps quote from the public list and adjust after customer pushback
- 02 Contract rates sit in CRM notes or regional spreadsheets
- 03 Dealers and inside sales use different tier assumptions
- 04 Reorder quotes disagree with the last signed deal
- 05 Finance reconciles account pricing after the PDF is sent
With Mercura
- 01 Selecting the customer applies the agreed price list
- 02 Contract and tier rates on the quote from the first line
- 03 Dealers and reps share published account price books
- 04 Reorder quotes start from the same account terms
- 05 Margin review sees the list the customer contract expects
Real-world example
Example workflow: automation components account price books
A distributor of PLCs, drives, and sensors serves national manufacturers with account-specific price books negotiated annually. Reps used to start from list price and search email for the last discount letter. After linking accounts to price lists in Mercura, selecting the plant applies the contract tier on the quote, dealers see the same tier, and reorder quotes match the agreement without a second revision cycle.
Business impact
Why customer-specific pricing is account context, not a bigger discount
Customer-specific pricing is how CPQ honours commercial agreements at quote time. It complements contract-pricing governance, dynamic roll-up, rule-based surcharges, volume tiers, and discount approval. Mercura does not replace your CRM or ERP as system of record for agreements. Someone must maintain account lists when contracts renew. If disputes start with "we have a better rate on file", attaching price books to customers in CPQ aligns inquiry, configuration, price, approval, and order with what sales already negotiated.
Business impact
Correct account price from first line
Account-linked price lists applied when the customer is selected.
Consistent channel pricing
Same account logic for inside sales, dealers, and portals.
Fewer quote revisions
Visible account price on the quote before approval.
Compare
Contract pricing vs customer-specific pricing
Customer-specific
What price list belongs to this account?
Primary object: account / segment / distributor tier
Price list attaches at quote time when the customer is selected
Contract pricing
Which formal agreement applies right now and to what scope?
Primary object: agreement with products, dates, commitments and conditions
Mercura checks agreement validity and scope
Pricing map
How starting price, adjustments, live calculation, discount control, and margin fit together
Starting price
Adjustment logic
Live calculation
Commercial control
Profitability check
Account price · list attached
See account price apply when the customer is selected
Book a demo and open a quote for a named account until contract rates appear before approval.
Let’s build together.
We empower manufacturers to master product modeling, streamline quoting process, reduce errors, and ultimately deliver the tailored solutions that customers demand.