How wholesalers tell lapsed customers that closed from ones that left
An account that stopped ordering may have closed, moved or gone to a rival. Checking each lapsed shop on the map tells sales and credit control which it is.
Part of the guide Workflow automation
A wholesaler can tell a lapsed customer that closed from one that simply stopped buying by looking each lapsed account up on the map and reading its status. If the shop now shows as closed, credit control should stop the account and reps can stop calling. If it shows as open at the same address, the customer is still trading and buying from someone else, which is a sales problem worth a visit. If it appears at a new address, it moved, and the delivery route needs updating.
This is for sales directors, credit controllers and route planners at cash and carry businesses, food and drink distributors and specialist wholesalers. It explains why lapsed accounts need sorting, how to sort them, a made-up example, and an AI employee that does it every week.
Why a lapsed account is three different problems
Your ordering system knows which accounts have not bought for six or eight weeks. It does not know why. Lumping them together leads to the wrong action every time: reps phone shops that no longer exist, credit control keeps lines open for businesses that shut, and the customers who quietly moved to a competitor get the same generic 'we miss you' email as the ones who closed.
- Closed. Stop deliveries, review the balance, remove the account from routes. Note who supplies the shop that replaces it, if one opens.
- Moved. Update the address, re-plan the route, and treat it as a warm customer.
- Still open, still trading. The real lost sale. A rep visit, a price check, or a question about service usually explains it.
How to sort lapsed accounts, step by step
- Pull the accounts with no order in the last six weeks from your system, with name, address and phone. Database query can read them straight from a PostgreSQL, BigQuery or Snowflake database, or upload them as a table in My data.
- Look each one up on online maps by its name near its address with Map business scan, set to Each place itself. Each account comes back with its status, address, phone, website and rating as the map shows them today.
- Split them with a Branch: closed or closed for now on one side, open on the other.
- Compare the found address and phone with yours. A different address on a match with the same name and phone usually means it moved.
- Hand each group to the right team: closed to credit control, moved to route planning, open to the rep.
A worked example (made up)
Say a made-up beverage wholesaler in Johannesburg has 2,400 active accounts. This week 96 have gone six weeks without an order. Looked up one by one, they split like this. The numbers are invented to show the method.
| Group | Accounts | What the map shows | Who acts |
|---|---|---|---|
| Closed | 21 | Closed, or closed for now | Credit control stops the lines and chases 4 balances |
| Moved | 7 | Same name and phone, new address | Route planning updates the stops |
| Open at the same address | 61 | Trading, recent reviews | Reps visit the 15 biggest first |
| Not found | 7 | No confident match | A phone call from the office |
A made-up weekly split for an imaginary wholesaler.
Most of the lapsed list is still trading. That is the uncomfortable but useful answer: the wholesaler has a retention problem, not a closure problem, and the reps now know which 61 doors to knock on. The 21 closures save the drivers wasted stops and give credit control a short, specific list.
Mistakes to avoid
- Writing off on the map alone. A status can lag reality by days or weeks. Call before you close an account with a large balance.
- Treating closed for now as closed. Renovations, holidays and seasonal shops show up this way. Hold the account and check again in a month.
- Checking only lapsed accounts. Customers who still order sometimes move. A monthly check of your best accounts catches a move before the driver does.
- Sending the whole list to every rep. Each rep needs their own territory's open accounts, ranked by what they used to buy.
- Forgetting the replacement. When a closed shop's unit reopens as a new business, it is a new prospect on a route you already drive.
How to do it with an AI employee
An AI employee in xMap Flows can sort the lapsed list every Monday before the sales meeting.
- A Schedule runs every Monday at 06:00.
- Database query reads accounts with no order in six weeks, at most 100 a run, oldest lapse first.
- Map business scan looks each one up as Each place itself.
- A Branch sends closed accounts one way and open ones the other.
- xMap LLM writes what to do with each: stop the line, update the address, or visit, with the reason in a sentence.
- Two Emails go out: the closed and moved ones to credit control and planning, the open ones to the sales team, grouped by rep.
For your whole customer base, a second employee with What changed set to Closed and Name or address checks every account monthly and only passes on the ones whose details changed, so closures surface before the orders stop.
Questions
How long without an order counts as lapsed?
It depends on how often your customers usually buy. Twice their normal ordering interval is a sensible line: six weeks for weekly buyers, three months for monthly ones.
Can the map status be wrong?
Yes, it can lag by days or weeks, and closed for now covers renovations and holidays. Call before closing an account with money owed.
How many accounts can be checked at once?
Map business scan looks up to 100 places a run, so larger lists are checked in batches over several runs.
Can it tell which competitor took the customer?
No. It tells you the shop is still trading. Which supplier it now uses is a question for the rep's visit.