You can sell into Saudi Arabia from a UAE Shopify store today, in riyals, without a Saudi entity, without a ZATCA e-invoicing stack and without SFDA registration, as long as the goods ship from the UAE and the customer is the importer of record. That's the honest answer to selling to Saudi Arabia from UAE Shopify setups. The moment you hold stock in Riyadh, clear shipments in your own name, or sell cosmetics, food or supplements at commercial volume, the picture changes and it changes fast. Most of the merchants who call us in January ran National Day offers in September, pushed harder after White Friday, saw Saudi become their second market by revenue, and only then discovered that the next step has a licence attached to it.
So here's where the lines actually sit.
What a UAE store can do in Saudi with no registration at all
Cross-border retail parcels from Dubai to Riyadh clear as personal imports in the customer's name. The buyer is the importer. Saudi customs assess 15% VAT at the border, plus duty where the GCC tariff applies, and the courier collects it or bills it back to you if you've bought a delivered-duty-paid service. Your Shopify order is a zero-rated export from the UAE. You issue a UAE tax invoice. ZATCA has no claim on you because you are not making a supply inside the Kingdom.
That model carries a brand further than people expect. SAR pricing, Arabic storefront, Tabby at checkout, three-day delivery, returns handled by paying for a reverse courier leg. We've seen UAE brands run a meaningful share of revenue through Saudi this way for a year or more before anything forces a change.
What it can't do: mada. Same-day Riyadh delivery. A local returns address that doesn't cost you AED 70 a parcel. And it can't touch regulated categories at any real scale.
ZATCA e-invoicing: who it binds, and what Shopify integration involves
ZATCA's e-invoicing rules apply to persons registered for VAT in Saudi Arabia. Non-resident sellers with no Saudi supply are outside it. Once you're registered, you're in: Phase 1 means every invoice is generated electronically in a structured format with a QR code, and Phase 2 means your billing system connects to ZATCA's Fatoora platform, stamps invoices cryptographically and submits them. B2C simplified invoices are reported within 24 hours. B2B standard invoices have to be cleared by ZATCA before you give them to the buyer.
Shopify does none of this natively, and no amount of theme work will make it. The order confirmation email is not a tax invoice. What a compliant setup looks like in practice:
- Shopify orders flow into an accounting system that holds a ZATCA-compliant e-invoicing module. Several Saudi and regional accounting platforms have this certified already, and so do the larger ERPs.
- A connector maps Shopify order lines, discounts, shipping and the 15% VAT split into the invoice schema. Discounts applied at order level rather than line level are where this usually breaks first.
- The cleared or stamped invoice gets pushed back to the customer, either by the accounting system or as a PDF attached to a Shopify notification.
- For B2B buyers you need their VAT number captured at checkout. On Plus that's a checkout UI extension; below Plus it's a cart attribute or a post-purchase form, which is uglier and leaks data.
Budget for the connector as a real build, not a plugin install. We quote this as custom app work because the mapping rules differ per accounting stack and the edge cases (partial refunds, exchanges, COD write-offs) all need handling.
What has to be on a Saudi VAT invoice
A simplified tax invoice for a consumer sale needs the seller's name and VAT registration number, the date and time of issue, a line-level description of what was sold, the amount excluding VAT, the VAT rate and amount, the total including VAT, and the QR code that encodes those fields. The invoice must be in Arabic. You can add English alongside it; you cannot replace Arabic with it. A standard invoice to a VAT-registered business adds the buyer's name, address and VAT number, plus a sequential number and UUID assigned by the system.
SFDA registration for cosmetics, food and supplements
This is the one that catches D2C brands out, because UAE market entry was comparatively easy and Saudi is not the same country twice.
SFDA governs food, supplements, cosmetics, medical devices and drugs. Products in those categories have to be notified or registered on SFDA systems before they're placed on the Saudi market, and the entity doing the notifying has to be a Saudi-licensed establishment. A foreign brand cannot register itself. You either incorporate, or you appoint an authorised representative or importer in the Kingdom who registers the products and takes on the regulatory responsibility that goes with them. Non-SFDA consumer goods still usually need a SABER conformity certificate through SASO before commercial shipments clear.
The practical consequence for cross-border: individual parcels of skincare or supplements posted to a consumer often pass as personal use, and brands take that as permission. Then volume rises, a consolidated shipment gets flagged, and the whole batch sits in a Riyadh warehouse while someone looks for a local representative. If skincare, perfume, food or supplements are your core catalogue, treat the Saudi representative as a prerequisite rather than a later optimisation, and plan on a lead time measured in months for the registrations.
Jewellery, apparel, home goods, accessories: far simpler. SABER where applicable, standard customs documentation, done.
SAR pricing in Shopify Markets, set up so it doesn't embarrass you
Create Saudi Arabia as its own market. Do not fold it into a "GCC" market with the UAE, because the two need different prices, different payment methods and eventually different tax behaviour. Then:
- Set SAR as the market currency with manual rounding rather than live conversion. AED 249 converting to SAR 254.37 looks like a machine priced it. SAR 255, or 249, looks like a brand did.
- Use price adjustments per market, or fixed SAR prices on the products where margin after freight and duty won't survive a flat uplift. Heavy items are the ones that need fixed pricing.
- Decide whether listed prices include the 15% import VAT. If the customer pays it to the courier on the doorstep after seeing a tax-inclusive-looking price, your support inbox will tell you about it.
- Run the Saudi market on an Arabic-first URL path. Arabic is the default reading language, the RTL layout has to be genuinely laid out rather than CSS-flipped, and product data needs translating properly, including size charts and care instructions.
- Check your admin before promising DDP at checkout. Shopify's managed duty collection isn't available to every merchant in the region, and if it isn't available to you the duty quote has to come from your carrier's API.
Checkout: mada, Tabby and Tamara
Saudi card behaviour is distinct. mada, the domestic debit network, carries a very large share of online payments, and a checkout without it reads as foreign. The catch: mada acquiring generally requires a Saudi entity and a Saudi bank account. Gateways serving the Kingdom will tell you the same thing. So if mada is the reason you're considering a Saudi presence, that's a legitimate reason, and it's often the first real trigger.
Tabby and Tamara both operate on either side of the border, and both matter: BNPL is close to a default expectation for anything above a couple of hundred riyals. Setup is per-country, per-entity. Your UAE Tabby account does not automatically serve Saudi orders at Saudi settlement terms, and Tamara in particular will route you through its Saudi onboarding. The clean configuration is to attach the Saudi BNPL providers to your Saudi market in Shopify so they surface only to SAR buyers, instead of showing a UAE-licensed instalment option to a shopper in Jeddah who then fails the eligibility check at the last step. That failure is expensive, because it happens after the customer has committed.
COD remains live in Saudi. Cross-border COD is possible, and it's also how you end up waiting three to four weeks for settlement in a currency you then have to repatriate, on orders with a refusal rate noticeably higher than prepaid. Price the COD fee into the product, cap it by order value, and watch the return-to-origin number weekly.
Shipping Dubai to Riyadh, with actual arithmetic
Two routes. Air express gets a parcel from Dubai to Riyadh in one to two working days. Road freight across the causeway and up through the Eastern Province takes three to five, costs a fraction per kilo, and makes sense once you're consolidating.
Run your own numbers, but model it like this. Take a SAR 400 order, 1.5 kg, and assume you've negotiated an express rate equivalent to SAR 60 for that weight band plus a SAR 15 handling and clearance fee. Import VAT at 15% is charged on goods plus freight plus duty: 15% of (400 + 60) is SAR 69 if no duty applies. Your landed cost to deliver that order is 60 + 15 + 69 = SAR 144 before product cost. On a SAR 400 order, that is 36% of revenue gone to logistics and tax. Add a 2% COD fee and a 12% return rate and the maths on cheap, light, low-AOV products stops working entirely.
The same order through consolidated road freight into a Riyadh 3PL might land at a quarter of the per-parcel freight. But the moment that stock sits in a Saudi warehouse, you are supplying goods from inside the Kingdom, and that is a VAT registration, which is a ZATCA obligation, which is the entity conversation. The logistics saving and the compliance cost arrive together.
Second Shopify store or Shopify Markets: the actual decision
Markets is the default and should stay the default longer than most founders want. One catalogue, one theme, one set of apps, one SEO footprint, SAR pricing and Arabic handled by configuration. A duplicate store doubles app billing, doubles theme maintenance, splits inventory across two systems that need syncing, and creates two sets of product pages competing for the same Arabic queries.
Stay on Shopify Markets when:
- Saudi is under roughly a fifth of orders and you're still learning what sells there
- Your catalogue is outside SFDA scope
- Cards and BNPL are converting acceptably without mada
- A three-to-five day delivery promise is competitive in your category
- Returns volume is low enough that paying reverse freight to Dubai is tolerable
Build the Saudi entity, local fulfilment and invoicing stack when:
- mada absence is visibly costing conversion, which you can test by comparing SAR checkout completion against your UAE baseline
- You need stock in-country for next-day Riyadh delivery
- You sell cosmetics, food or supplements and want shelf-legal commercial volume
- You're selling B2B or to government buyers, who will require a cleared standard tax invoice with their VAT number on it
- You want to list on Saudi marketplaces alongside D2C, which generally assumes local registration
Note that a second store and a Saudi entity are separate decisions. Plenty of brands register in Saudi, fulfil locally, invoice through ZATCA, and still serve both markets from one Shopify store with two markets configured. Expansion stores make sense when the Saudi catalogue diverges substantially, when you need a genuinely different merchandising and content operation, or when you're on Plus and the expansion store is already included. If you're weighing that, our notes on when Plus earns its licence fee apply to GCC merchants too: the threshold is usually checkout control and B2B, not traffic.
Questions from the first call
Do I need a Saudi entity to sell online there?
No, not to take orders and ship them from the UAE with the customer as importer of record. Yes, in practice, if you want mada, local stock, SFDA-registered products, or to be the importer yourself. The middle option is an authorised Saudi importer or distributor who holds the registrations and clears your goods while you stay a UAE company. It costs margin and gives up some control. For a brand testing Riyadh it's often the right trade.
How long does the entity route take?
Foreign investment licence, commercial registration, bank account, VAT registration, then ZATCA Phase 2 integration. Months, not weeks, and the ongoing obligations include GOSI, Saudization requirements and monthly or quarterly VAT filings. Get a fixed quote from a Saudi corporate services firm before you plan around a launch date.
Can I keep one price list across the GCC?
You can, and you'll lose money on one side of it. UAE VAT is 5%, Saudi import VAT is 15%, and freight differs. Price the markets separately.
What breaks most often on the first pass?
Arabic product data. Teams translate titles and descriptions, then forget variant names, filter labels, shipping policy, the returns page and the order status page. The customer hits one English screen in the middle of an Arabic journey and trust drops.
Where to start this week
Pull your last 90 days of Saudi orders. Split checkout completion by payment method, calculate landed cost per order using the arithmetic above against your real carrier rates, and list which SKUs fall under SFDA. That one spreadsheet tells you whether you're looking at a configuration change or a company registration. If you'd rather have a second pair of eyes on it, we do a free store audit and can walk through the Saudi setup specifically, or you can read how we work with brands already operating in the Kingdom on our Saudi Arabia page.