Loading…
Loading…
Book, dispatch, track and get paid on one connected system — with driver and customer apps that keep working when the network doesn't.
Free, no-obligation consult — just a real person.
Official ERPNext Partner
In business since 2011 · 200+ clients
It's 6:40 in the morning and the phone at the dispatch desk hasn't stopped. A customer wants a cab to the railway station in twenty minutes. The dispatcher scans a paper roster, calls two drivers who don't pick up, reaches a third who may or may not be closer, and writes the trip into a register. Somewhere out on the road a driver has finished three trips, collected cash for two of them, and nobody at the office will know until he comes in at the end of the day. The customer, meanwhile, has no idea where the cab is — so she calls again. And again.
That was the operating reality at Kera Cabs, a regional taxi service based in Kannur, Kerala, offering a range of vehicle options and handling thousands of trips monthly on a reputation built around safety, punctuality and reliable customer support. The demand was there. What wasn't there was a single system tying booking, dispatch, tracking and payment together — so growth meant more phone calls, more registers, and more places for a trip to go missing.
Acube, an Official ERPNext Partner, delivered an end-to-end platform: ERPNext configured for fleet, CRM, dispatch, billing and accounting, plus two cross-platform Flutter apps — one for customers, one for drivers — built to keep working offline and sync the moment a signal returns. Bookings now flow to the nearest available driver automatically, dispatchers and customers watch the vehicle move on a live map, and the invoice is generated against the trip rather than reconstructed from a register at closing time.
In business since
Clients served
ERP projects
Work by referral
| Client | Kera Cabs |
| Location | Kannur, Kerala, India |
| Industry | Land transportation & ride-hailing |
| Engagement | ERPNext implementation + Flutter customer and driver apps |
for booking, dispatch, tracking and payments — four separate habits held together by phone calls.
, from allocating a driver to raising the bill.
the office found out what happened after it had happened.
for either customers or drivers, in a business that lives entirely on the road.
, which ruled out any solution that assumed a live network. > The cost of staying as-is: in a taxi business, every minute between the call and the confirmed pickup is a customer deciding to try someone else — and every trip that isn't captured at the point of service is revenue you have to chase.
An end-to-end solution designed around how a taxi operation actually runs — the workflow first, then the configuration and the apps to match:
| Capability | What it gives you |
|---|---|
| ERPNext core — fleet, CRM, dispatch, billing, accounting | One centralised system holding bookings, invoices, routes and driver assignments, so the office works off a single record instead of four |
| Customer app (Flutter) | Customers book their own rides, follow the driver's ETA on a live map and manage payments — without calling the desk |
| Driver app (Flutter) | Drivers accept assignments, log trips, update status, capture signatures and collect payments from the vehicle |
| Booking & dispatch workflow | Automated assignment of the nearest available driver, scheduled pickups and drop-offs, and electronic invoices generated against the trip |
| Real-time GPS tracking | Dispatchers and customers both see vehicle location live during the trip — no more "where is he now?" phone calls |
| Integrated payments | Cash and digital payments supported, with automated receipt issuance and backend reconciliation |
| Offline-first design | Status updates and route logging keep working without connectivity; data syncs automatically once the device is back online |
| Training & deployment | Comprehensive training for dispatchers and drivers, so the switch-over landed as an operational change, not just a software install |
See it on your fleet: Call +91 62358 66111 or WhatsApp us.
one place to see what has been booked, who is on it and what state it's in.
through GPS tracking, so trips are evidenced rather than reported.
, with receipts issued at the point of service and reconciled at the back end.
on the back of app-based booking and ETA tracking — customers can see the cab coming instead of ringing to ask.
, because a weak signal no longer stops a driver from logging a trip or updating a status.
the fleet can grow and new features can be added without going back to the drawing board. The underlying shift is simple: the trip record is now created where the trip happens, by the person doing it, on a device in their hand — and everything downstream, from the customer's ETA to the invoice to the accounts, is a consequence of that record rather than a re-typing of it.
We didn't start with modules. We started with the dispatch desk: how a booking arrives, how a driver is chosen, what the driver has to do at pickup and at drop, and where the money changes hands. Only then did we configure ERPNext and design the two apps around those moments.
Two decisions carried the project. The first was building offline-first from the outset rather than bolting it on — in an operating area with patchy coverage, an app that needs a live connection to log a trip is an app drivers will stop using by the second week. The second was training dispatchers and drivers properly before go-live, in their own workflow, which is why adoption stuck instead of the old register quietly reappearing on the desk.
And we didn't leave at go-live. As an Official ERPNext Partner in business since 2011, with 70% of our work coming by referral, we stay on afterwards — because a live fleet system needs to keep pace with the fleet.
Official ERPNext Partner
It runs the operation. At Kera Cabs we configured fleet management, CRM, dispatch, billing and accounting as one system, so a booking, the driver assigned to it, the route, the invoice and the accounting entry are all the same record rather than five disconnected ones.
Nothing stops. Both apps were built offline-first: drivers can update trip status and log routes without a live connection, and the data syncs automatically once the device is back online. That was a design requirement from day one, not a later patch.
Yes, and they do different jobs. The customer app is for booking, live ETA tracking and payment; the driver app is for accepting assignments, logging trips, capturing signatures and collecting payment. Both were built in Flutter, so each runs on Android and iOS from a single codebase.
Automatically, to the nearest available driver, with scheduling for pickups and drop-offs. The dispatcher stays in control and can intervene, but the default path no longer depends on someone working a phone list.
Both are supported, with automated receipt issuance and reconciliation at the back end. Cash collected in the vehicle is recorded against the trip at the moment it's taken, which is what makes end-of-day reconciliation quick instead of forensic.
No. ERPNext is modular, so you can start where it hurts most — usually booking and dispatch — prove the value, then add tracking, payments, accounting or apps at your own pace. The architecture is the same whether you run twenty vehicles or two hundred.
Get a clear plan, an honest timeline, and a fixed scope. Talk to a real expert today — whether or not you work with us.
Kochi (Kadavanthra & Infopark) · Thiruvananthapuram · across India & overseas · In business since 2011