Field Operations Software in Kenya: Offline Mobile, Van Stock & Fleets (2026)
For installers, distributors, service crews, and survey teams, the office is wherever the van stopped — the 2026 guide to running field operations on offline mobile workflows, traveling stock, and fleet discipline.
A distributor's van leaves Nairobi at 6am with stock, cash float, a fuel card, and three delivery routes. A solar installer's crew heads to Kajiado with inverters, tools, and a job card. A water company's technicians scatter across a county with meters and spares. By evening, each of these businesses faces the same question: what actually happened out there? For most, the answer arrives as crumpled paperwork, WhatsApp photos, and numbers that reconcile approximately. Field operations is the discipline of making "out there" as visible as the warehouse.
The four field problems
| Problem | What it looks like | The discipline |
|---|---|---|
| Work you cannot verify | Jobs "completed" with no evidence; visits that may not have happened | Mobile job cards with photos, GPS stamps, and customer sign-off |
| Stock that travels | Van inventory that leaves full and returns empty-ish | Van stock as a location: loaded, sold/used, returned — counted at both ends |
| Assets in the wild | Tools, meters, and machines issued to crews and sites | Custody records per person and site, verified on a rhythm |
| The fleet itself | Fuel and repairs eating margins nobody computed | Cost per vehicle, fuel-to-distance reconciliation, service schedules |
Offline-first is the entry requirement
Field software that needs connectivity is office software with a battery. Kenyan field reality — county roads, basements, rural sites — means the system must capture everything offline and sync when the network returns: deliveries, job completions, stock issues, asset checks, payments. The test is simple: put the phone in airplane mode and run a full job. If anything blocks, the field team will revert to paper the first bad-signal Tuesday, and the system becomes a head-office fiction.
Van stock: the warehouse that drives away
- Each van is a stock location — loading is a transfer, not a hand-wave; the driver signs for quantities.
- Sales and deliveries from the van decrement van stock in real time (offline, syncing later).
- Evening return: remaining stock counted back; van variance = loaded − sold − returned, attributed to the route and the driver.
- Route profitability becomes computable: revenue minus van stock consumed minus the vehicle's daily running cost — per route, per day. The full treatment is in our van stock guide.
The evidence layer changes everything
A delivery with a photo, a GPS point, and a receiver's signature is not just proof against disputes — it changes field behavior the day it starts. Not because teams were dishonest, but because "the record is made where the work happens" ends the evening reconstruction where honest mistakes and quiet leaks both lived.
Jobs, crews, and the money they carry
- Job cards on the phone: scope, materials allocated, time on site, completion evidence, customer acknowledgment — one record from dispatch to sign-off.
- Materials against jobs: what each job consumed, so job costing is real and van stock reconciles — the same recipe logic manufacturers use, applied to installations and repairs.
- Field payments: cash and M-Pesa collected on-site recorded against the job or invoice at collection time, with the advance-and-liquidation discipline covering crew floats.
- Crew equipment custody: drills, ladders, test kits — issued to named people, returned or re-confirmed per job cycle.
The fleet: your most expensive employees
A van that costs KES 4,000 a day in fuel, wear, and financing needs to earn its route. Fleet discipline — fuel reconciled to distance, service on schedule, cost per vehicle per month — turns "the vehicles are expensive" into "route C doesn't pay and route A needs a second van". That is a management sentence instead of a complaint.
Your field operation is governed when
- Every job has evidence: photos, GPS, sign-off — captured on site, offline if needed.
- Van variances are computed nightly and attributed, not discovered at month-end.
- Every field asset has a named holder and a last-verified date.
- Fuel consumption reconciles to distance per vehicle, monthly.
- Route and job profitability are reports, not debates.
This is the operating pattern AWRA's field operations suite is built around — offline-first mobile, traveling stock, custody, and fleet, on the same governed platform as your warehouse and books.
Make "out there" visible
One route, one crew, one week — job cards, van stock, and evidence, running offline and reconciling nightly.
See AWRA for field operationsFrequently asked questions
Our field staff use basic Android phones. Is that enough?
Yes — offline-first mobile workflows are designed for ordinary Android devices, and photo-plus-GPS evidence needs nothing exotic. The constraint to plan for is charging and data discipline, not device cost.
How do drivers and crews take to being tracked?
Frame it accurately: the system records work, not people — job evidence protects crews from disputed deliveries and inherited shortages as much as it protects the company. Adoption follows the first time a driver is cleared of a customer dispute by their own GPS-stamped delivery record.
Can it handle cash sales from the van, not just deliveries?
Yes — van sales work like a mobile POS: sold from van stock, paid in cash or M-Pesa, recorded offline at the sale. The evening reconciliation then covers both stock and money per route, the same way a [shop closes its shift](/blog/retail-daily-close-mpesa).
What is the realistic rollout order?
Start where the leak is loudest: van stock for distributors, job cards for service businesses, custody for asset-heavy crews. One route or one crew first, two weeks of parallel running, then scale — field teams copy what visibly works for their colleagues.
