Field Sales App for Sales Reps: Offline Mode, 12 Requirements and Questions for the Vendor
12 requirements for a field sales app, the airplane mode test, sync conflicts, GPS and the Polish Labor Code, questions for the vendor and a table: off-the-shelf tool or custom app.
In short
- A field sales app is software on a phone or tablet that gives sales reps client records, a visit plan, orders and notes. In the field, one thing matters more than anything else: it has to work with no signal, when saving data too, not just when viewing it.
- The simplest test during a demo is airplane mode: add a note and an order with no connection, change the same client at the office in the meantime, then turn the network back on and see what is left.
- An off-the-shelf CRM with a mobile app is enough for a typical sales process. A custom app makes sense when your offer follows its own logic (calculators, variants) or your reps work with no signal. At UNSEEN, an app for a single process costs from 3,550 EUR net, a custom CRM from 11,550 EUR net.
- Typical sales process, reps usually have a signal
- Off-the-shelf CRM with a mobile app
- You already have an ERP system, reps collect orders
- ERP mobile module
- Offer with its own logic, work with no signal
- Custom app
If your sales reps take notes on their phones and in Excel and only work out quotes once they are back at the office, also see Field sales reps can’t prepare a quote until they are back at the office. This article helps you choose the tool: off-the-shelf or built for you.
What is a field sales app?
It is an app that replaces a sales rep’s notebook, spreadsheet and phone calls to the office: a client record with the history of visits and orders, the day’s plan on a map, a catalog with prices, orders and notes. The office sees the same data as the rep, without phone calls or retyping. These systems are also called SFA (sales force automation). Most often, the app is part of a CRM system or a mobile module of the ERP system in which the company manages its inventory and invoices.
What requirements should a field sales app meet?
Twelve requirements, from the most important down, and a way to check each one before you sign a contract. Vendors’ descriptions tend to be vague (“works offline”), and the difference only shows up in the field.
| Requirement | Why it matters | How to check it in a demo |
|---|---|---|
| 1. Works with no signal | Visits, notes and orders are saved even in a warehouse or out in the countryside with no network. | In airplane mode, add a note, an order and a new client. Viewing data alone is not enough. |
| 2. Sync with conflict resolution | Changes from the phone and from the office merge without lost data or duplicates. | Change the same client offline on the phone and at the office, turn the network on and see what is left. |
| 3. Visible upload status | The rep knows whether the order has reached the office. | Look on the screen for a counter of unsent changes and the time of the last sync. |
| 4. Client record | The history on the spot: visits, orders, notes, contact persons, consents. | With no network, open a client with a long history: is all of it there, or only the last few weeks? |
| 5. Orders in the field | The order reaches the office and the warehouse without retyping. | Place an order offline and change the price at the office. What happens after sync? |
| 6. Calculator and quote in front of the client | Pricing during the same conversation, not after the rep gets back to the office. | Price your typical product with a discount and a variant. If that is not possible, ask who will build the calculator and for how much. |
| 7. Voice notes | The note gets written right after the visit, not in the evening from memory. | Dictate a note with product names and numbers. Does dictation work with no network? |
| 8. Routes and GPS | A visit plan on a map and navigation to the client with one tap. | Plan a day and open navigation. Ask when the app collects location data and who can see it. |
| 9. Weak signal, not just no signal | With one bar of signal, the app does not freeze or lose an upload halfway through. | Test it somewhere with a weak signal: photos wait in a queue, the order goes first. |
| 10. Permissions and lost phones | Reps see their own clients, and the data on a lost phone can be locked. | Ask how to log out a lost device and whether the data on the phone is encrypted. |
| 11. Integrations | The catalog, prices and stock levels come from the ERP system, and orders go back to it automatically. | Ask for the list of ready-made integrations with your software and the price of one that is not on it. |
| 12. Reports for the manager | Visits, orders and deal stages are visible in real time, without spreadsheets. | Ask for a weekly team report. Does data collected offline show up in it right after sync? |
How does offline mode work, and what happens in a data conflict?
An app with a real offline mode keeps a copy of the data it needs on the phone: clients, the catalog, prices and history. Changes made with no network go into a queue and are sent when the signal returns. The trouble starts when someone at the office changes the same record in the meantime. That is a conflict, and every app resolves it somehow, often silently. The right approach depends on the type of data:
- Notes, visits and activities are only ever added, so there is no conflict: the note from the phone and the note from the office both stay.
- Client details are merged field by field: if the rep changed the phone number and the office changed the address, both changes stay. When both changed the same field, the later change usually wins, and the previous value stays in the history.
- Orders get their number on the phone already, so resending after a dropped connection does not create a duplicate. If the price or stock level changed in the meantime, the order waits for confirmation instead of going through at the old price.
Browser app (PWA) or an app from the app store?
You install an app either from a store (Google Play, App Store) or from the browser as a PWA, a progressive web app: an icon on the phone’s screen, offline work, one codebase for Android and iPhone, updates without the store. On iPhone, a PWA has two limitations worth asking about:
- No sending in the background. Safari does not support Background Sync, the mechanism that sends the queue of changes while the app is closed, so on iPhone changes go out once the app is opened. Chrome on Android does have this mechanism.
- Data of an unused site gets deleted. Safari with cross-site tracking prevention turned on deletes the data a site has stored if nobody has clicked or tapped on it during 7 days of browser use. So an unsent change should not sit on the phone for days.
Install the PWA on the home screen: when WebKit, the engine behind Safari, decides whether to store data persistently, one of the things it considers is whether the site is opened as an app from the home screen. An app from the store can send data in the background, but it usually means two versions (Android and iOS) and a higher cost.
GPS tracking of sales reps: what is an employer allowed to do?
A visit plan on a map and navigation to the client raise no concerns; tracking an employee does. In Poland, the Polish Data Protection Authority (UODO) treats locating an employee by GPS as “another form of monitoring” under art. 22³ § 4 of the Polish Labor Code (Kodeks pracy), permitted when it is necessary to organize work or to ensure the proper use of work tools (other countries have their own rules). The employer:
- sets out the purpose, scope and method of monitoring in the work regulations (or in a collective labor agreement or a notice);
- informs employees no later than 2 weeks before the monitoring starts;
- tells them what data it collects, how long it keeps the data and who has access to it, and uses the data only for the stated purpose.
For the app, this is a technical requirement: location only during working hours or at the start and end of a visit, with a set retention period. This is information about the law, not legal advice: agree on the rules for your company with a lawyer or a data protection officer.
Off-the-shelf tool or custom app: which should you choose?
| Criterion | Off-the-shelf CRM with a mobile app | ERP mobile module | Custom app |
|---|---|---|---|
| When it makes sense | A typical sales process (lead, quote, contract), reps usually have a signal | The company already has an ERP system, and reps mainly collect orders from a catalog | Your offer follows its own logic (calculators, variants, financing) or reps work with no signal |
| Offline work | Anything from view-only to full work: check in airplane mode | Usually the catalog and orders: check notes and new clients | You design it around your process |
| Calculator and quote | Price lists and discounts, custom logic usually through add-ons | Price lists and discounts from the ERP system | A calculator built for your products |
| Cost | A subscription, often per user, plus add-ons. It grows with your team | A license at the vendor’s list price plus deployment | A one-time build plus a server, no per-user fees. At UNSEEN from 3,550 EUR net (one process) or from 11,550 EUR net (custom CRM) |
| Getting started | From a few days: configuration, import, training | Depends on the scope of deployment and the connection to the ERP system | At UNSEEN, the first working module after 2 weeks, the full CRM in 8-16 weeks |
| Risks | You adapt your process to the software, and pricing changes are up to the vendor | Dependence on a single vendor | Higher upfront cost. Put rights to the code and access to your data in the contract |
Going for an off-the-shelf system? Our guide on how to choose a CRM system for your company will help. None of them can price your offer, or none works where your reps work? See what a custom CRM includes. For companies selling solar PV, heat pumps and energy storage, we also offer an industry-specific CRM as a subscription: from 950 EUR net per month, deployed in 2-4 weeks.
What should you ask the vendor before you buy?
The answer “yes, it works offline” is not enough. Ask them to show you, not just to assure you:
- What works with no network: only viewing, or also adding a new client, a note, an order and a quote?
- How much data is on the phone: all clients and their full history, or only part of it?
- What happens when the same data changes on the phone and at the office? Who resolves the conflict?
- Can an order sent twice over a connection that keeps dropping end up duplicated?
- What happens to unsent data after logging out, an update or switching to a new phone?
- How does sending work on iPhone and on Android: in the background or once the app is opened?
- When does the app collect location data, who can see it and how long is it kept?
- Will I get all of my data back if I cancel? And with a custom app: who owns the code?
What does this look like in our projects?
- CRM for the renewable energy sector (case study). Sales of solar PV, heat pumps and energy storage, in the field with a weak signal, previously tracked in Excel. We built a mobile CRM as a PWA: the full client history on the phone, offline work (activities and orders sync once the signal is back), routes on a map with navigation and 5 calculators for sizing and pricing installations. The rep prepares the quote in front of the client, and the contact history stays with the company, even when the rep leaves.
- Scanvet, a CRM for a veterinary distributor’s sales reps (case study). Reps keep a log of visits to veterinary clinics, place orders to wholesalers from the catalog and dictate notes by voice. The office plans routes and sees the car fleet with GPS data from the trackers next to sales analytics. The system works offline, and the reps also have an Android app.
- [Sales rep app](/systemy-ai/aplikacja-dla-handlowcow) for phone sales. One company at a time, with its details, consents and an AI cheat sheet before the call, and the outcome is saved with a single swipe of the card. By design, it does not make calls on its own (the rep calls, from their own phone), does not send an email without a person clicking, and does not score companies with AI points.
On a free call, we will go through your sales process and tell you whether an off-the-shelf CRM is enough or you need a custom app. If an off-the-shelf tool is enough, we will tell you so plainly.
Frequently asked questions about field sales apps
Update history
- First version. UNSEEN prices, the UODO position on GPS and browser support for offline work checked on November 13, 2026.
Sources
- UODO: rules for other forms of monitoring (presentation of October 4, 2018) (checked on November 13, 2026)
- MDN: browser storage quotas and eviction criteria (checked on November 13, 2026)
- MDN: Background Synchronization API (checked on November 13, 2026)
- Can I use: Background Sync support in browsers (checked on November 13, 2026)
- WebKit: Updates to Storage Policy (August 10, 2023) (checked on November 13, 2026)
Product names belong to their respective owners.
Need personalized advice?
Book a free consultation. We’ll analyze your business and propose specific solutions.
Book a free 30-min call