AWRA OpsHub Search
Intermediate Certificate on pass

Delivery Runs and Proof of Delivery

Plan a driver’s day from shipments, invoices and transfers, order the stops, send it to the driver’s phone, and keep a signature, photos and the recipient’s name for every drop, including deliveries that are only partly handed over.

3 lessons 40 min 6-question assessment 70% to pass

What you’ll learn

  • Plan a delivery run with a driver, vehicle, depot and notes, and add stops from shipments, invoices and transfers
  • Order the stops nearest-first, print the run sheet and open the route in Google Maps
  • Record delivered, part delivered and failed outcomes with a recipient, signature and photos
  • Explain what a run changes in stock and in sales orders, and what finishing a run does to stops nobody reached

Course content

3 lessons · 40 min of reading
01
Lesson 1 of 3 Practice 13 min

Planning a run and adding stops

Delivery runs are in Sales, on the Sales overview or from New Delivery Run in the Sales quick actions. A run is a driver, a vehicle and a depot for one day. Click New delivery run and choose the Run date, the Driver, a Vehicle from your assets or Or vehicle, as text such as KDA 123B, white Isuzu NQR, the Depot and Notes for the driver. The run appears under My runs in that person’s AWRA app; their role needs the Drive delivery runs permission. Planning needs manage delivery runs; reading runs needs view delivery runs.

Then add stops under Find a document, searching by shipment number, invoice number or customer. Three kinds of document can be a stop: a shipped sales order shipment, an invoice from the last 90 days, and a stock transfer in transit, provided it is not already on a run. Nothing here moves stock: the invoice checkout already did, and a transfer is still received at its destination. Each stop shows the address and phone, and Edit address and coordinates fixes a location, with Save to the customer too, for the next run. The reasons a driver may give for a failed drop are a list you keep under New reason; retiring one takes it off the list while stops that used it keep it.

In practice: a Nairobi beverage distributor plans Wednesday’s Westlands run for driver Peter on truck KDA 123B from the Industrial Area depot, with the note Load the cold-chain boxes last; gate code 4471 at the Westlands drop. The dispatcher adds eleven shipped sales order shipments and one transfer to the Westlands branch. Order nearest-first sorts the stops still to deliver by straight-line distance from the depot point, leaving any stop without coordinates at the end to place by hand, and Navigate opens the route in Google Maps in legs of nine waypoints. Print run sheet gives Peter a paper copy as a fallback.

Key takeaways

  • A run is a driver, a vehicle and a depot for one day; it appears under My runs in the driver’s app.
  • Stops are shipped order shipments, invoices from the last 90 days and transfers in transit not already on a run.
  • Order nearest-first sorts by distance from the depot; Navigate opens Google Maps in legs of nine waypoints.
  • Planning a run moves no stock; the invoice checkout or the transfer’s receipt does that.
02
Lesson 2 of 3 Practice 14 min

On the road: outcomes and proof of delivery

The driver opens the run under My runs in the AWRA app and taps Start run, which marks it On the road; on Android an ongoing notification shows the run’s progress until it ends. At each stop they record the outcome: Delivered, Part delivered or Failed. Proof of delivery is the recipient’s name under Received by, a signature, up to six photos and notes. If the signature cannot be stored, recording is refused outright rather than saved without it, because recording the outcome closes the shipment and the stop then locks. Use where I am now saves the spot where the goods were handed over, and can become the customer’s location for next time.

Part delivered asks how much of each line was handed over; whatever was not goes back to packed on the sales order, ready to ship again. For an invoice or transfer stop, Part delivered requires notes saying what was short. Failed needs a reason, picked from your list or typed, such as Gate locked, security would not sign. A driver can record outcomes only on a run assigned to them; a dispatcher with manage delivery runs can record one on any run when a driver phones it in. With no signal, the app keeps the outcome as Saved offline and sends it when the connection returns.

In practice: at a Westlands supermarket two cartons of a twenty-carton order are damaged, so Peter records Part delivered with 18 of 20, the receiving clerk’s name, her signature and a photo of the dented cartons. The two cartons return to packed on the order for Friday’s run. At the next stop the gate is locked, so he records Failed with that reason. At the end of the day he taps Finish run: the dispatcher is told the run is done, and any stop nobody reached is marked Not attempted, which frees its document for another run.

Key takeaways

  • Start run marks the run On the road; Finish run completes it and marks unreached stops Not attempted.
  • Proof of delivery is Received by, a signature, up to six photos and notes; a signature that cannot be stored refuses the outcome.
  • Part delivered returns what was not handed over to packed on the order; Failed needs a reason.
  • Drivers record only on their own runs; outcomes recorded offline are sent when the connection returns.
03
Lesson 3 of 3 Reading 13 min

Reviewing runs and the proof afterwards

The Delivery runs list filters by status (Planned, On the road, Completed, Cancelled), dates and driver, and searches by run number or vehicle. Each run’s page lists its stops with their type (Order shipment, Invoice or Stock transfer), their status (To deliver, Delivered, Part delivered, Failed or Not attempted) and the time recorded. Open a stop to see the proof: who received it, the signature, the photos, the notes, the reason for a failure and any warning raised while it was saved. The signature and photos open only for someone who may view delivery runs or who drove that run.

A delivered shipment closes on its sales order, exactly as if Deliver had been recorded on the order itself, and nothing more: stock already left the books at the invoice checkout, so a run never moves stock twice. A transfer stop records the handover only; the destination still receives the stock on the transfer. Cancel run is for a run that will not go out, and Edit run changes the driver, vehicle or depot while the stops stay as they are.

In practice: a customer in Ruiru disputes a delivery three weeks later. Customer service finds that day’s run under Delivery runs, opens the stop marked Delivered at 10:42 with the storekeeper’s name, her signature and two photos of the pallets at the loading bay, and sends them to the customer the same morning. Reading a month of Failed stops shows that most failures on one route give the reason Gate locked before 9:00, so the dispatcher moves that route’s first drop later.

Key takeaways

  • Runs are Planned, On the road, Completed or Cancelled; stops are To deliver, Delivered, Part delivered, Failed or Not attempted.
  • A stop’s proof (recipient, signature, photos, notes, failure reason) opens only for people who may view runs or who drove it.
  • A delivered shipment closes on its sales order; a run never moves stock, and transfers are still received at the destination.
  • Failure reasons are a managed list, which makes patterns by route visible.

Finished the material?

Take the 6-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center