How do you stop quotes and discounts going out before someone signs off?

A discount approval process only works if it holds the quote until a manager signs off, rather than sending someone a reminder after the fact. In Coevera (formerly Pipeliner CRM), that means an approval process on the quote itself: quotes below your threshold go out untouched, and quotes above it are locked until the right manager decides.

The problem is the tail, not the discounts

Discounting is part of how deals close, and most of the time it is what you want from your reps. If they had to ask for approval on every small concession, the whole team would slow down and gain nothing. The risk sits in the few quotes that go out with a discount or a total that no senior person would have accepted. Such a quote can go unnoticed until later: at booking, at invoicing, or when a margin report runs. By then, the customer already has that price in writing.

Why don’t checkboxes and email alerts stop unapproved discounts?

Four fixes usually get tried before a real approval process. Each one records an intention instead of preventing an action.

• A required “approved by manager” checkbox. The rep who wants the discount is the person who ticks the box. It ends up always checked and means nothing.
• An automation that emails the manager. The quote is already saved and ready to send when the email goes out. It tells you what happened. It does not stop it.
• A pipeline step called “Approval.” Reps move steps themselves, and a rep who needs to get a quote out will move past it.
• Naming approvers one by one. This works until the first reorganization. When someone changes teams, goes on leave or leaves the company, approvals sit waiting for a person who is no longer there.

What does a discount approval process need to enforce?

Whether you call it discount approval, price approval or a deal approval process, the requirement is the same: two things at once. A lock. While the decision is open, the quote is read-only for everyone except the people handling the approval. The quote is held, not just flagged. Routing by role. The approver is whoever manages the sales unit the quote belongs to, worked out at the moment the approval is raised. Nobody maintains a list of names, and it keeps working through reorganizations, holidays and departures. Just as important is what the process leaves alone. Below the threshold there is no extra step, no notification, nothing. Reps keep their room to negotiate, and managers see only the quotes that need them. Where to draw the line is a commercial decision. The mechanism works with whatever value you choose.

How does a quote approval threshold work in Coevera?

Say your sales leadership sets the line at a quote total of 10,000.

• A rep builds a quote for 8,000. Nothing happens. No approval is created, nobody is notified, and the rep sends it as usual.
• A rep raises an existing quote from 9,500 to 10,500. The approval triggers when a quote is created and when it is updated, so the edit is caught. The quote locks, and the request goes to the manager of that quote’s sales unit.
• The manager decides. In the setup the blueprint recommends, an approved quote moves to a step that reads as approved, so the decision is visible on the record. A rejected quote moves to a step that reads as rejected, and the owner is told.

The threshold does not have to be the total. The same filter can test a discount percentage, a margin field, or several conditions combined. Every decision is kept in the approval history: who decided what, and when.

What should you check in a Coevera quote approval process?

• An unanswered approval can approve itself. If approvals expire, the expiry result can be set to approve. A quote nobody looked at is then granted automatically, and the audit trail shows an approval no person gave. Set it to reject, and check this on any approval process you inherit.
• The lock is not a freeze. The people managing the approval can still edit the quote, which leaves an escalation path. Do not describe it to an auditor as unchangeable.
• The reject path is the one that gets skipped. The blueprint’s authors found the reject branch empty or partial in every build they reviewed. A rejected quote then stays on its current step, so the step alone does not show the decision. Build both paths at the same time.
• Created is not switched on. Creating, configuring and enabling the process are separate steps. A process can exist, be fully configured and never fire.

What signs show that the process is not working?

Four signs in your CRM data point to a problem:

• Approvals appear on quotes below the threshold.
• A pending approval has no approver.
• A quote above the threshold was closed with no approval in its history.
• Decisions are timestamped at exactly the expiry interval. That means the timeout decided, not a person.

Key takeaways

• A discount approval process has to lock the quote, not just notify someone.
• Set the threshold as a filter, so quotes below it are completely unaffected.
• Route approvals to the sales unit manager role, not to named people.
• Set unanswered approvals to reject, never to approve.
• Build and test the rejection path, not only the approval path.

Frequently asked questions

The full configuration, the recommended settings and the test plan are in the Coevera blueprint How do you stop quotes and discounts going out before someone signs off? It is written for whoever administers your CRM, so it is worth passing on to them.