One-Line Definition
A delivery attempt is a single instance in which a carrier brings a parcel to the recipient's address with the intention of handing it over — and either succeeds or fails for a specific, logged reason such as nobody home, an inaccessible entrance, or a refused package.
Real-Life Analogy
Think of a delivery attempt like a doorbell ring with consequences. A friend swings by your apartment at 2 p.m. to drop off your keys. They press the buzzer, wait about 30 seconds, and leave when no one answers. That was *one attempt*. They might try again tomorrow evening, or they might just tell you to pick the keys up from their place. Carriers operate the same way, except every ring is timestamped, geotagged, and photographed — and after a set number of failed rings, the parcel starts a countdown toward being returned to sender.
Core Formula
At its simplest:
Delivery Attempt = Arrival at Address + Handover Attempt + Outcome Logged
Each attempt produces exactly one of two outcomes:
- Successful (POD captured): signature, photo, or OTP confirms handover.
- Failed (exception raised): a reason code is attached, and the parcel moves to the next step in the carrier's workflow.
The failed-attempt reason codes matter more than most merchants realize. Common ones include:
| Reason Code | What It Means | Typical Next Step |
|---|---|---|
| `NO_ANSWER` / `RECIPIENT_ABSENT` | Someone was expected but didn't respond | Reattempt (often next business day) |
| `ACCESS_FAILED` | Gated community, locked lobby, no buzzer code | Reattempt or hold for pickup |
| `REFUSED` | Recipient declined the parcel | Return to sender |
| `ADDRESS_INVALID` | No such unit, wrong street number | Address correction requested |
| `CUSTOMS_HOLD` | Duties/taxes unpaid (cross-border) | Notify recipient to pay |
| `BUSINESS_CLOSED` | Delivered to a commercial address outside hours | Reattempt during business hours |
Comparison with Related Terms
Delivery attempt is often confused with adjacent logistics terms. Here's how they differ:
| Term | Definition | Key Difference from Delivery Attempt |
|---|---|---|
| **Delivery Attempt** | One physical try to hand over a parcel | The atomic unit — a single event |
| **Reattempt** | A second or subsequent attempt after a failure | A *new* attempt, usually with a fee or delay |
| **First Attempt Delivery (FAD)** | Industry metric for success on attempt #1 | A KPI, not an event; measures performance |
| **Delivery** | The successful completion of handover | The *outcome*, not the try itself |
| **Redelivery** | Carrier-initiated second attempt | Often scheduled by the recipient via portal |
| **Hold for Pickup** | Parcel routed to a locker, store, or depot | Alternative to further attempts |
| **Return to Sender (RTS)** | Parcel sent back after attempts exhausted | Terminal state after N failed attempts |
The critical distinction: a delivery is what you want; a delivery attempt is what actually happens — sometimes once, sometimes three times, sometimes never successfully at all.
Use Cases
1. Last-mile cost control. Every failed attempt costs a carrier roughly $10–$17 in the US and €8–€14 in the EU, versus about $2–$4 for a successful first attempt. With e-commerce parcels averaging 1.5–2.5 attempts in dense urban markets, failed attempts can consume 15–25% of last-mile operating cost. Carriers track attempts obsessively for this reason.
2. Cross-border customs friction. A parcel from Shenzhen to Frankfurt may clear customs but fail delivery because the recipient owes €12.40 in import VAT. That's a CUSTOMS_HOLD attempt failure — the parcel isn't lost, but it won't move until payment. Merchants who pre-collect duties (DDP) see first-attempt success rates jump by 20–35 percentage points.
3. High-value signature-required goods. Phones, laptops, and jewelry typically require a signature or OTP. If the recipient isn't home, the carrier won't leave the parcel — so a "failed" attempt is actually correct behavior, not a service failure.
4. B2B and commercial addresses. Deliveries to offices fail predictably outside 9 a.m.–5 p.m. windows. Smart merchants flag commercial addresses and route them to business-hours routes, lifting FAD rates significantly.
5. Subscription and grocery boxes. Perishables have a hard deadline. A failed attempt on a meal kit isn't just inconvenient — it's spoilage. These flows often use same-day reattempt or neighbor delivery protocols.
Misconceptions
"A failed attempt means the carrier didn't try." Usually false. Most carriers log GPS coordinates, timestamps, and often a photo of the door. If you see NO_ANSWER at 14:07, someone stood at your door at 14:07.
"Attempts are unlimited." Almost never. Standard practice is 1–3 attempts before the parcel is held or returned. DHL Express, for example, typically attempts once before routing to a service point. UPS and FedEx commonly attempt up to three times. After that, RTS fees apply — often $15–$25 plus original shipping.
"I can just tell them to leave it." Only if the merchant enabled authority to leave (ATL) or the carrier offers a signed release. For signature-required shipments, "just leave it" isn't an option — the attempt will fail by design.
"Reattempts are free." Sometimes, but not always. Many carriers charge $5–$15 per reattempt, and cross-border reattempts can trigger duplicate customs processing. Merchants often absorb this cost silently, which is why FAD optimization matters.
"Delivery attempt = delivery." No. A delivery attempt is an *event*; a delivery is a *result*. Confusing the two leads to bad dashboards and worse customer communication.
"If it failed, it's the customer's fault." Not necessarily. Invalid addresses, missing buzzer codes, broken access gates, and customs holds are merchant- or carrier-side failures. Blaming the recipient without checking the reason code is a rookie mistake.
Related Terms
- First Attempt Delivery (FAD) — the percentage of parcels delivered successfully on attempt #1; a core last-mile KPI.
- Reattempt / Redelivery — a subsequent try after a failed attempt.
- Proof of Delivery (POD) — evidence of successful handover: signature, photo, GPS, or OTP.
- Exception — the carrier's internal flag for any deviation from the expected delivery flow.
- Hold for Pickup / Service Point — redirecting a parcel to a locker or retail location after failed attempts.
- Return to Sender (RTS) — the terminal outcome when attempts are exhausted.
- Authority to Leave (ATL) — recipient pre-authorization for unattended delivery.
- Delivery Exception Code — the standardized reason label attached to each failed attempt.
- Last-Mile Delivery — the final leg of the supply chain, where attempts actually happen.
- DDP / DDU — Delivered Duty Paid vs. Delivered Duty Unpaid; determines whether customs friction causes attempt failures.
Bottom line: A delivery attempt is the smallest meaningful unit of last-mile execution. Track it, understand its failure codes, and optimize for first-attempt success — because every additional attempt burns margin, delays the customer, and inches the parcel closer to a return.