What is FleetFlow?
FleetFlow is AtashiTech's fleet management software for operators in India who run vehicles, drivers and deliveries at a scale where a phone call is no longer a control system. It covers the full logistics loop: consignment bookings and the documents that travel with them, route planning, dispatch to drivers, live GPS tracking, telematics from the vehicle itself, proof of delivery and the reporting that follows a completed run.
It is built for two kinds of user. The first is an enterprise that operates its own fleet, whether that is a manufacturer's outbound trucks or a distributor's delivery vans. The second is a third-party logistics provider that manages vehicles and shipments on behalf of several customers at once and has to show each of them only their own consignments. FleetFlow runs as a web control tower with a driver mobile app and an IoT layer for vehicle data, on .NET 10, Angular and PostgreSQL, with SignalR pushing updates to the screen and MQTT carrying telemetry in from the road.
Three problems FleetFlow is built to remove
Fleet management software earns its place when the cost of not knowing where a vehicle is, or why a delivery slipped, becomes larger than the cost of a system. FleetFlow is aimed at three situations that recur across Indian road logistics.
Enterprises running their own delivery fleet
A manufacturer or distributor with its own trucks usually plans routes from memory, tracks progress by calling drivers and learns about a late delivery when the customer complains. FleetFlow gives the dispatcher a live map, a dispatch board and an exception list, so the day is managed from the screen rather than from the phone.
3PL and contract logistics providers
A logistics provider serving several clients needs each client to see only its own shipments while the operations desk sees everything. The control tower separates client fleets under one login and gives each client a white-labelled tracking portal, which removes the daily round of status calls and emails.
Operators who lose disputes for lack of evidence
Damaged consignment, wrong address, nobody at the door: without a timestamped signature, a photo and a location, the operator pays. FleetFlow attaches electronic proof of delivery to every drop and supports an OTP-based handoff where the identity of the receiver matters.
How the fleet management software runs a working day
A day in FleetFlow passes through four stages. Each stage feeds the next, and every event is written to the shipment record so that the analysis afterwards is built on what actually happened.
Import and plan
Bookings arrive by CSV upload, by API from an order or warehouse system, or are keyed in by the booking desk. The route solver clusters stops, assigns vehicles by capacity and builds conflict-free manifests that respect delivery windows, driver shift limits and live traffic.
Dispatch to drivers
Manifests are pushed to the FleetFlow mobile app. The dispatch board shows every assignment as a drag-and-drop card with conflict detection, and the customer receives an SMS when the vehicle is dispatched and again if the estimated arrival changes.
Track and react
Vehicle positions stream over MQTT into the control tower. Geofence alerts fire when a vehicle enters or leaves a zone, harsh braking, speeding and idle events are logged against the driver, and cargo temperature and fuel level are read from the telematics unit where one is fitted.
Prove and analyse
At the door the driver captures a signature, a photo or an OTP, and the delivery record closes with time and location. After the run FleetFlow surfaces route-efficiency scores, exception reports and driver rankings, and pushes audit-ready exports to the ERP as PDF, CSV or webhook.
What the platform covers
The modules below are what an operator gets as standard. They share one shipment record, one vehicle record and one driver record, which is what lets a dispute, a fuel query and a customer complaint be answered from the same screen.
Bookings and documentation
Consignment booking, shipment identifiers and the paperwork that accompanies the goods, held against the shipment from pickup to delivery and available to the customer on the tracking portal.
Live GPS tracking
Real-time position on a map with filters by driver, zone and delivery window, and geofence alerts for depots, hubs and customer sites so an unplanned stop is visible as it happens.
Route optimisation
A multi-stop solver that balances delivery windows, vehicle capacity and shift limits against live traffic, with the aim of fewer kilometres per delivery and fewer missed windows.
Dispatch board and scheduling
Drag-and-drop assignment with conflict detection, and automatic customer notifications on dispatch and on any change to the estimated arrival, without code or configuration by the dispatcher.
Driver app and proof of delivery
Manifests, stop-by-stop status updates and e-signature, photo or OTP capture at the point of delivery, all attached to the delivery record in real time.
Driver performance scorecards
Automatic scoring of each trip on safety events, fuel efficiency and on-time rate, with coaching reports sent to each driver so the conversation is about data rather than opinion.
3PL control tower
Multi-client visibility for logistics providers, with each client's shipments segregated under one operator login and a white-labelled tracking portal per client.
Telematics and IoT
Engine diagnostics, fuel level, tyre pressure, cargo temperature, door sensors, odometer and idle time ingested over MQTT from OBD-II dongles or the OEM telematics hardware already on the vehicle.
Platform, integrations and deployment
FleetFlow's back end is .NET 10 over PostgreSQL. The control tower is an Angular web application, SignalR pushes live updates to the browser, and MQTT carries vehicle telemetry in from the road. The driver app runs on mobile, and the IoT layer accepts data from the OBD-II dongles and OEM telematics units an operator already has fitted, so the software does not dictate the hardware.
Integration with an existing order-management, warehouse or ERP system is by REST API on the way in and webhook on the way out; for NexERP users the outbound shipment link is scoped as part of the implementation. The application is packaged for container deployment, and hosting, environments and monitoring are set up by our cloud, DevOps and integration team as part of the engagement.
Industries that run on fleet management software
Road logistics in India spans everything from a three-van distributor to a national contract carrier. These are the settings where FleetFlow is a fit, and where a kiosk solution or another AtashiTech product sits naturally beside it.
Third-party logistics
Contract logistics providers use the control tower to run several client fleets at once and give each client a tracking portal instead of a daily status email.
FMCG and distribution
Distributors with fixed beats and hundreds of retail drops a day use route optimisation to shorten runs and proof of delivery to settle short-delivery claims quickly.
Cold chain
Pharmaceutical and food distributors read cargo temperature from the telematics unit and receive an alert while there is still time to act on the load.
E-commerce last mile
Brands that fulfil their own orders link FleetFlow to their storefront; for NexCommerce users that link is scoped in the same engagement, so an order becomes a booking without re-keying.
Manufacturing outbound
Plants dispatching finished goods use bookings and documentation with the ERP, and can pair the depot gate with a contractor induction and site access kiosk so visiting drivers are inducted before they enter the yard.
Depots and loading bays
Where trucks queue for bays, a queue management and token kiosk at the gate gives each driver a numbered slot and the yard a live display board, a natural companion to the dispatch board inside.
Implementation, customisation and support
An engagement begins with the operator's own data: vehicles, drivers, depots, customers and a sample of a typical day's bookings. We configure the fleet, zones and delivery windows, connect the telematics units in use, load routes and run a parallel period in which FleetFlow shadows the existing process before dispatch is switched over. Drivers are trained on the mobile app in their own vehicles, on their own routes, rather than in a classroom.
Because AtashiTech develops FleetFlow, changes to the product are in scope. A client-specific tariff structure, a custom manifest layout, an integration with a customer's portal or a report in the format a regulator asks for can be built into the platform rather than worked around. Where a customer-facing tracking experience needs its own design, our UI/UX design team handles it, and the driver app is maintained by our Android and iOS app development practice.
After go-live the system runs under an annual maintenance contract with monitoring, updates and support, described on the Software Consulting and AMC Support page. Every engagement is scoped and quoted individually on the size of the fleet, the integrations and the telematics involved; we publish no list prices. More on fleet operations, depot self-service and the fleet management software behind them appears on the AtashiTech blog.
Talk to us about your fleet
Tell us how many vehicles you run, where they go and what goes wrong on a normal day, and we will walk you through that same day inside FleetFlow. Reach us through the contact page, or see the rest of our products and services.