HyperLocal

HyperLocal puts the whole delivery lifecycle — forward and reverse — in one system.

1. 01Orders come in. Type a single order, upload a batch from a file, or let a merchant's own system push orders in over an API. Each order gets a unique tracking number (AWB) automatically.
2. 02Riders get the work on their phone. Orders are assigned to a rider (field executive), who accepts or rejects on the rider app. Nearby riders are automatically nudged about new pickups, widening the search radius if no one picks up.
3. 03Everyone can see where things stand. A live map of rider locations, a public track-order page, and a full status timeline on every order — operations, riders, and merchants all have their own view.
4. 04Proof is captured at the door. Delivery requires a photo. Failed deliveries and cancellations require a reason. Returns close with a dropback proof step recording whether the item went back to the warehouse or to the merchant's location.
5. 05Cash and accounts settle. Cash collected on delivery is tracked per order and reconciled separately against riders, merchants, and vendors, with downloadable PDF statements.

• Three flows built in: Last-Mile Delivery (forward, merchant to customer), Reverse Pickup (return journey, with warehouse or merchant dropback), and First-Mile Logistics (rider is sent to the merchant's pickup point before the delivery leg begins).
• Both B2C (merchant to customer) and C2C (sender to receiver) order shapes; a merchant can be set up for either or both.
• Assign orders manually or map riders to specific merchants.
• Dashboard with order volumes, status breakdowns, rider performance, and a delayed-orders watchlist.
• Rider attendance tracking — check-in, check-out, and worked hours.
• Warehouse and supervisor view with scheduled alerts for pending and uncompleted orders.
• Export order and merchant reports; manage master data for zones, merchants, vendors, riders, and reasons.

• Operations and dispatch teams — receive orders, assign riders, and keep deliveries on time (the web dashboard is built for them).
• Riders (field executives) — do pickups and drops entirely from the rider mobile app.
• Merchants (shippers) — shops, pharmacies, grocers, and businesses that hand over deliveries by typing them in, uploading a file, or pushing them from their own system.
• Warehouse managers and supervisors — watch for delays and orders running behind, and step in before they breach the promised time.

If you move parcels across a city every day and you're tracking riders, cash, and where orders are by phone calls and spreadsheets, this is built for you.

The ops team sets up master data first — zones, merchants and pickup locations, vendors, riders, and the reason list. Merchants are onboarded with their SLA, buffer times, and pricing model (zone-based or distance-based). Orders start flowing in by any method; riders are mapped to merchants and given the rider app. Day to day, ops assigns and tracks orders on the dashboard, riders run them from the app, and the team reconciles cash at the end of each cycle.

• TruckPoollong-haul road freight — the other end of the same network

HyperLocal runs a web operations console, a rider mobile API, and a merchant integration API against a single shared database. Integrates with mapping and geocoding services, and a Gulf address-resolution service for municipality to zone to street to building addressing in the Carson deployment.