How do you manage dealers, distributors and direct accounts in one CRM?

When we mapped a typical deal at Chauvet, a lighting manufacturer, the whiteboard filled up fast. There was the Chauvet rep. There was the dealer who'd sell the gear. There was the end customer. And there was a consultant who wrote the product into the spec before anyone else showed up.

Four parties, one deal. A basic CRM has a field for "company" and a field for "contact." That's it.

This is the most common problem I see at manufacturers. Not bad reps. Not bad products. A CRM built for a two-party sale, trying to hold a channel business with decades of relationships.

Why do dealers and distributors break a typical CRM?

Most CRMs assume one company buys from you directly. Channel sales have several companies on every deal, the same company playing different roles on different deals, and orders that land in the ERP under the distributor's name, not the end customer's. Without a model for that, reps fall back to spreadsheets.

Here's what usually goes wrong:

• Duplicates by role. The same distributor exists three times, once as a customer, once as a partner and once under a regional name.
• No hierarchy. A dealer with ten branches shows up as ten unrelated companies, so nobody sees the whole relationship.
• Invisible end customers. The order comes in through the distributor, so the venue, plant or contractor who actually uses your product never appears.
• Channel conflict. A direct rep and a dealer both chase the same project, and the customer gets two quotes.

A sheet metal fabricator we spoke with had 3 sister companies, each with its own sales team. They shared customers and never knew it, so cross-sell never happened. The fix wasn't a new tool. It was one shared view of who buys what, from whom.

What data model works for channel sales?

Use one record per real company, a type field that says what it is to you, a parent and child hierarchy for branches and locations, and deal roles for everyone involved. Key everything on ERP customer numbers. That model lets the same company be a dealer on one deal and a customer on another without duplicates.

The core pieces:

• Company type. Dealer, distributor, direct customer, end user, consultant or specifier. One company can carry more than one.
• Parent and child. The headquarters is the parent. Branches, plants and locations sit underneath. We used the same pattern for a freight broker; our answer on what a freight brokerage CRM should track shows it with shippers and their locations.
• Deal roles. On each deal, label who is the dealer, who is the end customer, who specified the product and which of your reps owns it. HubSpot calls these association labels; other CRMs have similar features.
• ERP keys. Every company carries its ERP customer number, so orders, quotes and pricing tie back to the right record.

How do you track a deal that runs through a dealer?

Create one deal and attach every party with a role: your rep, the dealer, the end customer and any consultant or specifier. Report on the deal from each angle. The dealer sees their pipeline, your channel manager sees all dealers, and leadership sees demand by end customer and region.

At Chauvet, the deal roles were rep, dealer, customer and consultant. Once they lived on the deal, the questions leadership cared about got easy to answer. Which consultants write us into specs? Which dealers close the projects we find? Which end customers keep coming back?

Pricing is the other half. At Chauvet, customer pricing lived in Sage, reps defaulted to the biggest discount they could and the approval rules lived with one manager. The first version of their quoting made any discount change go through an approval in the CRM. That one rule also made channel pricing visible: who got what price, through which dealer, approved by whom.

If you're earlier in the journey, start with our answer on how a manufacturer gets value from its first CRM. The data model here builds on it.

Who should own an account when several channels touch it?

Write down one owner per account and one rule for conflicts before you go live. A common pattern: direct reps own named strategic accounts, dealers own their territories, and a channel manager owns the dealer relationship itself. When a project touches both, the deal record shows who registered it first.

The rule matters more than which rule you pick. Without one, reps fight over accounts, dealers stop sharing projects and customers get confused. With one, the CRM settles the argument instead of a manager.

A few practical tips:

• Use deal registration. When a dealer brings a project, they register it, and the deal is theirs for a set period.
• Separate the relationship from the deal. The channel manager owns the dealer company. The dealer's rep owns their deals.
• Make it visible. Reps should see why an account is theirs, or someone else's, right on the record.

How do you see sales by channel and by end customer?

Bring order summaries from the ERP onto each company and deal, tagged with the channel they came through. Then report by dealer, by distributor, by direct rep and by end customer. You can't manage what you can only see in month-end exports.

At TASI Measurement, the operating companies ran on several different CRMs and an ERP, and the leaders wanted joined-up thinking across all of them. They also called the ERP quote history a treasure trove. That's true for most manufacturers. Years of quotes and orders already tell you which channels work, if you can see them in one place.

A flow meter manufacturer we spoke with had the opposite problem: quotes moved into the ERP and never came back to the CRM. Reps couldn't follow up on old quotes because they couldn't see them. Bringing quote and order summaries back onto the account fixed that, and turned old quotes into a follow-up list.

Before you connect anything, check your data. Our answer on how long a CRM audit should take explains how we find duplicates and gaps in days, not months.

How do you roll this out without breaking the channel?

Roll it out in phases: clean and type the company records first, then build the hierarchy, then add deal roles, then connect ERP data, then train reps and dealers on real deals. Each phase is useful on its own, so the team sees value before the full model is finished.

Two things I'd never skip:

• Test with real deals. Pull five recent deals that went through a dealer and rebuild them in the new model before go-live.
• Train on your own data. Dealers and reps learn faster when they see their own accounts on the screen.

And decide early who will run the model after go-live. Our answer on whether a manufacturer should hire a CRM admin or use a partner walks through that choice.

Frequently asked questions

Should dealers get their own login to our CRM?

Sometimes. A partner portal or limited dealer access helps when dealers register deals and share forecasts. Start without it: get your internal model right, then open a limited view. Giving dealers access to a messy CRM makes the mess public and makes them less likely to share projects with you.

How do we handle a company that is both a dealer and a customer?

Keep one company record and give it both types. Use deal roles to show what it was on each deal. That way you see the full relationship, including what they buy for themselves and what they resell, without duplicates that split the history across two records.

Do we need a separate pipeline for channel deals?

Often, yes. Channel deals usually move through steps like registration and dealer quote that direct deals skip. Two pipelines keep the stages honest and the forecast clean. Keep the stages few, and report across both so leadership sees total demand in one view.

What should we bring over from the ERP?

Start with summaries, not every transaction: last order date, what they buy, volume trend and open quotes. Key everything on the ERP customer number. Reps need the story of the account, not every invoice line, and summaries keep the CRM fast and easy to read.

Can one CRM handle several brands or sister companies?

Yes, with a business unit or brand field on companies and deals and clear rules on who sees what. That gives each sales team its own view while leadership sees shared customers and cross-sell openings across all of them.

Sources

• Chauvet, lighting manufacturer, 2026: deal roles for rep, dealer, customer and consultant, customer pricing in Sage, discount approvals held by one manager and a first version built on approval for any discount change.
• TASI Measurement, 2026: operating companies on several CRMs and an ERP, a goal of joined-up thinking and ERP quote history described as a treasure trove.
• RevOps Shop discovery work with manufacturers, 2026: a fabricator with 3 sister companies whose separate sales teams blocked cross-sell, and a flow meter manufacturer whose quotes moved into the ERP and never came back.
• Worldwide Logistics (WWL), 2026: parent company records with plants and distribution centers underneath, keyed on shipper IDs. See the WWL case study.
• HubSpot, Create and use association labels and Associate records.