Field sales software keeps which customer each sales rep visits on which day, what happened during the visit, the order taken and the payment collected in one place, usually through a mobile app and a management panel. In short: it answers "who went where today, what did they sell and what did they collect?" without an evening phone call. An order form is not enough for that; you need route plans, location verified visit logs, an order screen that works offline and prices that are confirmed on the server.
What does field sales software do?
In many distribution and wholesale companies the field team works with paper order slips, WhatsApp messages and a phone call to the office in the evening. Orders are entered the next day, prices are typed wrong, out of stock items are sold and managers notice that a customer has not been visited for weeks only when revenue drops. The software turns this into a single record.
- Route plan: a daily customer list and visit frequency for every rep.
- Visit log: check in and check out time, location, outcome and a note or photo.
- Mobile orders: with customer specific price lists, discounts and stock.
- Collections: cash, card or cheque payments recorded with a receipt.
- Manager panel: planned versus actual visits, sales and collections per rep.
Why are visits verified by location?
If a visit is logged by ticking a "done" box, the report is only the rep's word. The software reads the phone's location when the visit starts and compares it with the coordinates on the customer card; if the distance is outside a set radius (for example 200 metres) the visit is not blocked but saved with an "off site" flag and sent to the manager for approval. The goal is to document the visit, not to follow the person all day: location is taken only when a visit starts and ends.
The price on the phone is a suggestion; the final price is calculated on the server. Orders can be taken offline, but on sync price, discount and stock are checked again; if anything differs the order is not changed silently, it goes back to the rep and the customer for approval.
Offline orders and syncing
The field has basement warehouses and villages with no signal; if the order screen needs a connection, reps go back to paper. The app downloads products, price lists and customers to the phone in the morning, queues orders on the device and sends them when a connection returns. Every order carries a unique key created on the device, so if the same order is sent twice the server does not count the second one as a new order. For the details of this setup see our offline mobile app article.
type Visit = { customerId: string; lat: number; lng: number; startedAt: string };
type Customer = { id: string; lat: number; lng: number };
const MAX_DISTANCE_M = 200; // visit radius, read from settings
// Haversine distance in metres between two coordinates.
function distanceM(aLat: number, aLng: number, bLat: number, bLng: number): number {
const R = 6371000;
const toRad = (d: number) => (d * Math.PI) / 180;
const dLat = toRad(bLat - aLat);
const dLng = toRad(bLng - aLng);
const h =
Math.sin(dLat / 2) ** 2 +
Math.cos(toRad(aLat)) * Math.cos(toRad(bLat)) * Math.sin(dLng / 2) ** 2;
return 2 * R * Math.asin(Math.sqrt(h));
}
// A visit far from the customer is saved, but flagged for manager approval.
function visitFlag(v: Visit, c: Customer): 'ok' | 'off-site' {
return distanceM(v.lat, v.lng, c.lat, c.lng) <= MAX_DISTANCE_M ? 'ok' : 'off-site';
}
// Offline orders carry a device generated key; a resent order is not a new order.
type OrderLine = { productId: string; qty: number; unitPriceKurus: number };
type Order = { clientKey: string; customerId: string; lines: OrderLine[] };
const seen = new Map<string, string>(); // clientKey -> server order id
function receiveOrder(order: Order, serverPrice: (productId: string) => number) {
const existing = seen.get(order.clientKey);
if (existing) return { status: 'duplicate', orderId: existing };
const changed = order.lines.filter((l) => serverPrice(l.productId) !== l.unitPriceKurus);
if (changed.length > 0) return { status: 'needs-approval', changed }; // never fix silently
const orderId = crypto.randomUUID();
seen.set(order.clientKey, orderId);
return { status: 'accepted', orderId };
}Balances, collections and other systems
- Customer balance: before ordering, the rep sees the open balance and credit limit; the source is the accounts receivable software, and the app reads the balance instead of copying it.
- Collections: payments taken in the field are stored with a receipt number and stay open on the rep until handed in to the cashier.
- Dealer orders: if customers can also order themselves, both channels use the same price and stock rules; see our B2B dealer ordering system article.
- Reporting: planned versus actual visit rate, orders per visit and customers not visited for a long time.
Note: employee location is personal data; staff must be told clearly when and why it is collected. This article is a technical guide, not legal advice.
Conclusion
Good field sales software starts from the route plan, documents visits with location, takes orders offline but confirms prices on the server and reads customer balances from a single source. If you would like to design a mobile app and panel for your field team, see our corporate solutions page or request a quote.