Field Sales Tracking in Nepal: A Practical Guide for Owners and Sales Managers

Every distributor in Nepal knows the feeling. Your salesperson says he visited forty shops in Birgunj today. The order book has eleven orders. Did he really go? Did he skip the far shops? Did the shopkeeper say no, or was nobody asked? Without a record, you are left guessing, and guessing is a poor way to run a team of ten, let alone fifty.

Field sales tracking is the practice of recording where your salespeople go, what they do there, and what came out of it. Done well, it is not about spying. It is about replacing opinions with a shared record that is fair to the strong performers and honest about the weak ones.

This guide covers what to track, how to set it up, and the mistakes that make teams resent the whole idea.

What "field sales tracking" actually means

It is more than a dot on a map. A practical tracking set-up answers five questions every day:

1. Did the person start work, and when? Day start and day end, with location.
2. Where did they go? A route or a list of shops visited.
3. Were they really at the shop? A check-in at the outlet's location, ideally with a photo.
4. What happened? Order taken, payment collected, or a reason for no order.
5. What did it produce? Orders, kilograms or units, and money collected.

If you can answer those five without phoning anyone, you have tracking. If you need a WhatsApp message to find out, you do not.

The four building blocks

1. A clean outlet master list

Tracking is only as good as the list of shops behind it. Each outlet needs a name, owner, phone number, type (kirana, wholesaler, hotel, pharmacy), region and a saved GPS location. Without a saved location, nobody can prove a visit happened at the right door.

A common problem: salespeople add outlets themselves, sometimes duplicates, sometimes at the wrong place. A simple approval step, where a manager confirms a new outlet and its location before it goes live, keeps the list clean.

2. Routes (beats) that people actually follow

A route is an ordered list of outlets for a day. Without it, visits depend on the salesperson's mood and the weather. With it, you can compare plan against actual. See our guide to retail outlet visit planning for how to build them.

3. Check-in proof

A visit should be recorded when the salesperson is physically at the outlet. Two signals make that credible:

• Location match: the phone's GPS is within a reasonable radius of the saved outlet location.
• Photo proof: a quick shop-front or shelf photo, time-stamped.

Neither is perfect. GPS drifts between tall buildings in Kathmandu or Lalitpur, and photos can be reused. Together, and combined with the other signals below, they make fake visits hard and obvious.

4. Outcome capture

Every visit ends with a result. Order, payment, closing stock noted, or a no-order reason such as "owner away", "has stock", "credit blocked". The no-order reason is gold: after a month you can see why shops are not buying, which is often a pricing or credit problem, not a salesperson problem.

A sample day, from the owner's side

Here is what a tracked day can look like for a salesperson covering the Kalanki to Balaju belt:

Time	Event	What the manager sees
8:40	Day start	Location and time, late or on time
9:15	Visit 1, kirana	Check-in, photo, order for 18 kg
9:50	Visit 2, wholesaler	Check-in, payment collected by Fonepay QR
11:30	Visit 3	No order: "has stock", closing stock noted
13:00	Gap	Time between visits visible
17:30	Day end	Calls made, productive calls, kilograms sold

You can read that in two minutes. No calls, no arguments.

Setting it up in five steps

1. Clean the outlet list first. Import what you have, add missing locations, and remove duplicates.
2. Define regions and routes. Group outlets by area and assign them to people.
3. Decide the proof rules. For example: GPS within the shop radius, one storefront photo per visit, a no-order reason mandatory.
4. Write a one-page policy. Say what is tracked (working hours only), who sees it, and how it is used. Share it before launch.
5. Pilot with 3 to 5 people. Fix route and list problems, then roll out to everyone.

What to review, and how often

Do not stare at the live map all day. Use a rhythm:

• Daily (5 minutes): who started late, who has no visits, who has flags.
• Weekly (30 minutes): visits per day, productive calls, route coverage, top no-order reasons.
• Monthly: targets against achievement, outstanding collections, and a one-to-one with each salesperson. See monthly sales reports per agent.

For the integrity side, read stopping fake visits.

Mistakes that sink tracking projects

• Tracking without telling people. It destroys trust the first time someone finds out. Be open.
• Tracking outside working hours. Limit it to the working day.
• Using it only to punish. If the only message is "we caught you", good people leave. Use the data to recognise good work and fix problems early.
• Ignoring terrain. A shop up a hillside in Kavre takes longer than a roadside shop in Chitwan. Set expectations by region.
• Collecting data nobody reads. Decide in advance which three numbers you will act on.

Offline and low-signal areas

Nepal's coverage is uneven. A tool that needs constant data will fail on exactly the routes where you most need proof. Insist that the location trail is stored on the phone and uploaded once a signal returns, that the app fails loudly rather than silently when an order or visit cannot be saved, and that staff know to enter such work as soon as they reach coverage.

Getting buy-in from the team

The first week decides whether tracking is accepted. A few practical moves help:

• Hold a short meeting before launch. Explain the problems you want to solve: unfair comparisons, lost orders, late payments. Show a screen and say exactly what is and is not recorded.
• Ask for the team's pain points. Salespeople often have good ideas about broken routes or shops with wrong locations. Fixing those first earns trust.
• Show the upside. Accurate records protect honest staff when a shopkeeper claims nobody visited, and they speed up expense and commission checks.
• Pick champions. One respected senior person who uses the app well persuades more than any memo.
• Be patient with the first month. Expect forgotten check-ins and photo mistakes. Coach, do not punish.

Measuring whether tracking is working

After a month or two, ask whether the picture has improved. Useful before-and-after questions:

1. Do we know how many visits happened per day, by person?
2. Has the share of visits that produce an order changed?
3. Are overdue balances shrinking?
4. Are disputes about whether a visit happened less frequent?
5. Is the manager spending less time chasing information by phone?

If the answers are yes, keep going. If not, check whether the routes, outlet locations or targets are the real problem rather than the people.

A note on the Terai and the hills

Field conditions differ so much across Nepal that a single rule rarely fits. A Terai highway town offers fast travel and good signal; a hill route in Sindhupalchok might have a two-hour walk between two shops. Set expectations by region, give wider location radii where GPS is weaker, and accept that visits per day will differ. Comparing a hill officer to a valley officer on visits alone is unfair; compare each with their own plan and history.

How gamitrack handles it

gamitrack's field app starts with a day start and day end, each with GPS. Routes list the stops in order. At each outlet the salesperson checks in; the app checks the position against the saved outlet geofence and asks for a photo that goes to secure storage. The visit ends with an order, a payment, closing stock or a no-order reason. Background location during the working day queues offline and syncs later. Managers see a day movement map, store visits with time spent, and flags such as outside geofence, short visit or missing photo, with a daily integrity score. New outlets need approval before they go live.

If you want to see how this fits your own routes, start a free trial and add one team to try it. Industry-specific set-ups are described for masala and spices and FMCG and packaged food.

Key takeaways

• Tracking is a shared record, not surveillance. Say so and write it down.
• Clean outlet locations and routes come first, technology second.
• Combine GPS, photos and outcomes; no single signal is enough.
• Review a few numbers on a regular rhythm instead of watching a map all day.