Move guide
Take control of discounts and exceptions
Your report suggested a move on at least one of these three practices:
- who can give price away;
- what happens to exceptions;
- what guidance sales has in the moment of quoting.
They are one job, so this move guide takes them together. It sets the rules for giving price away, puts an end date on every exception, and gives sales a floor to quote against.
If you took the consumer check, go to the consumer section. If your products reach shoppers through retailers, go to the section for brands.
1. When it applies
Use this move guide if your report placed any of these three practices in the lowest two stages.
| Practice | Where it may sit today | Where this move guide aims |
|---|---|---|
| Who can give price away | Lagging: "Discounts are approved by whoever the salesperson asks." Basic: "An approval ladder exists on paper but is routinely bypassed for anything urgent." |
Competent: "Discount authorities are defined by size and level, recorded, and mostly followed." |
| What happens to exceptions | Lagging: "Every deal is an exception." Basic: "Exceptions are granted case by case and never revisited once won." |
Competent: "Exceptions are logged, time-limited and reviewed at renewal." |
| What guidance sales has in the moment of quoting | Lagging: "Sales quotes from memory and the last deal they did." Basic: "A price file exists, but the real reference point is what the customer paid last time." |
Competent: "Target, floor and walk-away prices exist for standard situations and are visible at the point of quote." |
If all three already sit at the middle stage or higher, skip this move guide.
If your report gave the foundation moves, with 15 or more practices in the lowest two stages, do those first. Discount rules need a pricing owner and one source of price data to stand on.
2. What to do
Seven steps, in this order. Steps 1 to 6 take about four weeks. Step 7 runs from then on.
- 1. Pull last quarter's invoices, week 1
- 2. See how far prices spread, weeks 1 to 2
- 3. Find the floor, week 2
- 4. Write the discount ladder, weeks 2 to 3
- 5. Record every approval, weeks 3 to 4
- 6. Open the exception log and set the deal guidance, weeks 3 to 4
- Weekly: 30 minutes on new exceptions and big approvals
- Monthly: test 20 random deals against the ladder
- At renewal: end each exception or renew it on purpose
Pull last quarter's invoices. You need one line per invoice line: customer, product, quantity, list price, net price, salesperson, and the approver if anyone approved it.
See how far prices spread. For your 20 biggest products, set the lowest and highest unit price paid against the average. Mark the customers paying well below it. These are your outliers. Table A below does this.
Find the floor. For each product group, work out the price below which a deal no longer covers its variable cost and the cost of serving it. No approval band may go below this floor.
Write the discount ladder. For each role, record:
- the most it may discount;
- the deal size it covers;
- who it escalates to.
Keep every band above the floor. Table B below does this.
Record every approval. Every discount above the first rung is recorded with the person who approved it. An email is the minimum, and a verbal yes does not count.
Open the exception log and set the deal guidance.
- Every price outside the ladder gets a reason, an owner and an expiry date, set no later than the customer's next renewal.
- For your ten most common deal situations, set a target, a floor and a walk-away price. Put them where sales writes quotes.
Review it.
- Each week, the pricing owner and the sales head spend 30 minutes on new exceptions and approvals above the second rung.
- Each month, test 20 random deals against the ladder.
- At each renewal, the exception either ends or is renewed on purpose.
- Track realised price, the price you actually get after every discount, for the outlier customers each month.
The three free worksheets do the recording:
- /worksheets/pricing-b2b/discount-authority for the ladder and the monthly test;
- /worksheets/pricing-b2b/exceptions for the log;
- /worksheets/pricing-b2b/deal-guidance for the three prices.
3. What to produce
Two tables, plus the three worksheets above.
Table A. Price bands: the same product, different prices
| Product | Units sold | Average net unit price ($) | Lowest ($) | Highest ($) | Customers more than 10% below average | Their share of the product's volume |
|---|---|---|---|---|---|---|
Table B. Discount ladder
| Role | Most discount off list (%) | Largest deal it covers ($) | Escalates to | Floor for this product group ($ or % off list) |
|---|---|---|---|---|
| Sales rep | ||||
| Sales or branch manager | ||||
| Sales director | ||||
| Chief executive |
A band that lets a deal go below its product group's floor approves a loss. Move the band above the floor.
4. A worked example
Illustrative. Written for this move guide. It describes no client.
A building-supplies distributor sells about 400 products to 1,500 trade customers, through 30 reps in six branches.
What the invoices showed.
- Last quarter's invoices showed its best-selling sheet product sold at an average of $42 a sheet. The range was $31 to $49.
- Forty customers paid more than 10% below the average. Between them they took 22% of that product's volume.
- Only nine of those forty prices had an approver on record.
- Lowest to highest: $31 to $49
- Average: $42
- Floor: $34
The floor.
- Variable cost plus delivery and handling came to $33 a sheet.
- Seven customers were paying less than that, so the business was losing money on every sheet it sold them.
- The floor for the product group was set at $34.
The ladder.
- List price$46.00
- Rep $43.70
- Branch manager $41.40
- Sales director $39.10
- Floor: $34.00
| Role | Discount off list | Deal size | Escalates to |
|---|---|---|---|
| Rep | up to 5% | up to $10,000 | branch manager |
| Branch manager | up to 10% | up to $50,000 | sales director |
| Sales director | up to 15% | any | chief executive |
At a $46 list price, 15% off gives $39.10, which stays above the $34 floor.
The exception log.
- It opened with 26 standing special prices.
- Eleven had no reason anyone could find, and they were set to end at the customer's next renewal.
- Fifteen were kept with a reason, an owner and an expiry date.
Three months on.
- 17 of 20 sampled deals inside the ladder
- 7 of 7 below-floor prices raised or ended
- 40 outlier customers tracked each month
- The monthly sample found 17 of 20 deals inside the ladder, and the three outside had approvals on record.
- The seven below-floor prices had been raised to the floor or had ended.
- The pricing owner was tracking realised price for the forty outlier customers each month.
On a retake, all three practices could be answered at the middle stage.
What it looked like in our work
From our own work. Figures changed.
An industrial distributor. We looked at what its largest trade customers paid for each product line, averaged across their biggest orders.
| Product line | Share of the order's value | Discount off list |
|---|---|---|
| Line A | 32% | 40% |
| Line B | 27% | 37% |
| Line C | 13% | 54% |
| Line D | 9% | 51% |
| Line E | 7% | 45% |
| Line F | 5% | 43% |
| Line G | 4% | 46% |
| Line H | 2% | 44% |
| Line I | 1% | 45% |
Every line carried a deep discount, between 37% and 54%. The two largest lines carried the smallest discounts. Lines that made up a few per cent of the order were discounted almost as deeply as the rest. The discount followed the customer, whatever the product.
This is the price-spread check in step 2 of what to do, run for one class of customer. It shows where a ladder set by product group would differ from one discount for everything.
The approval limit sat below breakeven
From our own work. Figures changed.
An agricultural equipment maker let its sales team discount down to a set gross margin without approval. The limit sat at half the margin a sale needed to break even on contribution.
- 8% Lowest gross margin the sales team could agree without approval
- 16% Gross margin a sale needed to break even on contribution
- About 480 Sales between the two: no approval needed, and losing money on contribution
- About 45 Sales below the limit, which needed approval
The approval rule caught about one loss-making sale in twelve. The fix was to move the limit up to breakeven, so every sale below it gets a second look.
A discount ladder by customer level
From our own work. Figures changed.
A steel distributor set its discounts as a ladder for each product group. The largest project customers sat at the top. Then came ten customer levels, and cash customers at the bottom. Each level had a starting discount, and a sales rep could go only a few points deeper.
- List price$100
- Cash $79
- Level 10 $76
- Level 9 $73
- Level 8 $71
- Level 7 $69
- Level 6 $66
- Level 5 $63
- Level 4 $60
- Level 3 $58
- Level 2 $55
- Level 1 $53
- Project, third tier $50
- Project, second tier $49
- Project, first tier $48
- Lowest price on the ladder: $48
Per $100 of list price. Each rung is the starting discount for that level.
| Customer level | How far a rep could go below the starting discount (points) |
|---|---|
| Project tiers | 2 |
| Levels 1 to 5 | 4 |
| Levels 6 to 10 | 5 |
| Cash | None |
Each product group had its own ladder. Some were flat: about 15 points from the top project tier to cash. Others were steep, at about 36 points. The ladder set the starting point, and the band set how far a rep could move from it.
5. Effort and dependencies
- Pricing ownerRuns it and writes the ladder.
- Sales headCo-signs the ladder and joins the weekly review.
- Finance analystPulls the invoices, works out the floors and runs the monthly test.
- Quoting system ownerPuts the guidance where sales quotes.
What you need
- One quarter of invoice lines with list and net price.
- Variable cost by product group.
- A rough cost of serving each customer type (order size and delivery are enough to start).
- The list of standing special prices.
How long
- About four weeks to steps 1 to 6.
- Then 30 minutes a week, a monthly sample of 20 deals, and the renewal review.
- If the price data is not in one place yet, fix that first. It is a separate move in your report.
What gets in the way. We have seen these in our own work:
- Approval limits set below breakeven. At an equipment maker, the limit for approving a margin hold sat below contribution breakeven in two markets. The deals it approved eroded margin.
- Rules that differ by site. At an industrial distributor, each site had its own discount authority, and front-line staff priced off a local cost figure. A fix through a large data clean-up did not stick.
- Overlapping schemes. At a distribution business, five discount schemes nobody had lined up handed pricing power to the largest distributors.
What we have seen. "Fixing discounts, rebates and price support has added 2–3 points of margin, and quickly." We have seen this in our own work. It is not a forecast for yours.
6. How will you know it worked?
The test is how deals are priced once the rules are in place. Retake the check after three to six months. Each practice should then sit at the middle stage, and each of these should be true when you answer:
| Practice | You can answer Competent when | A document alone does not count if |
|---|---|---|
| Who can give price away | The ladder is written, every discount above the first rung has a recorded approver, and the monthly sample finds most deals inside the ladder. | The ladder exists but nobody has sampled deals against it. |
| What happens to exceptions | Every live exception has a reason, an owner and an expiry, and those that reached renewal were ended or renewed on purpose. | The log has entries with no expiry date, or expiries that passed with no decision. |
| What guidance sales has in the moment of quoting | Sales can see the target, floor and walk-away for the common situations where it writes the quote, and quotes below the floor need an approval. | The guidance sits in a file that sales does not open when quoting. |
Realised price for the outlier customers is worth tracking, because it shows whether prices are converging. The test is still that the practices run as the Competent cells describe.
For consumer businesses
This section is for the B2C Consumer Pricing Health Check. The job is the same: price is given away by rule, by the right person, and on the record.
When it applies
Use it if your report placed the first two practices below in the lowest two stages, or the third at the middle stage.
| Practice | Where it may sit today | Where this move guide aims |
|---|---|---|
| Discounts, vouchers, price-matching and refunds | Lagging: "Nobody knows what vouchers, staff discounts, price-matches and goodwill refunds cost in total." Basic: "Leakage is visible in aggregate at year end, when it is too late." |
Competent: "Each leakage line is measured monthly, with rules for who can give what away." |
| Consistency across channels | Lagging: "The same product carries different prices across site, store and app by accident, and customers notice." Basic: "Channel differences exist for historical reasons nobody can defend." |
Competent: "Cross-channel price rules are explicit (aligned, or deliberately different with a reason)." |
| How pricing decisions get made | Competent: "Price and promo decisions follow a documented process with the analysis attached." | Advanced: "Routine decisions are delegated within guardrails; the forum handles the exceptions and the strategy." |
Is how pricing decisions get made in the lowest two stages? Then start with naming the owner and setting the calendar. Measuring each leakage line every month is in seeing where the price goes. This move guide writes the rules.
What to do
- Total last month's giveaways by line. Count vouchers, discount codes, staff discounts, price-matches and goodwill refunds. The leakage worksheet does this.
- Write who may give what away. For each line, set who may give it, the most they may give, the condition and the expiry. Table C below does this.
- Write the guardrails for routine price changes. Say what counts as routine, such as a move inside a category's price band or a promotion already on the calendar. Routine changes go ahead without a meeting.
- Write what a non-routine change must attach. That means the reason, the expected effect on units and margin, and who decided.
- Write the channel rules. For each product group, set one price across site, app, store and marketplaces, or write the reason for each difference.
- Check every month. Report each leakage line against its rule. Compare the prices of 20 products across every channel, and fix any gap nobody chose.
The three free worksheets do the recording:
- /worksheets/pricing-b2c-direct/leakage for the month of giveaways and the rules;
- /worksheets/pricing-b2c-direct/price-integrity for the channel rules;
- /worksheets/pricing-b2c-direct/decision-discipline for the guardrails.
What to produce
Table C. Giveaway rules
| Giveaway | Who may give it | Most per order or customer ($) | Condition | Expiry or cap | Recorded where |
|---|---|---|---|---|---|
| Voucher or discount code | |||||
| Price-match | |||||
| Goodwill refund or credit | |||||
| Staff discount |
A worked example
Illustrative. Written for this move guide. It describes no client.
A homewares retailer sells through 40 stores and a website.
What a month showed.
- Giveaways came to $310,000 on sales of $14m.
- Discount codes were the biggest line. One code meant for email subscribers had reached a coupon site.
- The website was cheaper than the stores on 120 of its 2,000 products, and nobody had chosen that.
The rules.
- Codes became single-use and expire after 14 days.
- Price-matches cover named competitors' in-stock items only. A store manager approves any match above $100.
- One price runs in every channel. Online clearance is the one stated exception.
- Category managers may move a price by up to 5% inside its band without a meeting. Anything else goes to the monthly forum with its analysis.
Three months on.
- Each giveaway line was reported monthly against its rule.
- The monthly channel check found six gaps, and all six were fixed in the month.
- The forum's agenda was exceptions and strategy.
On a retake, all three practices could be answered at the target stage.
Effort and dependencies
Who
- The pricing owner writes the rules with trading, e-commerce and store operations.
- Finance reports each giveaway line monthly.
- Store operations trains the staff who give refunds and price-matches.
What you need
- One month of giveaways by line.
- Current prices by channel for your main products.
How long
- About four weeks to write the rules and start the reporting.
- Then a monthly report and a monthly channel check.
What gets in the way
- Codes that travel. A code meant for one group of customers spreads to everyone. Make codes single-use or tie them to an account.
- Channels priced by different teams. The website and the stores each change prices on their own calendar. Put both on one repricing calendar.
How will you know it worked?
Retake the check after three to six months. Each of these should be true when you answer:
| Practice | You can answer the target cell when | A document alone does not count if |
|---|---|---|
| Discounts, vouchers, price-matching and refunds | Each giveaway line is reported every month, and written rules say who may give it and how much. | The rules exist but nobody reports the lines against them. |
| Consistency across channels | Each price difference between channels is one you chose, with its reason written down, and a monthly check finds the ones you did not. | The rules exist but nobody compares channel prices. |
| How pricing decisions get made | Routine changes go ahead inside written guardrails, and the forum spends its time on exceptions and strategy. | The guardrails are written but every change still waits for the meeting. |
For brands selling through retailers
This section is for the B2C via trade Brand Pricing Health Check. Here price is given away through terms, promotions and one-off deals. The job is to put each one on the record, with the right approver, and to explain every price difference between customers.
When it applies
Use it if your report placed either practice in the lowest two stages.
| Practice | Where it may sit today | Where this move guide aims |
|---|---|---|
| Who can give a discount or a deal, and how it is checked | Lagging: "Whoever the account manager asks; approvals are verbal and nothing is written down." Basic: "An approval matrix exists, but deals outside it are approved by email that is deleted after a couple of months, and the biggest customer has no written terms at all." |
Competent: "A written delegation of authority covers terms, promotions and one-off discounts; every deal outside the matrix has a recorded reason and approver; the terms in the system match the signed agreement." |
| Whether prices across customers and channels are defensible | Lagging: "A customer buying a tenth of another's volume can pay less per unit, and the explanation is the name of the rep who did the deal." Basic: "We can explain each anomaly by its history." |
Competent: "Net price by customer is plotted against volume and value each year, and the outliers are known and being fixed." |
What to do
- Write the delegation of authority. It covers terms, promotions and one-off discounts. For each, say who may approve what, up to what limit. Table C below does this.
- Log every deal outside the matrix with its reason and its approver.
- Check the terms in the system against the signed agreements for your top twenty customers. Fix each term that has no agreement behind it.
- Get written terms with any major customer that has none.
- Plot net price against volume for one category. Name the customers who pay less than bigger, better customers, and put a date on each fix.
The two free worksheets do the recording:
- /worksheets/pricing-consumer-trade/decision-rights-and-controls for the delegation, the log and the check against signed agreements;
- /worksheets/pricing-consumer-trade/price-relativities-across-customers for the plot and the dated fixes.
What to produce
Table C. The delegation of authority
| Decision | Account manager | Sales director | Commercial manager | Chief executive |
|---|---|---|---|---|
| A change to a retailer's ongoing terms | ||||
| A promotion inside the guidelines | ||||
| A promotion outside the guidelines | ||||
| A one-off discount | ||||
| New terms for a new customer |
Write a limit in each cell, or leave it blank where that person may not approve.
A worked example
Illustrative. Written for this move guide. It describes no client.
A health foods brand sells through grocery, pharmacy and health food stores.
- Approvals for deals outside the matrix went by email and were deleted after two months.
- Its largest customer group had no written terms at all.
- The delegation of authority set limits for terms, promotions and one-off discounts.
- The check against signed agreements found fourteen terms in the system that no agreement supported. Each was stopped or written into the next agreement.
- The plot of net price against volume found two small pharmacy groups paying less than the biggest chain. Both fixes had dates.
On a retake, both practices could be answered at the middle stage.
Effort and dependencies
- Who. The commercial manager writes the delegation. Finance runs the check against agreements. The sales director signs off the fixes.
- What you need. The signed agreements for your top twenty customers, the terms loaded in the system, and net price by customer.
- How long. About four weeks to write the delegation and run the first check.
- What gets in the way. A customer who will not sign written terms. Agree what you will keep paying until they do.
What we have seen. "Written decision rights and aligned incentives stop the leak at source. In one business we worked with, getting that discipline in place brought trade spend down by two to three percentage points of sales." We have seen this in our own work. It is not a forecast for yours.
How will you know it worked?
| Practice | You can answer Competent when | A document alone does not count if |
|---|---|---|
| Who can give a discount or a deal, and how it is checked | A written delegation covers terms, promotions and one-off discounts. Every deal outside it has a recorded reason and approver, and the system matches the signed agreements. | The delegation is written, but nobody has checked the system against the agreements. |
| Whether prices across customers and channels are defensible | Net price by customer is plotted against volume and value each year, and the outliers are known and being fixed. | The plot was made, but the outliers have no dates. |
The worked examples are illustrative.
Think we've used your work without proper credit? Tell us and we'll fix it.