Discount leakage: reporting pricing discipline

Discount leakage is the gap between list price and the price actually received. It includes obvious discounts and quieter concessions: payment discounts, freight paid by the seller, rebates, free units, and extended terms. Pocket price is what remains after all of them.

Leakage rarely appears as one large decision. It accumulates through small concessions that each seemed reasonable at the time, which is why it is easier to see in a waterfall than in a discount report.

Leakage percentage = (list value - pocket value) / list value x 100. Measure it on the same population of orders each month. Comparing this month's discounted orders with last month's full-price orders tells you nothing.

A price waterfall starts at list price and subtracts each concession in sequence. The final bar is pocket price. Show each step as a value and as a percentage of list, so the reader can see which concession is growing.

A hypothetical example on an index of 100: trade discount 12, volume discount 5, promotional support 3, rebate 2, freight concession 1. Pocket price is 77 and leakage is 23 per cent. The waterfall shows that trade discount is the largest single step and the first place to review.

Read the waterfall from the bottom up. If pocket price is stable but list price has risen, the discounts are absorbing the increase and the customer sees no change, while the business believes it has repriced.

Leakage at company level is a score, not a decision. Break it down by salesperson, customer, product, channel, and deal size. The question is where the discount is being given and whether the result justifies it.

Pair discount depth with margin. A 20 per cent discount on a 60 per cent margin product leaves 40 points; the same discount on a 25 per cent margin product leaves 5. Reporting the two separately hides that difference.

A useful layout has one row per salesperson or customer, with list value, pocket value, leakage percentage, gross margin, and the change against the previous quarter. Sort by leakage value, because a small percentage on a large account can outweigh a large percentage on a small one.

Define approval bands by discount depth and deal size, and make the band visible in the quoting tool. A policy that lives in a document nobody opens is not a control.

Review a sample of approved exceptions each month. If most overrides are justified, the band is too tight. If few are, the approval step is doing its job.

Bands should be simple enough to remember. A three-level structure, such as standard, manager, and director, is easier to enforce than a matrix with a dozen cells.

Leakage usually has a reason: an outdated price list, a competitor undercutting a specific line, a sales incentive that rewards revenue, or a bundling practice that hides a free product. Reason codes turn a suspicious number into a diagnosis.

If the price list has not moved with costs, the answer may be a repricing rather than stricter approvals. If commission is paid on revenue, expect discounting, because the salesperson keeps a share of a larger number.

Reason codes should be short and mutually exclusive: competitive match, volume commitment, strategic account, clearance, service recovery, and other. If more than a small share lands in other, the taxonomy needs work.

Thirty minutes, three charts: leakage trend, average discount by team, and the ten largest discounts of the month. Add approval compliance and one action per owner.

The meeting should end with named changes: a price list update, a band adjustment, a coaching conversation, or a customer renegotiation. Tracking leakage without changing a decision just documents the problem.

Pick one metric to hold the team to, usually leakage percentage on comparable orders, and report it alongside margin. A falling leakage percentage with falling margin means the mix changed, not that pricing improved.