Case File
Order & Operational Tracking System
Mobile client and backend integration so warehouse-to-delivery status is visible from one control surface.
- Domain
- Operations & Logistics
- Focus
- Role-based workflow, assignment, tracking
- Stack
- React Native, Supabase, Firebase
- Tools
- SQL Editor, Auth Systems
- Status
- Completed
- Year
- 2026
Case cover
Order tracking — main control view
Problem
Order and driver state lived in separate channels, so assignment lagged and delivery status was opaque. Duplicate entry increased error rates.
Approach
Separated warehouse, driver, and admin flows with role-based auth. Kept the order lifecycle in one data model; used Supabase for real-time updates.
Technical Structure
User roles
Warehouse: create orders and assign drivers. Driver: assigned route and status updates. Admin: full records and override.
Flow logic
Create → assign → route → delivery status. Role checks at each step; transitions are auditable.
Data structure
Relational schema for orders, users, routes, delivery; Firebase Auth for identity, Supabase for sync.
Outcome
Assignment and routing decisions are traceable from one panel; ops works off a single source of record.
Supplementary figures
