Look at the sample photos
Twelve PODs for a fictional Cape Town distributor. Three are badly lit, one is folded across a line item, one has "2 damaged, rejected" written across it in ballpoint.
Nothing changes for the driver.
Same phone, same WhatsApp group, same photo at the gate. What changes is when you get paid: invoiced Wednesday afternoon instead of the following Friday, so the payment clock starts a week earlier on every load. It reads the photo he already sends and pulls off the customer, the date, the order number, the line items, the quantities, and whether the thing is actually signed.
Delivery notes to invoices does not run on this page yet.
It will read the photographed delivery note, match it to the right load, and produce the invoice on the day of the drop.
Two things work today.
Different paperwork, same machinery: documents in, fields read off them, a sheet out, and anything unreadable flagged instead of guessed.
Play the receipts demoWhatsApp it to +27 73 932 6852 and we send back what comes out of it, usually the same working day. Your paperwork, not our sample.
Open WhatsApp20 minutes, screen share, your own documents. No slides.
WhatsApp them to +27 73 932 6852. The POD photographed the way your driver actually photographs it, sideways and half in shadow, not scanned neatly by the office afterwards. Add the load confirmation that goes with it. We send back the invoice draft it produces, the same working day.
That is the whole test. If it reads your worst note, it reads the rest. If it does not, you have spent four minutes and you know.
Email: [email protected]. Or call the same number, four minutes, and we will tell you whether it is worth sending anything at all.
A photo taken on a phone, in a yard, in the rain, at an angle. That is the realistic input and it is what the demo runs on.
A photo where the signature block and the line items are visible works. A photo of the back of the page does not, and the driver hears that while he is still at the gate rather than a week later.
| Field | Read from the note |
|---|---|
| Customer | Name and delivery address |
| Delivery note number | As printed |
| Order or reference number | Matched to your order where one exists |
| Date and time | From the note, and from the photo where the note carries no time |
| Line items | Description and quantity per line |
| Amendments | Anything the receiver wrote or crossed out, raised as a flag |
| Signature | Present or missing, plus the printed name where legible |
| Photo quality | Clean, or send it again now |
The amendment flag is the one that pays for itself. Handwritten short deliveries and rejected pallets are where invoicing disputes come from, and they are invisible until the customer short-pays you.
This one does not run on the page yet. When it lands, it will go like this.
Twelve PODs for a fictional Cape Town distributor. Three are badly lit, one is folded across a line item, one has "2 damaged, rejected" written across it in ballpoint.
Each photo becomes a structured record.
The rejected pallets are raised. The folded photo is sent back for a re-shoot rather than half read.
Eleven invoice drafts, one held back pending the short-delivery call.
Notes come back with the truck, or on Friday, or whenever someone empties the cab. Invoicing runs weekly. A missing note is an invoice that never goes out, and nobody notices, because nobody is counting notes against loads.
The note is captured at the gate. Invoicing is a same-day job. A load with no note against it shows up today, while the driver still remembers the drop.
Moving invoicing from the following Friday to the day of delivery pulls a week of revenue permanently forward. It happens once and then it stays. After that, the money is in the deliveries that were never invoiced at all, and in the disputes you currently lose because the note is gone.
One POD by WhatsApp needs nothing from you. A full batch runs in a secured session, and the demos page explains how that is opened.
The files go within seven days.
If a customer name is sensitive, black it out. What you are testing is whether it reads quantities, amendments and signatures off a bad photo.
Reading delivery notes is an agent's job, not a per-note rate.
Implementation is free for a standard agent. A complex build, with several note formats or an approval step for short deliveries and rejections, is quoted before we start, so you see the number first.
| What the agent does | A month |
|---|---|
| A simple agent: one job, one format, one destination | From R1,000 |
| A standard agent: several formats, your own rules, writing into two systems | From R2,500 |
| A heavy agent: high volume, many exceptions, several people relying on it | From R5,000 |
A depot reading delivery notes in one format, with the invoice landing in a single place, is a standard agent, from R2,500 a month. A fleet running several note formats, short-delivery flags and approvals, with several people relying on the output, is a heavy agent, from R5,000 a month.
The subscription covers the agent running, the model costs, monitoring, and the changes when a note format changes or your rules change. Nothing extra to buy when something shifts.
It is month to month. You own your data and the process map stays yours, and you can stop any time.
The numbers, in one place
Partly, and with more flags. Printed notes with handwritten amendments are the sweet spot. Fully handwritten notes read well when the writing is neat and badly when it is not. WhatsApp us ten of your worst and you will know by tomorrow morning.
Photos queue on the phone and go up when there is signal. It is a build detail rather than a blocker, but raise it early because it changes how the capture is set up.
Yes, once it can see your loads. That means getting whatever you plan loads in and the photo stream talking to each other, which is work we do before any AI is involved and which usually pays for itself on its own.
Implementation is free for a standard build. Then it is a monthly subscription: from R2,500 a month for a standard agent reading one note format into one system, from R5,000 a month for a fleet running several formats with approvals and several people relying on it.
That is your call. Most operators keep a person on anything with a flag on it and let the clean ones through. Start with everything reviewed and loosen it once you trust the flags, not before.
The next step
Or email [email protected], or book twenty minutes and we will walk one load from the gate to the money before anyone mentions software.
Or email [email protected]. No slides, and no invoice for the conversation.