AWRA OpsHub Search

AWRA Help Center

Copy link
Sales Customers Payments
01 Sales Module Guides 02 Sale to Invoice Step-by-Step Workflows 03 Payment Recording Step-by-Step Workflows

Delivery Runs & Proof Of Delivery

Plan a driver’s day on the web from shipments, invoices and stock transfers, put the stops in order, and let the driver record each delivery in the app with a name, photos, a signature and the phone’s location.

A delivery run is one driver, one day and a list of stops. Each stop is a document you already have: a shipped sales order shipment, an issued invoice from the last 90 days, or a stock transfer in transit. A document can be on only one open run at a time. The run itself moves no stock: the invoice checkout already did that, and a transfer is still received at its destination on the transfer.

Who Does What

  • Dispatchers plan runs, add and order stops, cancel runs and keep the list of failure reasons. They need the Manage delivery runs permission.
  • Drivers need the Drive delivery runs permission and can only start, record and finish runs where they are the named driver.
  • People with View delivery runs can follow every run, including the All runs list in the app.
  • Planning a run is web only. The app is for driving it.

Plan A Run (Web)

  1. Go to Sales → Delivery runs and press New run.
  2. Set the Run date and Driver. Optionally pick a Vehicle from your assets or type one, a Depot, the depot’s latitude and longitude (Use where I am now fills them in), and Notes for the driver. Press Plan run.
  3. On the run, under Add stops, search by document number or customer, tick shipments, invoices or transfers, and press Add to run.
  4. Press Order nearest-first to sort the stops still to deliver by straight-line distance from the depot point. Stops without coordinates go to the end; use the up and down arrows to place them by hand.
  5. Fix a stop’s address, phone or coordinates under Edit address and coordinates. Tick Save to the customer too, for the next run to keep them on the customer record.
  6. Press Run sheet for a printable list, or open the Open route in Google Maps link. A run of more than ten stops opens as several legs.

Leave the depot coordinates blank and the last run from the same depot lends its point. Only a run that has not started can be cancelled; its stops are released for another run.

Drive A Run (App)

  1. Open Sales → Delivery Runs. My runs shows your runs for today and any still open from earlier days.
  2. Open the run and press Start run. Use the Google Maps buttons for the route.
  3. Tap a stop. Use Navigate or Call to reach the customer.
  4. Under Proof of delivery, choose Delivered, Part delivered or Failed.
  5. For a delivery, type who it was Received by (required), add photos, and have the recipient sign on the Recipient’s signature pad. For a failure, pick a reason or type one, and photograph what stopped the delivery.
  6. For a part delivery of a shipment, type how many of each line were handed over. The rest goes back to packed on the sales order. For an invoice or transfer, say in the notes what was short.
  7. Press Record delivery. The phone’s location is taken at that moment, or earlier with Take the location now. If there is no GPS fix, the delivery is still recorded without one.
  8. When you are done, press Finish run. Stops with no outcome are marked Not attempted and can go on another run.

A delivered shipment stop closes the shipment on its sales order. Each stop can be recorded once. A dispatcher can also record an outcome on the web when a driver phones it in, with photos but no signature.

No Signal

  • The app keeps a copy of your runs. With no signal the button reads Save, send when online and the stop shows Saved, sending.
  • Start and finish are queued behind the deliveries, so the server receives them in the order they happened.
  • Each saved delivery carries a key, so sending it twice never records the stop twice.
  • On the web, the proof shows taken … sent later when it reached the server more than five minutes after it was captured.

Reading The Proof (Web)

On a recorded stop, open Proof of delivery to see who recorded it and whether from the driver app or the web, who received it, the signature, the photos, the notes, the quantities handed over, and the GPS point with its distance from the stop’s own point. Someone who can manage runs and edit customers can press Use as the customer’s location so the next run routes to where the goods were actually handed over.

Notifications & Failure Reasons

  • A failed stop and a finished run notify the dispatcher who planned the run, or everyone who manages runs if nobody did. Emails follow your workspace’s notification settings.
  • An email to the customer when their goods are delivered is off by default. A workspace can switch it on; it goes only to customers with an email address.
  • Dispatchers keep the list of reasons a driver picks from under Failed delivery reasons on the runs page. Retiring a reason takes it off the list; stops that used it keep it.

Common Issues

  • A document is missing from Add stops. It is already on a run, the shipment is not shipped, the invoice is older than 90 days, or the transfer is not in transit.
  • The run is not in the driver’s app. Check the run’s driver and date, and that their role has Drive delivery runs.
  • “The signature could not be read, so nothing was recorded.” The stop was not recorded. Ask the recipient to sign again and record it again. A signature is optional, but once one is taken it must be stored, because the stop locks after it is recorded.
  • Nearest-first did nothing. No stop still to deliver has coordinates. Add them, or order the stops by hand.
  • A photo is missing. The delivery was kept and a warning shows on the proof that a photo could not be saved.
Related guide: Sales Order Fulfilment covers picking, packing and shipping before a run, and Signature Capture explains what a captured mark proves.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide