Field Sales Tracking App: Routes, Orders and Offline Sync

A field sales tracking app lets reps take orders, collect payments and log visits from a phone while standing in the store. Off-the-shelf platforms charge per user, per month; a custom build is a one-time project cost. Three factors decide which fits: team size, ERP dependency and how reliable connectivity really is on your routes.

If your business moves goods through wholesalers, distributors or direct store delivery, most of your revenue is created in short conversations at a counter — not in your office. And your office usually learns what happened the next morning, from handwritten forms. That gap is the problem this software category exists to close.

This guide is vendor-neutral. It walks through the decisions you need to make before you compare quotes, including the technical realities that rarely come up in a sales demo.

What This Guide Covers

• What a Field Sales Tracking App Actually Does
• Van Sales, Pre-Sales or Hybrid: Pick Your Model First
• Route Planning and Visit Discipline
• Collections, Credit Risk and Cash in the Field
• Offline-First: The Part That Breaks Most Apps
• ERP, Accounting and E-Invoicing Integration
• GPS Tracking and Employee Privacy Limits
• Off-the-Shelf SFA or a Custom Build?
• Frequently Asked Questions

What a Field Sales Tracking App Actually Does

The category is usually labelled SFA — sales force automation. In practice, a field sales tracking app consolidates four separate ledgers into one screen: who to visit, what was sold, what was collected, and what stock remains. The rep opens a customer, sees that customer's price list and active promotions, enters the order, and prints a document from a Bluetooth printer if needed. Head office sees it immediately.

Why does that matter so much? Because the bottleneck in field sales is rarely selling skill — it is time. Field sales surveys published in 2026 put active selling at roughly 44% of a rep's week, with about 21% going to admin work and data entry. That is close to eight hours per rep per week spent away from customers. In a team that still re-keys paper order forms in the evening, the number gets worse.

The second cost sits on the shelf. Out-of-stock rates in retail typically run in the 7–10% range, and IHL Group's 2026 inventory research estimates that global inventory distortion costs the equivalent of roughly 6% of retail sales, with about two-thirds of that traced to items simply not being there. A rep who sees the gap, records it and triggers a replenishment order affects that number directly.

A typical feature set covers: customer records and visit history, a route calendar, customer-specific pricing and promotions, order entry, van or warehouse stock visibility, collections and balance, document printing, shelf and merchandising audits, and a reporting layer for managers. You will not need all of it on day one — but you cannot compare quotes sensibly until you know which items are critical for your operation. The pattern is close to the one we described in the hidden cost of running your business on Excel: the data exists, just not in one place and not in time.

Van Sales, Pre-Sales or Hybrid: Pick Your Model First

Before you evaluate any software, define how your team actually sells. Three models dominate, and each asks something different from the app.

Van sales (direct sales). The rep carries stock in the vehicle, sells it, delivers it and takes payment on the spot. The app must track van inventory in real time and issue documents from the vehicle. Common in bread, dairy, beverages and snacks — anything that turns over fast.

Pre-sales. The rep only takes the order; a separate delivery vehicle fulfils it later, usually the next day. The app must separate ordering from fulfilment and handle delivery routes and short deliveries. Distributors with wide catalogues favour this model.

Hybrid. Pre-sales for key accounts, van sales for small outlets. This is the most common structure in practice and the one packaged products struggle with most, because the same rep has to run two different flows on the same day.

The most expensive mistake here is buying a package before mapping the current process. Spending a week riding along with two reps and writing down the day step by step tells you more than any demo. Model mismatch kills user adoption in the first month.

Route Planning and Visit Discipline

A route plan defines which customer is visited on which day, in which order. A good one balances three things at once: visit frequency by customer tier (A accounts twice a week, C accounts monthly), geographic clustering, and a rep's realistic daily capacity.

Route optimisation is the mathematical layer on top. Academic studies and field deployments consistently report double-digit savings in distance and fuel from optimised routing, with the range widening when driver coaching and idle reduction are added. One caveat matters, though: optimisation cannot rescue a bad route plan. Visiting the wrong customers in the right order gains you nothing.

Technically, you have three options:

1. Manual sequencing. Group customers by district or postcode and order them by hand. Adequate for small teams, and it costs nothing extra.
2. Distance matrix from a maps provider. Compute the shortest path using real road data. For mid-sized operations, this is the sweet spot.
3. True fleet optimisation. Services that solve vehicle capacity, time windows and multi-vehicle constraints. Google's Route Optimization API billing charges per shipment and moves into the Fleet Routing SKU for two or more vehicles — so if you plan hundreds of daily stops, that becomes its own budget line.

Three metrics tell you whether the plan works: visit completion rate (how many planned visits happened), strike rate (how many visits produced an order), and average order value per visit. Together they separate a rep problem from a route-design problem. High completion but a low strike rate usually means the schedule is wrong, not the person — you are probably visiting some outlets more often than they can absorb.

Practical advice: do not jump to option three in version one. Establish visit discipline first, measure it, then invest in optimisation.

Collections, Credit Risk and Cash in the Field

The most expensive failure in field sales is weak collections control. What the software must do is simple to state and frequently missing: the moment a rep opens a customer, they should see the current balance, the overdue amount and the credit limit — and the system should block the sale or escalate it for approval when the limit is exceeded.

Requirements that come up on almost every project:

• Partial payments and mixed tender. Cash, card, cheque and promissory notes can appear in a single visit.
• Cheque photos and serial tracking. Record the instrument without waiting for the paper to reach head office.
• Discount authority matrix. Which rep can give how much, to which customer.
• Returns and swaps. In food especially, what condition returned stock re-enters inventory in.
• End-of-day cash reconciliation. Matching what the rep collected against what the system recorded.

These look like details, but in a custom project they drive a serious share of the budget. Your credit logic should match the rules in your custom CRM or B2B dealer portal — two different limit definitions in two systems guarantee an argument in the field.

Offline-First: The Part That Breaks Most Apps

Coverage maps and reality are different things. Even in markets with near-universal mobile broadband, phones still fail in basement stockrooms, inside covered markets and on rural roads between towns. Turkey is a good example: mobile subscriptions passed 99 million and 4.5G subscriptions reached 91.2 million by the end of 2025 according to the telecom regulator's quarterly market data, with 5G service starting in April 2026 — and reps there still lose signal several times a day.

So in a serious field app, offline mode is not a feature. It is the architecture.

The local database is written first. Every read and write goes to the on-device store. The UI never waits for a server. The rep enters an order and the screen responds instantly.

An outbox queue holds every change. Operations land in an ordered queue and replay to the server when connectivity returns. The queue survives app restarts and reboots.

Conflict rules are decided up front. If head office changed a price while the rep booked an order at the old one, what happens? Two common strategies exist: last-write-wins and field-level merge. Last-write-wins is simple, but device clocks drift, so use server receipt time or a logical version number rather than the handset clock. For numeric fields like stock and balance, sync the movement (increment/decrement) rather than the total — it is far safer.

Sync deltas, not the world. Re-downloading a 40,000-item catalogue on every launch punishes both data plans and batteries. Pull only what changed since the last sync.

Applying all four together is exactly where packaged products and custom builds diverge. Many packages advertise "offline support" but only cache a draft order; pricing, promotions and balance checks still reach for the network. During a demo, put the phone in airplane mode and complete a full visit end to end. Does the customer open? Does the promotional price calculate? Does the document print? Does the payment record? If any answer is no, that product will not work in your dead zones.

There is also a quieter failure mode: location services. Android's background location and battery guidance recommends balanced-power priority over high accuracy for most cases, the largest workable update interval, and a geofence notification responsiveness of five minutes or more. An app that polls high-accuracy GPS continuously will flatten a phone by mid-afternoon, and the rep will simply turn it off. A surprising share of "adoption problems" are really battery problems. If you want the broader trade-offs, our guide to web-based software covers where the browser stops being enough.

ERP, Accounting and E-Invoicing Integration

A field app is never an island. Customer accounts, product records, price lists and promotions almost certainly live in your ERP, and orders and payments need to flow back. In Turkey the common integration targets are Logo (Tiger, GO, Wings), Mikro, Netsis and cloud tools such as Paraşüt; elsewhere the names change but the pattern does not.

There are three methods and three risk profiles:

Direction matters as much as method. One-way flow (field to ERP) is the right first-phase scope for most projects and is quick to deploy. Two-way flow means balances, stock and price changes must travel back to the field, which introduces refresh frequency, conflict rules and an error queue. Decide in writing, at project start, which system is the source of truth for each data type — that single sentence prevents most later disputes.

Many companies adopt direct database writes as a short-term fix and then watch everything stop at the next ERP upgrade. Use the official interface wherever it exists.

E-invoicing is its own topic. In Turkey, taxpayers with 2025 gross sales revenue of 3 million TL or more must move to e-Fatura from 1 July 2026, and the threshold drops to 500,000 TL for e-commerce, real estate and motor vehicle trading. For a van sales team, that creates a hard requirement to issue electronic documents from the vehicle. Our e-invoice integration guide covers the process, and the Revenue Administration publishes the rules on its e-Belge portal. The implementation detail to watch is how document numbers are generated offline: pre-allocating number ranges to each device is the most practical way to avoid collisions.

GPS Tracking and Employee Privacy Limits

Location tracking is the most requested and most frequently mis-designed feature in this category. An employee's location is personal data, and processing it is bound by principles of lawfulness, purpose limitation and proportionality — under Turkey's Law No. 6698 as much as under GDPR.

Turkey's Data Protection Board issued a public announcement on principle decision 2026/921, dated 29 April 2026, which concerns biometric attendance tracking specifically but carries two messages for every employer. First, the structural power imbalance between employer and employee makes consent a shaky legal basis at work — "the employee signed it" is not a defence on its own. Second, where a less intrusive method achieves the same purpose, the intrusive one is not permitted.

Translated into a field app, that produces practical rules:

• Limit tracking to working hours. Nothing is collected outside the shift; when the rep ends the day, tracking stops.
• Log events, not a continuous trail. In most cases you do not need a second-by-second breadcrumb. A location stamp at visit start and end serves the purpose and fits proportionality far better.
• Be transparent. The privacy notice must state what is processed, for what purpose and for how long, and the app should visibly indicate when tracking is active.
• Set a retention period. Do not keep location records indefinitely; automate deletion.
• Restrict access. Only the relevant manager should see raw location data; summary metrics suffice in general reporting.

This lowers legal exposure and defuses the "we're being watched" tension inside the team. In our experience, companies that frame location as visit verification and commission evidence — rather than surveillance — get materially higher adoption.

Off-the-Shelf SFA or a Custom Build?

The honest answer: for most small teams, a packaged field sales tracking app is the right starting point. If you run a standard van sales operation, use a mainstream ERP and have no unusual business rules, a monthly subscription gets you moving quickly.

A custom build starts to make sense when:

• Your hybrid model or industry-specific rules do not fit a package — cold chain, consignment, weight-based selling, display agreements and similar.
• Subscription totals overtake a project budget as headcount grows. Rough maths: at 40 users, a per-seat monthly fee adds up to a serious investment over three years.
• Data ownership and integration depth are critical. You want your own API, your own reporting layer and your own mobile experience.
• The software becomes part of your product, opened up to dealers or customers.

For a rough budget figure, try our app cost calculator — a field app is, in practice, a mobile app plus an admin panel plus an integration layer. The buy-versus-build reasoning on the stock side is laid out in our inventory management software comparison, and it applies here almost line for line.

A concrete example helps. A mid-sized food distributor on Turkey's Aegean coast runs a pre-sales model with 12 reps and around 1,400 outlets. Handwritten order forms are keyed in at the office each evening, costing roughly two hours a day and producing a steady trickle of order errors. For an operation like that, the right first-phase scope is usually: customer records, route calendar, offline order entry, live balance visibility and one-way order transfer to the ERP. Route optimisation, photo-based shelf audits and commission calculation belong in phase two. That sequence makes adoption easier and keeps the initial investment small.

Frequently Asked Questions

What is the difference between a field sales tracking app and a CRM?

A CRM manages relationships, pipeline and communication history, usually from a desk. A field sales tracking app is built for the visit itself: route calendars, offline order entry, van stock, collections and location-stamped visit records. Many teams run both, with the field app feeding activity data into the CRM.

Does a field sales tracking app work without internet?

A properly built one works fully offline. Data is written to a local database on the device, operations wait in a queue, and everything syncs automatically once connectivity returns. Test this before you buy by completing an entire visit in airplane mode.

How is field sales software priced?

The common model is a monthly fee per user, with the total driven by seat count, which modules you enable (route optimisation, shelf audits, e-invoicing) and integration work. Setup, data migration and training are often quoted separately, so compare vendors on total first-year cost rather than the headline seat price.

Is it legal to track a sales rep's location?

Location is personal data and must be processed proportionately and for a stated purpose. Visit verification that is limited to working hours, disclosed in a privacy notice and subject to a defined retention period is generally defensible. Continuous tracking that extends beyond the shift carries a high compliance risk.

Can orders sync automatically into Logo, Mikro or another ERP?

Yes — once an integration is in place, orders and payments flow through automatically. The choice of method is what matters: an integration built on the ERP's official interface survives version upgrades, while direct database writes are fast to build but can put you outside vendor support.

Do reps need rugged handheld terminals?

Not usually. Most teams now work with standard Android phones and Bluetooth printers. Rugged terminals earn their price in dusty, wet or high-impact environments, in operations with heavy barcode scanning, and where long shifts demand serious battery life. Measure your daily scan volume and physical conditions before deciding.

How long does a custom field sales app take to build?

Scope decides it, but a first release covering the core modules typically reaches the field in two to five months. The longest pole is rarely the app itself — it is ERP integration and cleaning up existing customer and product data. Starting that preparation in parallel shortens the timeline noticeably.

Choosing field sales software is really a test of how well you understand your own operation. Write down your model (van sales, pre-sales or hybrid), design the offline scenario against a real working day, decide the ERP integration method up front, and put location tracking on a defensible legal footing. Get those four right and any route you take will be a sound investment.

At Master Web we build offline-capable mobile field apps, admin panels and ERP integrations for distribution and dealer operations. Let's walk through your current process and scope what actually fits: see our software services or get in touch.