Fleetark
Logistics · by Oadbox
Run your entire fleet on one platform
Vehicles, drivers, trips, billing, compliance and HR — with an offline-first app for the people on the road.
At a glance
- 24 built-in reports
- Offline-first driver app
- 48 permission keys
Built for
Commercial fleet and logistics operators running mid to large fleets.
Live at
fleetark.comThe problem
Used by dispatch desks, drivers and the workshop.
Fleets know revenue to the rupee and cost only approximately. Tracking — which is what most fleet software sells — answers neither, and the gap between the two is where the margin goes.
Fleetark replaces the spreadsheets, WhatsApp groups and standalone GPS portals that fleet operators stitch together. Vehicles, drivers, trips, invoices, compliance documents and payroll sit in one place.
The driver app is offline-first, because coverage on a highway is not a feature you can assume. It queues everything and syncs the moment there is signal.
A day on Fleetark
One ordinary Thursday, yard to ledger
Fleet software gets bought in an office, but it earns its keep in the yard before dawn, on a stretch of highway with no bars on the phone, and at the billing desk on the last day of the month. This is where Fleetark sits in a working day.
What we counted first
Fleetark began the way every Oadbox product does — standing in yards at loading time and sitting behind the dispatch desk with a notebook. Four numbers kept coming back:
6
Places one trip got written
The trip sheet, the GPS portal, the dispatcher's WhatsApp group, an Excel tracker, the invoice file and the ledger. One journey, six entries, none of them agreeing by Friday.
70
Location calls before lunch
Consignors, branch offices and the owner, all asking the dispatch desk where a lorry had reached — answered by ringing the driver and hoping he picked up.
11 days
From unloading to invoice raised
Billing waited for the trip sheet to travel back in a driver's bag, usually behind two more trips. Receivables aged for no reason but paperwork.
₹42,000
A year of avoidable fines
One lapsed permit and a fitness certificate found at a check-post rather than in a diary — and then the day the lorry stood still.
Counted on our own early yard and dispatch-desk visits, before Fleetark existed. Every operator differs — your numbers are the first thing we ask about.
- 5:20 am
The yard
The yard is still dark when the first lorries are allotted. The dispatcher works down the vehicle list rather than the wall board — this one is loaded and ready, that one is due for service, the third has no driver reporting until eight. Each allotment goes onto the vehicle's own record, not onto a scrap of paper that lives in a shirt pocket.
- 7:05 am
The dispatch desk
Six trips are dispatched before the shift meeting — vehicle, driver, route and consignor on each one. From the moment a trip opens, the office can watch it move: progress along the route, halts where they happen, completion when it comes. Nobody types a registration number into a separate GPS portal to find out where a lorry is.
- 10:30 am
The compliance file
The compliance screen throws up two warnings on the same lorry: the fitness certificate expires in nine days, the national permit a fortnight after that. Both would once have surfaced at a check-post, with the vehicle loaded. The workshop slot is booked this morning instead, while the lorry is between trips and the yard can spare it.
- 1:40 pm
The dead stretch
Past the state border the bars drop to nothing and stay there for the better part of an hour. The driver still marks the halt, enters the diesel he took at the bunk and closes the leg — the app holds it on the phone. Coverage returns short of the next town, everything uploads on its own, and the dispatch desk sees the halt it had been waiting for.
- 4:15 pm
The workshop
The lorry booked this morning goes into the workshop for its fitness work. Parts, labour and the date go against the vehicle's own record, so the next person who asks when the brakes were last relined reads it off the vehicle instead of asking the mechanic to remember. The renewed certificate is filed on the same record.
- 6:40 pm
The billing desk
The trip the driver closed on the highway is already on the billing desk, so the invoice goes out this evening rather than the week the trip sheet finds its way home. The load crossed a state line, so IGST applies and the customer's TDS is shown on the face of the bill. The clerk corrects a rate; the correction carries her name and the time.
- Month-end
The accounts desk
Driver payouts are worked out on the days actually run, with trip allowances beside them, so nobody reconstructs a month from attendance chits at eleven at night. And the review the owner sits for — margin by route, vehicle utilisation, diesel, what is still owed — is a screen someone opens rather than a week someone spends.
What quietly disappears
None of it is dramatic. It is the same operating day — minus the artefacts everyone had stopped noticing.
The trip sheet that travels home in a driver's bag
The dispatcher's WhatsApp group used as a tracking screen
The diary of permit and fitness expiry dates
The standalone GPS portal with its own login
The Excel tracker rebuilt every Monday morning
Key workflows
What it actually runs.
Vehicles and drivers
Complete masters with documents, servicing history and assignment tracking.
Trips with live GPS
Dispatch, route progress, halts and completion, visible to the office as it happens.
GST-ready invoicing
CGST, SGST and IGST handling with TDS and TCS support built into billing.
Compliance alerts
Automated warnings before insurance, permits, fitness certificates and licences expire.
HR and payroll
Attendance-based prorating, allowances and payouts for drivers and staff.
Offline-first driver app
A Flutter app that works without signal and syncs automatically when it returns.
Full audit trails
Field-level change tracking across the platform, plus a super-admin console.
24 reports out of the box
Trip profitability, vehicle utilisation, fuel, and receivables without custom work.
Why Oadbox
We know the industry
Fleetark was designed inside logistics operations, not adapted from a horizontal tool.
How logistics worksIt runs on our core
Tenancy, permissions, statutory compliance, offline mobile and audit trails are inherited, not rebuilt for each product.
Inside the platformWe still operate it
The team that built Fleetark runs it — monitoring, support, releases and the next version.
How we workMore from Oadbox
11 other products, same foundation.
Want to see Fleetark on your own data? That is the only demo worth having.
Thirty minutes with someone from the product team — how you work today, and an honest answer on whether this fits.