The problem with Saudi addresses on Shopify.
Saudi Arabia spent the last decade rebuilding how addresses work. Every building in the Kingdom now has a precise digital address — accurate to a single square metre — administered by the Saudi Post Logistics Hub (SPL). The visible part of that address, the part the customer would type, is the National Short Address: an 8-character code combining four letters and four digits, like RCTB4359 or JEDA1234. It's free to register, takes about three minutes, and now covers more than 7.6 million addresses across the country.
What changed everything for merchants is what happened on the courier side. Starting January 2026, the Transport General Authority requires major Saudi carriers — Aramex, SMSA, Zajil, Saudi Post, Mrsool — to have validated National Address information on every domestic shipment. Address text alone is no longer enough. The short address is part of the standard delivery process now.
This creates a practical wall for every Shopify merchant selling into Saudi Arabia. Shopify's standard checkout form has no field for the short address. It doesn't connect to SPL's validation database. So you're stuck. Either you collect address text the way Shopify hands it to you and hope your courier figures it out (they increasingly won't), or you bolt something extra onto the experience to capture and validate the short address. Neither is comfortable.
And there's a second wall behind the first one: most Saudi customers don't know their short address. They've registered it once on the SPL website, and from that point onward, they think of their address the way they always have — building number, street name, district, city. The 8-character code lives somewhere in an email or a memo on their phone. Asking the customer to find and type it at checkout is asking for friction the customer didn't sign up for.
What other solutions actually look like.
The address-app category on Shopify converged on a handful of patterns over the past two years. Each one solves a slice of the problem and leaves the rest. Here's the honest version of how each plays out in production.
1 / Ask the customer to type the short address.
The simplest pattern. A new field appears at checkout, labelled "National Short Address", and the customer fills it in. The trouble is that most customers don't have it memorized. They abandon, or they type something approximate and the validation rejects it, or they type random letters to push past the field and the courier deals with it later. Conversion takes a hit, support tickets go up, and the merchant ends up with a checkout that works against them.
2 / Post-checkout widgets on the Thank You page.
The dominant approach in the current address-app market. After the customer pays, a widget appears on the order confirmation page asking them to enter and verify their short address. This is appealing because it doesn't gate the conversion — the order is already captured. But it inherits a different problem: most customers won't do work after they've paid. The widget gets ignored, the email follow-up gets ignored, and the merchant ends up with an order that has no short address — the same place they started, except now they also have a delivery deadline ticking down.
3 / Email recovery for incomplete addresses.
Layered on top of the post-checkout widget. If the customer skips the widget, an automated email goes out with a link to a capture page. The email pattern is well-understood and works in some categories, but for fast-moving e-commerce orders the maths are unkind: response rates on transactional address-recovery emails sit in the low single digits, and by the time a reply does come back, your courier window is half-closed.
4 / Customer-account dashboards (Shopify Customer Accounts V2).
A dedicated page inside the customer's account where they manage their saved short addresses. Useful for repeat customers — second order onwards, the saved address is a one-tap select. But this only helps the small minority of orders that come from logged-in returning customers. First-time customers, the majority of orders for most growing brands, still hit the same wall.
5 / Native checkout extension on Shopify Plus.
The cleanest UX answer: a custom field embedded inside the actual checkout flow, validating the short address in real time before the order is placed. This is what every merchant wants — no post-checkout friction, no email loops, no abandon. The catch is that Shopify only allows this kind of checkout customization on Shopify Plus, which starts around $2,300 a month. For brands doing six or seven figures monthly, fine. For everyone else — most growing Saudi Shopify merchants — that's a price tag attached to a feature, not a business expense that pays for itself.
So the practical reality is: either you pay the Plus subscription for a feature, or you accept the post-checkout friction, or you live with broken deliveries. None of those is a good answer.
Enwany's approach.
Enwany is a different bet. The premise: the customer already typed their address. Building number, street, district, city — that's all there in the order Shopify just sent us. The short address is derivable from those fields, server-side, the moment the order lands. The customer never has to know what a short address is.
That's the entire pitch. No new field at checkout, no Thank You page widget, no email loop, no Shopify Plus subscription. The merchant installs Enwany, the merchant sells, and the resolved short address shows up on every Saudi order — automatically — written to a Shopify metafield, surfaced on the order detail view and the packing slip, ready for the courier label.
For the small number of addresses where the input is too sparse or ambiguous to resolve confidently, Enwany doesn't fall back to "ask the customer to fill out a form". It triggers an approved WhatsApp Business template directly to the customer's phone, in the language of their order, asking them to confirm one detail. The reply comes back, the address re-resolves, the short address writes to the order. The merchant's operations team is never paged.
How Enwany works.
1 / Order is placed.
The customer checks out normally on the merchant's Shopify store. Standard form, no SDK, no custom checkout extension required. Enwany picks up the order the moment it's placed.
2 / Smart processing — never blocks checkout.
Enwany resolves the address as the order comes in — fast enough that most orders ship out the door already tagged with a short address, same minute. Slower lookups continue working in the background so checkout is never delayed. This is the difference between an app that works at scale and one that breaks the moment things slow down.
3 / Multi-strategy resolution.
Enwany doesn't try a single lookup and hope for the best. Multiple resolution strategies run in priority order, and every result is validated against a 22-city Saudi alias map (Jeddah / Jiddah / جدة all collapse to one canonical city) plus a city-mismatch check that rejects results landing in the wrong region. The result: addresses get resolved correctly even when input is messy.
4 / WhatsApp recovery for the ones that fail.
This is the part nobody else does. When an address can't be resolved with sufficient confidence, Enwany doesn't fail silently and email the merchant. It triggers an approved Meta WhatsApp Business template — short_address_recovery — directly to the customer, in the language of their order, asking them to confirm or correct the address. The reply comes back through the WhatsApp Business API, the address is re-resolved against the cleaned input, and the short address is written to the order. No human in the merchant's operations team has to lift a finger.
"برنامج رائع وحلّ مشكلة كانت مأرقتني صراحة. هاد غير المتابعة والخدمة منهم."
— Shakhshirs · Shopify App Store review
5 / Written back to Shopify.
The resolved short address is written to the Shopify order as a metafield (order.metafields.enwany.short_address) and surfaced in the order detail view, the packing slip template, and the merchant's preferred fulfillment surface. Couriers integrating with Shopify pull the field on label generation. End-to-end, no manual data entry, no reconciliation work.