Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For logistics & field service
Job cards with the evidence attached, van stock that reconciles nightly, and tools with names on them. Stock movement is captured with no signal and syncs on return; job cards and selling are not offline, and the scope section says exactly where that line sits. Fuel is an expense coded to a project rather than a consumption log.
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.
Four operations captured with no connectivity — stock transfers, inventory check-out and check-in, and asset movements — synced when the network returns. Job cards and deliveries need a connection.
Photos and documents attached to the job, stock issued against it with a reason and a person, and time recorded — one record from dispatch to done. Two honest gaps: a job card carries no GPS coordinate and there is no captured customer signature, so sign-off is a photo or a note rather than a signed record.
Load-out transfers to a location per van, on-route movements, and nightly variance — with a named custodian on every van.
Tools and instruments issued to named people, verified weekly, cleared at exit.
Every vehicle on the asset register with a named custodian and full movement history, and custody movements carry a GPS stamp — which is where location actually is captured. Fuel is an ordinary expense coded to a project; it does not attach to the vehicle, no distance is held, so cost-per-kilometre cannot be computed. No maintenance visit, service interval or next-service date is recorded.
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, and which four operations survive it here.
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.
Ninety-four cartons left Industrial Area and eighty-nine arrived in Eldoret. The system knows what went on the lorry and what came off it — and has no opinion about the person in between.
Most Kenyan distributors do not own a fleet, they hire one. So transport is not a fuel problem but a rate problem: the arithmetic on the invoice is right, and nobody is checking the rate it was multiplied by.
Six things get assessed, and every one of them is evidenced by records a business already generates. The failure is almost never that the substance is missing — it is that nobody can produce it without reconstructing the year.
Questions we are asked here
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.
They can sell with a connection, and this is the question to be exact about because the answer shapes the route. A van sale decrements van stock and rolls into the nightly reconciliation alongside deliveries, so stock and money close together per route — but selling requires a connection on both the web app and mobile, so a van going out of coverage cannot take a sale while it is out there. What does work with no signal is stock movement: transfers, check-out and check-in, and asset movements. If your routes run through genuine dead zones, plan selling around coverage rather than assuming the van carries a till.
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.