This is a hypothetical channel case, not a report about named companies. It is designed to expose the evidence and policy choices that sit underneath a common complaint: “that customer is mine.” The lesson is not that one routing rule is universally correct. The lesson is that ownership disputes become expensive when the company has never separated geography, opportunity creation, account relationship and service responsibility.

The setup

Dealer West covers a metropolitan territory. Dealer Strategic has a list of named multi-location accounts across several states. A customer headquartered in West’s geography opens a new local facility. West performs a site visit after an inbound request. Strategic says the customer is on its named-account list and has an existing corporate relationship. Both submit forecasts for the same opportunity.

Why the map cannot decide it

A simple geographic rule favors West. A simple named-account rule favors Strategic. Neither answer addresses who originated the opportunity, whether the corporate relationship actually covers the new facility, who can provide local service, or how the end customer wants to buy. The conflict is not a bad attitude problem; it is a missing policy hierarchy.

Evidence packet before adjudication

The channel manager freezes duplicate quotes and gathers a short packet: customer legal entity and hierarchy, named-account effective date, opportunity creation timestamp, communications showing the relationship, local service requirements, customer preference if expressed, partner contract language, and any opportunity-registration record. Facts should be separated from claims. “We have always owned them” is not a data field.

Decision path A: named account keeps commercial ownership, local dealer gets service role

This can work when the corporate relationship genuinely drives the purchase but local execution is essential. The program needs a service-credit mechanism so West is not asked to perform unpaid work. It also needs customer-facing clarity; internal channel economics should not create a confusing handoff.

Decision path B: local opportunity registration prevails

If the program’s published rules give valid registered opportunities precedence and West created the opportunity before any active strategic pursuit, the company may route commercial ownership locally. Strategic may still receive visibility or account-level coordination. The key is consistency: a registration rule that is ignored whenever the disputed deal is large is not a rule.

Decision path C: split credit without splitting accountability

Revenue credit can sometimes be shared while one partner remains the accountable commercial owner. This is preferable to telling both parties to “work together” without defining who prices, who communicates, who services, and who gets paid. Shared credit should solve incentives, not create dual command.

Where legal review enters

Territory protection, exclusivity and customer restrictions can have competition-law implications that depend on the facts, market position and jurisdiction. U.S. FTC guidance is useful context but not a substitute for reviewing the actual agreement and market. If the proposed solution changes contractual exclusivity or restricts who may sell to whom, qualified counsel should review it.

What the company changes after the dispute

The fictional company adds a written precedence ladder, an evidence checklist, expiry dates for named-account lists, a definition of “active pursuit,” a local service-credit rule and a 48-hour conflict-review SLA. It also measures overrides by cause. The purpose is not to eliminate every dispute; it is to make the next one faster, more predictable and less political.

The transferable rule

A territory conflict should end with two outputs: a decision on the current account and a change—or a deliberate confirmation—to the rule that produced the conflict. If the company resolves the deal but learns nothing about the operating model, the same argument will return with a different logo next month.

Operator review notes before the next cycle

Reopen one recent ownership dispute after emotions have cooled. Remove the partner names and ask a neutral reviewer to apply the written rules to the facts. If the outcome changes when identities are hidden, discretion may be dominating policy.

Check the timestamps that mattered: first qualified activity, registration, customer response, reassignment notice and service engagement. Many disputes that look philosophical are actually evidence-order problems.

Look separately at sales credit and customer service. The partner that sourced an opportunity may not be the partner best placed to install or support it. A conflict process should be able to split those roles without pretending there can be only one winner.

Review what the customer was told. Internal territory rules should not force a customer to repeat discovery, wait for two partners to argue, or receive contradictory quotes.

After the case closes, code the root cause—unclear rule, bad data, late registration, inactive owner, parent-child ambiguity, service constraint or deliberate exception. The postmortem should improve the next routing decision, not just document who prevailed.

Final evidence-control appendix

A useful conflict file contains the facts available at the time of the decision, not a narrative rewritten after the winner is known. Preserve CRM timestamps, registration evidence, customer communications and the rule version that was in force.

If a manager overrides the normal hierarchy, record both the reason and the expected precedent. Some overrides should remain one-off; others reveal that the written rule is obsolete. Without that distinction, exceptions accumulate until no partner trusts the map.

Keep legal review separate from operational adjudication. A fair internal routing outcome does not itself establish that a contractual restriction is lawful, and a legally permissible structure does not guarantee good channel economics. Those are different questions with different evidence.

Sources

Related Reading