Reattempt Assignment: Turning a Failed Delivery Into a Recovered One in 2026

Reattempt assignment is the decision about when, by whom and on which route a failed delivery is tried again. It is made after a failed first attempt, using the reason for the failure, the customer’s new availability and the cost and risk of each option. Most operations answer it by default, pushing the stop onto tomorrow’s route, which is the slowest and often the most expensive recovery. Delivery experience depends on this moment, because the customer who missed the first window is already watching the second. For VPs of Operations and heads of delivery experience at retailers, grocers and brands that run their own or contracted last-mile fleets, this guide sets out a six-step reattempt ladder, the metrics to track and what to demand from software. Locus, the world’s first Decision-Intelligent, Agentic TMS, treats the reattempt as a dispatch decision with constraints.

Why Reattempt Assignment Matters: The Business Case

Missed windows lead consumer complaints. In Locus’s Q4 2025 survey of 1,000 US online shoppers, 21% of consumers named missed delivery windows as their biggest irritation, 17% reported “sorry we missed you” notices, and 93% said shipping and delivery influence how they evaluate a company.

The cost of a second miss is high. In AlixPartners’ 2026 home delivery survey, more than half of consumers said they would boycott a retailer entirely after just one or two missed deliveries, more than 85% said a poor delivery experience reduces their willingness to repurchase and nearly 90% said a late delivery at least weakens their relationship with the retailer.

A failed attempt also costs operations. According to Locus, a failed first attempt costs roughly twice as much as a successful one, because a re-delivery repeats the original attempt’s driving, handling and customer contact. The figure is Locus’s own estimate, so measure your own reattempt cost per order.

What Is Different About Reattempt Assignment

It starts from a reason, not a stop. A customer who was not home, a gate that was blocked and an address that was wrong need three different responses, and only the first is solved by trying again.

The customer’s availability is the new constraint. The second attempt is useful only if it lands in a window the customer has confirmed.

It competes with new orders. A reattempt takes the same driver time and vehicle capacity as the day’s other stops, so every insertion has a price.

It has a clock. The customer’s patience, perishable goods and promised windows on the same route all shorten the time available to recover.

It needs a limit. Without an attempt cap and a fallback, a hard-to-deliver stop can absorb several attempts at full cost.

How Locus Approaches Reattempt Assignment

Locus, the world’s first Decision-Intelligent, Agentic TMS, was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

Locus treats a confirmed customer window as a constraint in the route plan. Its DispatchIQ engine receives the confirmed window, the Fireworks routing engine anchors those stops first alongside vehicle capacity, driver hours, road restrictions and live traffic, and continuous re-optimization recalculates active routes when a customer asks for a new window, moving affected stops to the best available future slot while protecting the promises already made on the route. Its Dispatch and Capacity agents make the assignment, the Customer agent handles customer communication and six governance mechanisms, including explainability, autonomy levels and human-in-the-loop approval, keep dispatchers in control of what runs automatically. Locus models 250+ real-world constraints and has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries. Public sources do not describe a dedicated reattempt workflow, so during evaluation ask Locus how failure reasons are captured and used, how a same-day reattempt is priced against the rest of the route, how attempt caps and fallbacks are configured and how second-attempt success is reported. 

How to Assign a Reattempt in Six Steps

1. Capture the failure reason at the door

Have the driver record a structured reason code, with time, location and a photo where policy allows. Reasons such as customer not available, access blocked, address problem, refused and vehicle or time shortfall lead to different actions.

2. Classify what a reattempt can fix

Mark each failure as recoverable today, recoverable with customer input or not recoverable by trying again. An address error needs a correction first, and a refusal needs a return or a conversation, not another run.

3. Reconnect with the customer within minutes

Offer new windows or an alternative such as a pickup point or a safe place where your policy allows, and capture the answer as a structured availability. A reply that sits in an inbox does not change the route.

4. Price the options

Compare same-day insertion into an active route, the next day’s route and a dedicated trip on added drive time, driver hours, capacity and the risk to windows already promised. Insert same-day only when the vehicle has the capacity and time and no committed window slips.

5. Assign and resequence with the confirmed window as a constraint

Place the stop in the chosen route, treat the confirmed window as a hard constraint, cluster it with nearby stops and update the driver’s sequence and the customer’s ETA. The change has to reach dispatch before the plan is built, as the appointment guide linked above explains.

6. Cap attempts, escalate and learn

Set a maximum number of attempts per order, then switch to a fallback such as a pickup point or a return. Log the outcome of every reattempt so the policy improves.

Next-Day Default vs Rules-Based vs Decision-Driven Reattempt: Key Differences

What to Look for in Reattempt and Rescheduling Software

Structured failure reasons. Look for reason codes captured in the driver app that feed the reattempt decision, not a free-text note.

A reschedule loop into dispatch. Check that a changed window reaches the route plan before it is built, and that the original slot is released.

Mid-route insertion with constraints. Ask whether a reattempt can be added to an active route while respecting capacity, driver hours and committed windows.

Attempt caps and fallbacks. Look for rules that set attempt limits by reason and order value and switch to a pickup point or return.

Reattempt reporting. Check for first-attempt success, second-attempt success, recovery within 24 hours and cost per recovered delivery.

Delivery Reliability in Action: Real-World Results

Neither deployment below is a reattempt study. They show what constraint-based dispatch delivers where windows decide the outcome.

A leading Indian online grocery retailer serving 10M+ customers in 25+ cities. Perishable orders, express and slot-specific deliveries and a short window between order and delivery left little time to plan by hand. With AI route planning that treated customer time-slot preferences as constraints, built dynamic clusters and tracked planned against executed routes, the retailer reached 99.5% SLA adherence and cut distance traveled from 863 km to 741 km, a 14.28% saving, according to the Locus case study.

A leading Vietnamese beverage company serving thousands of small retail points a day. Routes were built by hand in spreadsheets, many shops had no validated delivery location so drivers found them on the road, and distributors had no live view of vehicles or deliveries. With automated route planning, address validation, mid-route re-optimization and a live dashboard, the company saw 37% less fuel consumed, 22% more orders per delivery trip, 12% less distance and 35% less time on route planning. Read the beverage distributor case study.

Common Reattempt Assignment Mistakes to Avoid

Defaulting every failure to tomorrow. It is the slowest recovery, so price same-day insertion when capacity allows.

Treating all failures as the same. A wrong address needs a correction and a refusal needs a decision, so retrying without the reason wastes an attempt.

Letting the reschedule sit in a message thread. A customer’s new window only helps if it reaches dispatch before the route is built.

Having no attempt limit. Without a cap and a fallback, one hard stop can cost several full attempts.

For operations and delivery experience leaders asking how to assign reattempts, Locus offers one platform that plans, re-sequences and communicates, so a failed first attempt becomes a priced decision and not a default.

To see how Locus would handle reattempts in your network, schedule a demo.

Frequently Asked Questions

What is reattempt assignment? It is the decision about when, by whom and on which route a failed delivery is tried again, made using the reason for failure, the customer’s new availability and the cost of each option. It sits between a failed first attempt and a recovered delivery.

Should a failed delivery always be reattempted the next day? No. Next-day is the default, but same-day insertion into an active route, a dedicated trip, a pickup point or a return can be faster or cheaper depending on capacity, the reason for failure and the promised windows on the route.

How many delivery attempts should I allow? Set a cap by reason and order value and define a fallback, such as a pickup point or a return, for when it is reached. The right number depends on your cost per attempt and customer tolerance, so measure both.

How does customer availability change a route? A new confirmed window becomes a constraint, and the stop is moved to a route and slot that meet it. The change has to reach dispatch before the plan is built, or the original window can be attempted again.

What metrics show whether reattempts are working? Track first-attempt success, second-attempt success, the share of failures recovered within 24 hours, attempts per order and reattempt cost per order. Break them down by failure reason.

Does Locus support reattempt assignment? Locus treats confirmed customer windows as constraints, re-optimizes active routes and reschedules stops while protecting promised windows. Ask Locus how failure reasons, attempt caps and second-attempt reporting work in your setup.