Building a Clean Retailer and Outlet List: Master Data for Nepali Distributors
Routes, credit, targets and visit proof all depend on one list of shops. Here is how to capture it properly, keep duplicates out and review it every month.
gamitrack team · · 6 min read
On this page
- Why master data is the quiet profit lever
- What to capture for every outlet
- Naming rules that prevent duplicates
- Capture the location properly
- Let the field propose and a manager approve
- A monthly clean-up routine
- An illustrative example
- Connect the list to the rest of the business
- A second example: one shop, three names
- Common mistakes
- Questions owners ask
- A five-minute duplicate check
- How GamiTrack handles outlets
- Key takeaways
Every promise a distribution business makes depends on one list: the list of shops. Routes are lists of shops. Credit limits are attached to shops. Targets are counted over shops. Visit proof compares a phone with a shop's position. If the list is messy, with the same shop under three names, wrong locations and closed shops still visited, every report built on it is wrong. This guide shows how to build and keep a clean retailer and outlet list in Nepal.
Why master data is the quiet profit lever
Most owners focus on the app, the scheme or the commission. But a mixed-up list causes silent costs:
- Salespeople waste time on closed or duplicate shops.
- Visit checks fail because the saved location is wrong, so honest visits look suspicious.
- Credit control fails when one shop has two accounts and each looks small.
- Reports of "active outlets" and coverage are inflated.
Good data is not exciting, but it makes everything else trustworthy.
What to capture for every outlet
| Field | Why it matters |
|---|---|
| Shop name as customers know it | Staff find it by search |
| Owner name | Who to talk to |
| Phone | Contact and duplicate check |
| District, municipality, ward and address | Reports by area |
| Outlet type (kirana, wholesaler, pharmacy, hotel, and so on) | Price lists and targets |
| PAN, if the shop has one | Invoicing needs |
| Map location | Visit proof and territories |
| Credit limit and credit days | Credit control |
| Supplying dealer | Who fulfils orders |
| Notes | Internal knowledge, such as best visiting time |
Do not collect fields you will never use. Every extra field is one more thing staff skip.
Naming rules that prevent duplicates
Write a naming rule and publish it. Example:
- Use the name painted on the signboard, in English or Nepali, but always the same script for the same company.
- Add the area after a dash, for example "Sharma Store - Kalanki".
- No abbreviations that only one person understands.
- Search by name and by phone before adding anything.
A phone number is often the best duplicate check, because one owner usually has one number.
Capture the location properly
The saved location is what visit proof is compared with. Capture it while standing at the shop door, with GPS switched on and after waiting a few seconds. A wrong point makes honest visits look like they happened away from the shop. If a point is wrong, correct it through a controlled change request rather than quietly editing it.
For territory work, see geofencing territories and regions and redesigning territories with real visit data.
Let the field propose and a manager approve
Salespeople find new shops first, so let them add outlets. But let a manager approve the new outlet and its location before it goes live. This single step keeps wrong locations and duplicates out, and it takes seconds per outlet.
A monthly clean-up routine
Set 30 minutes once a month and run this checklist:
- Pending outlets: approve or reject anything waiting.
- Duplicates: look for similar names, the same phone number or the same location.
- Closed or inactive shops: deactivate shops that have closed so they leave routes. Keep history.
- No orders for a long time: list shops with no order in a long period and decide whether to visit, re-activate or drop them.
- Wrong locations: check flagged visits, because many "away from outlet" flags come from a wrong saved point.
- Missing fields: fill in phone, ward, type and credit terms where they are blank.
An illustrative example
Invented numbers. A distributor with 1,200 outlets reviews the list. The review finds 45 duplicates, 60 closed shops and 80 shops with no order in the previous six months. After the clean-up the active list is about 1,050. Routes shrink, and the officers' strike rate improves because they stop visiting closed shops. Visit flags for "away from outlet" fall because 30 wrong locations were fixed. The numbers are only an illustration, but this pattern is very common when a list has never been reviewed.
Connect the list to the rest of the business
Clean outlets support retail outlet visit planning, dealer vs retailer price lists and field sales tracking. For shops that buy through dealers, see dealer and distributor management. If your list lives in Excel, moving from Excel and paper books explains how to bring it across.
A second example: one shop, three names
Illustrative case. A shop near a bus park appears in a distributor's list as "Ram Kirana", "Ram Kirana Store" and "Rama Store - Bus Park", added by three different salespeople in two years. Each entry has a small credit limit of NPR 20,000, and each carries a balance: NPR 14,000, NPR 18,000 and NPR 9,000. The owner is the same person with the same phone number.
Nobody sees a problem, because each account is under its limit. But the real exposure is NPR 41,000, double the intended limit of NPR 20,000. During the monthly review, a search by phone number shows the three entries. The manager keeps one, adds a note listing the old names, moves outstanding collection to a single plan, and deactivates the other two once their balances are settled.
| Before clean-up | After clean-up | |
|---|---|---|
| Entries for the shop | 3 | 1 |
| Total outstanding | NPR 41,000 across three accounts | NPR 41,000 on one account |
| Credit exposure visible | No | Yes |
| Visits per month | 3 salespeople, overlapping | 1 route, clear owner |
Duplicates do not just clutter the list. They hide credit risk.
Common mistakes
- Collecting too many fields. Staff skip them or enter junk.
- Letting anyone edit locations. Silent location changes break visit checks. Use a controlled request.
- No naming rule. "Ram Kirana" and "Ram Kirana Store" become two shops.
- Deleting instead of deactivating. You lose order and payment history. Deactivate closed shops.
- Never cleaning the list. Every month of delay makes the clean-up bigger.
- Letting the list live in several places. One in Excel, one in a notebook and one in the app means none is right.
Questions owners ask
Should wholesalers and retailers be in the same list?
Yes, as one list with a type. The type drives price lists and reports. See dealer vs retailer price lists and running a wholesaler business.
How do I classify outlets?
Start with a simple type, such as kirana, wholesaler, pharmacy, hotel or supermarket. You can add your own size grading later, based on real purchases, and use it to set visit frequency.
What do I do with a shop that changed owners?
Update the owner and phone number, keep the history, and add an internal note with the date of the change. Confirm any credit arrangement with the new owner in writing.
How do I move an Excel list into a system?
Clean it first: remove duplicates, fix phone numbers and add wards. Then load it in a batch and let salespeople correct locations on their first visit. See moving from Excel and paper books.
How many outlets should one salesperson cover?
It depends on visit frequency, shop density and travel time. Use route data from the first month to adjust, not a fixed rule. See retail outlet visit planning.
A five-minute duplicate check
- Sort or search the list by phone number and look for repeats.
- Search by the first word of the shop name.
- Look at shops that share a location on the map.
- Merge by keeping the oldest record, noting the other names, and deactivating the rest after balances are settled.
How GamiTrack handles outlets
In GamiTrack, every business is a party with a type (vendor, distributor, dealer, wholesaler or retailer), name, owner, phone, PAN, address, map location, credit limit, credit days and price list. A shop that buys through a dealer is linked with Supplied by. When a salesperson adds an outlet from the phone, it is saved as Pending approval and goes live only after a manager approves its location. Location changes also go through a request and approval, so the saved location is never changed silently. Parties can be deactivated and reactivated, and internal notes are visible to staff but not to dealers. See add parties and approve outlets and add an outlet from the phone. You can start a free trial.
Key takeaways
- Every route, credit limit and report depends on the outlet list.
- Capture a small set of useful fields and a correct location.
- Let the field propose and a manager approve.
- Review the list for 30 minutes every month.
Frequently asked questions
What details should I record for each retailer?
At minimum the shop name as customers know it, owner name, phone, address with district, municipality and ward, outlet type, PAN if applicable, the map location, credit terms and the supplying dealer if any.
How do I stop duplicate shops in my list?
Agree a naming rule, search before adding, and require a manager to approve new outlets. Run a monthly review that looks for similar names, same phone numbers and same locations.
Who should be allowed to add new outlets?
Let field staff propose them, because they find the shops, and let a manager approve before the outlet goes live. This keeps the list growing without letting wrong locations in.
How often should I clean the outlet list?
A short review every month works well: deactivate closed shops, merge duplicates, fix wrong locations and check shops with no orders for a long time.
Put this playbook to work
gamitrack gives your salespeople, delivery staff and dealers one app — and you one place to see sales and stock.