Logistics and fleet management system
Delivery tracking, invoice import, automatic WhatsApp notifications, proof of delivery and a fleet module with a live map.
- Year
- 2025
- Status
- In development (MVP)
- Context
- Packaging distributor with its own fleet · Client under NDA
The challenge
The distributor didn't know where each delivery was, and end customers called to ask. The fleet was tracked on paper: fuel, maintenance and driver hours with no searchable record.
The solution
Delivery tracking with per-stage status and proof of delivery captured on the driver's phone.
Invoice import to create deliveries without manual data entry.
Automatic WhatsApp notifications to the end customer on dispatch and on arrival.
Fleet module: live map, fuel control, maintenance and driver hours.
Architecture
Technical discovery and data modeling ran before the first line of code — deliveries, routes, vehicles, drivers and events as separate entities.
Supabase (PostgreSQL) for data and auth; MapLibre for mapping, with no proprietary licence dependency.
Next.js front-end with shadcn/ui, deployed on Vercel.
What I learned
The value here was in the modeling, not the screens. Getting the domain model right first is what let the fleet module land without a rewrite.