Illustrative engagement — describes the type of work we deliver; client details are withheld.
Business challenge
Customers called support for shipment status because tracking updates arrived hours late and were often incomplete.
Existing environment
- Status updated by batch file transfers
- Separate systems for hubs and drivers
- No customer-facing tracking API
Technical challenges
- Ingesting events from drivers with patchy connectivity
- Reconciling events from multiple hubs
- Scaling for seasonal volume
Our approach
- 1Built a driver app with offline-first event capture
- 2Created an event-driven tracking service
- 3Exposed tracking APIs for customers and partners
- 4Automated infrastructure and deployments
Architecture overview
- CaptureReact Native driver app and hub scanners
- EventsKafka topics with idempotent consumers
- ServicesSpring Boot tracking and notification services
- AccessCustomer portal and partner REST APIs
Technologies used
- Java
- Spring Boot
- Kafka
- PostgreSQL
- React Native
Implementation
- Phase 1
Design
Event model and API contracts agreed with partners
- Phase 2
Build
Driver app, services and portal
- Phase 3
Pilot
One region live with support feedback
- Phase 4
Roll out
Network-wide rollout and API onboarding
Results
- Near real-time shipment status
- Self-service tracking for customers
- Partner integrations through documented APIs
Business impact
Support teams handle fewer status queries, and customers plan around accurate delivery information.