Which delivery details belong in your checkout?
Ask for the details your chosen fulfilment method needs, explain why they are requested, and make optional information visibly optional. A home delivery, parcel pickup and business receiving desk do not always need the same fields. This guide helps Saudi store owners map the route before building the form, without presenting a design checklist as legal advice or a universal mandatory-field list.
In this guide
Start with the route, then decide which fields to show
A checkout form should collect enough information to complete the delivery option the customer selected. Write the fulfilment path first: courier to a home, pickup at a supported location, or delivery to a staffed business address. Then ask the courier or fulfilment partner which address elements it actually needs for that path. A field that is useful for one route may be irrelevant for another.
For ordinary home delivery, a store may need the recipient’s name, a contact method the courier can use, city, district and a precise location or address reference. A National Address may provide structured details such as building number, street, secondary number, district, postal code and city. Do not assume every courier integration requires every element in every order; confirm the specific service and make the form fit it.
If the customer selects pickup, the chosen pickup location may replace several home-address fields. A business delivery may need a company or receiving-desk name and delivery-hour instructions. These are design examples, not a statement that Saudi law mandates one universal checkout form. Confirm requirements with the delivery provider and a qualified compliance adviser for your store.
References: Saudi Post | SPL: National Address · Saudi Post | SPL: Doorstep service
Use a field map for each fulfilment method
A short field map prevents the checkout from becoming a copy of an old paper form. Keep required, conditionally requested and optional data distinct. In the table, “consider” means validate it against your carrier and delivery workflow before adding it.
Scroll the table sideways to read every column.
| Order route | Potentially useful fields | Before you make a field required |
|---|---|---|
| Courier to a home | Recipient name; mobile contact; city and district; address or map pin; delivery note when needed | Confirm the carrier’s accepted address format and whether the note is genuinely needed |
| Pickup point | Recipient name; contact method; selected pickup location; collection note if supported | Check that the location selector is current and that the provider can identify the order |
| Business receiving desk | Recipient name; business or desk name; contact; delivery address; receiving hours where relevant | Ask whether the address or hours change the delivery attempt |
| Large or scheduled item | Address; access or appointment instruction only when the delivery service uses it | Confirm the actual booking or access process instead of collecting broad personal details |
References: Saudi Post | SPL: National Address · Saudi Post | SPL: Doorstep service
Explain why you collect data and keep it to the purpose
The Personal Data Protection Law says personal data should be limited to what is necessary for the purpose of collection. Translate that principle into a form review: for each personal field, write the delivery or order task it supports, who uses it, whether it is required for every route, and when it is no longer needed under the store’s approved retention approach.
Use short labels and helper text. If a second phone number is optional, say so and explain when it helps. Do not ask for an identity number, detailed household information, or unrelated preferences just in case they might be useful later. Do not ask customers to type payment-card details into a general address field; use the payment provider’s supported checkout flow and follow its integration guidance.
Provide a privacy notice at the appropriate point in the journey. It should match the real collection and handling practices and be reviewed by the responsible person. This article is a practical design checklist, not legal advice; the store remains responsible for assessing its obligations, vendors, purposes and retention.
References: Saudi Personal Data Protection Law, Article 11 · SDAIA: Minimum Personal Data Determination Guideline
Show the delivery arrangement before the customer commits
Address fields do not replace clear delivery information. Before the order is completed, show the available delivery method, charge, destination limits and expected timing using the store’s current, verified rules. The Ministry of Commerce customer guide discusses information customers should receive about the product price, delivery charges and delivery arrangements. Confirm the current requirements for your business rather than treating this field map as a compliance checklist.
A useful Saudi example is a store that ships from one fulfilment point to customers in Hofuf and Mubarraz within Al Ahsa, then also accepts orders for Dammam, Khobar, Riyadh and Jeddah. It can offer the same online service across those cities while delivery options, carrier coverage and timing vary by destination. Biaway works online; the example does not imply a physical office or a guaranteed route in any city.
Use a fictional acceptance check: select a home delivery address in Al Ahsa, then a pickup option if offered, then a business address in Riyadh. For each, verify the chosen method, required fields, price and timing are consistent with the live courier configuration. Repeat in Arabic and English, on mobile and desktop.
References: Ministry of Commerce: Customer Guide
Test error handling and agree who maintains the form
For a hypothetical small store, start with two delivery routes rather than adding every possible field. If the courier only needs city, district, a validated National Address and one contact number for the chosen service, test that exact flow. Add a gate code or second contact only if a documented operational need supports it. This keeps the checkout easier to understand and makes later changes reviewable.
- List each delivery method the store actually supports and the provider used for it.
- Ask the provider for its accepted address format and map each requirement to a checkout field.
- Mark a field required only when the selected route cannot be completed without it; show conditional fields only for the relevant option.
- Test valid, incomplete and unsupported addresses in both language directions. Check labels, keyboard focus, error messages, confirmation and the order details received by fulfilment staff.
- Record the form owner, courier integration owner, privacy-notice approver and process for changing a field when delivery operations change.
References: Saudi Post | SPL: National Address · Saudi Personal Data Protection Law, Article 11
Plan the same online flow for customers across Saudi Arabia
An online store can serve customers ordering from Hofuf and Mubarraz within Al Ahsa, as well as Dammam, Khobar, Riyadh and Jeddah across Saudi Arabia, while delivery options and timing still depend on the seller's carrier and fulfilment setup. Test each supported destination in the actual route configuration; Biaway operates online and does not claim a branch or a guaranteed delivery service in those cities.
How this guide was prepared
Prepared with AI assistance, with platform and accessibility claims checked against the primary sources below at publication. The planning frameworks are Biaway’s editorial recommendations. Examples labelled illustrative are not client stories or measured results. Platform features and requirements can change.
Your questions.
01Does every Saudi online store have to request the full National Address?
This guide does not establish a universal field requirement. National Address elements can help identify a destination, but check the selected courier service, your order workflow and current legal advice before making fields mandatory.
02Should a phone number be required for delivery?
A courier may need a contact method for a delivery attempt, but confirm the provider’s process and explain the purpose. Offer an alternative or mark a second number optional when the route allows it.
03Should checkout collect card numbers in an address form?
No. Address fields are for fulfilment. Use the payment provider’s supported payment flow and do not put card data into a general checkout note or address field.
04Can the same checkout serve customers in Al Ahsa, Dammam, Riyadh and Jeddah?
One store can offer online checkout to customers across Saudi Arabia, but service coverage, available delivery methods and timing depend on the store’s carrier and fulfilment arrangements.
05What should I ask a web designer to deliver?
Agree the supported delivery methods, field rules, Arabic and English labels, conditional behavior, error states, order notifications, privacy-notice placement, test cases and who can update the form when a carrier changes its requirements.