Duplicate business entities across dealer networks

How one location becomes several

Duplicates are rarely a data-entry mistake. They are the natural result of systems that each mint their own identifier for the same place.

• A change of ownership or a rebrand creates a new dealer record while the old one stays active in feeds.
• A relocation creates a record at the new address without retiring the old one.
• A parts counter and a showroom are entered as two locations in one system and one in another.
• A distributor account number, a manufacturer dealer code and a map listing identifier are never mapped to each other.
• An acquisition merges two companies' systems without merging their records.

What a machine does with duplicates

Each record carries its own partial facts. One has the right phone and an old address. Another has the new address and no hours. A third has the services but the former brand. A system that cannot tell they describe one place will present them as alternatives, merge fields across them, or favor the one with the most inbound references, which is usually the oldest.

The failure is not a wrong value. It is a wrong count and a wrong history: the assistant lists two stores where there is one, and attaches the old store's lapsed authorization to the new store's address.

Entity resolution is a decision, not a match

Matching names and addresses finds candidates. Deciding that two records are the same place is a judgment with consequences, because merging deletes the independent history of one of them. The judgment needs evidence: a shared legal entity, a continuous phone number, a documented relocation, a date.

The result should be recorded, not just executed. A canonical record states which identifiers it absorbs, why, on whose confirmation and when. Without that, a later feed re-creates the duplicate and nobody can say why it was merged.

The canonical record

The durable fix is a single canonical record per physical location and per legal entity, with a mapping table from every external identifier (manufacturer dealer code, distributor account, map listing, aggregator ids) to that record. Every outbound feed publishes the canonical values. Every inbound copy is reconciled against it.

A retired identifier is not deleted. It is marked retired, with the date and the canonical record that replaced it, so a feed that still carries it can be recognized as stale.

Where to look first

Start with locations that changed: acquisitions, relocations, rebrands and lines added or dropped in the last several years. That is where the duplicates are. Compare each against the identifiers present in the manufacturer locator, the distributor portal and the main map listing, and list the ones that map to more than one record.

Questions