Deal registration lets a partner claim a specific sales opportunity. Once the vendor approves the claim, that partner is the only one credited for the deal, and other partners (and usually the vendor's own sales team) can't take it over for a fixed window. In the three public policies we read for this guide, that window is 90 days, or 180 days for resellers in one case.
It exists because partners do real pre-sales work before a customer ever touches your checkout: discovery calls, demos, scoping, sometimes a proof of concept. Without registration, a partner who spends six weeks warming up an account has no protection if the customer later calls your sales team directly, or a second reseller quotes a lower price. Partners who get burned once stop bringing you deals. That's the whole reason to run it.
How deal registration works, step by step
The flow is the same in almost every program, whether it runs in a spreadsheet, a CRM or a partner portal.
- The partner submits. They fill in a form with the customer's legal company name, the main contact, the product and rough deal size, the expected close date, and what they've done so far.
- You check for conflicts. Is this account already a customer? Is it in your CRM as an open opportunity? Has another partner registered it? Is it a public tender?
- You approve or reject, fast. Tell the partner which, and why. A registration sitting unreviewed for two weeks is worse than none, because the partner assumes it's protected.
- The clock starts. The protection window runs from approval (most policies) or from submission. The partner works the deal; you support it.
- The deal closes or expires. Won deals pay the partner their commission, margin or registration discount. Expired registrations either get extended or release the account.
The details in steps 2 and 4 are where programs differ, and where most arguments start.
Protection windows in real policies
Vendor blogs often quote a "standard" window. We couldn't find one. What we can show is what three vendors publish, checked on 8 October 2026:
| Vendor | Window | Starts from | Extension | Notable rules |
|---|---|---|---|---|
| Bugcrowd | 90 days | Approval | One extension of 90 days may be approved | Initial meeting with the account within 30 days; only one partner per opportunity; opportunities Bugcrowd already knew about don't qualify |
| Secure Code Warrior | 180 days (resellers), 90 days (referrals) | Approval | Not described; different periods only by written agreement | Agreement terms win if they conflict with the registration |
| Tier1 Asset Management | 90 days | Notification of approval | At Tier1's discretion, before expiry | First complete and accurate submission wins; deals Tier1 is already pursuing, public tenders and deals under a minimum size are ineligible |
A few things stand out. The window starts on approval, not submission, in all three, which puts pressure on you to review quickly. Two of the three tie the window to activity: Bugcrowd wants a meeting within 30 days, and Tier1 can rescind a registration if the partner goes quiet. And Secure Code Warrior gives resellers twice as long as referral partners, which makes sense because resellers usually carry the deal further.
How long should yours be? Start from your median sales cycle for deals of that size, then add a month. If most mid-market deals close in 60 days, a 90-day window covers them with room to spare. Enterprise deals that run nine months need either a longer window or an easy extension. Don't pick 365 days to look generous. Long windows let partners park accounts they aren't working, which blocks someone else who would.
The rules to write down
A deal registration policy fits on one page. These are the clauses we'd include, in this order:
What can be registered. An opportunity, not an account. "Acme Corp" isn't a deal; "Acme Corp, 200 seats of Pro, closing Q1" is. Bugcrowd says this in as many words: opportunities may be registered, not accounts.
What can't. Existing customers (unless you run an expansion program), accounts already open in your CRM, accounts another partner holds, public tenders, and deals below a minimum size if you set one. Define "already open" precisely. We'd use "an opportunity created in our CRM with activity in the last 90 days", because "we'd heard of them" can be stretched to cover anything.
First to register wins, if the submission is complete. Tier1 adds "complete and accurate", which stops a partner from grabbing an account with a one-line entry. Require the legal company name and a named contact as a minimum.
Response time. Commit to one. Two business days is fair for most teams. If you can't approve in that time, say the registration is provisionally protected from submission.
The window and the extension rule. One extension, requested before expiry, with a reason and a next step. Automatic renewals turn registration into a land grab.
What "working the deal" means. A first meeting within a set number of days, and updates at stage changes. Partners who register and disappear lose the protection.
What the partner gets. Commission, a higher margin or a registration discount on the quote, depending on your model. Write the number down.
What your own sales team may do. This is the clause most vendors skip, and the one partners care about most. More on it below.
Channel conflict: the cases that come up
Channel conflict is any situation where two parties who sell your product want credit for the same customer. Deal registration settles the easy cases. These are the ones that need a written rule:
Two partners register the same account. If the first submission is complete, it wins. If both are partial, ask both for evidence of work and decide on that. Tell the losing partner why, in writing.
The customer calls your sales team directly during the window. Route them to the registered partner, or bring the partner in on the call. If your team closes it anyway, pay the partner as if they had. Reps will push back on this. It's still the right call, because one story about a vendor stealing a registered deal travels around a partner community faster than any recruiting campaign.
Your sales team was already working the account. Reject the registration, but only if the CRM shows real activity before the submission date. A record created the day after the partner registered doesn't count.
The partner registered, then went quiet. Ask for an update. If there's no response within a week, release the registration and tell them.
A referral partner and a reseller both touched the deal. This is common in programs that run several partner types. Decide in advance whether you pay both (influence and sourcing) or one. If you pay both, cap the combined payout so the deal still makes money.
The customer buys a different product than the one registered. Most policies say the registration covers the opportunity, not the specific SKU. We'd agree, as long as it's the same buying decision.
Paying two parties for one deal
Some programs deliberately credit both a partner and the vendor's rep for the same deal, so the rep is happy to have the partner involved instead of fighting them. If you do this, fund it as a sales cost, and budget it so the margin still works.
Say a deal is worth $30,000 a year. A partner on a 20% referral fee earns $6,000 (30,000 × 0.20). If the rep's commission is 10%, that's another $3,000, for $9,000 of the first year's revenue. That may be fine for your margins, or it may not. Run the numbers once, before the first conflict.
Metrics worth tracking
Track these monthly once you have more than a handful of registrations:
| Metric | What a bad number tells you |
|---|---|
| Median time to approve | You're slow, and partners are working deals they think are protected but aren't |
| Approval rate | Very low: your rules aren't clear. Very high: you may not be checking the CRM |
| Win rate of registered deals vs your direct deals | Partners are registering junk, or partners close better than you do |
| Share of registrations that expire unworked | Your window is too long, or partners are parking accounts |
| Conflicts per month and how they ended | Repeated conflicts with one rep or one partner usually point at a person, not a policy |
| Partner-sourced revenue from registered deals | Whether the program pays for itself |
Running it in software
A spreadsheet works for the first twenty registrations. After that you need conflict checks against your CRM, a timer on each registration, and a record of who decided what. That's the job of a PRM (see what a PRM is).
PartnersWatch, our product, includes deal registration: partners register deals from their portal, each deal enters a pipeline with stages you define, every stage change is recorded, and a partner only ever sees their own deals. A deal reaching a won stage triggers commission accrual, which you can configure on the commission side. Leads can also be routed by territory. It won't write your conflict rules for you; the policy above is still your job.
Programs in our directory that list deal registration as a partner benefit:
| Program | Partner types | Terms | Model |
|---|---|---|---|
| Teamwork | Agency, Referral partner, Integrator / MSP | On request | — |
| SmartSuite | Reseller, Agency, Integrator / MSP | Referral commission on qualified closed-won deals; reseller margin | Revenue share |
| Jibble | Affiliate, Reseller | Up to 50% (1 year for affiliates, lifetime for resellers) | Recurring |
| Airia | Integrator / MSP, Referral partner, Reseller | On request | — |
If you're setting up a reseller track for the first time, SaaS reseller programs covers margins and structure, and affiliate vs referral vs reseller helps decide which partners need registration at all. Pure affiliates usually don't: their credit comes from a tracked link, not a claimed opportunity.
FAQ
What is deal registration?
Deal registration is a process where a partner submits a specific sales opportunity to the vendor for approval, and once approved, the partner is protected as the one credited for that deal for a set period. It stops other partners, and usually the vendor's own sales team, from taking over an opportunity the partner found and is working.
How long does deal registration protection last?
It's set by each vendor. Bugcrowd and Tier1 publish 90 days from approval, and Secure Code Warrior publishes 180 days for resellers and 90 for referral partners. Match the window to your sales cycle and allow one extension for deals that are moving but slow.
What happens when two partners register the same deal?
Most policies give the deal to the first partner whose registration was complete and accurate. Tier1's terms say exactly that, and Bugcrowd allows only one partner per opportunity. If both submissions are thin, ask for evidence of the work done, decide, and explain the decision to the partner who lost.
Can a vendor's own sales team take a registered deal?
A well-written policy says no for the length of the window, unless the vendor was already working the opportunity before the partner registered it. If a rep closes a registered deal anyway, the fair fix is to pay the partner as if they'd closed it.
Do affiliate programs use deal registration?
Rarely. Affiliates are credited through tracked links, coupons or billing data, because the customer buys online without a sales call. Deal registration is for sales-led partners: resellers, referral partners who make introductions, agencies and integrators.
Is deal registration the same as lead registration?
They overlap. A lead registration usually claims a contact or company that hasn't been qualified yet, and a deal registration claims a qualified opportunity with a product, size and close date. Many programs only protect the second, because leads are cheap to submit and hard to verify.