What is dealer point density and why OEMs track it

Dealer point density is a count. It's the number of dealer points an OEM has operating inside a defined market, usually a PMA, a DMA, or a state, divided by some measure of the demand underneath it: registered households, registered units in operation, or population. The result is a ratio you can compare market to market, region to region, year to year.

Most network planning teams track it because it's the fastest way to answer a question a GM or a board member will eventually ask: are we over-dealered in one market and thin in another? A single dealer count by itself doesn't answer that. Ten dealer points in a dense metro and ten in a rural multi-county PMA are not the same network posture, and point density is the quick normalization that makes the two comparable.

How the ratio actually gets built

The formula itself is simple. Points per market, usually expressed as dealer points per 100,000 registered units or per 10,000 households depending on the category. What takes the work is the denominator. OEM network planners pull registration data, Census or county-level population figures, sometimes a third-party market sizing report, and build a market-by-market table. Then they lay the current dealer footprint on top of it.

The output is a benchmark, not a verdict. A market running at 0.8 points per 10,000 units against a national average of 1.4 looks thin on paper. It might be thin because the OEM has underinvested there. It might also be thin because the demand in that market is concentrated in three counties out of twelve, and the other nine are genuinely empty of anything worth a rooftop. The ratio flags the market. It doesn't tell you where inside the market the opportunity sits, or whether there's a dealer-shaped gap at all once you account for where the units, fleets, or job sites really are.

Why the number alone runs out of road

This is where a lot of network density benchmarks stall out. A channel manager pulls the ranked list, sees which PMAs sit below the national average, and now has to decide: add a point, consolidate two underperforming points into one stronger location, or leave it alone and revisit next cycle. The density ratio can't make that call, because it was built from registration and population data that's often a year or two stale and doesn't show which sub-areas of a thin market carry real demand today.

That's the gap between "this market is below benchmark" and "this specific unincorporated county, this stretch of industrial corridor, this fleet depot cluster, has real activity and no dealer within a reasonable service radius." Density tells you where to look. It doesn't tell you what you'd find once you looked.

Some OEM teams close that gap by layering fresh site counts and fleet activity directly onto their existing dealer boundaries, once a year, so the low-density markets on the spreadsheet get checked against what's on the ground before anyone signs off on adding or pulling a point. Whitespace Mapping does exactly that: it overlays discovered sites and detected fleet density onto your territory map so a below-benchmark market shows you where the demand sits, not just that the ratio looks low.

Point density is still the right first screen. It's cheap to calculate, easy to rank, and every network planning meeting already speaks that language. A low ratio only tells you where to start asking the next question.

If you've already got a list of under-benchmark markets and want to see what's sitting in them before the next territory review, that's the exact overlay this site builds.