FlowsBook a callSign inCreate free accountSign up
AI employees and automation

An AI employee that checks your store list once a month

Branches and stockists close, move, change phone or slip in ratings. How to give one AI employee the monthly job of checking every store and reporting what moved.

Part of the guide AI employees

By the xMap team · · 5 min read

An AI employee that checks your store list each month takes every store on your list, looks it up again on the map by its name near its address, compares what it finds with last month, and sends you only the stores where something changed: closed or closed for now, a new address, a new phone or website, a different name, or a rating that moved by more than you set. Stores that did not change stay out of the report. You get a short, dated list of what to fix, not a spreadsheet to read.

This is for retail and franchise operations teams, brand managers whose products sit in other people's shops, and anyone who publishes a store locator or a list of branches. It describes the job in the terms of an employee (what it works on, when, what it is good at, where it reports), a made-up first month for a cosmetics brand, the settings worth getting right, the mistakes, and what to do with what it finds.

Why a store list needs a monthly check

A list of stores is correct on the day it is made. After that, a franchisee moves to a bigger unit, a stockist closes for good, a mall store closes for a refit, a branch changes its phone line, or a shop is sold and renamed. Each change breaks something: a store locator that sends customers to a shut door, a delivery that goes to an empty unit, a field rep who drives to the wrong street, an account manager who does not know a key stockist's rating has fallen. Nobody notices until a customer complains.

The job description

  • Works on: your store list, from a table in My data or a Google Sheets file the team already keeps.
  • When: once a month, on the first working day, early in the morning.
  • Good at: finding each store again by its name near its address and noticing what changed: status, address, phone, website, name and rating.
  • Reports to: the operations lead by email, with a copy as a PDF for the monthly review, and a note in the Team inbox.

A made-up first month for a cosmetics brand

Everything here is invented to show what the report looks like. Say a cosmetics brand sells through 120 independent stockists in Toronto, Lyon and Seoul and lists them all on its store locator.

The first run only looks: it finds each store and remembers what it saw. Nothing is reported, because there is nothing to compare with yet. The second run, a month later, sends this:

Stockist (made up)What changedSuggested action
A beauty shop in LyonClosedRemove from the locator; ask the rep about the stock
A pharmacy in TorontoNew address, 300 m awayUpdate the locator
A boutique in SeoulRating 4.6 to 4.1Account manager to visit
A salon in TorontoNew website and nameCheck if the new owner still stocks the brand

Invented example for illustration only.

Four of 120 changed. The operations lead fixes the locator in ten minutes, the Seoul account manager books a visit, and the rep in Toronto calls the renamed salon. The other 116 stores are not in the report at all.

Settings worth getting right

  • The rating threshold. In What changed, a move of 0.3 catches a drop from 4.6 to 4.3. Smaller and you will chase noise; larger and you will miss a slow slide.
  • Names and phones on the list. The lookup uses each store's name near its position. Short, common names can match the wrong shop next door; a phone number on each row helps you confirm the match.
  • New stores. Leave the setting that sends new stores off, so a store added to the list this month is only remembered, not reported as a change.
  • How much it does alone. Set it to Act and tell me: it sends the report and tells you it did. It changes nothing on your website by itself.

Mistakes to avoid

  • Running it daily. Store details move slowly. Monthly is enough for a locator; weekly suits a sales list with many small accounts.
  • Deleting a store the moment it shows closed. "Closed for now" is often a refit or a holiday. Check before you remove it.
  • Treating a rating drop as a verdict. A fall from 4.6 to 4.1 is a reason to look, not proof of bad service.
  • Letting the list rot. If you never write the fixes back to the source table, the same changes come back every month.

How to build it

In xMap Flows the employee is a flow of six blocks:

  1. Schedule: every month, on the first Monday, at 07:00.
  2. My data: your store list, with names, addresses and positions.
  3. Map business scan: around each incoming place, each place itself, adding the current address, phone, website, rating and status.
  4. What changed: closed, rating, phone or website, name or address.
  5. xMap LLM: one suggested action per change, in a few words, using only the change line.
  6. Make a report: the changed stores as a PDF, emailed to the operations lead.

On a month when nothing changed, the employee says so in one line. The Stockists that closed or moved, off the store locator template is this employee ready to hire, and What opens near my stores adds a second job: new rivals opening around each of your stores. You can rename the employee, for example Store list checker, so the team knows what it does.

Questions

How does the AI employee know a store changed?

It finds each store again on the map every month and compares the status, address, phone, website, name and rating with what it saw the month before. Only stores that differ are reported.

Will it update my store locator by itself?

No. It reports what changed and suggests an action. A person decides and makes the change, unless you build a further step that writes to your own system.

What happens on the first run?

It only looks and remembers each store. Changes are reported from the second run, once there is something to compare with.

How often should it run?

Monthly suits a store locator or branch list. A long list of small sales accounts that change faster may need a weekly check.

Templates that do this

Read next

More on ai employees and automation · 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.