How to Manage a Dealer Network in Your CRM

In a company that sells through dealers, the CRM has to be built in two layers: one for the dealer (who pays you) and one for the end user (who actually uses the product). A single-layer CRM shows the dealer as "the customer" and never shows the end user at all. The result: you know where revenue came from but not why it came — and when a dealer leaves, you have to learn that market from scratch.

Why is a dealer CRM built differently?

Because the sale happens twice. You sell to the dealer (sell-in), the dealer sells to the end user (sell-out). A conventional CRM only sees the first one. If a dealer is holding three months of stock, your sales chart starts falling while actual market demand is unchanged — or the reverse: sell-in climbs because the dealer overstocked, and next quarter no orders arrive.

The practical cost of that blindness is the production plan. A company without sell-out data infers demand from the dealer's ordering rhythm, and that rhythm follows the dealer's cash position, not the market.

What structure do you build?

1. Account hierarchy: the dealer is the parent account and end users are child records, so one screen shows a dealer's whole portfolio.
2. Record type field: every account is flagged "dealer" or "end user". Without it, every report blurs together.
3. Territory and permissions: a dealer sees only their own records — the prerequisite for any dealer portal.
4. Deal ownership: two fields on every deal — the dealer who brought it and your regional manager who follows it.
5. Project-based records: when two dealers quote the same end user, the project is one record and both dealers attach to it.

How do you measure sell-in and sell-out?

Sell-in is easy; it comes off your invoices. Sell-out requires data from the dealer, and it has to be built as a mutual benefit rather than an obligation. What works: route the dealer's warranty registration, installation form or service request through your system. The dealer supplies data because it makes their own work easier, and you get visibility of the end user.

Three numbers to track: monthly sell-in, monthly sell-out, and the gap between them — your estimated channel inventory. When channel stock passes two months, an order slowdown is coming, and you want to know that eight weeks ahead rather than at quarter end.

How do you measure dealer performance?

Revenue alone will not do, because an average dealer in a large territory outsells a strong dealer in a small one. Use four numbers:

• Share of territory potential: sales as a ratio of estimated market size in that region.
• Product breadth: how many product lines they sell. A single-line dealer is the first one you lose when a competitor arrives.
• New end users: are they growing the market, or reselling to the same 20 accounts?
• Payment performance: average days to collect and overdue balance.

Put those four in a quarterly table and sort dealers into three tiers: grow, maintain, review. The tier then governs how discount and support budget gets allocated — considerably more profitable than the reflex of giving the deepest discount to the biggest buyer.

How do you resolve lead conflicts?

This is the single most common source of friction in a dealer network. The rule must be written down and enforced in the CRM:

1. Every inbound request is searched in the CRM first; if the end user is already linked to a dealer, it goes to that dealer.
2. If there is no record, it is assigned by territory rule and locked with a registration date.
3. The dealer must touch the request within five business days; if they do not, it is released.
4. On project business, a registered project gives the first registrant 90 days of priority.

Without the fourth rule, two dealers undercut each other on the same project and you are the one who loses, because margin erodes from both sides.

What do you report back to the dealer?

A dealer produces data in proportion to what they can see of it. One page a month is enough: their own sell-in and sell-out chart, a comparison against the territory average, their open projects and outstanding receivables. The day that page becomes useful to them, chasing data entry stops being your job.

What are the most common mistakes?

• Keeping dealers and end users in one list; across 400 records you can no longer tell whose revenue is whose.
• Demanding sell-out data by mandate. A data request with nothing offered in return never works with any dealer.
• Leaving the lead rule verbal.
• Measuring dealer performance on revenue alone and ignoring payment behaviour.
• Outsourcing the end-user relationship entirely to the dealer: when the dealer changes, the market memory goes with them.

The hard part of a two-layer structure is not the design — it is producing the data. What was discussed on a given project, why the end user chose that product, which obstacle the dealer ran into: most of it stays inside phone calls. Closync extracts that from the conversations and writes it into the CRM, so a dealer network becomes a picture of the market you can plan against rather than a list of orders.