Arabic-First Loyalty: Designing for Gulf Customers

Most loyalty programmes in the Gulf are built in English and then translated. It shows. The card says the right words in the wrong order, the reward text reads like a manual, and the push notification arrives in a register no one actually speaks. Customers notice immediately, and a programme that feels foreign gets ignored no matter how good the offer is.

If the majority of your customers speak Arabic, Arabic is not a localisation task to complete after launch. It is the primary experience, and English is the alternate. That reordering changes a surprising number of design decisions.

Right-to-left is a layout problem, not a text problem

Switching a page to Arabic does not simply mirror the words. The entire reading order flips: the eye starts top-right, so your most important element — the reward balance, the stamp count, the call to action — belongs on the right, not the left. Progress fills right-to-left. Chevrons and arrows point the other way. A back arrow that still points left in Arabic reads as "forward" and quietly breaks navigation.

Numbers are the classic trap. Arabic text runs right-to-left but numerals inside it run left-to-right, so a phone number, a price or a stamp count placed carelessly renders in an order the customer has to mentally reassemble. Currency and date formats need the same care — "AED 45" and "٤٥ د.إ" are not interchangeable, and mixing conventions across a single card looks unfinished.

The card itself carries almost no words — make them count

A wallet pass gives you very little room: a business name, a programme name, a reward line, maybe a tier label. In English you can lean on brevity. Arabic words are often longer, so a label that fits comfortably in English wraps or truncates in Arabic, and a truncated reward line is worse than no reward line.

Three things worth checking on every card before you launch:

• Write the Arabic label first and let it set the space, rather than translating into a box that English defined. If it does not fit, shorten the Arabic — don't shrink the type.
• Decide whether your business name is transliterated or translated, then never vary it. A café called "Bloom" that appears as بلوم on the card, Bloom in the push notification and "مقهى الإزهار" on the poster reads as three different businesses.
• Test tier names out loud. Silver/Gold/Platinum translate literally but often land flat; the tiers that work in Arabic usually describe belonging rather than metal.

Push notifications are where machine translation gets caught

A wallet push is one short sentence on a lock screen, which is the least forgiving place for awkward phrasing. Formal Modern Standard Arabic is safe and universally understood, but it can read like an official announcement — fine for a bank, wrong for a coffee shop. Gulf customers are used to marketing that sits slightly warmer than MSA without drifting into a specific local dialect that excludes other nationalities.

Practical rules that hold up well:

• Keep one idea per notification. Arabic sentences carry more clauses comfortably in writing, but not on a lock screen.
• Put the offer before the reason. "قهوتك التالية علينا" lands; a sentence that explains the campaign first and reveals the reward at the end loses the reader.
• Avoid imperative stacking. Two commands in one Arabic sentence reads as pushy far faster than it does in English.
• Never machine-translate a pun. English loyalty copy leans on wordplay that has no Arabic equivalent, and the result is confusing rather than charming.

Names, numbers and the sign-up form

Registration is where Arabic-first thinking pays for itself. Ask for the fewest fields you can, because a form that feels like paperwork is abandoned in any language. Beyond that, a few realities specific to the region:

• Many customers will type their name in Arabic and their email in Latin script on the same form. Both must be accepted in the same field set without complaint.
• Names do not reliably split into first and last. A single full-name field avoids forcing a structure that does not fit.
• Phone numbers arrive in several shapes — with and without country code, with Arabic-Indic digits, with spaces. Normalise on your side rather than rejecting the customer's input.
• Never transliterate a customer's name automatically to make it fit your database. Storing someone's name incorrectly is a small insult that surfaces in every message you send them afterwards.

Bilingual by default, not bilingual as a setting

The strongest programmes do not ask the customer to choose a language. They detect it, follow it consistently across the card, the notifications and the registration page, and let the customer override it once if the guess was wrong. Language should never reset between the sign-up page and the reward message — a customer who registered in Arabic and then receives English pushes concludes the Arabic was a veneer.

The same applies to your staff-facing side. If the person at the counter reads Arabic more comfortably than English, the scanner they use all day should be in Arabic, or they will make mistakes that cost you customers.

How Sharaftona handles Arabic

Sharaftona is built bilingual rather than translated. The merchant dashboard, the staff scanner, the public registration page and the wallet card itself all run in native Arabic with full right-to-left layout, and a customer who signs up in Arabic keeps Arabic through every notification that follows.

Campaign copy can be written in both languages side by side, so the Arabic is authored rather than generated from the English. For merchants serving customers across the Gulf, that consistency is the difference between a loyalty card customers use and one they install once and forget.