Photo
The parcel where it was left, the shopfront, the handover. Resized on the device and uploaded in the background, so a weak connection slows nothing down.
Proof of delivery
Every delivery ends with evidence
A delivery is not finished when the driver says it is. It is finished when something on the record can settle the question three months later, in the ten seconds before a merchant decides whether to trust you.
What the driver captures at the door
Set per kind of delivery, so a hot meal is not held up by a signature that nobody needs.
Signature
Signed on the screen and stored with the name of whoever signed for it.
Delivery code
A code the recipient reads out, for anything that has to reach one specific person and nobody else.
Scan
Waybill or parcel barcode at both ends, so what was collected is provably what was delivered.
Where and when
Location and time recorded with the proof as it is captured, never typed in afterwards from memory.
The note
Left with the neighbour, gate code used, second attempt. The line of context that explains the photo.
Checked, not just collected
Estoul reads the proof before you have to
Collecting proof is the easy half. The hard half is knowing that what was collected is worth anything — and that is done as the photo is taken, while the driver is still standing there.
Does the photo show a delivery?
A pocket shot, a photo of the sky, a blurred frame: caught at the door and sent back for another attempt, instead of surfacing weeks later when it is the only evidence you have.
Was it taken where it should be?
Proof captured a street away from the drop point is flagged on the delivery itself, so the conversation happens while the driver still remembers the stop.
Does it match the job?
Parcel counts and visible labels are checked against what was meant to go out, which catches the swap before the customer does.
Patterns, not just incidents
Near-identical photos across a week, or proofs that always land minutes after the status changes, surface as a pattern rather than as somebody’s hunch.
You decide what each delivery has to prove
Requirements are set per service type and enforced in the driver app. A job does not close until what you asked for is there, so the rule is kept by the system rather than by whoever is on shift.
- Require a photo, a signature, a code, a scan, or any combination of them.
- Different rules at collection and at handover.
- A failed attempt needs a reason, and a photo too if you want one.
- Nothing closes a delivery until your rules are satisfied.
Find it again in seconds
Proof that takes an afternoon to locate is not proof. Everything captured stays attached to the delivery and searchable by the reference your own system uses.
Searchable by your reference
Support types the order number your customer just read out and lands on the delivery, its timeline and its proof.
Shareable without an account
Send a merchant or a customer exactly the proof for one delivery, without giving anyone a login or exposing the rest of your day.
Exportable for the month
When finance or a client asks for everything in a period, it is an export rather than a project.
See Estoul on your own operation
Tell us how many drivers you run and where they run, and we will walk you through what a day on Estoul looks like for your team.