What to look for in dealer management software

Dealer management software succeeds or fails on three things, and none of them appear in a product demonstration: whether the people at the far end of the channel will actually use it, whether it models how your dealers are really structured, and whether it can tell you what happened after dispatch. Everything else — dashboards, reports, mobile apps — is easier to build than any of those and gets far more airtime.

Here is what to ask about instead.

Will the dealer actually use it?

The question that decides the project, and the one most evaluations skip because the buyer is a manufacturer and the user is not.

A dealer has no obligation to adopt your system. They have their own business, their own counter, often several other brands, and no interest in maintaining data for your benefit. If your system asks them to do work that helps you and not them, it will be used for a month.

Ask a vendor: what does the dealer get out of this? If the honest answer is “visibility for you”, expect adoption to fail. Systems that survive give the dealer something they want — stock availability before they phone, order status without chasing, scheme balance without a claim conversation, credit position without asking.

Also ask: how many taps to place a repeat order? A dealer reordering the same items weekly should not be navigating a catalogue.

Does it model your channel as it actually is?

Most systems assume a clean hierarchy: manufacturer, distributor, dealer, customer. Real channels are messier.

• A dealer who buys direct for some products and through a distributor for others
• A sub-dealer who is not on your books at all but sells your product
• One owner with four counters under different names
• An architect who specifies but never transacts
• A contractor buying on a project account with different pricing

If the system cannot represent those, they get forced into whatever field is nearest and your reporting becomes fiction. Sketch your actual channel on paper before any demonstration and ask the vendor to model it live.

Can it see past dispatch?

Primary sales — what you dispatch to the channel — you already know. Secondary sales, what the dealer sells onward, is the number that tells you whether product is moving or sitting.

Most systems claim to capture it. The question is how, because every method has a cost.

Method	Accuracy	What it depends on
Dealer enters sales manually	Low	Dealer goodwill, which fades
Dealer’s billing system integrated	High	Their system having an interface, and their consent
Inferred from reorder patterns	Moderate	Regular ordering behaviour
Field team captures on visits	Moderate	Visit frequency and honesty
Scheme claims as a proxy	Partial	Only covers products in a scheme

There is no free method. Be suspicious of any vendor who presents secondary sales as a switch to turn on.

How does it handle schemes and claims?

In most building materials businesses this is not a feature, it is the commercial engine — and it is where packaged systems are weakest.

Ask whether scheme rules are configuration or code. If defining next quarter’s scheme requires the vendor, you will be waiting on them every quarter, forever. Schemes change constantly and the system has to keep up without a development cycle.

Ask what happens between earning and settlement. Calculating entitlement is the easy half. Claim submission, approval, dispute and payment reconciliation is where schemes lose money and dealer goodwill. A scheme that pays late is worse than no scheme, because the dealer stops believing the next one.

What should you ask that vendors do not expect?

• “Show me it working on a poor connection.” Your dealers are in basements and back-of-market shops.
• “Show me a dealer who left.” Not a reference customer — someone who stopped using it. What happened?
• “What percentage of dealers log in weekly?” Across their whole customer base, not their best account.
• “Who owns the data if we leave?” Ask before signing, not during the exit.
• “What does it connect to?” If it cannot exchange data with your ERP, someone will be re-keying.

The third question is the most revealing. Weekly active dealer percentage is the only honest measure of whether a dealer management system works, and very few vendors volunteer it.

What we built, and why

Sales360 came out of exactly these problems in the tile trade — dealer networks with no visibility past dispatch, architects who specify without buying, and schemes managed on spreadsheets. It is a working implementation rather than a reference design, which means we have also seen the parts that are hard.

If you are evaluating options, the questions above are worth asking us too.

Common questions

Should we build or buy?

It depends on how unusual your channel is and how much of the value sits in scheme logic specific to you. We have written a longer answer in build, buy or neither.

How long before we see anything useful?

Order capture and stock visibility can be useful quickly. Secondary sales reporting takes a few months of dealer usage before the data means anything, because early data reflects who adopted first rather than what the market is doing.

What if dealers refuse to use it?

Treat it as information rather than resistance. It usually means the system asks them to do work with no return. Making something genuinely useful to them — live stock, instant order status, visible scheme balance — works better than mandating adoption, which produces compliance data of no value.

Can we start with part of the network?

Yes, and it is usually wise. Choose a region with engaged dealers, get it working, then expand. A pilot that fails teaches you something cheaply; a national rollout that fails is expensive and hard to restart.

More on this: what to digitise first and why generic ERP breaks. For how we work with dealers, see distributors & dealers.