What Arabic support really means in business software

Every vendor in this region says they support Arabic. Almost all of them mean the menus are translated. That is the smallest part of the job, and the part a buyer can see in a demo - which is exactly why it is the part that gets done.

Here is what to check instead.

The documents your customer actually receives

An invoice, a delivery note, a statement, a payslip. These are the places Arabic matters most, because they leave your building. They are also the hardest to get right, because generating a PDF is not the same as rendering a web page: Arabic script joins, letters change shape by position, and a font that lacks the right forms produces text that is technically correct and visually broken.

Ask to see a printed invoice with an Arabic customer name, an Arabic item description and a long Arabic address, as a PDF, not on screen. If the letters are disconnected or reversed, you have found the limit.

Error messages and validation

When a user does something the system refuses, the refusal must be in their language. A system that explains itself in Arabic until something goes wrong, then switches to English for the one message that matters, has translated the comfortable part.

This is not cosmetic. The person reading that message has to decide what to do next, and a message they cannot read becomes a phone call to whoever speaks English, which is how a two-second correction becomes a twenty-minute interruption.

Sorting, searching and the two forms of a number

Arabic text does not sort the same way as Latin text, and a list sorted by raw byte order will look random to a reader. Search has to cope with the same word written with or without diacritics, and with the alef written three ways.

Numbers deserve their own paragraph. Arabic-Indic digits and Western digits both appear in real documents, sometimes in the same one. A system should display consistently and accept both on input, because a user typing an invoice number will type it the way their keyboard produces it.

Direction is a layout problem, not a text problem

Right-to-left is not a translation setting. The whole page mirrors: the table columns, the navigation, the icons that imply direction, the position of a total at the end of a row. A layout that was built left-to-right and flipped late shows up as numbers in the wrong column and headings over the wrong data.

The giveaway is a report. Reports have the densest layouts and the least attention, so if the tables mirror correctly there, the rest usually follows.

What good looks like

A system where both languages are first class has a few visible properties: every user-facing field exists in both; a document prints correctly in either; switching language changes direction and formatting, not just words; and nobody has to keep a second copy of a report in English because the Arabic one does not print.

Mobile apps are worth a separate check. They are usually built later and translated last, and an app your sales team uses in the street is not the place to discover that the item names are in English.