Admin language in Shopify is a per-person setting, not a store setting. Your picker in Al Quoz can run the admin in Arabic, your packer can run it in Urdu, and your merchandiser can run it in English — same store, same orders, same minute. That has been true for a while for the languages Shopify shipped. What changed with the 2 October release is that Arabic and Urdu got proper treatment across admin, checkout and customer accounts, with the interface language following whatever the person's own device is set to unless they override it. For a Dubai or Riyadh operation with a mixed-nationality floor team, that is the single most useful thing Shopify has done for back-office work in the GCC in a while.
The storefront side of RTL has been written about to death. The operations side has not, and it is where the money leaks.
How to change the Shopify admin language to Arabic
Each staff member does it themselves. Click your avatar in the top right of the admin, go to manage account, and set the language there. It applies to that Shopify account, which means it follows the person into every store they have access to. Worth knowing if you use a freelance developer across five clients: flip their account to Arabic and all five admins change for them. Nobody else sees any difference.
You cannot set it centrally for your team. There is no store-level switch that forces the warehouse into Arabic. If you are onboarding six pickers, you are walking six people through the same four clicks, or you are setting the device language before you hand over the tablet and letting the admin pick it up automatically.
Device language versus store language: three settings that do different jobs
These get confused constantly, so, plainly:
- Device language decides what the staff member sees in admin and in POS. It is the default now — log in from a phone set to Arabic and admin comes up in Arabic.
- Account language overrides the device for admin. Set it once if your laptop is in English but you want to work in Arabic.
- Store languages (Settings → Languages, published per market) decide what the customer sees — storefront, checkout, order status, notification emails. Completely separate. Publishing Arabic on your UAE market does nothing for your warehouse team, and switching your own admin to Arabic does nothing for your customers.
POS is the one that catches people out. The POS app takes its language from the iPad or Android device it runs on, not from the staff PIN. So a shared till in a Riyadh store shows one language for everyone on shift. If you want the counter in Arabic and the stockroom tablet in Urdu, that is two devices, configured separately.
Urdu in the Shopify admin for warehouse teams
A large share of warehouse and last-mile staff in the UAE and Saudi are from Pakistan and India. Urdu in the admin is not a diversity gesture, it is a mis-pick reduction. Someone reading an order screen in their first language scans it faster and misreads quantity fields less often.
Two caveats before you roll it out. First, Urdu rendering depends on the fonts on the device. On some Android tablets you get a Naskh fallback rather than Nastaliq, which is legible but looks wrong to a native reader and can slow people down rather than speed them up. Test on the actual hardware on the floor, not on your MacBook. Second, translating the interface does nothing to your data. If your product titles are English, an Urdu admin is an Urdu frame around English content. The picker still reads "Oud Musk 50ml EDP" in Latin script. That is usually fine, but do not expect the language switch alone to fix a catalogue with ambiguous variant names.
What still breaks in an RTL admin
Shopify's own surfaces mirror cleanly. The things around them do not.
- Embedded third-party apps. Your Aramex integration, your WMS connector, your COD reconciliation app — most of these render in English and LTR inside an otherwise RTL page. You get an LTR island in the middle of the screen. Not broken, but it confuses people who have just been told the system is in Arabic.
- Bidirectional text. An AWB number, an SKU with hyphens, or a phone number sitting inside an Arabic sentence can render in an order your eye does not expect. Segments flip. Teach the team to copy and paste tracking numbers rather than retype them from the screen. We have seen a two-digit transposition on a waybill cost four days of "where is my parcel" tickets.
- Admin search and Arabic names. Searching a customer called أحمد will not reliably match a record saved as احمد. Alef forms, ta marbuta versus ha — the admin does not normalise them for you. The fix is procedural: in the GCC the phone number is the real primary key. Train support and the warehouse to search by mobile, always.
- Exports and reports. CSV headers stay English. Some report views stay LTR. Anything your finance team touches at VAT filing time is effectively English-only, which is usually what they want anyway.
- Code and theme editor. Always LTR. Obviously.
Bilingual packing slips and order notes
Here is the part people assume is automatic and is not. The packing slip is a Liquid template you own, sitting in your shipping settings. It does not follow the admin language of whoever hit print, and it does not follow the customer's language either unless you write that logic yourself.
What we build for UAE and Saudi stores: Arabic line, English line beneath it, for every label the packer needs — item name, quantity, delivery instruction. SKU, barcode and order number stay in Latin characters and Western numerals, no exceptions, because those are machine-read and because a barcode scanner does not care about your localisation strategy. If the customer-facing product title only exists in English, fall back to it rather than printing an empty Arabic line.
Carrier labels are a different animal. Aramex and most of the local same-day couriers generate the label from their own API payload. Arabic address lines can come back mangled if the integration is ASCII-bound. Keep a Latin transliteration of the address as the field you push to the carrier, and keep the Arabic version in a metafield or note for the driver's call-ahead.
On order notes: a customer typing اتصل قبل التوصيل in the checkout notes box is clear to your Riyadh support agent and meaningless to a dispatcher who reads neither. Do not try to translate free text. Put an English tag vocabulary on top of it — call-before, gate-code, after-iftar — applied by support, because tags are what drive your fulfilment automations and carrier routing. During Ramadan the after-iftar delivery window alone will save you a stack of failed COD attempts.
Shopify POS with an Arabic interface for GCC retail
Set the device to Arabic and the POS UI flips, including the RTL layout. That covers the staff side. The receipt is separate: it follows your store and market settings plus whatever you have put in the receipt template.
For a UAE counter, the default we build is a bilingual receipt carrying the TRN, the 5% VAT line shown separately, and the item lines in both scripts. Whether your licence and transaction type need Arabic on the tax invoice is a question for your accountant, not for us — but bilingual is the configuration that never needs revisiting, so we start there. The same template logic serves a Riyadh store with the Saudi VAT and ZATCA fields your local advisor specifies.
Setting up customer accounts in Arabic
Two paths, and the choice matters more than people expect.
Shopify's newer customer accounts are rendered by the platform. You get Arabic and RTL handed to you, including on the login and order history screens, and the language follows the buyer's market and browser. The trade-off is that you control very few of the strings and almost none of the layout. Classic accounts render from your theme templates, so you control everything and you own every RTL bug in them.
Either way, three things need doing: publish Arabic as a language on your UAE and Saudi markets in Shopify Markets, translate your theme strings and product content (Translate & Adapt handles the mechanics, a human handles the quality), and translate your notification templates. Order confirmations, shipping updates and the OTP email all pick their language from the order's locale, so an untranslated template means an Arabic-browsing customer gets an English email after an Arabic checkout. That is the sort of detail that quietly erodes trust with first-time buyers who were already nervous about paying anything other than cash.
Dubai and Riyadh are not one market
A blunt opinion from doing this repeatedly: in Dubai, English-first with Arabic available usually outperforms Arabic-first, because so much of the buying population works in English. In Riyadh, Arabic-first is not a preference, it is the baseline, and an English-default storefront reads as an import. Separate markets in Shopify, AED and SAR pricing, separate default language per market, and separate Tabby and Tamara configuration since the approval and limits differ by country.
The back office can be unified even when the storefront is not. One admin, one catalogue, staff reading it in whichever of three languages suits them. That is the actual advantage here.
The arithmetic, honestly
Take a warehouse running 300 orders a day through White Friday week with a 1.5% mis-pick rate. That is 4.5 wrong parcels a day. Suppose language and layout fixes take it to 1.0% — 3 parcels — so you avoid 1.5 incidents daily. Cost of an incident: return leg roughly AED 20, redelivery AED 20, fifteen minutes of warehouse and support time at around AED 20 an hour, call it AED 45 all in. So 1.5 × 45 = AED 67.50 a day, a bit over AED 2,000 across a month.
Two thousand dirhams. That does not fund a project. It funds an afternoon of configuration and a one-page SOP, which is exactly what this work costs. Nobody should sell you a localisation programme off the back of it. Set the device languages, rewrite the packing slip template, agree the tag vocabulary, train the team to search by phone number, and move on to something that actually moves revenue.
Quick answers
Can two staff accounts use different languages on the same store? Yes, and it is the normal setup. Language lives on the individual Shopify account. Nobody needs permission from the store owner.
Does changing my admin to Arabic change what customers see? No. Those are unrelated settings. Storefront language comes from your published market languages.
Will the admin always match my phone's language? It defaults to the device, and an explicit choice in your account settings overrides it. Useful if you work on an English laptop and an Arabic phone.
Do packing slips translate automatically? No. The template is yours to edit. Budget a couple of hours of developer time for a bilingual version with the fallbacks handled.
If you are standing up a GCC operation and want someone to look at the whole chain — market setup, RTL theme, packing slip templates, carrier payloads — our Dubai team and Saudi practice do this work weekly. A free audit will tell you which of the breakages above you already have, before peak season makes them expensive.