Modernized a Fleet Management App for a Jeddah Logistics Company to Improve Vehicle Utilization by 32%

The company already had GPS devices. We retained the current tracking setup and changed how the app used the location details.

Previously, the map showed the positions of vehicles without context. The updated dashboard displays tracking information alongside the assigned trip.

• GPS data received through compatible telematics provider APIs
• Latest vehicle location displayed on Google Maps
• Trip start and completion events linked to vehicle movement
• Depot entry and exit recorded through geofencing
• Extended stops flagged for review
• Route deviations visible against the assigned journey
• Historical location records available to authorized managers

Tracking updates are delivered to the web console through WebSockets. The dashboard uses the latest available device information rather than assuming that every vehicle is reporting continuously.

The dispatch team had been relying on familiar vehicles when assigning trips. That worked on quieter days, but it left some trucks underused when shipment volumes increased.

We introduced allocation checks into the existing dispatch workflow. Before confirming a trip, the fleet management app checks vehicle availability and load capacity. It also checks whether the proposed assignment overlaps with another journey.

• Existing trip schedule verification
• Reassignment when a vehicle becomes unavailable
• Daily and weekly vehicle usage reports
• Idle vehicles highlighted in the dispatch console

Utilization reporting was configured around the company's agreed measurement method. Managers could compare actual vehicle usage instead of relying only on the number of trips completed.

This gave fleet managers a better way to identify vehicles that were spending too much time without assignments. Dispatchers could also check capacity and existing bookings before assigning another trip. It reduced the need to make allocation decisions using separate spreadsheets.

Drivers had an older mobile interface that wasn't well suited to reporting problems during a trip. Some updates were still sent through phone calls and messages.

We changed the app around the tasks drivers handled most often. They could check their assigned vehicle and report trip progress without moving between different screens.

• Daily assignments with vehicle details and pickup instructions
• Trip start and completion updates
• Pre-trip inspections with photographs
• Breakdown reports and driver notes
• Offline updates when mobile coverage drops

SQLite stores pending updates on the device. Once the connection returns, the app sends those records to the backend.

Each submission carries a unique event ID. Repeated uploads are checked so the same inspection or trip update isn't recorded twice.

Fuel expenses were being reviewed separately from trip activity. That made it difficult to identify which vehicles were consuming more fuel than expected.

We connected fuel transaction records with vehicle IDs and completed journeys. The application calculates consumption indicators using the fuel and distance information available.

• Distance travelled between refuelling events
• Consumption reports by vehicle
• Unusual fuel usage flagged for investigation
• Monthly fuel cost summaries
• Expense information shared with the ERP where supported

The system does not automatically label unusual consumption as misuse. Fleet managers can review the trip history and fuel records before deciding whether further checks are needed.

Completed trip counts didn't explain much about how a vehicle had been operated. Managers needed more information when investigating delays or repeated idle periods.

The modernized application uses available GPS and telematics events to prepare driver activity reports.

• Completed trips and idle time by driver
• Route deviations and extended stops
• Driver-reported incidents
• Weekly driver activity reports

The reports help managers review particular trips and identify where additional driver training may be useful.

We configured background jobs to check fleet activity and send alerts according to the event type.

• Upcoming vehicle service reminders
• Overdue maintenance alerts
• Extended idle vehicle notifications
• Vehicle breakdown reports
• Depot geofence events
• Changes to trip assignments
• Scheduled fleet utilization reports

Redis and BullMQ manage these jobs. Repeated events are checked to avoid sending the same alert several times. The alerts helped dispatchers see when a vehicle needed maintenance before assigning it to another delivery. Fleet managers could also follow up on overdue service records without checking workshop spreadsheets separately.

The ERP was not replaced during modernization. It remained responsible for transport orders and financial records.

We updated the integration between the fleet app and the ERP so that vehicle assignments and completed trip information could be linked to the relevant transport order.

• Transport order references imported through APIs
• Trip IDs linked to existing order records
• Completed journey information returned to the ERP
• Fuel and maintenance expenses shared where supported
• Failed requests placed in retry queues
• Duplicate updates checked before processing
• Integration errors recorded for support teams