POD and ePOD

Proof of Delivery (POD) is the legal evidence cargo was handed over. The platform captures it electronically on the driver app (ePOD) and attaches it to the shipment.

What's captured

At each delivery stop:

• Consignee name — typed or picked from contacts.
• Signature — drawn on screen.
• Photo(s) — of cargo / location (optional, tenant-configurable).
• Timestamp + GPS — auto-captured.
• Exceptions — shortage, damage, refusal — picked from a list with notes and mandatory photo evidence.

The PDF

The platform renders a POD document combining the captured signature, photos, stop details, cargo list, and any exceptions. Numbered (e.g. POD-2026-04-13-001), filed into Documents Center, versioned if regenerated.

Routing the POD

After each delivery, the POD is:

• Attached to the shipment record.
• Visible to the customer in the customer portal.
• Optionally emailed to the customer automatically (per tenant / per customer setting).
• Required before the shipment can be invoiced (some tenants make this mandatory; others allow invoicing without POD).

Exceptions

If the driver logs a shortage / damage / refusal:

• The shipment is flagged with an exception status.
• A task lands on the ops team's queue to follow up.
• The customer portal shows the exception; an email alert goes out.

Exceptions often trigger insurance claims.

No-signature deliveries

Some deliveries (parcel to locker, unattended drop) can't capture a signature. The driver picks "no-signature" and a photo of the drop is mandatory. Tenant policy governs which customers / cargo allow this.

Legal weight

ePOD is legally equivalent to a paper POD in most jurisdictions when it captures a signature, timestamp, and location. For jurisdictions requiring a paper CMR, the driver can still print the CMR on board and scan + upload on delivery.

API

PODs are fetchable via GET /api/shipments/{id}/pod. Webhooks fire on POD captured.