A partner that asks for more discount is usually telling you that something else is broken. Its margin does not pay for the presales, and service work your product needs, or another quote is undercutting it: from a competing partner, or from your own direct team. Sometimes did not protect it, or the rebate meant to pay for the effort arrives months after the deal. Find out which one it is before you touch the price list, because a bigger discount for everyone fixes one of these at most and often makes the others worse.
what the request usually means
Five causes sit behind most discount requests. They look the same in an email and need different answers.
- The margin does not pay for the effort. A security product that needs presales days, a POC, an implementation and a hand-held first renewal costs the partner engineer time on every deal. If the licence margin is its only income from the deal, every extra day comes out of that margin. The partner’s side of this is in the guide on services partners can attach. Here the symptom is a discount request on deals that ran long.
- A competing partner quoted lower. Two resellers chase the same customer. One cuts its price, and the other asks you to fund the match.
- Your own team quoted lower. Your direct seller, your website or your offered the same customer a better price. Channelnomics, in a 2024 piece on channel conflict, names partners competing with the vendor’s direct sales force as the classic form of conflict, alongside partners competing with each other for the same sale. In a Channelnomics survey cited in the same piece, with no sample size given, 25% of vendors and 16% of partners saw distribution as a source of conflict too.
- Registration did not protect. The partner registered, then waited for approval, found a second approval on the same deal, or watched a special price go to someone else.
- The back-end money arrives too late. The partner did the work this quarter, and the rebate or marketing fund that was meant to pay for it lands two or three quarters later, if the partner remembers to claim it.
Only the first cause is about the size of the margin. The other four are about prices and processes you control.
how to tell which one it is
Ask for the deal behind the request. “We need five more points across the range” tells you little. A request tied to a named customer and a date can be checked against your own records.
| Question | If the answer is yes, the cause is likely | Where to check |
|---|---|---|
| Is there another quote on this deal, and whose is it? | A competing partner, or your own team | The partner, your CRM, the bid desk log |
| Was the deal registered, and how long did approval take? | Registration that did not protect | Registration records, special price approvals |
| How many presales and POC days has the partner spent? | Margin that does not pay for the effort | The partner’s estimate, your engineer’s notes |
| When did the partner last receive back-end money, and for which period? | Rebates that arrive too late | Incentive and finance records |
| How long did your quote or special price take? | A slow process that makes the partner price defensively | Timestamps in your quoting tool |
Two patterns are worth separating. A request that comes from one partner on every deal is usually about its cost of doing business with you. Requests that come from several partners on the same customers, or in the last weeks of your quarter, usually point to a price someone else is quoting. Check your own team first, because it is the one you can fix today.
why more discount often lands in the wrong place
Run the request through the channel price waterfall, with the same illustrative numbers as that guide. A subscription lists at 1,000. You sell to the distributor at 650, the distributor sells to the reseller at 700, and a competing reseller quotes the customer 850. The first reseller matches at 850 and keeps 150.
Now give every reseller five more points to answer the request. Resellers buy at 650, and to leave the distributor its 50 you charge it 600. The competing reseller has the same five points, so it quotes 800. The first reseller matches at 800 and keeps 150 again. The customer pays 50 less, you receive 50 less, and the partner that asked is where it started.
Five more points for every reseller, on one deal
- list price1,000Unchanged.
- you receive60050 less than before.
- reseller buys650Every reseller, including the competitor.
- competitor quotes800It passes the five points to the customer.
- reseller keeps150The same as before the extra discount.
Leveling discounts has a second cost. If the extra points also go to partners that only process orders, you pay fulfilment the same as the partner that found and built the deal, and the gap that made registration worth anything shrinks.
Some vendors fund a bigger discount by raising the list price so their own net stays flat. Illustrative numbers again: list goes from 1,000 to 1,100 and the reseller discount from 30% to 36%, so the reseller buys at 704, close to where it was. A reseller that quotes 10% off list now asks 990 instead of 900. The customer that pushes gets the deeper discount. The customer that does not, and every renewal priced from list, pays more. The end price goes up for the quiet buyers, and the list price stops meaning anything.
To see where each extra point ends up with your own prices, run both versions in the channel price waterfall calculator.
what to offer instead
Match the answer to the cause. Most of the useful answers cost less than a permanent point of discount, because they go only to the deals and partners that need them.
The cause behind the request, and the answer that fits
the gap is about price protection →
the cause sits inside your company →
Registration protection that holds. A decision deadline you meet, one approval per customer and project, and a bid desk that does not give an unregistered partner a special price on a registered deal. The deal registration guide covers the rules and the test for whether yours is real.
A direct team that does not compete on price. If your seller earns more when a deal closes direct, partners will keep asking for discount to defend themselves. The credit and pay rules are in the guide on paying the channel team. Your own direct and online prices should sit at or above what a partner can sustain.
Paid support for the effort. Fund the POC instead of the price: engineer days, demo licences, a fixed contribution for a defined test. The partner-run POC guide shows how to set one up. Large vendors already separate this money from discount. AWS describes partner funding to help build pipeline and “explore proof of concepts”, and marketing development funds paid as cash or AWS promotional credits. Add priced service packages the partner can attach, so the effort becomes revenue.
Quote speed. A partner that waits days for a quote or a special price pads its number or asks for room to move. Publish a turnaround for standard quotes and special prices, and measure it from your own timestamps.
front-end, back-end and when the money arrives
Front-end margin is the discount on the invoice. Back-end margin is paid later when a condition is met. Both can be the same total over a year and feel very different to a partner pricing a deal this week.
Microsoft’s documentation shows how long the gap can get. Its co-op guide describes incentive earnings split between a rebate, paid at each programme’s payout cadence, and co-op funds. Co-op accrues over a six-month earning period, has to be used in the following six months and claimed in a six-month window, and unused earnings are forfeited. In the example table on that page, earnings from July to December 2023 could be claimed from 16 February to 15 August 2024. Microsoft’s earnings FAQ adds that commerce incentive earnings can be restated for a rolling .
That design suits a programme of Microsoft’s size and a partner with someone to track claims. A small integrator that bought engineer days in July cannot price a deal with a payment that may arrive the following summer. It prices with the money it can count on when it quotes, and it asks for that money as discount.
A workable split: front-end money for behaviour on this deal, such as a registered or partner-sourced opportunity or a new customer. Back-end money for behaviour over a period, such as growth, certified engineers or renewals. Pay the back-end on a published schedule, with a statement that shows which deals earned it.
the line you cannot cross in the EU
When partners keep cutting each other’s prices, it is tempting to tell them to stop. Under Article 4(a) of you may recommend a resale price or set a maximum. Fixing a minimum or fixed resale price is a hardcore restriction. Making a rebate or payment depend on a partner not discounting below a level can amount to the same thing, as the Commission’s Guidelines on vertical restraints describe for indirect pressure on resale prices. Use structure instead: registration, fewer partners per segment and your own prices. This is not legal advice, and any policy that touches resale prices belongs with competition counsel.
the next discount request
When a partner asks for five more points, answer with a question: five points to beat whom, and to pay for what?
checked figure
12 months
is the rolling period over which Microsoft Commerce Incentives earnings can be restated.
doesn't show One vendor's rule; it shows why back-end money is hard for a partner to plan with, not how every programme works.
source: Microsoft Learn: earnings troubleshooting FAQ (opens in a new tab)all numbers
glossary
POC
A time-boxed evaluation in the buyer's environment that answers whether the product does the job. A passed POC and a buying decision are two different layers, so the guide agrees to one only when the doubt can't be resolved more cheaply, a decision date exists and the buyer commits its own people. Public guidance clusters around two to eight weeks; GitLab designs its evaluations around 30 days with a check at day 15.
read more: how to run a security POC that ends in a decisionglossary
glossary
deal registration
A process in which a partner tells the vendor about a specific opportunity and, once it is approved, gets a better buy price than other partners quoting the same customer and project for a fixed period. In the public partner programme guides of large security vendors, 90 days from approval is the most common setting. It breaks on the vendor's side: slow approvals, two approvals for one deal, a direct team that ignores it and special pricing that erases the differential.
read more: deal registration is a promise. here is where it breaksglossary
glossary
special pricing
A price below the standard partner price, approved deal by deal, usually to meet competition. When a non-registered partner gets one on a registered opportunity, the registered partner's cost advantage disappears while its registration stays technically valid. Special pricing on a large share of deals is also one of the early signs of margin leakage in a channel.
read more: deal registration is a promise. here is where it breaksglossary
glossary
Vertical Block Exemption Regulation
The EU regulation that sets the limits of distribution agreements. A supplier may recommend a resale price or set a maximum, while fixing a minimum or fixed resale price is a hardcore restriction, and so is restricting passive sales to customers who approach a partner unprompted. It shapes deal registration, exclusivity, rebates and MDF conditions, and a policy built on it is a document for competition counsel.
read more: the channel price waterfall: from list price to the CISOglossary
glossary
MDF
Money a vendor gives partners for marketing, usually paid against proof of execution. The often repeated claim that 60% of MDF goes unused has no published study behind it: an August 2026 analysis by Technology Match traced it to a single vendor blog post. The agreed reasons funds stay unspent are pre-approval, co-funding and proof paperwork that cost a small partner more time than the money is worth, and the guide's fix is to fund outcomes such as registered deals.
read more: content your channel partners will actually sendglossary
questions
Should a vendor give partners more discount when they ask for it?
Only after finding the cause. If the partner is losing to another quote, extra discount for everyone usually goes to the customer. If its margin does not cover presales, POC and service work, paying for that work directly is usually cheaper and easier to target than raising the licence discount.
What is the difference between front-end and back-end margin?
Front-end margin is the discount on the invoice, known when the partner quotes. Back-end margin is paid later when a condition is met: rebates, incentives and market development funds. Partners price deals with the money they can count on at the time of the quote, so back-end money changes behaviour over a period more than the price of one deal.
Can a vendor stop partners from discounting in the EU?
No. Under Article 4(a) of Regulation (EU) 2022/720 a supplier may recommend a resale price or set a maximum, but fixing a minimum or fixed resale price is a hardcore restriction. Making a rebate or marketing fund depend on a partner's resale price can amount to the same thing. This is not legal advice.
sources
- Commission Regulation (EU) 2022/720, Article 4
- European Commission: Guidelines on vertical restraints (2022/C 248/01)
- Channelnomics: The changing face of channel conflict (2024)
- Microsoft Learn: Incentives co-op and claims overview
- Microsoft Learn: FAQs about troubleshooting your earnings in Partner Center
- AWS: Funding benefits for AWS Partners
Security Revenue · every Tuesday
How security vendors build pipeline.
Subscribe and get the Distributor Selection Kit: interview questions, the one-or-two arithmetic and a price waterfall worksheet. It comes with the welcome email, together with the other subscriber kits.
