Most bilingual business cards in the Gulf are not bilingual. They are English cards with Arabic on them, which is a different thing, and the difference is visible to every Arabic-reading person who receives one. Here is what actually goes wrong, in the order we see it.
None of this is exotic. All five are ordinary, all five are cheap to avoid, and all five are still on cards being handed out this week by organisations that would be embarrassed to know.
1. The name was transliterated, not written
The most common defect, and the one that causes the most quiet damage.
An Arabic name is not an English name converted by rule. It is the name, and the English version is the transliteration, usually chosen decades ago by whoever filled in a passport form. Running the process backwards, taking the English spelling on the HR system and converting it to Arabic characters, produces something that is recognisably not how the person writes their own name.
Sometimes it is merely slightly off. Sometimes it lands on a different name entirely, because several distinct Arabic names collapse into the same English spelling. Either way the recipient notices immediately, and what they conclude is not "the software made an error". It is that the organisation did not think it was worth asking.
The fix is procedural rather than technical: the Arabic field is a field, filled in by the person whose name it is. Not derived, not generated, not approved by a marketing team that cannot read it.
2. The layout was mirrored instead of laid out
Right-to-left is not left-to-right flipped. Flipping produces a card that is technically reversed and visibly wrong: logos land where nobody expects them, the eye enters the card at the wrong corner, and elements that should stay fixed regardless of language, a logo mark, a QR code, a photograph, get moved because the tooling moved everything.
A genuine RTL layout decides, per element, whether it belongs to the reading direction or to the page. Text and its alignment follow the language. A QR code does not. Neither does a logo, in most identity systems.
The tell is easy to spot once you know it: if the Arabic side looks like somebody held the English side up to a mirror, it was mirrored.
3. Numbers and punctuation went the wrong way
The subtle one, and the one that survives proofreading because the proofreader read the words and not the digits.
Arabic text runs right to left, but numbers inside it run left to right. Software that does not implement the bidirectional algorithm properly produces phone numbers with the country code stranded on the wrong end, extension digits transposed, and dates reversed. Brackets and slashes flip too: a perfectly correct string like +968 9889 9100 comes out with its parts in an order that will not dial.
The consequence is worse than cosmetic. A phone number that renders wrong on the card is a phone number that gets saved wrong, and nobody discovers it until a client cannot reach the person.
Check every card with a digit on it, in the language it will be read in, on a real phone rather than in a design tool.
4. The job title was translated instead of chosen
Job titles do not map cleanly between English and Arabic. Several English titles collapse onto one Arabic term, several Arabic terms have no single English equivalent, and the correct choice frequently depends on what your own organisation calls that role in its own Arabic correspondence.
Machine translation produces something grammatical and wrong. It will render a Business Development Manager into a phrase that is defensible in a dictionary and not what anyone in your company writes on a letter.
The organisation almost always already knows the right answer, because Arabic titles appear in employment contracts, on official letters, and in correspondence with ministries. That is the source, not a translation engine.
5. Only one language exists at the URL
The digital-era version of the problem. The printed card is beautifully bilingual, the QR code on the back opens a profile that is entirely in English.
This one is worth being blunt about because it undoes the effort spent on the other four. Increasingly the card is not the artefact, the profile is: it is what gets saved, what gets forwarded, and what the recipient actually reads. A bilingual card pointing at a monolingual page has bilingual packaging and monolingual contents.
What a card should carry is both languages under a single URL and a single QR code, opening in the language of the visitor's device with a one-tap switch, and writing both spellings into the saved contact so their phone finds the same person whether they search in Arabic or in English.
Why any of this matters commercially
It is tempting to file all of this under polish. It is not polish.
An English-only card handed to a procurement director at a ministry or a state-linked company quietly asks them to do the translation. That is a small signal, and business cards exist almost entirely to send small signals. In a market where a great deal of internal correspondence runs in Arabic, being the supplier whose card is correct in both languages is a cheap and durable advantage, and being the one whose card spells the recipient's colleague's name wrong is a cheap and durable disadvantage.
The costs here are asymmetric in your favour. Getting it right requires asking your own staff how they write their names, using the Arabic titles your own contracts already use, and testing the numbers on a phone. Getting it wrong is free, automatic, and visible to exactly the people you were trying to impress.
A checklist worth running before the next print order
- Every Arabic name was entered or confirmed by the person whose name it is
- The Arabic side was laid out, not mirrored: check the logo and QR positions specifically
- Every phone number was read on a real phone, in Arabic, and dials correctly
- Job titles match what your own Arabic correspondence uses
- The URL behind the QR opens in Arabic for an Arabic device, and the saved contact carries both spellings
Five checks. Most organisations fail at least two.
How bilingual digital cards are built, or upload your roster and see your own team's cards in both languages. Free for unlimited employees.