Saudi Arabia is one of the fastest-growing eCommerce markets globally, and as of 1 January 2026, it has a new mandatory addressing requirement that every merchant shipping to the Kingdom must comply with. If your Magento store ships to Saudi Arabia and your checkout hasn't been updated, this guide walks you through what the change involves, what it requires technically, and how to get ahead of it cleanly.
What Is the Saudi Short Address Code?
The Short Address Code is an 8-character alphanumeric identifier structured as 4 letters followed by 4 digits (e.g., RAGI2929). It is issued by Saudi Post (SPL) as part of the country's National Address System and maps uniquely to a single building. Not a street. Not a postal zone. One building.
The system was built to solve a real operational problem: informal, unstructured address descriptions that made last-mile delivery in Saudi Arabia inconsistent, especially in newer residential developments where street-level data was incomplete or unreliable.
Why It's Now Mandatory
The Transport General Authority (TGA), Saudi Arabia's official regulator for transport and logistics, officially announced that from 1 January 2026, all parcel delivery companies are required to reject any shipment that does not carry a valid National Address. This applies to both domestic and cross-border shipments.
Saudi Post confirmed this on its National Address page, and major carriers have followed, advising shippers to begin collecting the Short Address Code immediately.
The bottom line is simple: no valid Short Address, no delivery.
What This Means for Your Magento Checkout
A standard Magento address form collects street name, building number, city, and postal code. That is no longer sufficient for Saudi orders. The Short Address Code needs to be treated as a first-class address field, not an optional note or a free-text afterthought. Concretely, it must be:
- Captured in a dedicated, clearly labeled input field at checkout, separate from existing address lines
- Validated client-side against the pattern ^[A-Za-z]{4}[0-9]{4}$ before the order is submitted
- Stored against the order and passed through correctly in the payload sent to your shipping carrier and customs documentation
If any of those three fail, you are either collecting bad data silently or creating a downstream problem at the carrier or customs level.
How Customers Find Their Short Address Code
Saudi residents can look up their Short Address through several official channels:
- SPL Online (Saudi Post's official portal)
- Government apps: Absher, Tawakkalna, Sehhaty, and Maha
- Google Maps (right-clicking on any residential building inside Saudi Arabia surfaces the Short Address Code)
For merchants handling high order volumes, SPL provides a public validation API that lets you programmatically verify Short Address Codes before a shipment is created, which is worth integrating if you're processing hundreds of Saudi orders per day.
How MageDelight's Google Map Checkout Extension Fits Here
Implementing a validated Short Address field in Magento 2 is straightforward at face value, but there are real edge cases that make it harder in practice. You need country-conditional field rendering (the field should only appear for SA orders), frontend validation with clear inline error messaging, and you need the value to flow correctly through to your shipping module and carrier API calls. Getting all of that right without breaking the existing one-page checkout takes careful implementation.
The Locate Me at Checkout Using Google Map extension by MageDelight takes a different approach to this problem and, for Saudi orders specifically, it changes the reliability profile of your address data significantly.
How It Directly Addresses the TGA Requirement
The core failure mode with Short Address capture is behavioral, not structural. Customers mistype the code, paste an old one, or use a code from a previous address. The code passes format validation (^[A-Za-z]{4}[0-9]{4}$) but refers to the wrong building. The shipment gets created, dispatched, and delivered to the wrong location or returned.
The MageDelight extension approaches this by embedding an interactive Google Map into the Magento 2 checkout. Instead of entering address data manually, customers drop a pin on their exact building. The extension then auto-populates the standard address fields from the resolved coordinates. The Short Address Code is entered against a geographically confirmed location, which means a mismatch between the code and the pin becomes visible before the order is submitted, rather than after the shipment fails.
This creates what is effectively a two-signal address confirmation: the customer's pinned location and their declared Short Address Code. For merchants shipping to Saudi Arabia at any meaningful volume, that cross-validation is operationally significant.
Business Benefits Beyond Just Being Compliant
Treating the TGA mandate as a floor rather than a ceiling is worth thinking about. Here is what accurate address data at checkout actually does to your Saudi operations:
First-attempt delivery rate goes up. Carrier data consistently shows that address quality is the primary driver of failed first attempts. In cross-border e-commerce, the global benchmark for address-related failures sits at 5 to 8 percent. Accurate Short Address data at the source directly compresses that number.
Support volume drops. Failed deliveries generate "where is my order" tickets, chargeback disputes, and re-shipping costs. Each one has a real cost attached. Fixing the address input upstream eliminates the class of support cases that stem from bad delivery data rather than carrier or warehouse errors.
Checkout conversion is protected. A mandatory field with no guidance, no inline validation, and no visual confirmation is a friction point. The map interface provides spatial feedback that a text input cannot, and customers who can visually confirm their location on a map before submitting are less likely to abandon.
Carrier handoffs get cleaner. Address data passed to Aramex, DHL, FedEx, or SPL that has been spatially validated at source requires fewer manual corrections during processing. Carriers sometimes levy surcharges for address correction at the point of dispatch; spatially validated data reduces that exposure.
It scales. For stores processing significant Saudi order volumes, the compound effect of even marginal improvements in address accuracy translates directly to fewer operational exceptions per week. A systematic fix at checkout scales with your order volume; a case-by-case fix at the fulfilment level does not.
Recommended Action Checklist for Magento Merchants
1. Add a country-conditional Short Address Code field.
The field should render only when the shipping country is set to SA. Label it clearly as "Short Address Code" and include placeholder text like e.g., RAGI2929 to guide customers. Implement this at the layout XML level using Magento_Checkout module customizations so it fits cleanly into the existing address form.
2. Validate format client-side before submission.
Use the regex pattern ^[A-Za-z]{4}[0-9]{4}$ in your checkout validation. Display an inline error message if the format does not match rather than letting the form submit and failing silently downstream.
3. Ensure the field passes correctly through to carriers.
Check how your shipping module maps custom address fields to carrier API payloads. Some carriers accept a dedicated field for the national address code; others expect it concatenated into an address line. Verify this with Aramex, DHL, FedEx, and SPL individually.
4. Communicate the requirement to your Saudi customers.
Update your FAQ, order confirmation emails, and checkout help text. Most Saudi users are familiar with their Short Address Code already; they just need to be prompted for it at the right moment.
5. Use map-based checkout for higher address confidence.
The MageDelight Google Map Checkout extension handles the map integration, coordinate-to-address resolution, and the geo-confirmation layer described above. For stores with meaningful Saudi traffic, it is a more robust solution than a standalone text field, and it gets you to compliant address capture faster.
Bottom Line
The TGA mandate is official and enforceable from 1 January 2026. Saudi Post has the infrastructure in place. Carriers are already communicating enforcement timelines. The only open variable is whether your Magento checkout captures and transmits the Short Address Code correctly before that date.
The implementation is achievable, but it requires more than dropping a new text field into your address form. Format validation, conditional rendering, carrier payload mapping, and customer communication all need to be accounted for. Stores that treat this as a proper integration task rather than a quick config change will have fewer operational problems when enforcement begins.
