Proof of Delivery and POD

Proof of delivery is the documented end of the supply chain: it confirms that a shipment was handed over at the agreed location and at the agreed time. In international logistics jargon, this is referred to as POD – Proof of Delivery. For online retailers, fulfillment service providers, and end customers, POD is far more than a formality. It protects against payment defaults, clarifies disputes over "package not received," and provides measurable KPIs for delivery quality.

Without reliable proof of delivery, claims, chargebacks, and A-to-z guarantee cases remain on the retailer's desk – even if the package was actually delivered. Conversely, a well-archived POD helps resolve legitimate customer inquiries quickly and reduce support costs.

What do proof of delivery and POD mean?

Proof of delivery refers to any evidence documenting the successful handover of a shipment to the recipient or an authorized person. POD (Proof of Delivery) is the English technical term for the same concept and is used in a standardized way in carrier APIs, 3PL contracts, and international freight documents.

Typical components of a POD:

Date and time of delivery (scan timestamp)
Recipient name or delivery location (e.g., neighbor, parcel locker)
Signature, photo, or GPS coordinates (depending on carrier product)
Tracking number as a link to the order
Delivery status (delivered, not met, delivery refused)

Proof of delivery closes the chain that begins with the tracking number and tracking. While tracking makes the package's journey visible, POD legally and operationally completes the process.

Important: A tracking status of "Delivered" in the shop is visible to the customer – however, the complete POD with signature or photo is often only available from the carrier or in the 3PL archive. Both must be linked.

Types of proof of delivery

Carriers and fulfillment providers distinguish between several POD formats. The choice depends on the product, the value of goods, and contractual requirements.

Classic signature (paper POD)

The delivery driver obtains a physical signature – on a handheld device or paper receipt. The signature is digitized and assigned to the shipment record. Common for:

High-value shipments and B2B deliveries
Cash on delivery and payment upon delivery
Shipments with age verification or identity check

Electronic proof of delivery (ePOD)

With electronic proof of delivery, scans, signatures, photos, and metadata are transmitted directly to the carrier system. The retailer retrieves ePOD via API or portal. Advantages:

Faster availability (often minutes after delivery)
Better archiving and searchability
Integration into WMS and ERP without paper filing

Photo POD and location-based proof

Modern delivery processes in the last mile use photos of the handover location (front door, parcel box, reception desk). GPS coordinates can additionally document the delivery location. This reduces disputes over "package was not left," but does not replace a qualified signature everywhere.

Alternative delivery methods

Not every delivery corresponds to the classic handover at the front door:

Delivery method

POD content

Typical risk

Retailer relevance

Personal handover

Signature + name

Low with correct identification

Standard B2C

Safe place / drop-off location

Photo + "left" scan

Theft, weather exposure

Customer communication important

Neighbor delivery

Neighbor name + signature

Recipient denies knowledge

Check POD name for claims

Parcel locker / store

Locker scan + pickup code

Unclaimed packages

Use reminder emails

Delivery refused

Scan + reason code

Return costs, stock

Initiate returns process

POD formats at a glance

Format

Availability

Cost

Evidentiary value

API integration

Paper POD

Delayed (digitization required)

Higher (paper, scan)

High with qualified signature

Limited

ePOD

Minutes after delivery

Included in tariff

High (signature + metadata)

Fully via API

Photo POD

Quickly available

Low

Medium (location-based, no recipient name)

Partially as image download

POD in the fulfillment process

Proof of delivery is not created in the warehouse, but by the carrier – yet it is used multiple times within the fulfillment ecosystem.

Process flow: POD from delivery driver to archive

1

Delivery by carrier driver

2

Scan + POD capture (signature/photo)

3

"Delivered" event in carrier API

4

Webhook/polling into WMS or OMS

5

Order status "Delivered" in shop

6

POD file in document archive

7

Retrieval for claims or chargebacks

Role of WMS, 3PL, and shop system

In professional fulfillment, POD data flows through interfaces:

Carrier API provides delivery event and optionally POD image or PDF
WMS or shipping software stores the reference to the tracking number
ERP/shop sets order status and may trigger review requests
Archive retains POD according to retention period (often 90–180 days at carrier, longer recommended for retailer)

Those working with a fulfillment center or 3PL should specify in the SLA how quickly POD data is provided and forwarded in dispute cases.

Linking with order and shipment data

A POD is only as useful as its assignment. Mandatory links:

Order number ↔ tracking number ↔ POD reference
SKU and packing date for partial deliveries
Customer address for comparison in "wrong address" claims

Without the link, support loses valuable minutes – and in the worst case, the retailer loses a dispute.

Legal and economic significance

POD serves as evidence in various scenarios:

Customer claims non-receipt: Carrier POD with signature or photo exonerates the retailer, provided delivery was proper
Marketplace A-to-z / eBay Money Back Guarantee: Platforms often require tracking through "Delivered" plus POD for high-value cases
Chargebacks (credit card): Issuer checks proof of delivery; without POD, risk increases in favor of the buyer
B2B deliveries: POD can complete delivery note and invoicing (OTIF context)

Warning: "Delivered" in tracking is sufficient for some marketplaces – for high-value goods or repeated claims, payment providers explicitly require signature or photo POD. Contract and terms clauses alone do not replace carrier proof.

KPIs and quality assurance with POD

POD data can be used to derive operational metrics used in service level agreements and fulfillment reports:

KPI

Definition

Data source

Target value (guideline)

Delivery rate

Share of shipments with "Delivered" status

Carrier tracking + POD

> 98 %

First-attempt delivery

Delivery on first delivery attempt

POD timestamp vs. attempts

> 90 %

POD availability

Share of shipments with retrievable POD

API/archive check

> 99 %

Non-receipt claim rate

Cases "package not there" / total deliveries

CRM + POD comparison

< 0.5 %

Statistic – POD availability: Share of B2C shipments with digital ePOD within 24 hours – trend 2020 to 2025 rising from approx. 72 % to over 94 % due to mandatory scanners at major carriers.

Best practices for retailers and 3PLs

The following recommendations have proven effective in e-commerce fulfillment:

Organizational

Integrate POD retrieval into claims workflow (who retrieves which proof when?)
Define retention periods (at least beyond the 120-day chargeback period)
Support training: explain difference between tracking status and complete POD

Technical

Use carrier webhooks for "Delivered," not just nightly batch import
Store POD files (PDF/JPG) centrally, not just as a link to the carrier portal
Maintain a unified data model in the OMS for multi-carrier setups

Communication

Inform customers after delivery (with tracking link, not POD data for data protection reasons)
Offer prior consent for safe-place delivery at checkout where the carrier supports it

Tip: For recurring "non-receipt" cases at the same address: present POD with recipient name and delivery location to the customer in a structured way – this often resolves the case without a replacement shipment.

Checklist: Setting up POD processes

Review carrier contracts: Which POD types are included in the tariff?
API documentation: Are signature and photo provided as downloads?
WMS/shipping software: Automatic import of "Delivered" event configured
Archive: Storage location and retention for POD files defined
Support guide: Process for "package not received" with POD retrieval documented
3PL contract: Response time for POD requests anchored in SLA
Partial deliveries: Each tracking number individually traceable with POD
Data protection: Use POD internally only, no unnecessary sharing of personal data with third parties

Common mistakes and how to avoid them

001. Only storing tracking status, not archiving POD

Many shops store "Delivered" but not the associated signature image. Months later, proof is missing at the carrier. Solution: Automatically download POD on delivery event and attach to order.

002. Confusing order and tracking numbers

Support searches for POD at the carrier using the order number – without success. Solution: Always prominently display the tracking number in every customer email and in the admin.

003. No process for neighbor delivery

Customer denies being informed by the neighbor. Solution: Check POD for neighbor name; define internal policy for replacement delivery.

004. SLA with 3PL without POD clause

In a dispute, the partner delivers "later" – the marketplace deadline expires. Solution: Contractually fix maximum response time for POD forwarding.

005. Ignoring international shipments

POD standards differ by country and carrier. Solution: Check per target market which proof is considered sufficient.

Frequently asked questions about proof of delivery and POD

Is tracking "Delivered" the same as POD?

No, POD is the detailed proof (signature/photo/metadata).

How long does DHL store POD?

Carrier-dependent, often 90–120 days; retailers should archive themselves.

Do I need POD for letter shipments?

Yes for goods value and claim risk; for pure letter products often only delivery confirmation without signature.

Can the customer view the signature?

For data protection reasons, usually only upon legitimate request and without third-party data.

What if the package is damaged despite POD?

POD proves handover, not intact condition; separate photo documentation upon delivery is relevant.

Connection to other shipping terms

Proof of delivery stands at the end of the chain of shipping and tracking terms. It builds on the tracking number, completes the last mile, and becomes relevant as soon as returns or claims arise. Those who document pick-pack-ship and carrier scans consistently have the strongest starting position in POD disputes.

Workflow: "Package not received" claim

1

Record customer inquiry

2

Identify tracking number

3

Check tracking status

4

Retrieve POD from carrier/3PL

5a

POD confirms delivery: inform customer

5b

No POD or contradiction: investigation or goodwill per policy

6

Document case and update KPI