Failed Delivery Versus Attempted Delivery: Carrier Policies And Documentation

A delivery that was not completed successfully and may require reattempt, customer contact, or return.

Failed Delivery is a delivery that was not completed successfully and may require reattempt, customer contact, or return. In carrier and logistics terminology it’s essential to distinguish a true failed delivery from an "attempted delivery" or other exception codes because the classification affects fees, liability, and next steps.

Carriers maintain precise definitions and codes in their operating procedures and tracking systems. An "attempted delivery" usually indicates the driver visited the address but could not hand over the shipment for a specific reason (recipient absent, access denied, abnormal conditions). A "failed delivery" is often the broader outcome when the shipment ultimately cannot be completed within the expected number of attempts or delivery window and requires escalation or return.

How Carriers Define Each

Each carrier’s manifest or tracking API will show statuses such as "Out For Delivery," "Attempted Delivery - No Access," "Delivery Exception," and "Returned To Sender." Knowing how your chosen carriers mark these statuses is important for SLA calculations and customer messaging. For example, one carrier might mark a package as "Customer Not Home" on the first failed attempt and still consider the shipment active for three days, while another may immediately route it back to a sorting center for hold or return.

Required Documentation And Proof

Documentation around failed attempts is critical for dispute resolution and billing. Carriers typically capture electronic proof: GPS coordinates, driver notes, photographs of the delivery location, and timestamped status updates. When disputes arise (for example, customer claims non-delivery), these records are the primary evidence for claims handling.

• POD Data: Proof of delivery or attempted delivery entries with timestamps and reasons.
• Driver Notes: Free-text explanations for access issues, refusals, or hazards.
• Multimedia Proof: Photographs or video of the delivery location, parcel condition, or notice left.

Liability, Fees, And Who Pays

Responsibility for failed deliveries depends on contractual terms. If the carrier’s route or handling caused the failure, the carrier may absorb re-delivery costs. If the customer provided incorrect address details, the shipper (merchant) often bears re-delivery and return fees. High-value or insured shipments add another layer: carriers may refuse liability for damage or loss if handling instructions were unclear.

How This Affects Claims And Refunds

Merchants and carriers should adopt a standard process for claims following failed deliveries. That includes retrieving the delivery attempt documentation, confirming the recipient’s communication history, calculating incremental costs, and deciding whether to refund, resend, or issue a credit. For marketplace sellers, platform policies often require evidence of failed delivery attempts before issuing refunds or allowances to buyers.

Practical Scenarios And Carrier Examples

Scenario: A carrier records three "attempted delivery" statuses over 48 hours. The customer never responded to SMS notifications and did not pick up from the local depot, so the carrier marks the shipment as "Returned To Sender." The merchant then absorbs return freight and restocking costs, unless the original address was incorrect in which case fee negotiations may occur with the carrier.

Tips For Merchants And Logistics Teams

• Understand Carrier Codes: Map each carrier’s exception codes to your own internal statuses to automate workflows.
• Collect Proof: Require carriers to enable photographic or location-based evidence for failed attempts to reduce disputes.
• Address Verification: Validate addresses and prompt customers to confirm delivery details for high-value items.
• Contractual Clarity: Define liability and re-delivery fee responsibilities in carrier contracts and 3PL SLAs.
• Automate Notifications: Push exception notifications from carrier APIs into your customer service platform to speed resolution.

In short, the Failed Delivery status carries operational, financial, and contractual consequences. Distinguishing it from an "attempted delivery," collecting robust documentation, and aligning carrier contract terms with your recovery processes reduces disputes and control costs associated with exceptions.