Proof of delivery

Proof of delivery that arrives from the driver and lands on the right booking

The driver sends the POD photo on WhatsApp or the app. It is matched to the booking and stop, flagged if sent before, saved when you approve. Billing stops waiting for paper. Built for transporters whose customers pay on POD.

*No credit card required

What happens to a POD photo

Sent from the road

WhatsApp or the driver app; both land in AI Inbox with sender, time and source.

Matched with a score

"POD → Booking (LR number), 95%", with booking, vehicle, pickup, drop-off and capture time on the card.

Stop by stop

Stop: seq=1, 2, 3 on each card; several photos for one stop grouped as "POD (2 photos)".

Repeats flagged

"This image was received before. Review carefully before approving."

Saved on Approve

"Link POD → Booking" runs when you tap Approve; Mark Done closes without linking.

Reply to the driver

Received, approved or rejected, sent back on WhatsApp if replies are on.

Send us one of your POD photos

A 30-minute demo where a driver sends it and we bill the load. No credit card, no setup fee.

Why billing waits for POD

Most customers will not pay without proof of delivery. In most offices the proof is a photo in a WhatsApp group, taken by a driver, found days later by scrolling. Which LR is it for? Is it the one from yesterday? Which of the three stops? NShine ERP answers each as the photo arrives.

Control

  • POD photos: Off, Suggest or Auto in AI Inbox Settings. Suggest, the usual setting, means you tap Approve.
  • "Let AI read every photo and file that comes in" switches the reading on.
  • "Send WhatsApp replies to the driver (received / approved / rejected)" switches replies on.
  • Low-confidence matches are marked for manual review.

Then the invoice

The approved POD sits on the booking. The invoice is raised from that booking with the LRs picked, tax and TDS added, the same day.

Before and after

WhatsApp groups

POD by scrolling:

  • Searching chats at billing time
  • Photos filed against the wrong LR
  • Duplicates and missing stops
  • Invoices delayed for weeks

NShine ERP

POD on the booking:

  • One inbox for every driver photo
  • A suggested booking and stop, with a score
  • Repeat and low-confidence warnings
  • POD on the booking the invoice comes from

From delivery to approved POD

  1. The driver delivers and photographs the signed document.
  2. He sends it on WhatsApp or uploads it in the app, optionally with the stop or odometer.
  3. AI Inbox suggests the booking with a score; multi-photo sends are grouped; repeats are flagged.
  4. You approve; the POD is linked to the booking and stop.
  5. The driver gets a reply; billing raises the invoice from the booking.

What you need to get started

A WhatsApp number drivers already send to, or the driver app switched on

Bookings in the system so photos have something to match

A free trial with no credit card and no setup fee

Transport businesses that run on NShine ERP

Watch the product in action

A walkthrough of the transport management software, in your preferred language.

Frequently asked questions

POD capture is included in every plan

Plans are priced by bookings per month and own vehicles, with a free trial and no setup fee. Pick the one that fits, or book a demo first.

Ready to Take Control of Your Business?

Start your 7 day free trial today

No credit card | No commitment | Just try it and see