To test offline sales visit capture and synchronization in an SFA demo, record a visit with connectivity disabled, reconnect, and verify that the server accepted it once. Run a four-state acceptance test—saved locally, queued, synchronized and accepted—with defined evidence and failure handling before the demo. A field rep losing signal in a store basement can make the demo look fine; the real question is whether that visit reached the server once, passed validation and left an auditable status.
Define the expected evidence and failure handling before the demo. Ask the vendor to confirm offline support and the exact fields supported offline; do not assume either from a generic sales force automation (SFA) demonstration. Airpalm’s public site (checked 9 October 2026) describes mobile visits, route planning, store audits, sales orders, inventory and promotion management, but that public description does not establish offline capture or synchronization rules. Those need explicit confirmation and a demonstration.
Agree the record states before the demo
Vendors use different labels. Agree what each state means and what evidence proves it. A record visible on the device is not proof of server acceptance.
| State | What it should mean | Evidence to demand | Failure handling |
|---|---|---|---|
| Saved locally | Captured on the device but not sent | Local record or status identified by the vendor, with device time and store/user IDs | Cannot distinguish local data from server-accepted data |
| Queued | Marked for sending and waiting for connectivity | Queue count or pending status, plus proof the server has no record yet | No queue visibility or queued state disappears |
| Synchronized | Transport is complete and the server has the payload | Server record with received timestamp and matching payload | Fields change silently during transfer |
| Accepted | Server validation and business rules passed | Final accepted status, validation log and no open exception | Only a synchronized status, or rejected records are hidden |
Run the scripted record test offline
Use distinctive test values so you can trace the record. Test one supported network condition first. Keep screenshots, timestamps and support logs.
Step 1. Prepare the baseline online
Create a demo store, assigned rep and visit task while connected. Include one order line or no-order reason and one store audit answer. Write down the store ID, visit ID, order reference and server timestamp.
Expected evidence: the server record is visible before disconnect with matching IDs. Failure handling: if no server baseline exists, stop; later receipt cannot be proven.
Step 2. Disconnect in a controlled way
Use airplane mode or disable both Wi-Fi and mobile data. Note the device, operating system, app version and network condition. An offline indicator can be captured, but it is not proof of data handling.
Expected evidence: the app remains usable or fails predictably. Failure handling: log a hang, logout, data loss or unexplained blocking with screenshots; stop the step.
Step 3. Capture the visit offline
Complete check-in, the store observation or audit, and the order or no-order reason. Capture only fields the vendor has confirmed are supported offline.
Expected evidence: a local saved status or record identified by the vendor, with device time and user/store IDs. Failure handling: if a required field is blocked, data disappears, or the local record cannot be distinguished from server-accepted data, mark the field unsupported and do not score it as passed.
Step 4. Reconnect and watch synchronization
Restore connectivity and watch the record move from local to queued to synchronized. Note start and finish times. Ask what should happen if the app closes, the device restarts, the session expires or the user logs out while data is queued.
Expected evidence: the queue drains without retyping and status changes are visible or traceable. Failure handling: if data stays queued, repeats, or arrives with missing values, keep screenshots and support logs.
Step 5. Verify receipt, duplicates and conflicts
Open the server record. Compare the visit count for the store, order lines, quantities, audit answers, timestamps and final status. One capture should create one visit record, not two.
Ask the vendor to demonstrate a supported conflict scenario: the same visit edited from two devices, a stale version submitted after reconnect, or an order changed on the server while the rep was offline. If no safe method exists, request documented rules and test them in a pilot.
Expected evidence: one accepted server record with a matching payload, validation status and audit trail. Failure handling: if the record is synchronized but not accepted, duplicates appear, or conflicts have no visible resolution, log severity and require a written fix and retest before rollout.
Record evidence and confirm vendor scope
Keep a compact evidence pack: device, OS, app version, network state, tester, timestamps, before-and-after server IDs, final status, validation log, record counts and any vendor ticket reference. Treat a demo that shows only the local screen, uses synchronized as a final status, or cannot name the fields supported offline as incomplete.
Ask the vendor to document which devices, OS versions, roles and modules support offline capture; which visit, audit and order fields are available offline; what happens to queued data after logout, app update, device restart or session expiry; how duplicate submissions and conflicts are resolved; and what evidence they will provide after the test.
If you are evaluating Airpalm, start from its public product information at airpalm.com and ask the vendor to run this script and confirm offline scope by field and module. For a related test of visit evidence, see Store Audit Data Quality: Test It Before Buying SFA Software.
Frequently asked questions (FAQ)
Does airplane mode prove offline support?
No. It simulates one network-loss condition on one device. It does not prove that required fields can be captured offline, queued data survives app restarts or sessions, or duplicates are prevented. Ask the vendor to define the supported offline conditions and test each one.
What is the difference between synchronized and accepted?
Synchronized means transport finished and the server has the payload. Accepted means server-side validation and business rules passed. A record can arrive but be rejected for a duplicate, stale version, invalid store or missing field, so ask for the final status and validation log.
Which fields should we capture in the offline test?
Use a small representative set the vendor explicitly confirms, such as store and visit IDs, check-in, one audit answer, and one order line or no-order reason. Add a photo only if supported. Document blocked fields and do not count them as passed.
Put this guide into practice
This general-purpose worksheet is a starting point. Adapt its fields, responsibilities and rules to your business process.



