Digital Proof of Delivery: Replacing the Paper Slip in Nepal

The paper delivery slip has one job: prove the parcel reached the right person. It does that job badly.

The slip is signed at the door, carried around in a rider’s bag for the rest of the day, handed in at the branch, filed in a box, and then — three weeks later, when a merchant says a parcel was never delivered — someone has to find it. Often it is found, illegible, signed with a squiggle by someone whose name nobody recorded.

Digital proof of delivery is not about removing paper. It is about the record being complete, immediate and findable.

What to actually capture

A proof of delivery record that survives a dispute needs more than a signature image.

Who received it. Not just a signature — a typed name and relationship. “Received by: Sita Shrestha, neighbour” resolves a category of dispute that a squiggle never will. In practice a large share of deliveries in Nepal go to someone other than the addressee, and pretending otherwise just makes the record wrong.

When, precisely. Device timestamp, captured at the moment of delivery, not when the rider syncs at the branch. The gap between those two matters when a customer says they were not home at that time.

Where. GPS coordinates at the point of capture. Not to police riders — to answer “was this delivered to the right address” without a phone call. Accuracy will be imperfect in dense areas; that is fine, it only needs to distinguish the right locality from the wrong one.

A photograph. The most useful single field, and the cheapest. A photo of the parcel at the door, or with the recipient, closes almost every “it never arrived” dispute instantly. It also documents condition, which handles the other half of disputes: “it arrived damaged.”

The amount collected. For COD, the actual cash taken, entered by the rider, separate from the COD amount on the consignment. When they differ, that difference is the single most important fact in the record.

Who captured it. The rider’s identity, from their authenticated session, not typed in.

Offline first, not offline as an afterthought

Riders lose signal. In parts of the valley and on most highway routes, they lose it for extended periods. A proof of delivery app that requires connectivity at the moment of capture will be worked around — riders will mark everything delivered in bulk when they get back to the branch, and every timestamp in your system becomes a lie.

The app has to capture locally and sync later, and the record has to distinguish clearly between the capture time and the sync time. Both should be stored. A record captured at 14:20 and synced at 18:05 is normal; the same record should never be presented as though it was captured at 18:05.

Failed attempts need proof too

Most systems capture proof on success and a dropdown reason on failure. That is backwards — failed attempts are where the disputes are.

A merchant being charged a return fee will challenge whether the attempt genuinely happened. “Customer not available” with no evidence is not an answer. A failed attempt should capture the same GPS and timestamp, the call attempt and its outcome, and ideally a photo of the closed door or the building.

This changes the conversation with merchants completely. It also changes rider behaviour, because a rider who knows the attempt is evidenced makes the attempt.

Retention and retrieval

The record is only worth something if it can be produced quickly. That means:

• Proof attached to the consignment, retrievable by tracking number, by customer phone, or by merchant and date range
• Images stored durably, not on the rider’s device
• A merchant-facing view, so a merchant can check for themselves before raising a dispute at all

That last point removes more disputes than anything else. Most merchant disputes are not accusations — they are a merchant who cannot see what happened. Give them a view and the volume drops.

Signature is the least useful field

Worth stating plainly, because it is the one everyone starts with: a captured signature is the weakest part of a digital POD record. It is unverifiable, frequently illegible, and proves less than a photograph and a typed name.

Capture it if customers expect it. Do not build the system around it.

What good looks like

A courier running digital POD properly can, in a few seconds, answer a merchant’s query with: delivered on this date at this time, received by this named person, at these coordinates, photographed, this amount collected, by this rider, and here is the image.

Nobody argues with that. The dispute process stops being adversarial and becomes a lookup.

We build the logistics management system that courier and cargo operators across Nepal use for offline-capable proof of delivery, failed-attempt evidence and merchant-facing tracking. If your PODs are in a filing box, talk to us.