Fleet Management App Development: Tracking & Costs

How many separate apps does this need?

01

Driver mobile app (iOS + Android)

Vehicle handover checklist, photo-based damage reports, fuel receipt uploads, task and route lists, background location reporting, and queueing when there is no network coverage.
02

Fleet manager mobile app

Live vehicle map, geofence and idling alerts, inspection, insurance and maintenance reminders, driver violation notifications, and one-tap approval of vehicle assignments from the field.
03

Web admin panel

Vehicle records, document calendar, fuel and mileage reports, driver behaviour scores, telematics device pairing, permission roles, and cost breakdowns that feed accounting.

What the app includes

Vehicle handover form with four-side photos and odometer entry
Inspection and insurance alerts triggered by both date and mileage
Instant alert to the fleet supervisor when idling exceeds the threshold
Geofence entry and exit logs for depots, sites and customer yards
Fuel receipt photo posting litres and amount to the vehicle record
Toll and bridge charges (Turkey's HGS system) added to trip cost
Driver score from harsh braking, sharp cornering and speeding events
Tyre position, tread depth and seasonal changeover records
Location sharing that starts and stops with the driver's shift
Vehicle key assignment and full custody history per driver
Driver fault report flowing into service approval and work order
Next service date estimated from actual daily mileage

State of the sector

In haulage, shuttle transport, distribution and field service businesses, vehicles are the largest cost item after staff, and fuel and maintenance costs feed directly into contract pricing. Corporate customers now ask for trip tracking, arrival notifications and vehicle status reports at the tender stage, and smaller firms that cannot provide them get eliminated. As tracking hardware has become cheaper, the difference no longer lies in the device itself but in how the data is processed. In a fleet with no document calendar, a single missed inspection can leave a vehicle off the road for days and bring a fine; because those costs are never recorded, they also stay invisible.

Metrics that matter here

Fuel consumption per 100 kilometres (by vehicle and by driver) — Because the app measures idling, harsh acceleration and route deviation, you can see which driver and which route is driving consumption up.
Vehicle availability rate (days idle and days in the workshop) — When maintenance and inspection alerts arrive early, unplanned breakdown stoppages fall and vehicles spend fewer days in the workshop.
Daily idling time — Time with the ignition on and speed at zero is totalled automatically, turning into a measurable cost in fuel and engine wear.
Empty (unladen) mileage ratio — Combining trip records with location history lists the vehicles running empty on the return leg, so job planning can be corrected accordingly.

Common mistakes in this sector

Equating the project with the live map Dots moving on a map look impressive but produce no decisions on their own. The real value sits in the vehicle card, the document calendar, the cost reports and the driver handover form. The map should be built on top of that structure, not made the centre of the project.
Designing the driver app purely as a monitoring tool An app that offers the driver nothing gets switched off in the field, permissions get revoked and the data flow stops. Features that shorten the driver's work, such as route instructions, digital vehicle documents and receipt uploads, belong in the same app.
Storing raw location data indefinitely Each vehicle produces tens of thousands of points a day; as the data grows, reports slow down, costs rise and you accumulate a pile that is hard to defend under KVKK. Raw data should be reduced to daily summaries after a defined period.
Building the system around one device brand A system written against a single tracker brand's data format has to be rewritten the moment a different brand enters the fleet. Unless the device layer is abstracted behind parsers, every new group of vehicles becomes a project of its own.

Regulation and compliance

Vehicle location combined with driver identity is personal data under KVKK (Turkey's data protection law, aligned with GDPR); drivers must be clearly informed, tracking must be switched off outside working hours, and a reasonable retention period must be set for location history. In freight and passenger transport, UETDS (Turkey's transport tracking system) reporting obligations make trip notifications mandatory depending on the type of operating licence. For vehicles with digital tachographs, driver card data must be downloaded and stored regularly, and compliance with driving and rest periods is checked during inspections. Documentation of maintenance and fuel spending must comply with the e-Fatura (Turkey's mandatory e-invoicing system) and e-Arsiv framework.

The real challenges in this sector

Keeping the driver's phone reporting location through the whole shift

On Android a foreground service and a persistent notification are mandatory; aggressive battery optimisation on Xiaomi, Samsung and Oppo devices kills the service, so the user has to be shown a brand-specific permission screen. On iOS, background location permission and a distance filter are configured. Reporting triggered by a movement threshold rather than a fixed interval cuts battery drain dramatically during the hours the vehicle is parked.
Not losing location history when coverage drops

Data cuts out in tunnels, industrial zones and intercity dead spots. Location packets should be written to a local database on the device with a timestamp and sent in bulk once the network returns; the server side needs a unique record key to guard against the same packet arriving twice. Otherwise the same route is drawn twice and the mileage report is inflated.
Drawing an eight-hour route on a map without freezing

A single vehicle generates tens of thousands of location points over a shift; rendering all of them locks up the app on mobile. The point count is reduced on the server with Douglas-Peucker style simplification, the trace is map-matched to the road network, and raw points for a region are fetched as the user zooms in. The raw data is kept in a separate time-series table for reporting.
Reducing different tracker brands to a single model

Most fleets carry several brands of tracking device bought at different times, and each speaks its own protocol. A separate parser is written per device and translated into a shared event model: location, ignition, speed, fuel level, harsh braking. That way, adding a new brand never touches the app or the panel.
Not confusing fuel loss with idling

A drop in the fuel level sensor does not on its own mean theft; gradients, sloshing and temperature all produce false drops. A threshold that weighs ignition state, speed, location and the rate of the drop together is needed, and fleet card spending must be matched to tank increases by time and location. Refuellings that do not match show up as a separate list in the panel.

Required integrations

Telematics and GPS hardware (protocols for devices such as Teltonika and Concox) with CAN-bus/OBD-II data reading
UETDS (Turkey's transport tracking system) trip and haulage notifications
Digital tachograph and driver card data downloads for driving and rest time compliance checks
Import of fleet fuel card statements (Opet, Shell, Petrol Ofisi and similar Turkish fuel networks)
Matching HGS/OGS motorway toll records (Turkey's electronic toll systems) to vehicles and trips
Transfer of maintenance, fuel and trip costs to e-Fatura (Turkey's mandatory e-invoicing system), e-Arsiv and pre-accounting software

Who this page is for

Regional haulier or distributor with ten to twenty vehicles

The priority is not a live map but vehicle records, a document calendar, fuel logging and trip cost. Phase 1 alone is usually enough; telematics and mandatory transport reporting follow as the fleet grows.
Field-service business running its own technician vans

Here the van carries the work order. Job lists, time on customer site measured by geofencing and parts held in the vehicle matter most; fuel loss and driver scoring come second.
Newly founded rental or urban delivery venture

Starting from zero, handover forms, damage photos and custody history must be right from day one, and arrival notifications plus vehicle status reports for corporate clients belong in scope early.

A phased plan that splits the budget

1

Phase 1 — Vehicle records, document calendar and driver app 6-8 hafta

Vehicle and driver records, an inspection-insurance-service calendar with alerts, plus a driver app for handover checklists, damage photos, fuel receipts and odometer entry. It runs on its own without any telematics hardware and already ends missed inspections and unattributed fuel spend.
2

Phase 2 — Location, route history and geofencing 4-6 hafta

Background location from the driver's phone, offline queueing when coverage drops, simplified route history, a live map and geofence entry/exit logs. Because Phase 1 already defined vehicles and shifts, every location point can be tied to the right vehicle and the right driver.
3

Phase 3 — Telematics devices, cost and compliance integrations 4-6 hafta

Tracker protocols mapped into one event model, ignition, fuel level and fault-code reading, idling and driver scoring, fuel-card statement matching, U-ETDS trip reporting (Turkey's mandatory transport notification system) and cost export to accounting. Hardware spend comes last on purpose: the first two phases show which vehicles actually need a device.

Typical scope and timeline

Typical scope: vehicle and driver records, document and maintenance calendar with alerts, driver mobile app (handover checklist, damage photos, fuel receipts, background location), manager mobile app, and a web panel with a live map, route history, idling and mileage reports and role-based permissions. Telematics device integration, UETDS reporting and fleet card reconciliation are added in a second phase. Scope and budget are set after a scoping call.

Estimated timeline: 12-18 weeks

Off-the-shelf or custom build?

Topic	Off-the-shelf	Custom build
Hardware lock-in	A tracker vendor's own portal ships with its hardware and works on day one, but once another brand enters the fleet you end up watching two separate portals.	The device layer is written as a parser: different tracker brands are normalised into one event model, so the panel stays the same as the fleet changes.
Sector-specific workflow	Standard needs such as tracking, document dates and idling are already well covered off the shelf; rebuilding them from scratch is usually wasted money.	The difference shows in your own flows: material issued to a site tied to vehicle custody, or a field team's work order and trip record living on one screen.
Monthly subscription and per-vehicle fees	With few vehicles the monthly per-vehicle fee looks small and needs no upfront outlay; as the fleet grows it turns into a permanent fixed cost.	Custom development is largely a one-time cost; as vehicles are added you scale servers and maintenance, not licences.
Data ownership and portability	In a packaged system years of route, fuel and service history sit in the provider's database; if the contract ends, the export is only as complete as the provider allows.	The database belongs to the business; raw location retention, deletion rules and the data-protection rationale are set as your own policy.

Sector glossary

Idling: Time with the ignition on and the vehicle stationary. It builds up while waiting to load or running the air conditioning, and is measured as fuel and engine hours per driver and route.
Geofence: A virtual boundary drawn on the map around a depot, site or customer yard. Entry and exit are logged and notified automatically, which settles arguments about arrival times.
CAN bus / OBD-II: The access point to the vehicle's own electronics. Odometer, ignition state, engine fault codes and on some vehicles fuel level come from here, which is exactly the data a phone can never supply.
Empty (deadhead) mileage: Distance driven without load or job, usually on the return leg. Matching trip records with route history reveals which lanes are regularly run empty.
Total cost per vehicle: Fuel, service, tyres, insurance, fines and tolls added up for a single vehicle. It is the figure used to compare leasing with buying and to decide which vehicle to retire.

Frequently asked questions

Can we track a fleet with phones alone, without fitting tracking devices to the vehicles?

You can, but there are limits. The driver's phone gives you location and route and carries trip and delivery records; what it cannot give you is ignition state, real fuel level, engine fault codes or vehicle odometer readings. For light commercial fleets and service teams, the phone alone is usually enough. If you need to monitor fuel loss, the cost of idling or refrigerated vehicle temperatures, a device wired into the vehicle is required.

Will drivers actually use an app they know is tracking them?

Adoption depends on the tracking being limited to the shift and visible while it happens. The driver's screen should clearly show that location reporting is on, and reporting should stop when the shift ends. The app also has to give the driver something back: route instructions, digital copies of vehicle documents, freedom from photographing fuel receipts and handing them over in person, and transparent records of bonuses and overtime. Apps built purely as a monitoring tool get switched off in the field.

How does inspection, insurance and maintenance tracking work in the app?

For each vehicle, the dates for the roadworthiness inspection, compulsory traffic insurance, comprehensive insurance, emissions test, operating licence and tyre changes are recorded on the vehicle card. The system raises alerts by both date and mileage; scheduled servicing is usually mileage-based, and the daily distance derived from location data lets you forecast the service date. Alerts reach the fleet supervisor as notifications and as an upcoming-jobs list in the panel.

Can we reconcile fuel card spending through the app?

Yes, and the typical setup is this: the fuel company's fleet card statement is imported into the system, and each refuelling record is compared with the vehicle's position at that moment using the time and the station location. If the vehicle was in another city at that hour, or no increase in the tank is visible, the record is flagged as suspect. Cost per litre and consumption per hundred kilometres are also reported broken down by vehicle and driver.

Does this investment make sense for a small fleet?

Even in a fleet of fifteen to twenty vehicles, tracking runs on hand-kept spreadsheets: inspection dates slip, idling stays invisible, and whose shift the damage occurred on becomes a matter of debate. For a small fleet the priority is not the live map but the vehicle card, document calendar, fuel records and driver handover form. The scope can start with that core and leave telematics integration and behaviour scoring to a later phase.

How long do we need to keep location data?

Where the regulations do not name a specific number of days, the business itself has to justify the retention period. The common approach in practice is to hold raw location points for a limited window, then reduce them to daily summaries of mileage, consumption and violations. That satisfies the proportionality expectation in KVKK (Turkey's data protection law, aligned with GDPR) and lowers database costs at the same time. The retention period and deletion rule should be written down at the start of the project and enforced automatically by the system.

Other sectors

All sectors →

Seeing where a vehicle is does not mean the fleet is being managed

How many separate apps does this need?

Driver mobile app (iOS + Android)

Fleet manager mobile app

Web admin panel

What the app includes

State of the sector

Metrics that matter here

Common mistakes in this sector

Regulation and compliance

The real challenges in this sector

Keeping the driver's phone reporting location through the whole shift

Not losing location history when coverage drops

Drawing an eight-hour route on a map without freezing

Reducing different tracker brands to a single model

Not confusing fuel loss with idling

Required integrations

Who this page is for

Regional haulier or distributor with ten to twenty vehicles

Field-service business running its own technician vans

Newly founded rental or urban delivery venture