Attempted Delivery Vs Delivery Exception: Key Differences

A delivery attempt that could not be completed because of access, signature, address, customer, or carrier issues.

Attempted Delivery is a delivery attempt that could not be completed because of access, signature, address, customer, or carrier issues. While closely related to delivery exceptions, the two terms are not interchangeable and have different operational and contractual implications.

Clarifying the difference between an Attempted Delivery and a delivery exception helps logistics teams manage customer expectations, process claims correctly, and decide on reattempt or return workflows.

How The Terms Differ

An attempted delivery documents that a carrier physically reached the delivery location but could not complete the drop. A delivery exception is a broader term that covers any unexpected event that disrupts the normal shipment flow, including in-transit damage, customs delays, or carrier routing errors.

• Attempted Delivery: Location reached; action failed due to access, signature, or recipient issues.
• Delivery Exception: Any disruption that deviates from the planned transit, which may occur before, during, or after an attempted delivery.

When Each Status Is Used

Carriers use standardized status codes. An attempted delivery is recorded specifically at the point of attempted drop-off. A delivery exception may be logged at multiple points—when a shipment is damaged, when weather halts operations, or when paperwork delays customs clearance.

For example, a driver who cannot access a gated apartment and marks an attempted delivery has created a local exception, but the carrier may also classify it under a broader delivery exception category in internal reporting.

Impact On Liability And Claims

Understanding which status applies affects claims, liability, and the applicable timeframes for refunds or insurance. An attempted delivery provides evidence the carrier made an effort; if the reason is recipient unavailability, the carrier may not be liable. If the attempt fails because the driver used the wrong address, the carrier may bear responsibility.

• Carrier Responsibility: Carriers are liable when internal errors or negligence cause the failed delivery.
• Shipper Responsibility: Shippers who supplied incorrect addresses or inadequate instructions usually assume the cost of reattempts or returns.
• Insurance Claims: Proof of attempted delivery can be required to settle disputes over loss or damage occurring after the attempt.

Operational Differences For Merchants

For a merchant's operations team, distinguishing between the two determines the next steps: schedule a reattempt, authorize alternate pickup, file a claim, or initiate a return. Incorrectly treating a delivery exception as a simple attempted delivery can delay resolution and increase costs.

Merchants should map status codes from their carriers to internal workflows so that each exception type triggers the correct customer notification, refund window, or escalation to carrier support.

Practical Examples

Example 1: A driver arrives at an address but cannot enter a locked building and logs "Attempted Delivery – No Access." The merchant contacts the buyer to confirm building access and schedules a reattempt.

Example 2: A shipment is held up in customs due to missing documents. The carrier logs a "Customs Exception." This is not an attempted delivery—the package was not presented to the recipient but is delayed in transit at a border facility.

Tips For Reducing Confusion

• Status Mapping: Build a mapping table between carrier codes and your internal statuses to avoid incorrect handling.
• Automated Alerts: Trigger different customer messages for attempted deliveries ("We tried to deliver") versus exceptions ("Shipment delayed due to customs").
• Evidence Collection: Require carriers to capture photos, GPS, and reason codes for attempted deliveries to support dispute resolution.
• SLA Definitions: Clarify in contracts what constitutes an attempted delivery, an exception, and who bears the cost for reattempts and storage.

In short, the Attempted Delivery status denotes a failed physical delivery attempt caused by access, signature, address, customer, or carrier issues; a delivery exception is a broader category of disruptions. Distinguishing them ensures proper operational responses, correct liability assignment, and clearer customer communication.