Zip code boundaries vs. county boundaries for dealer territories

Every territory redraw starts with the same argument in the room: zip code or county line. It looks like a formatting choice, but it decides what "whitespace" even means once you go looking for it later.

County boundaries: stable, coarse, political

County lines don't move. They match census data, DMV registration pulls, and most public demand datasets you'll ever buy, so year-over-year reporting stays clean. The tradeoff shows up fast in any county with a real city in it: a dense urban core, a ring of suburbs, and forty miles of farmland can all sit inside one county, assigned to one dealer. Demand inside that boundary is never flat, but the line treats it like it is. A dealer parked in the low-density corner of the county gets credit for volume he never touches, while a fast-growing suburb on the far side waits years for anyone to notice it's underserved.

Counties also vary wildly in size by region. A county in Texas and a county in New England aren't really the same unit of measure, even though both get labeled "county," which makes a national territory map built purely on county lines harder to compare region to region than it looks on paper.

Zip code boundaries: granular, unstable, commercial

Zip codes track population and commerce more closely, because they were drawn around mail delivery density rather than political history. Carving territory at the zip level lets you follow a growing suburb or pull a half-built-out corridor out of a dealer's patch without touching the rest of the county. That resolution is the whole appeal.

It's also the whole cost. USPS splits, merges, and retires zip codes on its own schedule, not yours, so a territory map built on zip lines needs upkeep or it drifts out of date. Zip codes were never meant to describe trade areas either. A boundary drawn to route mail carriers doesn't care where a customer drives to buy or service equipment, and in rural zip codes that gap can be a long one.

Trade area definition is the real question

The boundary type is a stand-in for a harder question: what trade area does a customer travel out of to reach a dealer? In metro markets that distance is short, and zip-level granularity earns its upkeep cost. In rural and exurban territory, drive time matters more than either boundary, and a county-sized unit is often close enough to reality that the added precision of zip lines doesn't change the answer.

Most networks end up mixing units: county-level territory in low-density regions, zip-level carve-outs around metro dealers, drive-time rings to sanity-check both. That mix matches the unit of measure to how customers actually behave in that part of the map.

Where the boundary stops being the problem

A territory map, drawn at any resolution, only shows you the lines you already own. It can't show you the new construction site outside the line, or the fleet of equipment now running in a county that's had the same dealer assignment since 1994. That's a separate layer, built from what's on the ground rather than from how the map was carved.

If you're about to redraw lines anyway, it's worth seeing where the demand sits first.