deal registration is a promise. here is where it breaks

Deal registration is a promise from the vendor to the partner: find the opportunity, tell us first, and we will protect your price on it. When the promise holds, partners register early and the vendor sees pipeline it would otherwise never see. When it breaks, partners stop registering, quote at the last minute and compete on discount. Channel practitioners name four places where it breaks, all of them on the vendor’s side.

what registration does, in one plain paragraph

A partner submits an opportunity: customer, project, products, estimated value, expected date, and evidence it is working the deal. The vendor or its distributor approves it. From that point, the registered partner gets a better buy price for that customer and project than anyone else quoting it, for a fixed period. Another partner can still quote, but from a worse cost base. That differential is the whole mechanism.

Registration does three jobs at once. It lets the partner that did the work hold its price against partners that did not. It gives the vendor an early signal of pipeline. And it ties the partner, implicitly, to staying on the deal with your product instead of switching to a competitor halfway through.

the settings that show up in public programmes

Parameters vary, but the public partner programme guides of large security vendors cluster around a recognisable set:

• Protection period: 90 days from approval is the most common setting.
• Extensions: often up to two, granted when the partner updates the status.
• Decision time: the fastest published commitment is 72 hours. Some local distributors publish 48 working hours.
• Minimum deal size: several programmes have dropped it, or approve registrations automatically below a threshold with the base discount.
• Conflict rule: usually the first complete registration with evidence of activity wins. Some programmes, when two partners both show real activity, follow the customer’s first order.
• Renewals: handled outside registration, through protection for the partner that serves the customer today.

Copying these numbers is fine. What breaks programmes is the gap between the published rule and how it gets applied.

where it breaks

1. slow approvals

A partner registers on Monday and hears nothing for two weeks. Meanwhile it has to quote. It either quotes at standard price and risks losing to a competitor, or waits and risks losing the customer. Either way, it learns that registering costs time and buys nothing. Publish a decision deadline and meet it. “No answer” should never mean approval, so the deadline is the vendor’s problem.

2. two approvals for one deal

The vendor approves registrations from two partners for the same customer, sometimes because the opportunity was described differently, sometimes because two channel managers did not check. Now both partners hold the same “protected” price and compete on margin anyway. Define the opportunity by customer and project together, and check for existing registrations before approving.

3. the direct team ignores it

The partner registers, runs the POC, builds the business case. In the last week of the quarter, the vendor’s own rep calls the customer with a better price. Whether the direct team is bound by registrations is a separate rule. Many programmes state it. Some leave it vague, and vague rules get resolved in favour of whoever escalates loudest.

4. special pricing erases the differential

This is the quiet one. A non-registered partner asks the vendor’s bid desk for a special price to “meet competition”. The bid desk approves it. The registered partner’s cost advantage is gone, even though its registration is technically still valid.

There is one test for whether your registration protection is real. When a registered partner and an unregistered partner bid for the same deal, does the registered partner’s cost advantage survive the special pricing process? If your bid desk routinely matches the unregistered partner’s request, registration is worth nothing, partners will stop using it, and your pipeline visibility goes with it.

public tenders need their own rule

A public tender adds an equal-treatment obligation. Once a contract notice is published, every bidder should get the same conditions. A sensible policy allows a registration before publication as information for the vendor and the distributor, and puts all bidding partners on equal terms after publication. Some vendor programmes exclude formal RFPs from registration entirely. Either way, write the rule down before the first tender in which two of your partners bid against each other.

the EU limit on protection

Registration protection has a legal edge in the EU. Under Regulation 2022/720 you may, in some structures, restrict a partner’s active selling. Restricting passive sales, meaning a partner answering a customer who came to it unprompted, is a hardcore restriction.

The safer design builds protection as a privilege for the registered partner, through a better price and more support, instead of a ban on others selling. A customer still has the right to choose its partner. If a second partner can show the customer approached it, it can quote at standard terms. If the customer names a different partner in writing, the registration should lapse.

If your distributor also sells directly to end customers, registration data is sensitive for partners. The Commission’s Guidelines on vertical restraints limit information exchange in dual distribution to what is needed to run the agreement. Separate teams and CRM permissions are the practical answer.

None of this is legal advice. A registration policy is a document for competition counsel.

a decision tree for conflicts

When two partners claim the same opportunity, the channel manager needs a rule that works on a Friday afternoon:

1. Is there an active, approved registration for this customer and project? If not, approve the first complete one.
2. If there is, did the second partner receive a request directly from the customer? The customer may choose its partner. The registered partner keeps the registered price, the second partner may quote at standard terms.
3. Has the registered partner shown activity in the last 30 days? If not, ask for an update. No answer within five working days, the registration can be withdrawn.
4. Has the customer named a different partner in writing? Then the registration lapses.
5. Anything the rules do not settle goes to the channel lead, with a written decision and a reason.

Written decisions matter more than their exact content. In my view, partners live with a rule they dislike more easily than with a decision they cannot predict.

what to measure

• Registrations per partner per month.
• Time to decision, as a median and at the 90th percentile.
• Share of registrations that end in an order.
• Number of conflicts and time to resolve them.
• Share of deals where a special price went to a non-registered partner on a registered opportunity.

The last number is the one that predicts whether partners will keep registering.

Registration is one of six areas in the partner program scorecard, which checks the rest of the programme from the partner’s side.

the question to ask your channel team

When was the last time a registered partner lost a deal to your own bid desk, and did anyone tell the partner before the customer did?