FlowsBook a callSign inCreate free accountSign up
Business and places data

Why the same business can appear twice in a list, and when it should

Overlapping searches, renamed shops, two listings for one building and companies hiring in several cities all make repeats. How to tell a true duplicate from two real places.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

A business appears twice in a list for one of a handful of reasons: two searches that overlap both found it, it is listed under an old and a new name, one building holds two listings for the same trade, or one company shows up once for each city or job it posts. Some repeats are true duplicates to merge; others are two genuine places that only look alike, such as two branches of a chain or a pharmacy inside a supermarket. The skill is telling the two apart before you merge.

This article is for anyone who builds lists of businesses for sales, research or operations. It names each way a repeat arises, gives a test for each, walks through a made-up list from Mexico City, and shows how a flow in xMap Flows keeps one of each item without losing real places.

Five ways one business becomes two rows

  • Overlapping searches. You search around each of your stores and two stores are 1 km apart: a cafe between them is found by both searches. This is the most common cause and the easiest to fix, because both rows are identical.
  • A change of name. A restaurant rebrands and both names stay listed for a while, with the same address and phone.
  • Two listings for one business. The owner listed it once as a bakery and once as a cafe, or a company listed its head office and its shop at the same door.
  • Your own table next to a search. Your customer file says "Panaderia Rosa" and the search says "Rosa Bakery". Same shop, written two ways.
  • One company, many postings. In job data, a firm hiring in three cities is three postings. For a sales list you want the company once.

When two rows are really two places

Merging too eagerly is as harmful as not merging. Keep both rows when:

  • They are branches of the same chain at different addresses. Same name, different places.
  • One business sits inside another: a pharmacy counter in a supermarket, a cafe in a bookshop, a bank branch in a mall. Same building, two businesses with their own customers.
  • Two different firms share a generic name, such as "City Dental", in different districts.

How to test a suspected repeat

  1. Same ID? Merge without a second thought.
  2. Same phone number? Compare digits only, ignoring spaces, brackets and the country code. A shared number is strong evidence of one business, unless it is a chain's central line.
  3. Same website? Compare the domain, without www or the page. Again, beware chains, whose branches share one site.
  4. Same name within a few dozen metres? Likely the same place. Same name 3 km apart: likely two branches.
  5. Still unsure? Keep both and mark them, rather than lose a real place.

A worked example from Mexico City

A made-up case; the rows and numbers are invented. A coffee equipment supplier in Mexico City builds a list of cafes around each of its five showrooms and adds its own customer table. The raw list has 412 rows.

What was foundRowsWhat to do
Same place found by two showroom searches58Merge: same ID
Customers that also appear in the search, spelled differently31Merge: same phone
Same name, different addresses (chain branches)24Keep all
Cafe and bakery listings at one address, one phone6Merge: same phone, keep the better rated
Cafes inside bookshops and hotels9Keep: separate businesses

Invented figures to show how each kind of repeat is handled.

After merging, the list holds 317 cafes, each once, and the 24 chain branches are still there for the rep who sells to chains. Had the supplier merged on name alone, those 24 branches would have collapsed into a handful of rows, and the sales team would have missed most of a chain's locations.

Mistakes that make it worse

  • Merging on name only. It collapses every branch of a chain into one row.
  • Merging on a chain's shared phone or website. Same problem through the back door. Check whether the number is a branch line or head office.
  • Deleting instead of merging. When two rows are the same place, keep the fields of both: one may have the website, the other the phone.
  • Cleaning once. A list that grows every week needs the same rules every week, or the repeats return.

How a flow keeps one of each

In xMap Flows several blocks deal with repeats, each at a different point:

  • When two blocks feed one block, items with exactly the same name and position are joined into one before the next block sees them.
  • Remove duplicates keeps one item when the same one arrives more than once in a run. You choose what makes two the same: the place's own ID (recommended), the name, the phone (compared by its last 9 digits), the website (compared without www or the page) or any field, and which to keep: the first, the best rated or the highest fit score. Items with nothing to compare are all kept.
  • Place classifier can merge places that came in twice, by the same place ID or the same name within 60 metres, keeping the fields of both, while it gives each place one clean category.
  • Only new works across runs: an item the flow found before does not come through again, so a daily email never repeats yesterday's places.

A typical order: My data and Nearby places both feed Remove duplicates set to Same phone, then Only new, then Email. What lands in the inbox is each business once, with the fields of the row that was kept. The templates Watch new competitors and Hotels and restaurants to supply, researched show these blocks in use.

Questions

What is the best field to match businesses on?

The place's own ID from the map it came from. Without one, a phone number compared by its digits is next best, then the website's domain. Names alone are the weakest, because of chains and generic names.

Will removing duplicates merge branches of a chain?

Not when you match on the place ID. Matching on name, or on a shared website or head-office phone, can. Choose the field with chains in mind.

Does Remove duplicates remember earlier runs?

No, it looks within one run. To skip items that earlier runs already found, add Only new.

What happens to a row with no phone or website?

If the field you match on is empty, the item is kept and never merged with other empty ones, so nothing is lost by accident.

Templates that do this

IndustriesB2B sales

Read next

More on business and places data · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.