Skip to content
KKoderClub
GCC & Localisation
6 min read Sara Al Mansoori, Regional Delivery Director, GCC

Arabic RTL is an architecture decision, not a translation task

Adding Arabic to an enterprise platform touches layout, typography, data formatting, document generation and content operations. Treating it as a late-stage translation exercise reliably produces a second rebuild.

Published 2 June 2026 · Updated 15 July 2026

Arabic RTLLocalisationUAESaudi Arabia

Key takeaways

  • Mirror the layout with logical CSS properties from day one, not with RTL overrides later.
  • Bidirectional text in generated PDFs and invoices is the most common late failure.
  • Numerals, dates, currency and sorting are locale rules, not string replacements.
  • Content operations — who writes and approves Arabic — decides whether localisation survives.

Design in logical properties

Using inline-start and inline-end rather than left and right removes most mirroring work before it exists. Icons with direction — arrows, chevrons, progress indicators — need explicit flip rules; brand marks and media controls generally do not.

Documents are where localisation fails

Invoices, delivery notes and statements are generated server-side, often by a library with weaker bidirectional support than the browser. Test Arabic PDF output in week one of the project, with real customer names, mixed Latin part codes and VAT numbers.

Compliance is regional, not generic

UAE and Saudi VAT, ZATCA e-invoicing phases and Arabic-language document requirements are concrete deliverables with formats and deadlines. They belong in the backlog as engineering work, not in a compliance appendix.

  • Bilingual tax invoices with correct field ordering
  • ZATCA-compliant e-invoice generation and reporting
  • Data-residency options where the client's policy requires them

Content operations decide longevity

A platform that ships Arabic without a named owner for Arabic content degrades within two release cycles. Define who writes, who approves, and how untranslated strings behave in production before launch.

Apply this

Get this reviewed against your own systems

Send us the constraint you are working on. A senior practitioner responds with an approach note, phased plan and the metrics worth committing to.

Ask about this topic

Share your current systems and constraints. A senior consultant responds within one business day, under NDA.

NDA friendly. We never share your details.

FAQ

Questions readers ask about this topic

CallBook a consultation