Most ERP vendors will tell you they support Arabic. Usually that means the interface has been translated. For a business operating in Saudi Arabia, that is the smallest part of the requirement.
Where Arabic support is actually tested
- Printed and PDF documents: invoices, delivery notes, purchase orders and statements that have to render right-to-left correctly, not just display Arabic characters.
- Mixed content: Latin product codes and figures inside Arabic sentences, which is where text direction most often breaks.
- Numerals, where a reporting pack has to pick a convention and hold it everywhere.
- Names and addresses that must survive being exported, re-imported, and sent to a government platform unchanged.
The compliance angle
ZATCA e-invoicing makes this concrete. Required fields must appear in Arabic on the document, and the document has to remain valid through generation, signing, archiving and retrieval. An interface translation does nothing for any of those stages.
If Arabic only exists on the screen and not on the document, the system is not Arabic-first.
A practical test before you buy
Ask for a real invoice, in Arabic, generated from the system you are being sold — with a Latin product code and a long customer name on it — and look at the PDF. Most of what matters shows up in that one document.
