DAMN99 DispatchCost-aware routing
Local optimization runs by default, with HERE enabled only when you choose it.
Mobile POD capture
Drivers upload delivery photos and return to the route list without getting stuck.
Super Admin controls
Monitor app-wide HERE usage, blocked calls, cache hits, and estimated spend.
A complete route day from import to proof of delivery.
DAMN99 is designed around the real dispatch sequence: collect orders, make route decisions, assign drivers, monitor exceptions, and confirm the delivery with evidence that admins can review later.
Import and prepare orders
Upload orders, normalize addresses, reuse cached geocodes, and keep customer delivery details in one clean queue.
Build routes without runaway spend
Local route optimization is the default path, so dispatch can keep moving without triggering expensive HERE Tour Planning calls.
Assign drivers and monitor progress
Give drivers active routes, watch stop status change, and keep dispatch focused on exceptions instead of manual check-ins.
Capture proof and close the loop
Drivers capture compressed delivery photos, optional signatures, recipient names, and notes directly from mobile.
Every panel has a job.
The app avoids marketing fluff inside the workflow. Admins get dense operational tables, drivers get simple mobile actions, and Super Admin gets global control with usage telemetry.
Orders
CSV-ready
Batch import, validate customer emails, geocode missing coordinates, and keep pending orders ready for routing.
Routes
Local-first
Generate single or multi-driver route plans with fallback optimization available before any paid HERE optimization is used.
Drivers
Mobile
Drivers see assigned stops, customer details, click-to-call phone numbers, and proof-of-delivery controls on one stop page.
Super Admin
Global
See app-wide users, routes, orders, audit activity, and HERE API usage across the whole project.
HERE Cost Analytics
$0.00
Paid requests
0 today
Cache hits
Tracked
Blocked calls
Budget-aware
Refresh
30 seconds
HERE APIs are treated like billable infrastructure.
Expensive route optimization is off by default. Geocoding uses memory and database cache layers. Super Admin can see request counts, cache hits, blocked events, errors, and estimated spend for the whole app.
Designed for the phone in a driver's hand.
The driver stop screen keeps the critical path short: review the customer, take a delivery photo, collect an optional signature, mark Delivered or Failed, and immediately return to the route.
Stop #18
Customer delivery
99.9%
workflow uptime target
30s
cost panel refresh
0
default HERE tour calls
24/7
driver route access