Deal Registration, Lead Routing, and MDF Claims

Two of your distributors call your channel manager within 48 hours of each other. One is in Cleveland. One is in Pittsburgh. Both are quoting the same large school district HVAC retrofit — same buildings, same engineering specs, same close window. Neither knows the other is involved. Both think they're competing against another manufacturer's distributor, so both have already gone aggressive on price. By the time your channel manager pieces it together, both have committed to roughly six points off normal channel pricing. The school district is delighted. Your margin is gone. And now your channel manager has to broker peace between two distributors who, until last Tuesday, trusted each other and trusted you.

You've lived this. You may have lived it more than once. The post-mortem always lands in the same place: "We need a better way to know who's working what." Then someone says deal registration. Then someone else says, "We tried that — the spreadsheet died." Then the meeting ends and nothing changes until it happens again.

This is the case for a real partner portal. Not a B2B webstore with a different banner. A control plane with three workflows that together turn channel chaos into channel discipline: deal registration, lead routing, and MDF/co-op claims. A generic e-commerce platform — Shopify B2B, BigCommerce B2B, even Magento — cannot do these. It was never designed to. These workflows live in the world of channel software: Salesforce PRM, Impartner, ZINFI, Channeltivity. If you want to stop the Cleveland/Pittsburgh scenario from repeating, this is the toolkit.

The Cleveland/Pittsburgh Problem in One Sentence

Two of your tier-A partners independently chase the same end account because there is no shared, time-stamped, contractually backed record of who saw it first.

Everything that follows in this article is the answer to that sentence.

What Distinguishes a Distributor Portal from a B2B Webstore

A B2B webstore is a self-service order channel for buyers who consume what they purchase. Spot orders, account-based pricing, reorder lists, punchout integration. Useful, sometimes essential — but unrelated to the problem above. Adding a webstore would not have prevented the Cleveland/Pittsburgh deal. The webstore doesn't know what a deal is. It knows what a cart is.

A distributor portal is your control plane over a contracted reseller network. It knows that Cleveland HVAC Supply is a tier-A partner authorized to sell the commercial chiller line in northeast Ohio, that they're on a 38-point margin program, that they earn 2% MDF accrual on quarterly sell-through, that they have two unclosed registered deals over $50K, and that the Pittsburgh partner is authorized in western PA but not in northeast Ohio. It enforces rules. It records timestamps. It produces an audit trail. The webstore does none of that. (For the longer version of this distinction, see distributor portal vs B2B webstore.)

The three workflows below are what make a portal a portal.

Workflow 1: Deal Registration

Deal registration is, at its core, a contract: the partner who logs the prospect first gets exclusive rights to that opportunity for a defined window. Other partners who try to register the same end account see "registered to another partner" and step back. If the first partner doesn't close inside the window, the deal opens up. This is what would have prevented the Cleveland/Pittsburgh collision — Pittsburgh would have seen "registered to Cleveland HVAC Supply, expires October 14" the moment they tried to log it, called your channel manager, and either backed off or formally requested release.

The Registration Form

What a partner submits when they register a deal is more than a name and a number. A serious deal-reg form captures:

• End account name and location (the school district, the contractor, the property owner — whoever ultimately writes the check)
• Project name and brief description ("Lakewood HS chiller retrofit, four AHUs")
• Estimated total deal value
• Expected close date
• Products under quote (SKU-level if known, family-level if early-stage)
• The partner's named sales rep on the account
• Whether the partner is competing against your manufacturer's other partners or a different manufacturer entirely

That last field matters. If a partner registers and discloses they're competing against another brand, you know the deal is genuinely yours to win or lose. If they leave it blank, your channel team has a flag to investigate.

Approval Workflow

Not every registration should auto-approve. A reasonable policy looks like this:

The threshold matters because auto-approval below a certain dollar value keeps friction low for the bread-and-butter deals (every distributor has fifty $5K opportunities at any given time), while manual review above the threshold lets your channel team catch the Cleveland/Pittsburgh scenario before it ships. A good portal also flags any registration where the end-account name fuzzy-matches an existing registered deal or an existing customer of record.

Conflict Resolution

When two partners try to register the same account, the timestamp wins. Period. Do not adjudicate by relationship strength, sales rep tenure, or who called your channel manager first to complain. The portal's timestamp is the single source of truth, and your channel team enforces it without negotiation. The moment you make exceptions — "well, Pittsburgh has been with us for fifteen years" — the system loses credibility and partners stop trusting the registration to mean anything.

The exception that's defensible: if the second partner can show they had documented, dated communication with the end account before the first partner's registration timestamp, your channel team reviews and may award the deal to the second partner with a documented decision attached to both partners' records. This happens rarely. When it does, the audit trail makes the call defensible.

Window Length and Extensions

Standard exclusivity windows run 60 to 90 days, with the choice driven by your typical sales cycle. HVAC commercial retrofits often need 120 days; consumable industrial products may justify 30. Choose one default per product line and write it into the partner program guide.

Partners can request extensions before expiration. The form asks: where is the deal in the cycle, what's the new expected close date, and what's the reason for the slip (procurement timing, end-customer budget cycle, engineering revision). Extensions are reasonable when the deal is genuinely active. Extensions are not reasonable when the partner has gone dark on the account for 45 days. The portal shows the channel team the partner's last activity timestamp on the deal, which makes the extension decision factual rather than negotiated.

Why the Audit Trail Is the Whole Point

When a deal-reg conflict surfaces six months later — and they always surface six months later, usually in front of the VP of Sales — the audit trail is what ends the argument. Who registered first. When. What was disclosed. Who approved. When the window opened or expired. What activity each partner logged. Without this, you're back in "he said, she said" territory, and the loud distributor wins. With it, the policy wins, which means in the long run, your margin wins.

For a deeper treatment of how deal-reg interacts with territory definitions and the broader anti-conflict framework, see channel conflict, territory mapping, and deal reg.

Workflow 2: Lead Routing

Deal registration handles partner-originated demand. Lead routing handles manufacturer-originated demand: the inquiries that come in from your trade show booth, the contact forms on your website, the leads from your latest product launch campaign, the names that came out of a co-marketed webinar. None of these belong to a partner yet. Your job is to hand them to the right partner under rules that are visible, fair, and enforceable.

Routing Rules

A working routing engine layers four rules in order:

Territory. Route by ZIP code, county, or state, depending on how your partner agreements define exclusivity. ZIP-code precision matters in dense markets — the Cleveland/Pittsburgh problem partly exists because the dividing line between northeast Ohio and western Pennsylvania has overlapping commuting and trade-flow patterns. Get the boundaries written into the portal and have the routing engine respect them.

Certification level. Some leads require partners with specific training. A complex industrial automation lead with a system integrator should not route to a tier-C reseller who has never been through your controls certification. Tag leads by complexity at intake; tag partners by certification level in the partner profile; let the engine match.

Recent performance. A partner who has missed the last three lead follow-ups should not get the next one until they catch up. The portal tracks accept/decline history and first-contact timestamps. If a partner's 30-day acceptance rate drops below 70% or their 30-day first-contact-on-time rate drops below 80%, the engine routes around them until they recover.

Round-robin within tier. Once the eligible pool is narrowed by territory, certification, and performance, distribute leads round-robin among the qualifying tier-A partners. This prevents your largest partner from quietly absorbing every inbound lead in the geography while the second- and third-largest partners feel starved.

SLAs That Actually Bite

A lead-routing system without SLAs is a lead-leaking system. Two SLAs matter:

• Acceptance SLA: 24 hours. The partner accepts or declines the lead within one business day. No response triggers auto-reassign to the next eligible partner.
• First-contact SLA: 72 hours. Once accepted, the partner logs first contact with the lead within three business days. Missed first-contact triggers escalation to the partner's principal and reassignment if appropriate.

Both SLAs need to be visible to the partner in real time — a counter on their portal dashboard showing leads aging — and visible to your channel team in aggregate. The reason most lead programs fail is not that partners are bad; it's that no one is watching the clock until the trade show ROI report comes out and there are 47 untouched leads.

Named-Account Carve-Outs

Some accounts should never be routed. Strategic named accounts — your largest end customers, government accounts, OEM partnerships — sit on a named-account list with assigned partners (or, occasionally, direct-managed by your team with named-account commission paid to a partner of record). The routing engine checks the named-account list first and routes those leads to the assigned partner regardless of geography. This is the workflow that prevents your enterprise-class lead from going to a generalist tier-B partner just because the trade show booth was in their ZIP code.

Workflow 3: MDF and Co-op Claims

Market Development Funds (MDF) and co-op funds are how you co-invest with partners in demand generation: trade show booths, regional advertising, lunch-and-learns with engineering firms, sponsored content in trade publications, sales spiff programs. The structural problem is simple — most manufacturers leak 30 to 50% of their MDF budget through bad tracking. Funds are accrued and never claimed. Activities are pre-approved and never executed. Claims are submitted without proof and paid anyway because the channel team is buried. Money goes out the door without driving the demand it was meant to drive.

A real MDF workflow has four stages, each with its own discipline.

Accrual

Accrual rules need to be transparent and machine-calculated. The most common structure: a percentage of quarterly sell-through accrues as MDF, with caps. Example: a tier-A partner accrues 2% of net quarterly sell-through, capped at $25,000 per quarter, with a use-it-or-lose-it window of two quarters from accrual.

The portal calculates accrual automatically from POS or sell-through reporting. The partner sees their balance in real time. Your finance team has a single defensible source for what's accrued, what's committed, what's claimed, what's expired.

Pre-Approval

Spending against MDF requires pre-approval. The partner submits a planned activity — "regional HVAC contractor breakfast, 75 attendees, June 18, $4,200 budget" — with detail on objective, target audience, expected leads, and how the funds will be used. Your channel marketing team reviews and approves, partially approves, or rejects with reasons.

This is the stage that prevents the most leakage. Without pre-approval, claims arrive after the fact for activities that don't fit the brand, don't fit the strategy, or — common — don't fit the program rules. With pre-approval, both sides have agreed on what the money is for before it's spent.

Claim Submission

After execution, the partner submits a claim with proof:

• Photos of the booth, the event, the printed materials
• Vendor invoices (the actual receipt from the printer, the venue, the ad agency)
• Attendee lists or registration scans
• Any leads or contacts captured (which feed back into your lead routing system as appropriate)
• A short post-event narrative: what happened, what the partner learned, what follow-up is in flight

Claims without proof get rejected. This is non-negotiable, because the moment you start paying claims on the strength of a partner's word, the rest of your partners notice and the program loses integrity.

Approval and Payment

Channel marketing reviews the claim against the pre-approved plan. Variance under 10% of approved budget — pay it. Variance over 10% — review and either approve with documented reasoning or partially pay. Payment terms run net-30 from claim approval, paid as a credit memo against open invoices or a separate ACH depending on the partner's preference and your finance system's capabilities.

The portal shows the partner exactly where their claim sits in the workflow at any moment. "Submitted June 22, under review by channel marketing." This kills 80% of the inbound calls your channel team gets about MDF status.

What 30–50% Leakage Looks Like in Dollars

Take a manufacturer with $80M in channel sell-through, an average MDF accrual rate of 1.5%, and the typical 35% leakage rate. That's $1.2M in MDF accrued, $420K leaked. Some of the leak is in funds that simply expire because partners didn't use them (which is on the partner — but those are dollars you committed and didn't get demand-generation value from). Some is in claims paid for activities that didn't happen. Some is in approved activities that never got executed. Tightening this workflow with a real portal commonly recovers 15 to 25 points of leakage — on this example, $180K to $300K of demand-generation spend that actually drives demand.

Why These Three Live in One Portal

The same partner uses all three workflows, often on the same day. A tier-A distributor logs in to register a deal in the morning, accept a routed lead from your trade show in the afternoon, and submit an MDF claim for last week's contractor lunch in the evening. If those workflows live in three separate tools — deal-reg in a Salesforce custom object, leads in HubSpot, MDF in a SharePoint folder with email approvals — the partner experience is fragmented and your channel team's view of the partner is fragmented.

You want to be able to look at a partner profile and see, in one place: registered deals, accepted leads, accrued and claimed MDF, performance against SLAs, certification status, current product mix, sell-through trend, open RMAs. That's a partner relationship dashboard. You can't build it if the source data lives in five different systems with three different identity models for "who is this partner."

This is also why generic B2B platforms aren't substitutes. They were built for a different problem.

What the Vendor Landscape Actually Looks Like

The two product categories overlap in name only. If you're solving the Cleveland/Pittsburgh problem, you're shopping in the left column. If you're solving "my key accounts want to place reorders without calling inside sales," you're shopping in the right column. Many manufacturers eventually need both — but they are two implementations, not one.

For an end-to-end view of how OrderHUBx fits into the channel-side stack, the home page and managed e-commerce operations page lay out where we sit relative to PRM-class tools and what we co-exist with.

Implementation Order

If you're starting from nothing and have to sequence these three workflows, the order is not arbitrary.

Deal registration first. Highest-pain workflow, fastest ROI, most defensible budget conversation with your CFO. The Cleveland/Pittsburgh story has happened in your business; you have the dollar number for what one collision costs. Two prevented collisions usually pay for the first year of the platform. Deal registration also forces you to do the discipline work of writing your channel program rules down, which makes the next two workflows much faster to configure.

MDF second. Where the leakage is biggest in absolute dollars. Tightening accrual, pre-approval, and proof-of-execution claims is the workflow with the largest measurable financial recovery. This is also the workflow where partners notice the improvement most — they can finally see their balance, see their claim status, and stop chasing your channel team for answers.

Lead routing third. Not because it matters less, but because it requires marketing-ops alignment that the first two don't. You need clean lead intake from your marketing automation platform, you need agreement on tagging conventions, and you need a partner certification-level data model to route well. Doing lead routing well requires marketing and channel to agree on definitions. That alignment is worth doing — but it takes longer than turning on deal registration, which mostly just requires the channel team to be aligned with itself.

What Changes the Day You Turn It On

The first week, partners log in and complain about having to use a new tool. The second week, the first deal-reg conflict is decided cleanly by timestamp instead of by phone call, and one of the partners — privately — admits the rule is fair. The first month, your MDF accrual balance becomes visible to partners and inbound questions to your channel team drop by half. The first quarter, you stop having Cleveland/Pittsburgh meetings, because the conflicts get caught at registration time instead of at quote time.

That's not transformation. That's discipline made operational. The portal is the place the discipline lives.