Shipping delay and failure handling

Every Egyptian store eventually ships a parcel that stalls in transit, gets a failed delivery attempt, or simply goes quiet on the courier's tracking page, and what separates a calm store from a chaotic one is not luck but a written protocol that everyone on the team follows the same way every time. When a shipment goes wrong, the clock is your enemy: a buyer paying cash on delivery who hears nothing for four days starts assuming the worst, and a silent merchant is the fastest way to turn a recoverable delay into a refused box, a chargeback-style dispute, or a one-star Instagram comment.

This lesson is your internal escalation playbook for exactly those moments — how to detect that a shipment is in trouble, who you contact first, what you say to the courier and to the customer, and how you decide between reshipping and refunding. It is deliberately not your public shipping promise and not your guide to picking a carrier; it is the operating procedure your team runs after the parcel has already left and something has gone wrong on the road.

Detect the problem before the customer does

The goal is to catch a stuck shipment from your side, so you are the one breaking the news, not reacting to an angry message. Define clear triggers and check them daily, ideally every morning.

• Tracking stalls. A shipment that has not changed status in 24 hours inside Greater Cairo, or 48 hours to the Delta, Alexandria, or Upper Egypt, is a flag — not a disaster yet, but it enters your watch list.
• Failed delivery attempt. The courier marks "customer unreachable," "wrong address," or "rescheduled." This is the most common failure in Egypt and almost always means a phone or address problem you can fix fast.
• Courier silence. No scan for 72 hours anywhere in the country means escalate immediately; the parcel may be sitting in a hub or lost.
• Promised window breached. Any order that has passed the delivery window you quoted at checkout, regardless of tracking, gets a proactive update from you.

Use your store's shipment view and order history to spot these without chasing each parcel by hand. The earlier you see it, the more options you still have.

The escalation steps, in order

Run the same sequence on every flagged shipment. Skipping straight to a refund before you have talked to the courier wastes money you did not need to lose.

1. Confirm what the courier sees. Open the tracking detail and, if it is unclear, contact the courier's merchant support with the AWB number. Ask one question: where is the parcel right now and what is blocking it.
2. Fix what you can on your side. If the failure is "wrong address" or "unreachable," re-verify the customer's phone and address from your records and from a quick WhatsApp message, then hand the corrected details back to the courier for a re-attempt.
3. Tell the customer before they ask. Send a short, honest WhatsApp or call: acknowledge the delay, give a realistic new date, and confirm their address. For a COD order, reconfirm they still want it — this single step prevents a wasted re-delivery.
4. Set an internal deadline. Give the courier a firm window to re-attempt (for example 48 hours). If it lapses with no movement, escalate to a supervisor at the courier or trigger a recall.
5. Resolve the case. Once the situation is clear, choose to reship, recall and refund, or close as delivered. Never leave a flagged shipment open with no decision.

Reship, recall, or refund — how to decide

The right ending depends on whether the parcel is recoverable and how the customer paid.

• Reship when the item is back with you or never moved and the buyer still wants it. Cover the second shipping fee yourself if the failure was your error or the courier's; this protects the relationship for a few EGP.
• Recall and refund when the parcel is genuinely lost, the customer has cooled off, or a re-attempt already failed. For a prepaid order, push the refund through your normal channel promptly. For COD, no money changed hands, so simply confirm the cancellation and stop the round-trip fee from repeating.
• Hold and investigate when the courier claims delivered but the customer denies receipt. Request the proof of delivery and signature before refunding, because this is where fraud and courier mistakes both hide.

Whatever you decide, the refund and exchange mechanics themselves belong in your returns process, which this protocol simply triggers once a refund is the chosen path.

Log the failure so the pattern shows

Every escalated shipment is data. Record the courier, the governorate, the failure reason, and how it ended. After a month you will see that most failures cluster — one courier weak in Upper Egypt, one governorate with chronic address problems, or a spike during a Ramadan rush when everyone's last mile slows. That pattern tells you whether to switch carriers on a route, demand prepayment in a problem governorate, or tighten your confirmation step before dispatch.

Related lessons

• The COD confirmation SOP — confirming intent and phone before dispatch prevents most failed-delivery cases this protocol has to clean up.
• The returns and refunds SOP — the step-by-step refund and exchange flow this escalation hands off to when you decide to refund.
• Choose the right courier for an Egyptian online store — the patterns in your failure log tell you when a route needs a different carrier.

This Storix Academy lesson is published as "Shipping delay and failure handling". Every step below is written for merchants selling online in Egypt, so apply one change at a time and measure the result before moving on.