Basements, stockrooms, shopping centres and rural areas. If the app needs a connection to work, the team ends up writing on paper.
Offline mode is the ability to record a complete visit with no internet connection. Checklist answers and photos are stored on the device itself and sent to the server as soon as there is signal, with nobody having to intervene and no risk of losing work already done.
It is the point where most field tools lose the team's trust. One visit lost to a dead zone is enough for someone to go back to noting things on paper "just in case", and from then on the platform data stops reflecting reality. Team adoption is a direct consequence of reliability.
Before leaving, the app stores on the device the stores, brands and checklists you will need. Nothing special to do.
With no signal the behaviour is identical: answer the checklist, take photos, log tasks. There is no separate mode to learn.
If you close the app, run out of battery or the phone restarts, the draft survives. Nothing is lost.
Once the connection returns, visits are sent in the background, photos included, with no manual re-sending.
The app shows how many visits are pending sync, so nobody is left wondering whether the work went up.
Weak coverage inside and on lower floors, even in well-served urban areas.
Where stock gets checked and where there is rarely a signal.
Areas with intermittent coverage where the connection drops mid-record.
Background syncing avoids waiting and lets you choose when heavy photos go up.
A merchandiser audits the shelf in a store on the lower floor of a shopping centre, with no signal at all. They fill in the checklist, take twelve photos and log two incidents. Walking out to the car park, the connection returns and the visit syncs on its own in under a minute.
A seven-store route in a region with intermittent coverage. Visits are recorded through the day and sync in batches whenever there is signal. By the end of the day there is nothing pending and nothing to rewrite.
Recording is interrupted when the phone shuts down. On restart the draft is intact, with the answers and photos already taken, and the visit continues from where it stopped.
| App that requires a connection | Offline recording |
|---|---|
| The visit is lost if the connection drops | The draft is safe on the device |
| The team writes on paper "just in case" | They record once, in the app |
| Photos re-sent by hand | Automatic background syncing |
| Nobody knows what went up | Sync state visible |
| Platform data ends up incomplete | The platform reflects what happened |
| Concurrent offline visits | No practical limit, bounded only by device storage |
|---|---|
| Offline photos | Stored at full quality, compressed on upload |
| Syncing | Automatic in the background, as soon as there is a connection |
| Draft persistence | Survives app close, restart and battery loss |
| Conflicts | Each visit is independent, so there are no concurrent edits to resolve |
| Platforms | Android, iOS and browser |
| Indicator | Pending-sync counter visible in the app |
No. The app stores what it needs while connected. Simply having opened the app with a connection at some point in the day is enough.
Yes, at full quality. They are compressed only at upload time, so no data is wasted.
There is no imposed limit. In practice the limit is free device storage, and a visit with photos takes a few megabytes.
They are lost, like any local data in any app. It is worth checking the pending-sync counter is at zero before uninstalling or changing phone.
You get two independent visits, both kept. There is no conflict to resolve, because a visit is a record of a moment rather than a shared document.
Almost all the weight comes from photos, which are compressed on upload. A typical visit with ten photos lands in the low megabytes.
Everything agreed with the retailer only counts if it is actually in the store. Retail execution is the discipline of verifying that, with evidence, and acting when it is not.
Every store visit produces information worth keeping for years. Recording it was never the problem: getting back to it is.
The checklist decides the quality of everything that follows. If the questions are vague, no analysis can rescue them.
It is the test we recommend most: take the app into a store with bad reception and see what happens.