Discount approvals stop large discounts reaching a customer unchecked. In Treepie Flow you set thresholds — for example, up to 10% needs no approval, 10–20% needs a sales manager and above 20% also needs finance. A quote past a threshold is locked until the named approvers agree, and each decision is recorded on the deal with the reason, margin and approver.
Because the usual approval is a message at 17:40 saying "fine by me". It is not on the record, the approver does not have the margin in front of them, and nobody can reconstruct it at year end.
Discount approval routes any quote past a threshold you define to a named approver, records their decision with the reason given, and keeps both on the deal.
Thresholds are set per pipeline, product line or value band, and can escalate in steps. The approver sees the deal, the rate card, the discount requested and the margin it leaves before deciding.
A 22% request on a Cavendish Group renewal reached the approver with Loop's delivery cost attached, showing the account already ran at 4% margin. It was refused, and the counter-offer closed at 9% off.
It will not stop a discount you have authorised. Thresholds enforce who decides, not what they decide, and a low threshold with a permissive approver is theatre.
Books reads the approved discount when it bills, quote versions record which discount was approved, and reporting can show discount by rep, product and quarter.
| Email or chat approvals | Approval step in another tool | Treepie Flow | |
|---|---|---|---|
| How a request is made | A message to the manager | A form outside the CRM | Automatically, when the quote crosses a threshold |
| What the approver sees | Whatever the rep pasted | The request form | Deal, margin, rate card and customer history |
| Can the quote go out early | Yes | Often | No — locked until approved |
| Where the decision lives | In someone’s inbox | In the other tool | On the deal, with the reason |
| Reporting | None | Separate | Discount by rep, reason, pipeline and period |
Yes. Bands can route to a manager, then a director, then finance.
Delegation is set on the personnel record in Nest, so cover is a rota rather than an exception.
You decide. Requiring it is what makes discount reporting worth reading.
Yes. Renewals, new business and partner deals can each have their own thresholds and approvers.
Yes. Rules can use discount percentage, resulting margin, deal value or a combination.
Yes. Approvers can be required in sequence — manager then finance — or together, with the quote released once all have approved.
Yes. Requests arrive by email and notification with approve and reject actions, and the full context is one tap away.
Only if the change affects the discount or margin past the approved level. Editing wording or dates doesn’t.
Yes, from a list you define — such as competitive, multi-year or volume — with an optional note.
Yes. Reports show discount given by rep, reason, pipeline, customer and period, with every figure openable to its quotes.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.