Discount Approval

A salesperson wants to offer a customer 12% off a catalogue price, and company policy may permit a small reduction without review but require a manager to assess this one. The customer should receive only the final approved offer.

A discount is a change to selling price, not automatically a loss of the same amount from margin: if a product listed at $200,000 is reduced by 12%, revenue falls by $24,000 before tax and other terms, and the change in gross profit depends on cost and whether volume changes. Describe the $24,000 as a price reduction rather than margin lost, because that label is not accurate without a cost and volume model, and calculate the resulting margin separately.

HubSpot's quote-approval documentation describes configured filters, including discounts above an amount or on a specific line item, and Salesforce shows a sales discount approval workflow. The software is one way to enforce a company's own authority rules.

Set approval bands from actual economics and risk, since a 5% discretionary limit may fit one product but destroy margin on another, and thresholds can vary by category, customer type, contract term or total contribution. The approver should see list price, proposed price, direct cost, customer history, payment terms and reason for the request, because a one-line "please approve 20%" message may hide a loss-making deal or a competing supplier's different scope.

Check whether the price is already promotional, as applying a discretionary discount on top of an advertised offer can reduce the price far more than intended, so define whether discounts stack and where the baseline comes from. Approval should happen before the quote is sent, because a manager cannot undo a price promise easily after a customer relies on it.

If an offer was made in error, handle it through an honest customer conversation rather than changing the records silently. Record who approved, what version, for which customer and until when, since a discount approved for one order does not automatically apply to renewals or related companies, and include volume and payment conditions if those drove the decision.

Large or unusual offers may need finance review, as a lower unit price can be justified by reliable volume or lower service cost, but those assumptions should be documented and a projected sale is not a guarantee that the customer will meet a minimum. Keep standard offers fast: if every minor reduction waits for three senior managers, a competitor may win before approval arrives, so provide clear pre-approved ranges and turnaround targets, with escalation for real exceptions.

A system can route approvals, but it needs reliable price and cost data, because an old cost sheet can make a risky discount look safe. Review discount patterns, because if one team repeatedly seeks large reductions, the list price, incentives or customer fit may need attention, and a salesperson should not be judged solely by average discount without comparing product and segment.

A customer may ask for a lower price because terms or scope changed, so explain the trade-off clearly: fewer services, longer commitment or faster payment could justify a different price, and a higher-quality offer should not be claimed identical to a lower-cost competitor without checking. For owners, discount approval is a pricing control tied to real economics and authority, so make thresholds practical, check the full deal and ensure the quote matches the approved version.