Running a reseller channel across three regions and four currencies

The situation

A security product at an average of 65,000 USD per year does not sell itself. Resellers run the pre-sales engagement, handle the security questionnaire, and often provide first-line support afterwards. That work justifies a margin rather than a referral commission, and it also means a reseller who loses a deal to the vendor's own team has lost real invested cost, not a finder's fee.

With a direct team operating in the same three regions, collision is not an occasional accident. It is the default outcome unless something prevents it.

Channel conflict, decided in advance

The only workable approach is a rule published before the first collision, applied mechanically afterwards. Partners accept losing a deal to a rule. They do not accept losing one to a judgement made after both parties are already invested, because it always looks like the vendor protecting its own quota.

• Registration grants a 30 day exclusivity window. A reseller who registers an account first gets 30 days of exclusivity on it, extendable once with evidence of active progress. Timestamped, and visible to both sides.
• The direct team registers too. The rule is symmetrical or it is not a rule. If the direct team can take an account without registering it, resellers correctly read registration as a formality that binds only them.
• Declines carry a reason. A registration rejected because the account is already active with the direct team is survivable. A rejection with no explanation ends the relationship with that reseller's sales team, whatever the contract says.
• House accounts are named up front. A published list of accounts that are permanently direct is far better received than discovering the exclusion after a registration is refused.

Four currencies, and the errors that erode trust

Paying in EUR, AED, SGD and USD introduces failure modes that produce no alerts and surface only when a partner arrives with their own spreadsheet. In a channel where a single partner's annual margin runs into six figures, a partner who cannot reconcile their own payments will assume the error runs in the vendor's favour.

• Fix the rate at approval, and store it. The exchange rate used is recorded on the commission record itself, so any historic payment can be reconstructed. A rate that floats between calculation and payment guarantees every payout differs from the figure the partner was shown.
• Round once, at the payment boundary. Rounding at each intermediate step compounds across a tiered calculation, and the drift is always noticed.
• Define tier thresholds in one currency. A rule of the form 'top tier above X' has to name the currency of X and convert consistently. Summing mixed-currency volume into a single figure without a stated conversion basis produces tier assignments that are wrong and plausible, which is the hardest kind of error to find.
• State who pays the transfer fee. In the agreement. A partner expecting 40,000 and receiving 39,960 reads the difference as a short payment, not a bank charge.

Concentration is the risk nobody plans for

In this model 6 of 18 resellers carry the large majority of volume, which is the normal shape of a reseller channel rather than a failure. The risk it creates is rarely managed: a top reseller leaving takes their customer relationships with them, because in a reseller motion the partner owns the commercial relationship and often the support one too.

The practical mitigations are unglamorous. Maintain a direct relationship with end customers even on reseller-sold accounts, so a partner departure is not a customer departure. Keep renewal dates and contract terms in your own system rather than only in the partner's. And treat a top reseller's engagement level as a leading indicator worth monitoring, because the notice period on a channel partner is usually shorter than the time it takes to replace them.