How to handle failed deliveries, returns and exchanges for an online brand in Egypt

By the Ora Dash team · Last updated:

The short answer

A failed delivery is any courier attempt that does not end with the customer holding the parcel: no answer, a wrong address, a refusal or a postponement. To handle failed deliveries, returns and exchanges well, check every courier-reported exception with the customer directly, keep each parcel open until it is delivered or physically back in your warehouse, and run returns and exchanges as a fixed sequence with a recorded reason for every case.

What counts as a failed delivery, a return and an exchange?

The terms often get mixed up, and that causes confusion. Use these definitions with your team and your courier so everyone means the same thing.

  • Failed delivery attempt: the courier tried to deliver and did not succeed. Common causes are no answer, a wrong or incomplete address, or the customer not being available.
  • Refusal: the customer was reached but did not accept the parcel.
  • Postponement: the customer asked for delivery on a later date.
  • Return to origin (RTO): a parcel that was never delivered and travels back from the courier to the sender.
  • Customer return: an item that was delivered, then sent back by the customer.
  • Exchange: the customer sends an item back and receives a different item, size or colour in its place.
  • AWB or waybill: the shipping label and tracking number the courier issues for each parcel. It is the reference you use for every follow-up.

How do you check a courier-reported refusal or postponement?

A courier status is a report, not a confirmed fact. It records what happened at the door, and the customer may see it differently, for example a request for another time that was logged as a refusal. Checking with the customer before you accept the status saves orders that would otherwise turn into returns.

  • As soon as the courier reports a failed attempt, a refusal, a postponement or an address problem, message the customer on WhatsApp and ask whether it is correct.
  • If the customer confirms, record it and plan the next step: a new date, a corrected address, or a return.
  • If the customer's answer differs from the courier's report, have a person on your team step in before the order is treated as a return.
  • Log every contact on the order so anyone on the team can see what was said and when.

How do you track late, stuck and lost parcels with a courier?

Late parcels rarely get lost all at once. They slip through because nobody owns a single view of them. Keep one list for every parcel that needs attention, and review it on a fixed routine.

  • Put late, stuck and lost parcels in one list, including parcels created directly in the courier's own dashboard.
  • Group them by situation: the customer has not received it yet, it has not come back to you yet, or it is lost or damaged.
  • Note the reason for each one, such as never collected, no movement, past the promised date, or repeated attempts.
  • Flag every lost parcel that has no compensation claim yet, and track each claim until it is closed with the courier.
  • Use the waybill number in every message to the courier so each case is easy to find.

When is a parcel really closed?

Treat a parcel as open until one of two things happens: the customer has it, or your warehouse has scanned it back in. A courier status that says "returned" is not enough on its own, because the item is not in your hands yet. This single rule stops returns from disappearing between the courier and your stockroom.

What is a good returns process for an online store in Egypt?

Run every return through the same stages, in the same order. Each stage has one owner and one clear end.

  • Request: the customer asks to return an item, and you record the order, the item and the reason.
  • Courier pickup: you book the return pickup with your courier.
  • Received: your warehouse scans the parcel when it arrives.
  • Restock or damaged: a person on your team inspects each unit and decides whether it goes back to stock or is marked damaged. Keep this a human decision.
  • Refund: record the refund only after the item has been received and inspected, never before.

How should you handle exchanges?

Handle an exchange as two linked orders rather than editing the original one. The original order keeps its history, the new order carries the replacement item, and the link shows anyone on the team that the two belong together. Decide per case whether the new item goes out in the same visit as the pickup or only after the old item is back.

Why record a reason for every cancellation and return?

Reasons turn individual cases into patterns you can act on. A run of size-related returns points to the size guide. Repeated address problems point to the checkout form. Repeated refusals from one customer point to a review before you ship to them again. Make the reason a required step, and follow up with the customer when the reason is unclear.

How do you process returns in a Shopify store?

Shopify's admin lets you create a return on the order, mark items as returned, choose whether to restock them and record the refund. Shopify's own help center documents each of these steps. Process the return in Shopify after the item is received, so your stock and your order history match what is physically in the warehouse.

How Ora Dash handles failed deliveries, returns and exchanges

Ora Dash, the operations system for e-commerce brands in Egypt, builds this workflow in. When the courier reports a refusal or postponement, Ora Dash asks the customer on WhatsApp, and if the answers differ, a person on your team steps in before it becomes a return. Late, stuck and lost parcels sit in one list, including parcels created outside Ora Dash, and lost parcels with no compensation claim are flagged. A parcel leaves that list only when the customer has it or your warehouse has scanned it back. Returns are followed from request to courier pickup to receipt to refund, your team decides restock or damaged for each item, exchanges are handled as linked orders, every cancellation and return gets a reason, and returns are processed in Shopify. You can book a demo to see it on your own workflow.

Frequently asked questions

How can an online store in Egypt reduce failed deliveries?

Collect a complete, clear address at checkout, then check every failed attempt, refusal or postponement with the customer on WhatsApp as soon as the courier reports it, and agree a new date or a corrected address before the next attempt.

What does RTO (return to origin) mean?

RTO is a parcel that was never delivered and travels back from the courier to the sender. It is different from a customer return, which is an item that was delivered and then sent back.

When should I refund a returned order?

After the item has arrived in your warehouse and been inspected. Recording a refund before receipt opens the door to returns that never come back.

What should I do if the customer says they did not refuse the parcel?

Do not treat the order as a return. Have a person on your team follow up with the customer and the courier, log what happened on the order, and book a new delivery date if the customer still wants the order.

How do I follow up a lost parcel with the courier?

Add it to your list of late and lost parcels, open a compensation claim using the waybill number, and track the claim until it is closed. Flag any lost parcel without a claim so it is not forgotten.

Should an exchange be recorded as an edit to the original order?

It is clearer to record it as a new order linked to the original one, so each order keeps its own history and the team can see the two belong together.

Does Ora Dash process returns in Shopify?

Yes. Ora Dash processes full and partial returns in Shopify after the item is received. Exchanges are handled inside Ora Dash as linked orders.

One operations system runs everything after the order.

Book a demo