Structure the address, do not free-type it
Use separate fields for governorate, city or district, street, building, floor and apartment. Structured fields map cleanly to carrier systems and reduce misreads.
Use dropdowns for governorate and area so spelling never varies, and where the list is long, offer a search box instead of a long scroll. Leave free text only for what cannot be listed: street name, building details and the landmark.
Why Egyptian addresses are hard to deliver
Many streets are known by a common name that differs from the official one, new compounds and cities appear faster than maps update, and postal codes are rarely used in daily addressing. Couriers therefore rely on landmarks and phone calls, which is why a missing landmark or a wrong number costs so much.
Your job is to capture the information a driver would otherwise have to guess. Think of the form as a conversation with the courier that happens before the parcel leaves.
Write form labels that get good answers
Customers type what the form asks for. Clear labels with a short example produce much better data than a bare box marked “address”.
- Landmark: “for example, next to the pharmacy on the corner”.
- Building and floor: “building 12, floor 3, apartment 7”.
- Mobile number: “11 digits, starting with 01”.
- Delivery notes: “gate code, security desk, best time to call”.
The seven-point checklist
Before a waybill is created, confirm that each of these is present and plausible.
Treat the checklist as a gate, not a suggestion: an order missing a required point is held until it is fixed. It is far cheaper to ask the customer one question now than to chase a courier later.
- Governorate and area selected from a list
- Street and building number
- Floor and apartment
- A nearby landmark
- Receiver's full name
- A reachable mobile number
- An alternative contact when possible
Keep phone numbers clean
A wrong digit turns a good address into an unreachable customer. Standard Egyptian mobile numbers have eleven digits and start with 01, so validate the length and prefix at checkout and normalise the format before it goes to the courier.
Ask for a second contact where you can, such as a family member or a colleague, and make clear when the courier may call it. Many first-attempt failures are simply a phone on silent.
Catch problems after the order too
Flag orders with short or suspicious addresses for a quick confirmation call. A thirty-second call is cheaper than a returned parcel.
Build a quick review for orders that tend to fail: very short addresses, missing building numbers, addresses with only a district name, phone numbers of the wrong length, and the same address appearing under different names. A person scanning that list for a few minutes each morning catches most of them.
When an address is unclear, ask for a pin
For addresses that stay ambiguous after your checks, ask the customer to share their location on WhatsApp or a maps link. A pin does not replace the written address, because a courier still needs a landmark and a phone number, but it resolves arguments about which side of a long road a building is on.
Fix addresses at the source every month
Every failed delivery caused by an address is a lesson about your form. Collect them, find the patterns and change the checkout so the same mistake cannot happen again.
- Export last month's failed deliveries caused by address or contact problems.
- Group them by cause: missing landmark, wrong area, wrong number, unclear building.
- Change a form label, a required field or a validation rule for the top cause.
- Compare next month's failures to see whether the change worked.