COD delivery failure reasons

Why does an unreachable phone cause so many failures?

Most carriers call or message ahead of a delivery attempt to confirm the customer will actually be available at that time, especially for home delivery where a wasted trip costs real driver time and fuel that nobody recovers afterward. If that call goes unanswered, drivers often skip the stop entirely rather than making the trip anyway on the small chance someone happens to answer the door, and the parcel returns as a failed attempt logged against the order without further explanation. A phone that was valid at order time can still be unreachable at delivery time days later: switched off to save battery, out of credit and unable to receive calls, or simply not picked up because the number calling looks unfamiliar on the screen and gets ignored like spam from a stranger. Collecting a second phone number at confirmation gives the driver a genuine fallback instead of a dead end when the first number does not answer on the day.

Why does address quality matter this much?

Because a landmark is not an address in the sense a driver working an unfamiliar route actually needs to complete a delivery successfully. "Near the big mosque in [commune]" might be enough for a local resident giving spoken directions to someone who already knows the neighborhood well, but it is not enough for a driver working through a route of twenty stops who has never been to that specific street before today and has no time to search around asking strangers. A specific building number, floor, or a nearby fixed point plus a phone number the driver can call for final directions closes the gap that a landmark alone leaves wide open on delivery day. Stores that switch from free-text address fields to a structured wilaya, commune, and detail field usually see failed-attempt rates drop measurably within a few weeks of making that one change to their intake form.

What does "customer not available" actually cover?

Genuine unavailability at the specific time a driver attempts delivery, which is distinct from a phone that cannot be reached at all regardless of when it is tried during the day. A customer at work during normal daytime hours, or traveling for a few days on business or family matters, who confirmed the order in good faith but was never told, or asked, about a delivery window that might not actually suit their schedule that particular week. Some carriers support scheduling or a callback before the attempt is even made; using that option where it is available, and asking the customer during confirmation for a rough availability window, reduces this category without needing better addresses or faster phones, since the underlying issue here is timing rather than reachability itself.

How do these four reasons compare in practice?

The first three are logistics problems solvable with better data collection at the intake stage, before a parcel ever leaves the warehouse. The fourth is a confirmation problem wearing a delivery-failure label in your reporting, and no amount of address detail fixes a customer who never really agreed to the order in a way that would hold up once the driver actually arrives at the door.

What is the highest-leverage single change here?

Adding a second phone number as a required field at confirmation, if you collect only one today and have not yet made this simple change to your process. It is the cheapest change to make of any on this list, touches every single order rather than a subset of them, and directly addresses what is usually the single largest reason a delivery attempt fails on the first try in the field. Pair it with asking for a specific address detail beyond a landmark alone, and most of the fixable share of delivery failures gets addressed without touching confirmation policy or shipping speed at all, leaving those as separate levers you can pull once this one is already in place and working.