Most failed Saudi deliveries are decided at checkout, long before a courier leaves the depot. If your checkout collects an address as free-text directions, never asks for the National Address Short Address in a validated field, and never passes structured data and coordinates to the carrier, every order depends on the customer answering an unknown number on delivery day. The fix is simple: capture the Short Address at checkout, validate it while the customer can still fix it, and hand the carrier coordinates and clean structured fields — not directions.
What your shipping policy should promise is covered in our Arabic Saudi shipping-policy page guide. The other checkout leak — payment failure — is covered in our mada decline troubleshooting guide.
The short answer: capture the Short Address at checkout, validate it, and pass coordinates — not directions — to the carrier
Ask for the 8-character Short Address as its own field whenever the destination is Saudi Arabia. Check its format instantly, verify it against official records where your platform allows, and store it on the order. Pass the resolved address and, where accepted, coordinates in the booking payload, print the same data on the label, and audit non-delivery reports monthly.
Why deliveries really fail: the free-text address your checkout asked for
A free-text box invites data a courier cannot route: a district name, a landmark, "behind the mosque, white gate". A neighbour can follow that; a sorting hub and a driver on a planned route cannot. The parcel reaches the right city, then stalls — manual sorting, a route built on guesswork, and the phone call every Saudi merchant knows, asking for a WhatsApp location pin. If the customer is busy, the attempt fails and a cash-on-delivery order dies in transit.
The failure was created at the checkout, when the store asked the wrong question. No courier contract repairs data never collected.
The National Address in one page: six layers, one 8-character Short Address
The National Address, managed by Saudi Post (SPL), is the Kingdom's standardised building address. As SPL describes it, a full address is built from a building number, street name, district, city, 5-digit postal code and secondary (additional) number, plus a unit number where needed. SPL's FAQ sets out registration through SPL Online and the SPL app; addresses can also be viewed through Absher and Tawakkalna.
The Short Address compresses that record into 8 characters: four letters, then four numbers — region, branch, division and a unique code, then the building number. It is short enough to type on a phone, structured enough to validate, and resolvable back to the full address.
Checkout field design: ask for the short code without killing conversion
Place the field in the delivery-address step, only when the destination is Saudi Arabia, labelled in Arabic and English with its format as placeholder guidance. Keep it to one field — never six boxes for the full record.
City and district work better as selectable lists than free text, because a typed district arrives in countless spellings. A mobile number remains essential — verified data reduces driver calls, it does not abolish them. Keep a delivery-notes box for gate or floor details, never as the address itself.
Help the customer who does not know their code (lookup routes inside the checkout)
Many customers have a National Address and cannot recall the code at purchase. Do not make them leave checkout to hunt for it. Put a helper line under the field, in both languages, naming SPL's routes: the code appears with their registered address in SPL Online and the SPL app, and can also be viewed through Absher and Tawakkalna. One line, where hesitation happens, turns abandonment into a short lookup.
For the customer who still cannot produce one, let them complete with structured fields and a mobile number, flag the order unverified, and capture the code before dispatch. An order repaired before booking beats a customer lost at the field.
Validation strictness: block, warn or repair later? Deciding per platform
Validation has three honest levels. Format validation is the floor: four letters and four digits before the order confirms, catching typos instantly. Lookup validation is stronger: the code is checked against official records and resolved to its full address, as the Shopify apps below do at checkout — use it where your platform supports it without delay.
Hard blocking suits high-value or remote shipping, but costs genuine customers who cannot retrieve a code under time pressure. The practical default is warn-and-capture: validate format strictly, verify where possible, allow completion with a warning, and repair before booking. Write the rule down so everyone applies it consistently.
Setup by platform: Salla, Zid, Shopify, WooCommerce and custom stores
On Salla and Zid, enable the National Address options your plan exposes, make district selection structured, and confirm the code is stored on the order where fulfilment can read it — per the platforms' own documentation, since plan features change. Wider requirements are in our web development in Saudi Arabia guide.
On Shopify, Onwan's listing describes verifying Short Addresses at checkout against official records, with capture also by email, SMS, WhatsApp and accounts, reminders for unverified orders, and Arabic and English with RTL support. Enwany's listing instead generates Short Addresses after the order into metafields, notes and labels, with WhatsApp recovery on failure. Prefer capture at checkout — a repaired address is good, a correct one is better. On WooCommerce and custom stores the same pattern applies via a plugin or integration; a custom build can hold field, validation and payload mapping natively, as in our custom web application development work across Saudi Arabia.
The handoff that matters: structured address and lat/long in the carrier payload and on the label
Capture is half the job; the other half is what leaves your system. When you book with SMSA, Aramex, SPL or another carrier, the payload should carry the Short Address, the resolved structured fields and, where accepted, latitude and longitude, so the driver's app receives a location rather than a paragraph. Confirm which fields each carrier consumes; coordinates in an unread field change nothing.
Check the label as printed, not as designed. Arabic names must survive your printer exactly as stored: test with real Arabic addresses on your actual printer, because garbled characters on the one document the driver holds undo every validation step. Print the Short Address prominently — the field a human can read aloud at the door.
Audit your failures: reading the NDR report by reason code, monthly
Your carrier's non-delivery report (NDR) is the scoreboard. Monthly, group failed attempts by reason code, in the carrier's own categories, and track the address-caused share per carrier and city. If it is not falling after the new field goes live, the problem is downstream — validation, payload or label.
The same discipline guides our Dubai e-commerce build work for stores shipping into the Kingdom.
The COD connection: why address latency cancels cash orders
Cash-on-delivery orders live on timing and trust. A prepaid customer whose parcel is delayed is annoyed; a COD customer whose parcel arrives days late, after missed calls and a rescheduled attempt, can simply refuse it — and your store pays for both journeys and the locked stock. Every day spent re-attempting cools intent. Compare refusal rates on first-attempt versus re-attempted deliveries in your own NDR data; the mechanism needs no one's benchmark.
Common mistakes: a short-code field nobody validates, and three more
The first mistake is adding the field and validating nothing, so the field becomes decoration. The second is demanding the code with no helper guidance, then blaming customers for abandoning it. The third is capturing the code and never passing it on — stored on the order, absent from payload and label. The fourth is skipping the audit.
FAQ
What is the Short Address and what does it contain?
The Short Address is the compact form of a Saudi National Address: 8 characters, four letters followed by four numbers. As SPL describes the full address, it stands for a record built from a building number, street name, district, city, postal code and secondary number; in the short form, the letters carry the region, branch, division and a unique code, and the numbers are the building number.
What do I do when a customer does not know their Short Address?
Help them inside the checkout. Put a helper line under the field naming the lookup routes SPL provides: their registered address and code appear in SPL Online and the SPL app, and a registered address can also be viewed through Absher and Tawakkalna. If they still cannot find it, let them order with structured fields and a mobile number, flag the order unverified, and capture the code before dispatch.
Should I block checkout when the Short Address will not validate?
For most stores, no. Validate the format strictly, verify against official records where your platform allows, but let a genuine customer complete with a warning and repair the address before booking. Reserve hard blocking for high-value or remote deliveries where a failed attempt costs more than a lost order.
Which address data must reach the carrier?
The Short Address, the resolved structured address fields, and — where the carrier's booking accepts them — the latitude and longitude of the resolved address, sent in the booking payload rather than only printed on the label. The label itself must print the same data cleanly, with Arabic names uncorrupted and the Short Address prominent.
How do I audit failed deliveries properly?
Monthly, from your carrier's non-delivery report. Group failed attempts by the carrier's own reason codes, track the share caused by address problems per carrier and per city, and compare refusal rates between first-attempt and re-attempted deliveries. If the address share is not falling after your setup changes, look downstream: validation, payload or label.
Get your checkout and delivery data set up properly (CTA)
If your NDR report still reads like a list of preventable phone calls, the fix is a checkout and handoff built as one system. Our e-commerce web development service sets this up on Salla, Zid, Shopify, WooCommerce and custom stores. Send a month of reports and we will show you, in an itemised proposal within 24 business hours, where your data breaks.
