Customer specific pricing: how to keep every customer's price straight
Short answer: Customer specific pricing means a price set for one customer or one group of customers instead of the list price. It can be a percent off, a fixed contract price, a tier, a quantity break or a cost-plus formula. To keep it straight, store each price type separately, give each one a start and end date, decide in writing which price wins when several apply, and keep one price source that your ERP (the system that runs orders, stock and accounting), quotes and ordering portal all read from. Most errors come from copies of prices living in different places.
Every customer has their own prices and discounts, and you want to stop quoting the wrong number to the wrong buyer.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
What is customer specific pricing?
It is any price that depends on who is buying. A wholesale distributor might have a dealer price for all dealers, a contract price for one big account and a list price for walk-in buyers, all on the same part.
Examples of customer specific pricing
- Percent off list: 15% off one product line for one buyer.
- Fixed contract price: $6.40 each on 30 parts until December 31.
- Price tier or level: every dealer gets the Dealer price, every distributor gets the Distributor price.
- Quantity break: a lower price from 500 units.
- Cost-plus: your cost plus 18%, so the price moves when your cost moves.
Things that look the same but are not
- A rebate is money paid back after the sale, often at year end. It does not change the invoice price. It needs its own tracking. See my guide to price agreements and rebate contracts.
- A promotion is a short-term price for everyone, not for one account.
- A negotiated line price typed on one quote is not a standing price. If it is not saved, the next order goes back to list.
Which price wins when several apply?
This is the question that causes most mistakes. Write the order down. Here is a made-up example. A part lists at $10.00.
| Price type | Rule | Price |
|---|---|---|
| List | Public price | $10.00 |
| Dealer tier | 30% off list | $7.00 |
| Quantity break | 500 or more, dealer tier | $6.50 |
| Acme contract | Fixed price until Dec 31 | $6.40 |
Acme is a dealer who orders 600. Does Acme get $6.40, $6.50 or both discounts stacked? Without a written rule, your clerk guesses. My default rule: the most specific price wins, and discounts do not stack unless the contract allows it. A customer contract comes first, then the tier, then list, and a quantity break applies only inside the price it belongs to. Under that rule Acme pays $6.40.
The right rule is whatever your sales team can explain to a buyer in one sentence. If they cannot, customers will notice the inconsistency before you do.
How do ERPs and accounting tools handle it?
NetSuite
NetSuite, a cloud ERP, uses price levels. You can set up to 1,000 of them. A customer can have a price level on their record, and NetSuite's help says item-level price levels on the customer record override both that level and the levels for pricing groups. A pricing group is a set of items, such as all laptops, with a level assigned to it for a customer. A pricing group's level overrides the customer's overall level but not item pricing. At the top sits absolute pricing: NetSuite says an absolute price, set with the Custom price level on a customer's item, always overrides any other pricing. Users can still type a different amount on a transaction, so decide who is allowed to.
Acumatica
Acumatica is a cloud ERP used by distributors. MYOB's help for MYOB Acumatica, its version of the product, describes the order it checks: a price for the customer first, then a price for the customer's price class (a group of customers), then the base price, then the item's default price. It only uses prices that are effective on the document date, and it uses the quantity tier that matches the line. Prices load through worksheets: you can upload customer, class and base prices from an Excel file, and they go live only when you release the worksheet on its effective date. Prices of the same type for the same item cannot overlap in time. Discounts are handled in a separate topic, so check how they interact with your negotiated prices.
QuickBooks Online
QuickBooks Online is small-business accounting software. Intuit's help says price rules can limit a discount or different rate to selected customers or customer types, to selected items, and to a date range. The page marks the feature as Beta, says it is not available in Simple Start or Essentials, and bundles cannot be added to a rule directly. If more than one rule matches, QuickBooks shows the default rate with a warning, and the user picks. That is workable for a few dozen special prices. I would not rely on it for thousands of contract lines. See my QuickBooks alternatives guide if you are outgrowing it.
Where does customer pricing break?
- Spreadsheet copies. One price sheet per customer, emailed around, edited by three people. Nobody knows which is current.
- No end dates. A contract price expires on paper but stays live in the system for two years.
- Systems disagree. The ERP has one price, the quote tool another, the ordering portal a third. The customer sees all three.
- Cost changes. A supplier raises costs 8% and your fixed contract prices now lose money. Nobody gets alerted.
- Typed overrides. A rep types a one-time price on an order and it quietly becomes the habit.
- Exceptions pile up. After a few years you have thousands of one-off lines and nobody can explain them.
How do I manage it step by step?
- List your price types. List, tiers, quantity breaks, contract prices, cost-plus. Name them the same way everywhere.
- Write the winning order. One page, plain words, as in the Acme example above.
- Add dates to everything. Every special price gets a start date and an end date, or a review date.
- Name an owner. One person approves changes. Others request them.
- Pick one source of truth. Usually the ERP. Quotes and portals should read from it, not keep copies.
- Add a margin check. Flag any price below a minimum margin before it is saved.
- Review quarterly. Pull every price with an end date in the next 60 days, and every price nobody has used in a year.
Start with your top 20 customers. They usually hold most of the special prices and most of the revenue, so getting them clean first pays back fastest.
Can AI help with customer pricing?
Yes, in a few narrow jobs. AI tools can read a customer's price agreement in a PDF and pull out the parts, prices and dates into a draft table. They can compare two price files and list what changed. They can flag a price that looks out of line with similar customers. See my guide on AI document processing for how reading documents works.
What I would not do is let AI set a price on its own. A person should approve every price before it goes live, because a wrong number is a margin loss or a lost customer. Use AI to prepare the change, and keep the approval human.
What does a pricing engine inside a portal and quote tool look like?
A pricing engine is the one piece of software that answers the question, "What does this customer pay for this part, in this quantity, today?" Everything else asks it. The ordering portal asks it when a customer logs in. The quote tool asks it when a rep builds a quote. The ERP stays the place where orders and invoices live.
With that setup, a price changes once and shows up everywhere. It also lets you build a customer portal where each buyer sees only their own prices and order history. Where your ERP's built-in pricing cannot express your rules, a custom layer on top of your ERP can hold them.
How I'd approach this
Do not buy software first. Spend a week writing down your price types, your winning order and your top 20 customers' special prices. Most of the mess is in the rules, and no tool can fix rules nobody has written.
Then test your ERP against that page. If the ERP can hold every price type with dates, use it and tidy the data. If it cannot, or if your quotes and portal need the same prices, build a small pricing layer that reads from one table. I would rather build the smallest thing that gives you one answer than a large system with a dozen settings nobody understands. My quote template and price list management guide are good next steps. A closer look is in a price list template with customer-specific prices.
Questions people ask
What is customer specific pricing?
It is a price set for one customer or group of customers instead of the list price. It can be a percent off, a fixed price, a tier, a quantity break or a cost-plus formula.
What are examples of customer specific pricing?
Examples include 15% off a product line for one buyer, a fixed price on 30 parts until a set date, a dealer price for all dealers, and a lower price from 500 units.
How does NetSuite handle customer specific pricing?
NetSuite uses price levels, up to 1,000, set on the customer record or per item. Item-level levels override the customer's overall level, and an absolute price set with the Custom level overrides all other pricing for that item and customer.
How does Acumatica handle customer specific pricing?
Acumatica-based systems check a customer price first, then a customer price class, then the base price. They use only prices effective on the document date and pick the quantity tier that matches the line.
Is there software for customer specific pricing?
ERPs, B2B ecommerce platforms and quote tools all hold some customer prices. If yours cannot hold your price types, a custom pricing layer can sit on top of your ERP and feed your portal and quotes. See my custom ERP guide.
How do I keep contract prices from expiring unnoticed?
Give every special price an end date and run a monthly report of prices ending in the next 60 days. Review each one with the account owner before it lapses or is renewed.
More in this topic: B2B: quotes, CPQ and pricing (8 guides) →
Sources
- Setting up price levels for customers (Oracle NetSuite Help)
- Creating pricing groups (Oracle NetSuite Help)
- Absolute pricing for customers (Oracle NetSuite Help)
- Sales prices: rules of price selection (MYOB Advanced Help)
- Sales price worksheets (MYOB Advanced Help)
- Sales price uploading (MYOB Advanced Help)
- Set pricing rules in QuickBooks Online (Intuit)