Book delivery
Instant and scheduled booking flows backed by an Express API that creates deliveries, prices them, and routes them into payment and dispatch states.
A production-grade logistics platform with instant and scheduled delivery booking, secure payment confirmation, NIN-gated riders, real-time dispatch, and route-aware operational workflows.
The product combines transaction integrity, dispatch operations, rider verification, and realtime status updates inside one operational flow.
Instant and scheduled booking flows backed by an Express API that creates deliveries, prices them, and routes them into payment and dispatch states.
Realtime delivery tracking via Socket.IO with a state machine covering payment, assignment, acceptance, transit, arrival, and completion.
Dispatcher-facing assignment workflows with admin override so operations stay in control even when automated dispatch does the first pass.
Paystack initialization, verify, and webhook handling tied directly into delivery state transitions and post-payment dispatch automation.
Rider verification gates so unverified users cannot go online or be eligible for assignment in production workflows.
Leaflet, OSM/Nominatim, and OSRM wired together so route and distance data can support rider matching and dispatch decisions.
Client-side booking and portal interfaces.
Safer product and API contracts for operational flows.
Auth, validation, payment, rider, and delivery routes.
Realtime tracking and delivery event propagation.
Relational state model for logistics and permissions.
External systems integrated into core workflow logic.
Deliveries should not complete or move forward on untrusted payment events.
Server verification and HMAC webhook checks ensure delivery transitions only happen on trusted payment confirmation.
Dispatching the wrong rider breaks logistics efficiency and trust.
Nearest eligible online rider selection uses vehicle matching, radius rules, and verification status.
Tracking data should not leak across sessions or unauthorized listeners.
JWT-based Socket.IO authentication restricts realtime updates to valid users.
Production cannot silently accept invalid payment or identity states when provider keys are missing.
Production paths require real keys and fail loudly instead of pretending success.
Dispatch and tracking work as a live operational flow rather than a static booking experience.
Payment correctness is embedded into delivery state transitions.
Operational safety improves when assignment depends on trusted rider verification.
Evoke Logistics reflects the kind of product work I enjoy: payment integrity, role permissions, realtime status flows, routing, and operational correctness under live usage.
I build for what happens after launch, when data, users, and edge cases start colliding.
Open to backend and full-stack roles involving payments, workflows, logistics, permissions, and state-heavy systems.