Case study 02 · Mobility operations
Connected fleet and rental operations
One system for bookings, vehicle availability, payments, GPS events, owner earnings, and reconciliation.
Multi-surface system specification · Client name withheld
Challenge
Rental and fleet businesses juggle customers, vehicles, drivers, owners, payments, maintenance and live location, often across separate tools and manual reports.
Keep bookings, leases, payments, vehicle status, safety alerts and owner revenue consistent in one model, and give each role its own view.
System response
Shared vehicle and transaction records sit behind separate customer, driver, owner and admin views. Booking, payment, return, GPS, loyalty, maintenance and reconciliation are mapped end to end.
- Bookings
- Payments
- GPS events
Product scope
- Rental booking and monthly lease lifecycles
- Vehicle availability and conflict checking
- Local and card payment orchestration
- GPS tracking, geofences, and behaviour alerts
- Owner revenue and payout visibility
- Maintenance, loyalty, support, and admin reporting
System architecture
Role-aware entry points separate customer, driver, owner, and admin work.
Bookings and leases reserve the same fleet inventory.
Payments reconcile against rentals, deposits, leases, and refunds.
GPS events feed alerts and operational status.
Reports combine utilisation, revenue and exceptions.
Observable outcome
What the product and its repository show. These are not confidential client figures.
A coherent model for web, admin, and field-facing experiences
Traceable money movement from customer payment to owner payout
Exceptions shown next to the workflow they affect
Repository evidence
- Complete relational schema and workflow documentation
- Role-specific dashboard specifications
- Payment, tracking, maintenance, and reconciliation contracts
Built with
- Next.js
- TypeScript
- PostgreSQL schema
- Payment interfaces
- GPS interfaces