Dealer directory data is wrong in more places than one

One dealer, six copies

A dealer is not one listing. It is a set of copies, each maintained by a different party for a different purpose, and each aging at its own rate.

• The manufacturer's dealer locator: authorized lines, certified service, showroom and parts departments. Owned by the manufacturer, refreshed from its dealer master on its schedule.
• The distributor's portal or branch list: account status, territory, which branch serves the dealer. Owned by the distributor.
• Aggregator and data-supplier feeds: name, address, phone and categories, copied onward into dozens of smaller directories.
• Map and search listings: hours, departments, photos, phone routing. Owned by whoever claimed the listing, and editable by the public.
• Inventory and marketplace syndication: what is on the lot or the shelf, pushed out by the dealer management system.
• The dealer's own website: the version the dealer controls and updates last.

What actually goes wrong

The visible errors are address and phone. The costly ones are structural.

• A brand the dealer dropped two years ago is still listed as an authorized line, so a buyer is sent for a product the store cannot sell or service.
• Parts and service are described as one department when they are two, with different hours, phones and ordering rules.
• A relocated location appears twice, once at each address, each with its own history.
• A certified-service designation lapses at the manufacturer and persists everywhere downstream.
• A territory change at the distributor is reflected in the portal and nowhere else.

Why corrections do not stick

Correcting a downstream copy fixes it until the upstream source refreshes it. Aggregators pull from suppliers who pull from each other, so the same wrong value arrives again from a different direction. Each source has its own claim process, its own owner and its own review cycle, and none of them knows that the others exist.

The deeper problem is that no copy says it is the authority. A directory rarely records where a value came from, who confirmed it or when. Without that, a correction is an opinion competing with other opinions.

What an assistant does with the disagreement

An AI assistant asked which dealer carries a line, or where to buy a part near a job site, reads several of these copies and has to choose. It has no way to tell which is current unless the sources carry dates and an order of authority. In practice it weighs agreement, prominence and recency, which favors the copy repeated in the most places, not the copy that is right.

That makes directory errors worse than they were. A wrong listing used to misdirect the person who found it. Now it can become the answer a system gives to everyone who asks.

The record that sets the order

The fix is not another directory. It is one checked record of the dealer's facts in which every value carries its source, the person who confirmed it and the date, and in which each kind of fact has a named owner.

• The manufacturer owns authorizations and certifications.
• The distributor owns territory, account status and branch assignment.
• The dealer owns hours, departments, staff and what is physically on hand.
• A change at the owner updates the record. The record publishes to every feed, and a comparison runs against what each downstream copy currently says.

What a comparison shows

The useful output of that comparison is a list of disagreements ranked by who can fix them: values the dealer can correct today, values only the manufacturer can correct, and values that are wrong because a feed is stale. That is how a directory problem becomes an operational queue instead of a recurring surprise.

Lehvel builds this record and runs the comparison. The method is described in Business Truth and in Lehvel's product information chain study.

Questions