A discount approval policy should help a salesperson reach a sound answer quickly. Yet many policies do the opposite. They specify a percentage limit, send every exception to a director and ignore the costs that determine whether the deal creates value.
The result is predictable: routine quotes wait for approval, unusual commitments hide inside “approved” discounts and teams discuss revenue without calculating contribution. At AB Consulting, a practical policy starts with deal economics and decision rights—not an arbitrary universal discount ceiling.
This guide explains how to define approval bands, calculate the real effect of a discount and capture exceptions without blocking good deals. The figures are illustrative, not client results or recommended universal thresholds.
Define what the discount approval policy protects
A policy should protect more than list price. It should protect contribution margin, cash timing, delivery capacity and commercial consistency. A five-percent reduction may be harmless on one offer and destructive on another because the variable cost, implementation effort or payment terms differ.
Start by agreeing the economic measures used in every quote:
- Net revenue: list price less discounts, credits and customer-specific rebates.
- Variable cost: the cost that changes because the company accepts and fulfils this deal.
- Deal contribution: net revenue less variable cost and identifiable deal-specific costs.
- Contribution margin percentage: deal contribution divided by net revenue.
- Cash exposure: the funding required before the customer pays, including tax and milestone timing where relevant.
These definitions must match the company’s accounting and pricing practices. If sales uses catalogue cost while finance uses expected landed cost, the workflow will create an illusion of control. Link the policy to a maintained cost source and state how long a quote calculation remains valid.
Discounts can serve legitimate goals such as securing a committed volume, accelerating cash collection or simplifying delivery. Stripe’s overview of discount economics notes that discounts reduce the gap between price and cost unless another benefit—such as more volume or faster payment—offsets that reduction. The approval request should name and quantify the expected exchange.
Build discount approval policy bands around economics and risk
Give routine deals a fast lane
Define a self-approval band for standard offers that meet all policy conditions. Conditions might include a current price list, an approved contract template, minimum deal contribution, ordinary payment terms and deliverable capacity. The seller records the rationale, but does not wait for a meeting.
Use a second band for exceptions that one designated commercial manager may approve. A third band can require finance or executive review when the commitment is material or unusual. Name a substitute for absences and set a response target that begins only when the request is complete.
Add non-price escalation triggers
A percentage alone misses important risks. Require review when a deal includes custom development, unlimited support, long price locks, acceptance clauses, unusual warranties, cancellation rights, customer-favoured pricing commitments or extended payment terms. A zero-percent discount with an expensive service promise may be worse than a transparent price reduction.
Keep legal or compliance checks distinct from commercial approval. If a mandatory contract requirement has not been satisfied, a sales director should not be able to waive it merely by approving the price. Conversely, not every stakeholder who provides advice needs a veto.
For reseller arrangements, review competition rules in each relevant jurisdiction. For example, the UK Competition and Markets Authority explains that a supplier requiring a retailer not to resell below a specified price can constitute resale price maintenance. This article is operational guidance, not legal advice; obtain qualified advice for the markets and channels involved.
Discount approval policy calculation: test the margin effect
Illustrative example: a service package has a €100,000 list price and €60,000 of variable delivery cost. At list price, contribution is €40,000 and contribution margin is 40%.
| Scenario | Net revenue | Contribution | Margin |
|---|---|---|---|
| List price | €100,000 | €40,000 | 40.0% |
| 10% discount | €90,000 | €30,000 | 33.3% |
| 10% discount plus €4,000 custom work | €90,000 | €26,000 | 28.9% |
The arithmetic is simple but important. A 10% price discount reduces revenue by €10,000. Because the original contribution was €40,000, contribution falls by 25%: €10,000 ÷ €40,000. If the deal also requires €4,000 of identifiable custom work, contribution becomes €90,000 − €60,000 − €4,000 = €26,000.
Suppose management wants to preserve the original €40,000 contribution through additional volume at the discounted economics. Each discounted deal contributes €30,000 before custom work. The company needs €40,000 ÷ €30,000 = 1.33 discounted deals for the same contribution. In whole deals, two would generate €60,000 of contribution, but only if capacity exists and the extra sale would not have occurred at the normal price.
Also calculate stacked discounts correctly. Two sequential 10% discounts leave 81% of the original price: €100,000 × 90% × 90% = €81,000. The combined reduction is 19%, not 20%. Your CRM or quoting tool should display the final net price and contribution, rather than asking an approver to reconstruct the calculation.
Turn your discount approval policy into a learning loop
Use a short request with required fields: customer and opportunity, list and net price, volume, variable cost source, contribution, payment terms, capacity impact, nonstandard obligations, reason for the concession and expiry date. A blank field should return the request automatically rather than start a chain of emails.
Record the decision, approver, conditions and reason code in the CRM. Restrict reason codes to a useful set—competitive match, committed volume, accelerated payment, capacity fill, recovery or approved strategic exception—while retaining a note for context.
Review outcomes monthly by seller, segment, product and reason. Compare approved discount with realised net revenue, contribution, payment performance and promised volume. Do not reward “approval compliance” if teams simply move concessions into free scope or payment terms.
Connect the review to sales management and to the decision rights matrix that becomes available before this article. The policy defines the commercial boundary; the matrix clarifies who recommends, checks, decides and implements.
Before launch, confirm that:
- margin and cost definitions are shared by sales and finance;
- routine approval bands have explicit conditions;
- non-price commitments trigger review where appropriate;
- mandatory legal checks cannot be waived commercially;
- the calculation shows net price, contribution and cash timing;
- approvals expire and exceptions have an audit trail; and
- management reviews realised outcomes, not just approved forecasts.
Make pricing discipline support sales speed. Contact AB Consulting to discuss a strategy session or operational deep-dive covering approval bands, margin logic, CRM workflow and management reporting.
