FlowsBook a callSign inCreate free accountSign up
Business and places data

How to keep a business list up to date without checking it by hand

Business lists go stale as places close, move, rename and change numbers. A weekly routine that rechecks every row, flags what changed and adds what is new.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

To keep a business list up to date, recheck every row on a schedule against a live source, record what changed since the last check (closed, renamed, new phone or website, moved), and add the businesses that appeared in your area since then. Done by hand this takes days and never happens; done by an AI employee it happens every week, and the list's owner only reads the handful of rows that changed.

This article is for anyone who owns a list that other people rely on: a distributor's outlet list, a bank's merchant list, a franchise's competitor file, a city directory, a sales team's accounts. It covers why lists decay, what a refresh should check, a worked example and the flow. It assumes the list is already clean; if it is full of duplicates and half-filled rows, clean it once first and then keep it that way.

Why a list that was right in January is wrong by June

A business list is a snapshot, and the businesses in it keep moving. In any city, every week, some places close, some open, some change hands and get a new name, some move to a bigger unit down the road, and many change a phone number or website without telling anyone. None of it is announced to you. The decay is quiet: a rep calls a number that no longer works, a delivery goes to an empty shop, a report counts a competitor that closed months ago.

The cost is not the bad rows themselves but the trust they cost. Once a sales team finds three dead numbers in a list, it stops using the list.

What a weekly refresh should check

For each row you already have, ask four questions:

  • Is it still open? A place that now shows as closed should be marked, not silently deleted, so you can see the history.
  • Is it still the same business? A new name at the same address often means a new owner, which for a supplier or a lender is a new relationship.
  • Can you still reach it? A new phone number or website, compared by the number's digits and the site's domain, not by how they are written.
  • Is its reputation moving? A rating that drops sharply is worth knowing about for a key account.

And for the area the list covers, one more: what is new here that is not on the list?

A worked example: a beverage distributor in Nairobi

The following is made up. A distributor of soft drinks keeps 600 retail outlets in Nairobi in six tables, one per delivery zone of about a hundred outlets: shops, kiosks, small supermarkets and restaurants. Its route planners build delivery days from that table. Every quarter someone was supposed to recheck it; nobody did.

The operations manager sets up two checks. The first runs each night on one zone's table, so every outlet is rechecked once a week; the second runs on Sunday night:

  1. The first takes each outlet in the table and looks it up on online maps by name near its position, then compares what comes back with what the flow saw last week.
  2. Only outlets that closed, changed name or address, or changed phone or website go on, each with a line saying what changed and the old value.
  3. Those rows are written back to the outlets table with the new values, and listed in an email to the manager.
  4. The second check searches Nairobi for the same kinds of shop, drops anything already in the table, keeps only places the flow has not seen before, and emails them as new outlets to visit.

Each morning brings a short email of outlets that changed in one zone, and Monday adds the week's new ones. The route planners use a table that was checked the night before.

How to do it with an AI employee

The recheck flow, block by block:

  1. Schedule: once a week at 22:00, on a different night for each zone's copy of the flow.
  2. My data: your list, uploaded as a table. Rows without a position get one from their address and city when you upload.
  3. Map business scan, Around each incoming place, Look for each place itself: each row looked up by its name near its position, with its current status, phone, website, rating and address. It looks up to 100 places a run, so split a bigger list into tables of that size and check each on its own day.
  4. What changed, watching Closed, Name or address, Phone or website, and Rating moved by 0.5.
  5. Save to my database, or a Google Sheets app block: the new values written back, the old ones kept in the change line.
  6. Email: the changed rows, with what changed.

And the add-new flow:

  1. Schedule and Area of interest: the area your list covers.
  2. Nearby places: the kinds of business on your list.
  3. Match with my table: your list, keeping only the places not found in it.
  4. Only new and Email: new businesses, each sent once.

The first real run of What changed only remembers: there is nothing to compare with yet, so expect an empty first email and real changes from the second week on. Templates that work this way: Changes at my key accounts, with what to do and Merchants at risk of leaving, every week.

Rules that keep a living list healthy

  • Never delete, mark. Add a status column: open, closed, moved, renamed. Closed rows are history your reports may need.
  • One owner, one table. Two copies of a list drift apart within a month. Let the flow write to one table and have everyone read from it.
  • Check the big rows more often. Key accounts can be rechecked daily in a smaller flow; the long tail weekly or monthly.
  • Watch the size of the change email. If it suddenly lists half the table, something upstream changed, such as a renamed column. Look before you write back.

A list that updates itself becomes something different: not a file someone owns, but a record of how a market moves, week by week, which is useful in its own right.

Questions

How often should a business list be refreshed?

Weekly suits most sales and distribution lists. Key accounts can be checked daily; a reference list used for an annual plan can be monthly.

Will rechecking every row find businesses that moved?

Often, when the business kept its name and moved nearby: the address comes back different. A business that moved far or renamed itself may not be found near its old position and shows as no match, which is worth a call.

What happens to rows the lookup cannot find?

They stay in your table. The flow reports what it found; a row with no match is a reason to check by phone, not proof that the business has gone.

Does it work for lists outside one country?

Yes. The lookups and the places database cover most of the world, so one table can hold outlets in several countries.

Templates that do this

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.