Introduction
Proof of delivery (POD) is the documentation that confirms a delivery was completed: who received it, when, where, and in what condition. For courier fleets and 3PLs, POD is simultaneously a legal protection, a client trust-building tool, and increasingly a contractual requirement.
What is proof of delivery?
A complete POD record captures:
- The delivery address
- Date and time of delivery (timestamp)
- Identity of the person who accepted (consignee name), if applicable
- A visual record of the delivery (photo)
- The recipient's acknowledgment (signature), where required
- GPS coordinates at time of capture
- Driver notes about delivery conditions
Types of proof of delivery
1. Paper POD (manual)
A physical delivery receipt signed by the recipient.
- Universally understood, but documents get lost, there is no timestamp or GPS metadata, searching historical records is slow, and it cannot scale.
- Still common in some B2B freight contexts.
2. Photo proof of delivery
A photograph taken by the driver at the moment of delivery, timestamped and GPS-tagged automatically.
- Works for unattended residential deliveries. Provides visual evidence of package condition and placement.
- This is the standard for consumer last-mile delivery in 2026.
3. Electronic signature capture
A digital signature collected on the driver's device, stored with timestamp and GPS.
- Standard for high-value parcels, regulated goods (pharmaceuticals, alcohol), and B2B deliveries where a named recipient must acknowledge delivery.
4. Barcode and QR code scanning
Drivers scan a barcode on the package at key events (pickup, load, delivery).
- Creates a chain-of-custody record.
- Common where packages are pre-labeled and individually tracked through the supply chain.
5. Consignee name capture
Capturing the name of the individual who accepted the delivery, entered by the driver at handoff.
- Valuable for business deliveries and regulated delivery contexts.
A complete POD record
Alchemira captures photo, signature, GPS coordinates, consignee name, notes, and timestamp at delivery. [1] The full record is stored immediately and accessible to dispatchers in real time. For client dispute resolution, the record is available the moment a dispute is raised.
Why POD matters for couriers and 3PLs
Financial risk: delivery disputes
Without POD, every "we never received it" claim is a judgment call. Photo POD with GPS timestamp makes most disputes straightforward to resolve. [1]
Client relationship risk
B2B clients increasingly require POD documentation as a condition of service contracts. For regulated industries — pharmaceuticals, alcohol, age-verified products — POD requirements may be legally mandated for the carrier. [20]
Operational intelligence
Aggregate POD data reveals patterns invisible in daily dispatch: which zones have the highest dispute rates, which drivers have anomalies in capture, whether packages are placed appropriately. [1]
Legal and regulatory considerations
Pharmaceutical delivery: Controlled substances often require signature POD and identity verification. Requirements vary by state and DEA schedule classification. [20]
Alcohol delivery: Age verification is required in all US jurisdictions. POD must document that verification occurred. [20]
High-value parcel insurance: Cargo insurance policies frequently specify POD requirements as a condition of coverage. [19]
Note: This guide provides general orientation, not legal advice. Consult with legal and compliance advisors for requirements specific to your operation.
Implementing POD in a fleet operation
- Step 1: Define required POD by service type — photo for standard residential; photo + signature for high-value parcels; signature + consignee name for pharmaceutical and alcohol delivery.
- Step 2: Set driver photo quality standards — package fully visible; address number or signage in frame; adequate lighting; package in a safe placement location.
- Step 3: Require POD as part of delivery completion — the stop doesn't close in the driver app until the required evidence is captured.
- Step 4: Ensure immediate cloud upload — photos should leave the driver's device immediately, not stay local.
- Step 5: Make POD part of client reporting — include exception reports and on-time delivery data as standard client deliverables, not on-request outputs.
What to look for in delivery software for POD
- In-app photo capture built into the delivery completion workflow, not a separate step
- Electronic signature capture available for service types that require it
- GPS coordinates recorded at capture, not estimated from route data
- Consignee name capture for deliveries requiring recipient identification
- Driver notes field linked to the delivery record
- Timestamp automatically applied at capture, not editable
- Immediate cloud upload — photos leave the driver's device at capture
- Dispatcher real-time access — POD visible in dashboard without waiting for sync
- Connection to billing and on-time reports
- Configurable by service type — different POD requirements applied automatically