AWRA OpsHub Search

The Driver Who Came Back With Six Crates

A delivery note signed on a bonnet at four in the afternoon is the only record of what reached the customer, and it is in the van until Monday. A delivery run on the driver’s phone — stops in order, a signature, a photo and a GPS point at each, and the short delivery recorded as short.

Logistics & Field Service Washingtone Aura 7 min read

A soft-drinks distributor in Thika sends out four lorries a day to dukas, supermarkets and schools. On Tuesday, Peter’s run has eleven drops. At the eighth, a mini-market in Juja, the owner takes 34 of the 40 crates on the order: the storeroom is full. Peter comes back with six crates, a delivery note marked in biro, and no way for the office to know any of this until he parks. By then the invoice has gone out for 40.

A run is built from documents you already have

Under Sales, Delivery runs, the dispatcher creates a run for a date with a driver, a vehicle (typed, or picked from your asset register) and a depot. Stops are added from three kinds of document already in the system: a sales order shipment that is out for delivery, an issued invoice, or a stock transfer in transit to another branch. A document already on another run cannot be added twice.

The stops can be dragged into order, nudged up and down, or put in order automatically: starting from the depot, the run goes to the nearest stop with a location, then the nearest to that, and so on. A map link opens the route in the phone’s maps app, and each stop has its own navigate link. A stop’s location can be corrected on the spot and saved back to the customer for next time.

At the stop

The driver signs in to the AWRA app and sees My delivery runs — only their own, because a driver’s permission reaches the runs assigned to them and nothing else. At each stop they record one of three outcomes.

What the phone records, and what the office sees

Driver, at the door

Peter in Juja

  • Outcome: delivered, part delivered or failed
  • Who received the goods, by name
  • A signature on the screen
  • Photos of the goods or the signed note
  • The phone’s GPS point and its accuracy

Dispatcher, in Thika

Seconds later, or when the van finds signal

  • The stop marked with its outcome and time
  • The shipment closed, or cut down to what was handed over
  • A failed stop with its reason
  • A notice to whoever planned the run
  • The run completed when the driver finishes

A stop locks after it is recorded. There is no second mark to argue about later.

The recipient’s name is required. A failure needs a reason, picked from your own list — shop closed, refused, wrong address — or typed. If a signature cannot be stored, nothing is recorded and the driver is asked to have the recipient sign again; recording the outcome closes the shipment, so there is no second chance to collect it. A photo that fails to save is different: the delivery stands, with a warning on the stop.

Thirty-four crates delivered is not a failed delivery. It is a delivery of thirty-four, and the books should say so.

The six crates

Peter records Juja as part delivered and enters 34 against the 40 on the shipment line. The shipment is cut down to 34, which is what was handed over, and the six that came back step out of shipped: still picked and packed, ready to go out on another shipment, without anyone re-keying a stock movement. No stock moves at the stop at all, because stock already left the books when the invoice was checked out; the run is logistics, not a second stock posting. What happens to the invoice for 40 is the credit decision your team already makes — and now it is made on Tuesday afternoon rather than on Monday.

For an invoice stop or a transfer stop there are no shipment lines to cut, so a part delivery needs a note saying what was short. A transfer stop records the handover; the receiving branch still receives the goods on the transfer itself, so the stock count at the other end is still a count somebody did. The wider question of who chases a short delivery is in a short delivery is not a refusal.

Where there is no signal

The stretch past Juja towards the quarry has no signal for twenty minutes. The app queues proofs of delivery, and the run’s start and finish, on the phone and sends them in order when the connection returns. Each carries its own key, so a proof sent twice is recorded once. On Android a progress notification shows how far through the run the driver is and how many stops are still waiting to sync. Recording the first stop on a run nobody pressed start on starts it.

3
kinds of stop: shipment, invoice, transfer
1
mark per stop, then it locks
0
stock movements posted at the door

Failed stops and completed runs notify the dispatcher who planned the run, never the driver who caused them. A delivered notice to the customer exists and is off by default; switch it on in notification settings if your customers want it. More on the screen on the delivery runs page, and the general case for proof of delivery in proof of delivery in Kenya.

Three questions for your dispatch desk

When did we last learn about a short delivery on the same day?

What you will probably hear

When the driver got back.

How to read it

Then the invoice went out wrong and the credit note is a week behind it.

Where is the signed delivery note for last Tuesday’s Juja drop?

What you will probably hear

In the van, or the file.

How to read it

A proof that cannot be found when the customer disputes it is not proof.

Can a driver see other drivers’ runs?

What you will probably hear

Everyone uses the same login.

How to read it

Then nobody knows which driver recorded which stop.

The straight answer

What AWRA OpsHub does today

  • Delivery runs with a driver, a vehicle, a depot and ordered stops from shipments, invoices and transfers.
  • Stop ordering by hand or by nearest next stop, with map and navigate links.
  • Proof of delivery: outcome, recipient name, signature, photos and GPS, locked after one mark.
  • Part delivery that cuts the shipment to what was handed over and returns the rest to packed.
  • Failure reasons from your own list or typed.
  • A driver app that shows only the driver’s runs and queues proofs offline.
  • Notices to the dispatcher on a failed stop or a finished run, and an optional one to the customer.

More we can add to your workspace

  • Live vehicle tracking on a map between stops. Commission it
  • Route optimisation that accounts for traffic and delivery windows. Commission it
  • An SMS to the customer with an arrival estimate. Commission it
  • Cash-on-delivery collection recorded at the stop, against the invoice. Commission it
  • Returns and empties collected on the same run, such as crates and gas cylinders. Commission it

Where we point you to a specialist

  • A signature and a GPS point are evidence of a handover. Whether they settle a dispute under your terms of sale is for your contract and, if it comes to it, your lawyer.

Returns and empties on the run are what beverage and gas distributors ask for first.

More we can add to your workspace

Anything above that you need, we can build for you

Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.

The operational work, which is what most commissions actually are

An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.

The module-shaped additions, which are the ones readers ask for most often

A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.

The report, document or pack nothing currently produces

The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.

Systems, rails and hardware you already run

The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.

How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.

Tell us what your operation needs

See delivery runs

Plan a driver’s day from your shipments, invoices and transfers, and get proof of delivery back from the stop.

Explore delivery runs

Frequently asked questions

What does proof of delivery capture?

The outcome, the recipient’s name, a signature, optional photos, the phone’s GPS point with its accuracy, and the time it was captured.

What happens when a customer takes only part of a shipment?

The driver records a part delivery with the quantities handed over. The shipment is cut to those quantities and the rest returns to picked and packed, ready to go out again.

Does delivering a stop move stock?

No. Stock leaves the books when the invoice is checked out. A delivery run records the handover and closes the shipment.

Can the driver work without signal?

Yes. The app queues proofs of delivery and the run’s start and finish, and sends them when the connection returns. A proof sent twice is recorded once.

Can a driver see every run?

No. A driver sees and records only the runs assigned to them.

Share this article

LinkedIn X WhatsApp

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