• Home
  • /
  • Posts
  • /
  • Blog
  • /
  • Discount approval thresholds in food and beverage: why they stop controlling discounting

Discount approval thresholds in food and beverage: why they stop controlling discounting

Most food and beverage businesses control discounting with an approval threshold. Above a set level, a deal needs sign-off; below it, the rep can proceed. The control usually reports high compliance while total discounting keeps growing, because a threshold governs only the concessions that pass through it. Deals cluster just underneath the limit, orders are split, and the remaining value moves into credit notes, extended payment terms, free-of-charge stock or promotional support. None of those routes sit under discount approval, so the reporting stays clean while account margin drifts. The threshold starts working again when the full cost of a customer agreement is visible in one place, not when the limit is lowered.


What is a discount approval threshold?

A discount approval threshold is the point at which a proposed discount, or a deal value, requires authorisation from someone above the person agreeing it. Sales agree up to the limit. Anything beyond it goes to a sales manager, a commercial director or a margin committee.

On paper it is a clean control. It sets a boundary, it creates a record, and it puts a second pair of eyes on the deals that carry the most risk.

The intent is sound. The difficulty is that a threshold is a single number applied to a commercial negotiation with many moving parts, and only one of those parts is the discount itself.

Why does a threshold behave like a target rather than a limit?

Once a limit is published, it becomes the reference point for every conversation that follows.

A deal needs 8%. Sign-off starts at 7.5%. The deal is agreed at 7.4%, and the remaining value is found somewhere the threshold cannot see.

That is not a failure of judgement by the rep. It is a rational response to a control that measures one variable and ignores the others. The customer still needs the same commercial outcome. The rep still needs to hold the account. The threshold has simply told everyone which route is monitored, which by definition tells them which routes are not.

The pattern shows up in the data as a cluster of agreements landing immediately below the limit. A distribution of genuine commercial negotiations rarely bunches that tightly against a round number.

Where does discounting go when it cannot pass through the threshold?

Three routes come up repeatedly in food and beverage.

The order is split. Two orders raised on the same day, each sitting under the value at which authorisation is required. The customer receives one delivery and one commercial outcome. The system records two compliant transactions.

The discount arrives afterwards. The order is charged at the agreed rate and a credit note follows the next week to settle the difference. It is not a delivery shortfall and not a quality query, so it does not surface in either exception report. It is a discount taking a different road, and it lands in a ledger that is rarely read alongside the pricing file.

The concession moves sideways. The customer cannot have the extra 0.6%, so instead they receive extended payment terms, a contribution towards a promotion, additional stock, or a waived delivery charge. None of those sit under discount approval, because none of them are discounts. Each carries a real cost, and that cost usually sits with finance, supply chain or marketing rather than with the account.

There is a fourth route that is quieter still. The threshold has not been reviewed in years while costs have moved. What was once an exceptional level is now routine, so the queue fills with deals nobody has time to interrogate, and sign-off becomes an administrative step.

Why does the approval route itself weaken the control?

A threshold assumes the second pair of eyes is neutral. Usually it is not.

The rep carries a volume target. The sales manager who approves the deal carries the same target across the team. The regional manager above them carries it across the region. Every layer of the approval route is measured on the number that the deal helps deliver.

That does not make anyone dishonest. It makes approval a commercial decision rather than a check. The deal is reviewed by the people who need it to close, often at the point in the quarter when they need it most.

Ask a sales director how many discount requests were declined last quarter and the answer is usually approximate. Ask how many were approved in the final week of the period and the answer is usually harder to assemble.

The control was designed to catch the deals carrying the most risk. It ends up being reviewed by the people under the most pressure to let them through.

What does this cost commercially?

None of these are dramatic events. Each is a reasonable response by someone trying to hold on to a customer or land a quarter.

The effect is consistent, though. The control keeps reporting compliance, because every deal it can see sits inside the limit. The discounting it cannot see lands somewhere else: in credit notes, in terms, in stock, in promotional support.

The variance turns up at account level months later, in a margin review, and cannot be traced back to a decision anyone remembers making. By that point the account has a settled expectation, the concessions have become the running rate, and unwinding them is a renegotiation rather than a correction.

The commercial risk is not the size of any single concession. It is that the true cost to serve an account is assembled from four or five sources that never meet, so nobody can state it in a single number when it matters.

How can you tell whether your threshold is controlling behaviour or describing it?

A short exercise, using deals already agreed rather than a new report.

Take the agreements signed last quarter and plot them against your threshold. Look at the shape of the distribution rather than the average.

Then take the accounts sitting just underneath the limit and pull everything else those customers received in the same period. Credit notes raised, payment terms applied, free-of-charge stock, promotional contributions, delivery concessions.

Four things are worth establishing about any threshold.

  1. How many deals land just below it, and whether that pattern looks like chance.
  2. Which customer concessions sit outside the approval route entirely, including payment terms, free-of-charge stock and promotional support.
  3. Who signs off, what they are measured on, and how many requests they declined last quarter.
  4. When the threshold was last reviewed against current cost.

If those answers are hard to assemble from the systems you already have, the threshold is describing behaviour rather than controlling it.

What does better discount control look like in practice?

The answer is rarely a lower threshold. Lowering the limit moves more volume into the queue and makes sign-off more of a formality, not less.

Three things tend to matter more.

The first is coverage. Every concession that carries a cost belongs in the same approval framework, whether it is expressed as a percentage, a payment term, a case of free stock or a promotional contribution.

The second is traceability. When an exception is agreed, it is recorded against the account with a reason and an owner, so the credit note raised six weeks later can be read alongside the decision that caused it.

The third is a single account view. Customer, product and price records need to line up well enough that everything an account received can be rolled up to one place, including sites trading under different codes within the same group.

Control comes from visibility rather than from a tighter number.

How Allsop helps food and beverage businesses close the gap

At Allsop, we work with food and beverage businesses through intelligent software for Customer Order Management, Data Workbench and Customer Margin Management.

Customer Order Management handles orders through a controlled route, so split orders, manual adjustments and out-of-process amendments are visible rather than absorbed.

Data Workbench improves the process behind master data, so customer hierarchies, product records and agreed price records stay accurate and consistent. That is what allows every concession an account receives to roll up to the right customer, including group structures trading across multiple sites and codes.

Customer Margin Management brings the agreed terms, the invoiced position and the after-the-fact adjustments together, so account margin can be read as one figure rather than reconstructed from several.

We do not decide what a customer should pay. We work on the process around that decision, so approvals hold, exceptions are recorded where they can be seen, and the full cost of an agreement sits in one place rather than four.

If your approval reporting looks healthier than your account margin, it might be worth a closer look. Speak to us, or read more about how we help protect margin across the order-to-invoice process


Frequently asked questions

What is a discount approval threshold?

It is the level at which a proposed discount or deal value must be authorised by someone senior to the person agreeing it. Below the threshold, the salesperson can proceed. Above it, the deal goes for sign-off. It is one of the most common margin controls in food and beverage businesses.

Why do discount thresholds stop working over time?

Because they control one variable in a negotiation with several. Once the limit is known, deals cluster just below it and the remaining commercial value moves into routes the threshold does not cover, such as credit notes, payment terms, free stock or promotional support. Thresholds also lose relevance when they are not reviewed against current cost, so an exceptional level becomes a routine one.

How does discounting show up in credit notes?

An order is invoiced at the agreed rate and a credit note is raised afterwards to settle a difference that was agreed verbally. Because it is not logged as a delivery shortfall or a quality issue, it does not appear in either exception report, and it sits in a ledger that is rarely read alongside the pricing file.

Should we lower our discount approval threshold?

Lowering the limit usually increases the volume of deals in the approval queue, which makes sign-off faster and less considered rather than more rigorous. Coverage tends to matter more than level: bringing payment terms, free-of-charge stock and promotional contributions into the same framework as percentage discounts.

Who should approve discounts in a food and beverage business?

The practical question is what the approver is measured on. If every layer of the approval route carries the same volume target as the person requesting the discount, approval becomes a commercial decision rather than a check. Involving a function that is measured on margin rather than volume, and recording declines as well as approvals, gives the control more weight.

How do you measure the true cost of a customer agreement?

By bringing the agreed price, the invoiced position and every after-the-fact adjustment together against one customer record. That requires accurate customer hierarchies, so group accounts trading under several codes roll up correctly, and a record of exceptions with a reason and an owner attached.

Grow Your Business with Automation

Start your free trial with Allsop Software now and we will contact you right away to arrange a call at a convenient time