How to track secondary sales when all you can see is dispatch

There is no reliable free method of capturing secondary sales. Every approach costs something — dealer goodwill, integration effort, accuracy, or all three — and any vendor presenting it as a feature you switch on has not run one. The practical question is not how to get perfect data but which imperfect method your channel will actually sustain.

Start by being clear about why you want it, because that determines how accurate it needs to be.

What does secondary sales data actually tell you?

Primary sales — what you dispatch — measures what you pushed into the channel. It can look healthy while product sits in dealer godowns for months.

Secondary sales measures what the channel sold onward. The gap between the two is inventory sitting in the network, and that gap is where several expensive surprises live:

• A scheme that looks successful because dealers loaded up to claim it, and then bought nothing for a quarter.
• A product you believe is selling that is actually stuck at three large dealers.
• Production planned against dispatch rather than demand, so you build the wrong things.
• A region that appears strong because one distributor is stockpiling.

None of those are visible from your own invoices.

What are the actual options?

Method	Accuracy	What it costs you	Where it fails
Dealer enters sales in your portal	Low to moderate	Dealer goodwill	Enthusiasm fades after the first month
Integrate with the dealer’s billing system	High	Integration work, per system	Small dealers have no system to integrate
Field team captures on visits	Moderate	Visit time, honesty	Reflects visit frequency, not sales
Infer from reorder patterns	Moderate	Nothing	Breaks when dealers buy irregularly
Scheme claims as proxy	Partial	Nothing extra	Only covers products in a scheme
Warranty or QR registration by end customer	Low coverage, high accuracy	Incentive cost	Only products customers bother to register

Most working systems combine two or three. Integration with your largest dealers, who carry most of the volume and usually have billing software, plus inference for the long tail who do not.

Why does dealer-entered data always decay?

Because it asks a dealer to do work that helps you and not them.

A dealer entering their sales into your portal is doing data entry for a manufacturer’s benefit, on top of running their own counter. It happens during the launch, when someone from your team is calling weekly. It stops when the calls stop.

The way round this is not enforcement, it is exchange. If the same screen where they report sales also shows their scheme balance, their credit position, live stock availability and their order status, the visit has a reason. The reporting becomes a by-product of something they wanted to do anyway.

The test: if you removed the sales-entry field entirely, would dealers still open your portal weekly? If not, the reporting will not survive either.

How accurate does it need to be?

Less accurate than most people assume, provided it is consistent.

If you are using secondary sales to decide production volumes, direction and trend matter more than precision. Knowing that a product is moving three times faster in one region than another is actionable even if both numbers are understated by a fifth — as long as they are understated by roughly the same fifth.

Where precision does matter is scheme settlement, because dealers will dispute it. Do not use inferred data to calculate money owed. Use it for planning, and settle schemes against primary invoices or verified claims.

Confusing those two uses is the most common way a secondary sales programme loses dealer trust.

How should you start?

1. Decide what decision the data will change. If you cannot name one, do not collect it — you will build a report nobody opens.
2. Start with your top dealers. A minority usually carry most of the volume. Integrating twenty is a project; integrating six hundred is not.
3. Give before you ask. Ship the stock visibility and order status first, and add reporting once dealers are using it.
4. Accept partial coverage. Sixty per cent of the channel reporting consistently is worth far more than a mandate that produces fabricated numbers from everyone.
5. Measure adoption weekly from the start, so you see decay while it is still fixable.

This is the problem Sales360 was originally built around, in a tile network where dispatch was the only visible number.

Common questions

Can we make secondary sales reporting mandatory?

You can require it as a condition of a scheme or a credit term. Expect compliance data rather than accurate data — dealers will enter something to stay eligible. Mandates produce coverage; usefulness comes from giving them a reason.

What about dealers with no computer at all?

Common in this trade, and worth designing for rather than treating as an exception. WhatsApp-based reporting or field team capture works where a portal will not. Do not build for the dealers you wish you had.

Will dealers see this as surveillance?

Some will, particularly if they suspect you are assessing whether to appoint someone nearby. Being straightforward about what you use the data for helps more than pretending the question is not being asked.

How long before the data is useful?

Several months. Early data reflects who adopted first rather than what the market is doing, and reading it as market signal in month one produces confident wrong conclusions.

More on this: the scheme settlement problem and why your dealers do not use the app. For how we work with the channel, see distributors & dealers.