Back to Case Studies
Web AppLogisticsCustomer Portal

Logistics Delivery Tracking Portal

Provided transparency to customers and streamlined driver dispatching.

Client
Private Logistics Firm
Role
Architecture & Development
Timeline
4 Months

The Context

A regional B2B logistics company with 25+ drivers and hundreds of deliveries per day was handling a large volume of "Where is my order?" calls. Customers had no way to track shipments; they had to call the office, which then had to call or message drivers. The company served manufacturing and distribution clients who needed reliable ETAs and proof of delivery for their own operations.

The Challenge

"Dispatchers were manually assigning routes using whiteboards and WhatsApp. Drivers had no unified way to update statuses—some used WhatsApp, some called in—so the office often had incomplete or stale information. Customers were left in the dark until delivery occurred, and failed deliveries or address issues were only discovered after the fact. Proof of delivery was paper-based and often lost or delayed."

The Solution

We created a comprehensive logistics suite: a customer-facing tracking portal where clients can see all their shipments and ETAs, an admin dispatch dashboard for assigning loads and viewing driver status, and a mobile-responsive driver interface so drivers can update statuses and capture proof of delivery from the road without installing a native app.

Customer Portal

  • Secure login to view all active and past shipments with search and filters
  • Real-time status tracking and estimated delivery windows
  • Automated email and SMS notifications at key milestones (dispatched, in transit, out for delivery, delivered)
  • Digital proof of delivery: signature and optional photo visible in the portal
  • Downloadable shipment history and POD for accounting and disputes

Admin & Dispatch

  • Visual dashboard for route assignment, load sequencing, and driver availability
  • Driver mobile interface for status updates (Picked Up, In Transit, Delivered) and notes
  • Exception handling: delays, failed attempts, address changes, with timestamps and notes
  • Map view of active routes and last-known driver positions (milestone-based, not live GPS)
  • Reports on on-time delivery rate, exception reasons, and driver performance

System Interface

Customer shipment tracking view

Customer shipment tracking view

Admin route assignment dashboard

Admin route assignment dashboard

Driver mobile status update interface

Driver mobile status update interface

Digital proof of delivery capture

Digital proof of delivery capture

Business Outcomes

Reduced customer inquiry calls by 70% as clients could self-serve tracking and POD

Improved dispatch efficiency, allowing the same team to handle 50% more daily routes

Eliminated paper delivery manifests and paper POD; everything digital and auditable

Faster dispute resolution with instant access to proof of delivery and status history

Architecture Notes & Lessons

We initially over-engineered the driver tracking by attempting continuous GPS polling. We pivoted to a milestone-based status update system (e.g., Picked Up, In Transit, Delivered) which saved battery and data for drivers and was sufficient for customer transparency. For future projects we would validate "good enough" tracking with customers before investing in real-time GPS.

Architecture

A Node.js/Express backend serves as the central hub, with MongoDB storing flexible shipment documents (waybills, status history, POD). The React frontend uses a mapping provider to visualize routes and driver positions based on status updates rather than continuous GPS. Twilio powers SMS notifications; email is sent via a transactional provider. We avoided constant GPS streaming to keep driver battery and data usage low.

Tech Stack

Frontend
ReactViteTailwind CSS
Backend
Node.jsExpressMongoDB
Infrastructure
Google Cloud RunMongoDB Atlas
Integrations
Google Maps APITwilio (SMS)