Field sales tracking app
The van, the shop, the order — captured where there is no signal.
An offline-first mobile app for teams who work away from a desk: visit plans, geo-verified check-ins, order and collection capture, competitor notes and photo evidence. The phone is the source of truth; the server catches up when a connection returns.
Usually arrives as
- Reps filling a form in the evening from memory
- Visit claims nobody can verify
- Orders re-keyed from WhatsApp into the ERP
- No view of route coverage against the plan
- Attendance and expenses reconciled by hand
Built from
Offline-first from the first commit. Conflict rules are a product decision, decided in design.
What is in it
Modules, not features. Each one is a decision you can keep or drop — nothing here is bundled because it was easier to build that way.
Beat and route planning
Journey plans by rep, territory and frequency, with coverage measured against the plan rather than against activity.
Geo-verified check-in
Location and time captured at the shop, with an offline queue and a tamper-evident record. Distance from the mapped outlet is stored, not hidden.
Order and collection capture
Catalogue, schemes, credit limit and outstanding visible at the counter. Orders sync into the ERP with an idempotency key so nothing double-posts.
Evidence
Photographs of shelf, display and competitor pricing, compressed on device and uploaded on connection.
Expense and attendance
Distance travelled derived from the visit trail, claims raised against it, approvals routed to the reporting manager.
Manager view
Live coverage, order value by route, exceptions and non-productive calls — read from the same records the rep created, not a separate report.
Questions we are asked
Does it work with no signal at all?
Yes. The local store is the source of truth for the interface; the network updates it and never gates it. A full day can be worked offline and synced at the end of it.
Can it connect to our ERP?
That is the normal case. Orders, customers, stock and outstanding sync both ways over an API or a staged file exchange, with idempotency so a retry cannot duplicate an order.
How do you stop check-in being gamed?
Location, time, accuracy radius and distance from the mapped outlet are all recorded and visible to the manager. Mock-location detection is on by default. The system reports what it saw rather than silently accepting or rejecting.
Have something worth building?
Tell us the constraint you are working against. If we are not the right people for it, we will say so.
Or write to connect@jannex.in