Skip to content
QuickE
Start free

Last mile delivery

Plan the round, prove the drop, review the misses

QuickE runs the daily loop of a last mile fleet: the day's orders built into routes by area, each driver's stops in driving order, proof and cash captured at every door, and failed attempts explained by reason and area, so tomorrow starts from what actually happened today.

Start freeBook a demo

The problems, in your words

My drivers cross the same streets twice in a shift, and I pay for every kilometre of it.

Routes are built from where the day's orders actually sit. Stops in the same area are grouped so one driver works a neighbourhood through, street by street, with vehicle capacity and promised windows as constraints. A round carries more drops for the same driving, which is the only honest way cost per drop comes down.

See route optimisation

The vans are loaded by seven, and they sit there while we argue about who takes what.

Assignment rules hand each order to a driver by zone, weight, value and payment type the moment it is ready, so the morning starts with the lists already made. The person who used to allocate the whole day by hand now only touches the orders the rules could not place.

See dispatch and auto assignment

Half my addresses are a district and a description of a gate, and the driver phones the customer from the street.

Every stop in the driver app carries the address, the map pin and navigation to it, and the location is captured at handover. The next delivery to that customer starts from a confirmed point instead of a description, and an attempt that fails because the address was wrong is recorded as exactly that.

See the driver app

I know deliveries are failing. I could not tell you in which area, on which day, or for which reason.

Every failed attempt carries a reason the driver picks at the door. The reports break failures down by reason, by area and by driver, and a heat map draws where deliveries succeed and where they do not, so you work on a cause rather than an average.

See analytics and heat maps

How a delivery day runs

The same loop every day. Plan it, route it, prove every drop, and start tomorrow knowing what failed today and why.

  1. 1

    Plan the day

    The day's orders arrive from a store, a file or the API into one queue, so what has to be delivered today is one list, not three sources.

  2. 2

    Route it

    Routes are built around drop density, vehicle capacity and delivery windows, and each driver opens the app to their stops in driving order.

  3. 3

    Deliver with proof

    At each door the driver captures photo, signature or code, records any cash against the shipment, and the office sees it as it happens.

  4. 4

    Review the misses

    Failed attempts line up by reason, area and driver, and tomorrow's plan is built knowing exactly where today went wrong.

Questions operators ask

How does QuickE improve drop density?
Drop density improves when stops going to the same area end up on the same round. QuickE groups the day's orders by where they actually sit, builds each route to work one area through before moving to the next, and respects vehicle capacity and promised delivery windows while doing it, so a driver spends the shift delivering rather than driving between districts.
What happens when a delivery fails at the door?
The driver records the failure with a reason at the stop, and the attempt is kept against the shipment. If it was cash on delivery nothing is credited, the parcel is routed to a return or another attempt, and the failure appears in the reports under its reason and area the same day.
How does QuickE deal with unreliable addresses?
Each stop carries the address, a map pin and navigation to it, and the driver's location is captured at handover, so the next delivery to the same customer starts from a confirmed point rather than a written description. An attempt that fails because of the address carries that as its recorded reason, so areas with an address problem become visible in the reports.
Can drivers run their day in Arabic?
Yes. Each driver chooses Arabic or English for themselves, and the stop list, the amounts to collect and the proof capture all follow that choice. The app keeps working through patchy signal, storing scans, cash entries and proof on the phone and sending them the moment the connection returns.
Does it handle cash on delivery rounds?
Yes, as money rather than as a note. The amount to collect shows on each stop, the driver records what was actually paid at the door, and it posts to that driver's cash ledger against the shipment. A partial payment and a refusal are recorded as what they are, and the evening handover is counted against a figure instead of a memory.

Run tomorrow through it

Start free, load a day of orders and watch the routes, the proof and the failed attempt reasons come back. Or book a demo and walk through a delivery day with someone who knows operations in the region.

Start freeBook a demo