Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For logistics & field service
Job cards with evidence, van stock that reconciles nightly, tools with names on them, and fuel that answers to arithmetic — offline-first, because the field doesn't wait for signal.
If any of these ring true, you are exactly who this was built for.
What happened out there arrives as crumpled paperwork, WhatsApp photos, and numbers that reconcile approximately.
Loaded full, sold some, returned some — and the difference belongs to nobody.
The fleet is the second-biggest cost and the least accounted — liters never meet kilometers.
Field software that needs connectivity becomes head-office fiction the first bad-signal Tuesday.
Each capability links to a deeper feature tour.
Jobs, deliveries, stock, and evidence captured with zero connectivity — synced when the network returns.
Photos, GPS stamps, materials consumed, and customer sign-off — one record from dispatch to done.
Load-out transfers, on-route movements, and nightly variance — attributed by route and driver.
Tools and instruments issued to named people, verified weekly, cleared at exit.
Cost per vehicle, fuel-to-distance reconciliation, and service schedules that beat breakdowns.
Cash and M-Pesa collected on-site, recorded against the job at collection time.
Van stock or job cards live on one team — two weeks of parallel running builds the proof.
Sync, count, reconcile — variance attributed same-day, and it shrinks within a month.
Routes, crews, and vehicles onboard one at a time; route contribution becomes a report.
For installers, distributors, and service crews the office is wherever the van stopped — job evidence, traveling stock, custody, and fleet discipline in one guide.
The airplane-mode test, sync queues and conflict rules, two-minute capture design, and the nightly heartbeat — what offline-first actually means.
The van is a warehouse that drives away; the site is a store with no walls — load-out transfers, nightly variance, job-costed materials, and crew custody.
Yes — capture is fully local (jobs, stock movements, photos, GPS stamps) and syncs when connectivity returns, whether that is an hour or three days later. Run the airplane-mode test in the demo: a complete field day with the network off.
Ordinary Android phones. Photo and GPS evidence needs nothing exotic; plan for charging discipline and screen-readable workflows rather than hardware budgets.
Yes — van sales decrement van stock at the sale, take cash or M-Pesa references offline, and roll into the nightly reconciliation alongside deliveries, so stock and money close together per route.
Natively — van load-outs are transfers from depot stock, job materials post to job costs, field payments land on invoices, and fleet costs post per vehicle. The field is a set of locations in the same governed system, not a satellite app.
A load-out, a day's deliveries, a nightly count, and the variance — demonstrated on your own route.