Why Arabic-first ERP matters for UAE construction
Translation isn't localization. Here's what Arabic-first design actually changes for site teams, accounting, and consultants in the UAE.
If you've spent any time on a UAE construction site, you already know: the people doing the work β foremen, QA inspectors, storekeepers, and site engineers β communicate in Arabic. The systems we ask them to use don't.
That mismatch isn't cosmetic. It's the difference between a daily report that arrives on time with photos and an empty form that nobody filled in.
Translation is not localization
Most ERPs sold in the GCC are global products with an Arabic translation layer pasted on top. The English-first product was designed first; the Arabic strings were added later. You can spot it instantly:
- Truncated buttons. "Submit" in English fits in 80 pixels. "Ψ₯Ψ±Ψ³Ψ§Ω" needs the same space, but the button label flows out of its container.
- Reversed icon spacing. A back arrow that pointed left in English still points left in Arabic β pointing the user the wrong way.
- Mixed-direction PDFs. Headers in Arabic, line items pulled unchanged from the English template. Consultants reject these.
- Number formatting that doesn't match local convention. Western numerals are universal in UAE business β 1,500.00 β but the comma vs. decimal separator matters when you're filing FTA returns.
Localization means designing the layout, the typography, the iconography and the content flow with both directions in mind. From day one. Not later.
What changes when you start Arabic-first
When the foundation is bilingual, three things happen:
Site adoption goes up. Foremen who were avoiding the previous system because it felt foreign actually start using the field app. They submit daily reports because the prompts are in their language and the photos upload correctly.
Accounting accuracy goes up. Supplier invoices arrive in Arabic half the time. An OCR engine that was trained on English numerals and Latin labels misreads them. One trained for Arabic context gets the VAT line right.
Audit and compliance get faster. When the FTA asks for documentation, your records are already in the language they expect. Translating backwards under audit pressure is a genuinely terrible time.
Three places this shows up daily
1. The WhatsApp field bot
Site foremen don't open new mobile apps. They live in WhatsApp. If your field reporting tool isn't in WhatsApp β and isn't in Arabic β you don't get reports. You get sporadic, incomplete, half-hearted submissions that fail every analysis you try to run on them.
A field bot that prompts in Arabic, accepts photos, and writes back structured data into the project record gets used. Daily. By the people you actually need to use it.
2. WPS and end-of-service
The UAE Wage Protection System requires a specific SIF (Salary Information File) format that banks accept. The accounting team building that file needs employee names in both Arabic and English β Arabic for the WPS file, English for the bank statement. An ERP that stores both natively generates files that pass on the first try.
Same for end-of-service liability. The calculation is mandated by labor law; the labor law is in Arabic. A system that maps the law to the rules in plain Arabic, instead of a translated paraphrase, is the one whose output you can defend in a labor dispute.
3. Bilingual handover packs
When a project hands over, the consultant wants a PDF evidence pack β inspections, NCRs, signed approvals, as-builts. That pack needs to read correctly in both directions. Headers in Arabic, item references in English (because contracts are usually drafted in English), photos with captions in both. A handover pack that flips between languages without breaking layout is the difference between a one-shot signoff and three weeks of back-and-forth.
What we built
ORKSTRA is built Arabic-first. Every screen, every PDF, every email β both languages, both directions, from day one. Not a translation pass.
Pick any module β Tender Management, BOQ Importer, Quality Management, Workforce + Payroll β and toggle the locale switcher. The numbers stay Western. The fonts swap from Inter to Cairo. The icons mirror. The layouts flow in the right direction. The PDFs render correctly without manual fixes.
This is what we mean by "Arabic-first." Not "Arabic-also." Not "Arabic later." Arabic from the foundation up.
If you've struggled with a global ERP's Arabic mode, you already know why this matters. If you haven't, ask the people on your site who use it every day. They'll tell you.
β Built in Abu Dhabi π¦πͺ