What Does "Out for Delivery" Mean, And Why the Status Often Fires Before the Van Leaves
A mid-size courier operation in the northeast pulled its Q1 contact-centre data and found something uncomfortable. Call volume was up 38% on the prior quarter. Every spike traced to the same window: 7:15am to 8:30am, Monday through Friday. That's the hour when their warehouse management system fires the "Out for Delivery" notification at depot load scan. The vans, in many cases, didn't actually roll until 10am or later.
Customers were watching the status flip on their phones, refreshing tracking pages every few minutes, and calling support when nothing happened. A handful posted reviews. None of it was the drivers' fault. The status was firing three to four hours before the wheels turned.
This is the gap most search results won't explain. So let's answer the literal question, then expose what's really happening.
The 38% Call Spike That Exposed What "Out for Delivery" Really Means
The operations manager who flagged the spike thought it was a driver problem at first. Late departures. Long coffee breaks. Maybe a dispatch issue.
It wasn't.
The drivers were on schedule. The vans were loaded by 7:30, briefed by 8:15, rolling by 9:30. Normal morning rhythm for an 80-stop urban route. The problem was upstream of the driver entirely.
Their tracking system was wired to fire "Out for Delivery" the moment a parcel was scanned onto its assigned van at the depot. That's an industry-standard trigger. It's also wrong for the customer experience.
Because the customer reads "Out for Delivery" as "the driver is on the way to me right now". And for two to four hours each morning, that wasn't true.
Once they reconfigured the trigger to fire on the GPS departure event from the depot gate instead of the load scan, the morning call spike collapsed. Same drivers. Same routes. Same parcels. Different status timing.
That's the entire story of "Out for Delivery" in 2026. The notification is doing its job. It's just being fired at the wrong moment.
The Plain-English Definition (And the One Most Carriers Won't Print)
Here's the textbook definition first, because that's what most people land here looking for.
"Out for Delivery" means a parcel has been loaded onto its final delivery vehicle and is in the hands of the driver who will hand it to the recipient that day.
In EDI exchanges between warehouse management and transport management systems, this maps to event code OFD, often expressed as status code 19 in carrier-shipper feeds. It sits between "In Transit" (the parcel is moving through the carrier network) and "Delivered" (the parcel is with the recipient).
That's the clean answer.
The asterisk most carrier help pages don't print: the status is set by a scan event, and every carrier chooses which scan triggers it. The definition is technically the same. The trigger configuration is wildly different.
So the parcel is "on a delivery vehicle". Sure. Is the vehicle moving? That's the question the status doesn't answer.
What Actually Triggers the "Out for Delivery" Status, Depot Scan vs Vehicle Departure
There are three plausible trigger points a carrier can use:
1. The depot load scan. Each parcel is scanned as it goes onto its assigned van. Easy to capture. Cheap to wire up. Common default in legacy WMS-TMS integrations.
2. The vehicle departure GPS event. The status fires when the van's telematics show it crossing the depot geofence. Requires fleet GPS integration. Reflects what the customer actually wants to know.
3. The first-stop departure. The status fires when the driver leaves the first delivery of the day. Useful for stop-by-stop notifications but unusual as a global "OFD" trigger.
Most national carriers use option 1, mostly for historical reasons. The scanning infrastructure was built before fleet GPS was ubiquitous. The trigger never moved.
The USPS Office of Inspector General has flagged scanning accuracy issues across multiple audits, finding that a measurable share of "Out for Delivery" scans are recorded at depot induction rather than at actual vehicle departure. The same pattern shows up in private-carrier complaint data.
This isn't carriers being lazy. It's a definition that made sense in 2005 and didn't get updated when the customer-facing app got built.
Why Your ETA Feels Wrong: The Gap Between Status Update and First Stop
The trigger problem cascades into the ETA problem.
If the status fires at 7:15am, the system has to publish an ETA window. Most carriers publish a static window: "today between 9am and 6pm". Some publish a tighter "by end of day". A few attempt a dynamic ETA based on the planned route sequence.
The dynamic ETA is closer to truth. The static window is closer to legal cover.
Here's the catch. Even the dynamic ETA, calculated at 7:15am off the planned route, is often optimistic by 90 minutes or more. Why? Because the route plan assumes a 7:30 departure. The driver actually departs at 9:30. Every stop's ETA is shifted by two hours, but the customer's notification still says "11:42am".
McKinsey's last-mile research notes that recipient communication accuracy is one of the top three drivers of repeat-delivery cost, with last-mile expenses representing roughly 41% of total parcel supply-chain costs. The cost of the inaccurate ETA isn't just an annoyed customer. It's the failed first attempt, the redelivery fee, the support call, the negative review. Each failed attempt compounds.
The fix is straightforward in concept: recompute the ETA from real-time vehicle position, not from the planned route. Locate2u's route engine does this natively, pushing live ETAs to the recipient as the driver moves through the route. The status moves with reality, not ahead of it.
How Major Carriers Differ: When Each One Fires the Notification
The trigger varies more than most customers realise. Here's a snapshot of what each major carrier has historically done, based on their public documentation and customer-facing tracking behaviour.
| Carrier | Typical OFD trigger | ETA accuracy |
|---|---|---|
| UPS | Depot load scan, with route-based dynamic window for some service tiers | Tighter on premium tiers, broad window on ground |
| FedEx | Depot scan with vehicle-load confirmation | End-of-day window, narrowing closer to delivery |
| USPS | Depot induction scan, often hours before carrier departure | Day-level only for most mail classes |
| DHL | Vehicle-load scan with route-start confirmation on express tiers | Tight window on express, day-level on standard |
| Amazon Logistics | Driver app handoff plus route-start GPS | Often live stop-by-stop ETA |
| Self-managed fleets | Configurable, depending on platform | Best when wired to GPS departure plus dynamic ETA |
Notice the pattern. The carriers customers complain about most for "Out for Delivery" timing tend to be the ones triggering on depot scan. The ones with stop-by-stop visibility, like Amazon Logistics, generate fewer "where is my driver" calls because the customer can see for themselves.
For self-managed fleets, the trigger is whatever you configure it to be. Which means the experience is yours to fix.
From "Out for Delivery" to "Delivered", The Stops in Between
What happens between the OFD status and the doorbell? More than most recipients realise.
A typical urban route in 2026 looks like 70 to 100 stops across an 8-hour shift. The driver leaves the depot, drives to a cluster of stops in the first suburb, works through them, drives to the next cluster, and so on. The route is sequenced for efficiency, not for the order parcels were loaded.
Your parcel might be stop 4 or stop 84. The status alone doesn't tell you which.
Here's the in-between:
- Pre-route. Parcel is on the van but the van hasn't left.
- En route to first cluster. Driver is moving but hasn't started delivering.
- Active delivery cluster. Driver is doing 8 to 15 stops in close proximity.
- Inter-cluster transit. Driving between cluster zones, no stops being made.
- Delivery attempt. Driver is at the address, ringing the bell or scanning the parcel.
- Delivered or attempted. Final status set.
A recipient who's stop 80 of 80 might see "Out for Delivery" at 7:15am and not see "Delivered" until 5:45pm. That's a ten-and-a-half-hour gap where the status hasn't moved. Nothing is broken. They're just at the end of the route.
This is where proof of delivery closes the loop. The "Delivered" status alone is just text. A geotagged photo, a signature, or a barcode scan turns it into evidence the recipient and the shipper can both trust.
What Dispatch Teams Should Configure Differently (Trigger on Departure, Not Scan)
If you run dispatch for a fleet of any size, the fix list is short and high-impact.
1. Move the OFD trigger to the vehicle-departure GPS event. Set a geofence around the depot. Fire the status when the van crosses it outbound. This single change closes the morning expectation gap.
2. Publish dynamic ETAs from the live route engine, not from a static delivery window. The route optimiser already knows the planned sequence. Recalculate ETAs every 15 minutes against actual driver position. Push the updated ETA to the customer.
3. Send a second notification at "Next Stop". Some recipients want to know when they're next, not just that the van is somewhere out there. A "your driver is 3 stops away" message converts angst into a specific window.
4. Capture proof of delivery on completion. Photo, signature, barcode. All three for high-value or contested deliveries.
5. Audit the carrier fee differently. Failed first attempts often trigger a redelivery surcharge. Each one is a sign that the customer wasn't ready, which is often a sign that the ETA was wrong.
The Locate2u driver app handles trigger configuration in the dispatcher settings. Pair it with real-time tracking and the recipient sees the van move on a live map, not a stale status from three hours earlier.
Gartner research indicates that delivery-status accuracy ranks among the top customer-experience drivers in retail logistics, with status-mismatch events being a leading cause of contact-centre escalation. The fix isn't a new feature. It's a configuration change.
What Recipients Should Do When the Status Stalls
If you're the one waiting for a parcel, the practical guidance is different.
Hour 1 to 3 after OFD: nothing. The driver may not have left yet, or may be at the start of a long route. This is normal.
Hour 4 to 6: still likely fine. The driver is probably mid-route. Check the carrier's tracking page for any updated ETA window. If you're at the end of an urban route, this is your range.
Hour 7 to 8: start watching. End of standard delivery shift is approaching. If you have a delivery instruction (back porch, signature waiver, secure location), make sure it's set in the carrier app.
End of day with no delivery: check the status. If it still says "Out for Delivery", the driver may have run out of time. Most carriers will roll the parcel to the next business day automatically. Contact the sender if it matters.
Status hasn't moved for 48 hours: something has gone wrong. The parcel may be stuck on a van that returned to depot, mis-scanned, or held at a sort facility. This is the moment to call the carrier with your tracking number.
The hardest thing to accept: "Out for Delivery" doesn't mean "soon". It means "today, probably". Statista's parcel-volume reporting shows the bulk of delivery-status complaints concentrate in the final-mile leg, where this single status is the most-viewed event. Patience helps. Live tracking helps more.
Frequently Asked Questions About Out for Delivery
How long does "Out for Delivery" take?
Anywhere from 30 minutes to 10 hours, depending on where you are on the route and what time the carrier triggered the status. Urban routes typically run 8 to 9 hours from first to last stop. Rural routes can be longer.
Can "Out for Delivery" come the next day?
Yes, occasionally. If the driver runs out of time, can't access the address, or the parcel is mis-scanned back into the depot, the delivery rolls to the next business day. The status sometimes updates to reflect this, sometimes doesn't until the next morning's scan.
What if the status doesn't update?
Wait 24 hours. Most stalled statuses resolve themselves overnight when the parcel is rescanned. If the status hasn't moved after 48 hours, contact the carrier with your tracking number. Don't contact the shipper first; they'll just check the same tracking page you're looking at.
Does "Out for Delivery" mean it will be delivered today?
Usually, but not guaranteed. Carriers commit to "today" when they fire the status, but factors like weather, vehicle issues, address access, or driver hours can push the parcel to the next day. The status is an intent, not a contract.
Why does my ETA keep changing?
If your carrier publishes dynamic ETAs (good), the window narrows as the driver moves through the route. If your carrier publishes a static window (less good), the ETA shouldn't change at all. A wildly shifting ETA usually means the route is being resequenced live, often because of a missed earlier stop.
What's the difference between "In Transit" and "Out for Delivery"?
"In Transit" means the parcel is moving through the carrier network: line-haul trucks, sort facilities, depot transfers. "Out for Delivery" means it's on its final-mile vehicle for handoff to you. PwC's transportation analysis highlights that real-time visibility across these stages is a core differentiator for carrier and shipper customer experience.
If you run a fleet and you've recognised your operation in any of this, the trigger configuration and live-ETA fix is something Locate2u handles in our last-mile delivery platform, with the same logic working for courier service operators from three vans up to thousands. Talk to our team if you want to walk through how the OFD trigger lives inside your dispatch flow today, and what it would look like wired to vehicle departure instead. The 38% call spike at the top of this article wasn't a software problem. It was a configuration problem. Most are.