First, a filter that will save you the rest of this page: if you're a member of a pallet network, stop reading — your network mandates its own ePOD system and you'll be using that. This guide is for the fleets the software industry mostly ignores: 1 to 20 trucks, general haulage, FMCG and container work, running on paper delivery notes and a diary.
For that fleet, most "proof of delivery software" is the wrong shape. It's built for parcel couriers doing eighty drops a day, or sold as a module of a transport management system you don't want. Here is what actually matters, in the order it actually matters.
Every POD app fails or succeeds on one thing: will your drivers use it on a wet Tuesday in February? Most products require an app install, a login, and a new habit. Some of your drivers will take to it. The ones who won't — agency drivers, the owner-driver who subs for you, the driver whose phone is five years old — are exactly where your paperwork gaps already are.
So ask the vendor: what does the driver have to install, and what happens with a driver who won't? If the answer involves "training", multiply the rollout cost accordingly. The alternative approach is to use the channel drivers already use — most UK fleets already receive POD photos over WhatsApp — and put the software on the office side of the conversation instead of the cab side.
A small fleet doesn't control what happens at the delivery point. You'll be handed carbon-copy CMRs, customer-branded delivery notes, and tickets signed on a tailgate. A POD app for this market has to work from a photo of a messy paper document — reading the PO number, the signature, the date, and the handwritten notes in the margin — not assume a clean digital signature capture on a company device.
The margin notes matter most. "Waited 2 hrs", "1 pallet damaged", "short 3 cases" are where your money and your legal position live. If the software just stores the photo without reading it, you've bought a filing cabinet, not an admin saving. (More on that in the waiting time guide.)
Three questions with checkable answers: Where is the data hosted (UK/EU hosting keeps your GDPR story simple)? Is it encrypted in transit and at rest? And how long is the archive — because PODs are business records you should be keeping for at least six years (the retention rules are here), which rules out anything that quietly deletes images after ninety days.
You already invoice from Sage, Xero or QuickBooks, and that shouldn't change. What you want from a POD tool is a clean, structured export — driver, PO reference, status, charges — that goes into the invoicing run without retyping. Be suspicious of anything that wants to become your invoicing system; that's a migration project wearing a subscription's clothing.
Most POD apps price per driver per month — typically somewhere in the £25–£35 range at list price. That reads as cheap and scales as expensive: ten drivers is £250–£350 a month before you've added the office seats. Flat fleet-band pricing inverts this: HaulBot, for comparison, runs from £39/month for an owner-driver with up to 3 trucks to £129/month for a fleet of up to 20 — the whole fleet, not per seat. Whichever tool you pick, put your actual driver count into both models before deciding; the answer flips depending on your size.
And insist on month-to-month terms. A tool that needs a 12-month contract to keep you is telling you something about month two.
The fastest way to evaluate any of this is to try it on your own paperwork. Message a photo of a real delivery note to HaulBot on WhatsApp and see what comes back — extracted, validated, flagged — in under a minute. No card, no setup, no app.