A sales team that works in the field is hard to see. The owner sits in an office in Kathmandu, Pokhara or Biratnagar while ten or thirty people spread across districts, visit shops, take orders and collect money. What the owner knows about that work comes from a phone call, a paper book or a spreadsheet filled in at the end of the month. Sales force automation, often shortened to SFA, is the name for software that closes that gap. This page explains what a field sales app for Nepal should do and how gamitrack does it.
The problem with running a field team on paper
Most Nepali production and distribution companies start with the same tools: a printed order book, a notebook of udhaaro, and phone calls to the office. These tools are cheap and familiar, and they work while the team is small. They stop working when the team grows or the territory spreads.
Visits are reported from memory. A salesperson says they covered twelve shops; nobody can check. Orders arrive in the evening, by chat or at the next morning's meeting, so the warehouse plans a day late. Collections are written in a book that only the salesperson reads. Commission is argued over at month end because nobody agrees on what was sold, to whom, and when. A new salesperson spends weeks learning the beat from a colleague who may be about to leave.
None of this is dishonesty. It is the cost of having no shared, time-stamped record of field work.
What sales force automation software must do
When you compare options, check for these basics rather than a long feature list:
- A mobile app that staff can use with little training, in Nepali as well as English.
- Route or beat plans with ordered shops, and a way to start and end the working day.
- Proof of visit: location checked against the shop, plus a photo.
- Order taking from the correct price list, with taxes handled properly.
- Payment collection recorded against the shop's balance.
- Targets with daily pace, so a salesperson sees where they stand.
- Commission and expense handling that a manager can verify.
- Alerts for unusual patterns, not only reports after the fact.
- A manager view of the whole team, today, without waiting for anyone to report.
- A path from field orders to stock, dispatch and invoices, so the data is not retyped.
How gamitrack does it
Gamitrack is built around the working day of a field team in Nepal. Here is how the main workflows run.
Start of day
A salesperson opens the Today tab, starts the day with GPS, and sees the route with ordered stops. Attendance is derived from the day start, in Nepal time, with late, absent and early-leave states against the company's holidays and work week. Managers see who has started and who has not.
At the shop
On arrival the salesperson checks in. The visit is geofenced around the shop location and takes a photo as proof. They record closing stock of key items, take the order from the right price list, collect any payment, note the outcome, and set a follow-up if the shop asked to be visited on a specific day. If there was no order, they choose a reason, which builds a picture of why shops are not buying.
Tracking and integrity
Background GPS runs through the working day and is queued if the phone is offline. The admin map shows the day's movement, stores visited and time spent, and compares a day with the person's own 30-day average and the team average. Detectors flag visits outside the geofence, very short visits and visits without photos, and a daily integrity score summarises them. Alarms notify the salesperson as well as the manager, so problems are corrected early instead of argued about later.
Orders to invoices to money
Orders are priced from price lists, with VAT only on taxable lines. When dispatched, an order produces an IRD-format tax invoice. Payments by cash, eSewa, Khalti, Fonepay, bank or cheque are recorded and matched to the oldest invoices, and the ledger and aging show what each shop owes.
Targets, commissions and expenses
Managers set monthly officer targets with a daily pace. Commissions are calculated on secondary orders, with universal and personal rates and a minimum achievement rule, and month-end drafts are reviewed before they are finalised. Officers claim field expenses with a receipt photo, and managers approve or reject with a reason.
Communication
Managers can send broadcasts to everyone, to regions or to named people, and staff receive them in the app inbox with push notifications.
Who it is for
Gamitrack suits companies that sell packaged goods through shops and dealers, with a field team of a few people up to a few dozen. It is used by teams in masala and spices, FMCG and packaged food and beverages, and the same workflows apply to dairy, pharma distribution and other categories. It is not a payroll system and it does not replace your accounting package; it covers the sales, delivery, stock and collection side.
Paper and Excel, generic software, and gamitrack
| Need | Paper and Excel | Generic software | gamitrack |
|---|---|---|---|
| Proof of visit | Salesperson's word | Check-in without shop context | Geofenced visit with photo and flags |
| Orders | Books, calls, chat | Often a separate order tool | Taken in the app from price lists, flows to dispatch |
| VAT invoices | Typed again in the office | Usually not IRD format | IRD-format invoice at dispatch |
| Collections | Notebook | Manual ledger | Payments matched to oldest invoices, with aging |
| Targets and commission | Month-end spreadsheet | Fixed templates | Daily pace, rates, drafts and payouts |
| Nepali language | Handwritten | Rarely supported | English and Nepali throughout |
| Team visibility | Phone calls | Dashboards without field data | Live day, movement map and alerts |
Getting started
Start with one region and one small team. Load your products and price lists, add shops with their location, build routes, and run the app alongside your usual process for two weeks. Compare visits, orders and collections with what the paper process captured. The gaps tell you where the value is.
See pricing for plans, or contact us to see the app on a demo company.