Why do Arabic dashboards come out broken?
You build a KPI dashboard in a global tool, switch the language to Arabic, and get a surprise: numbers jump to odd positions, headings overlap, and dates read backwards. The problem is not Arabic; it is that most of these tools were built English-first and had Arabic bolted on later.
Problem one: numbers inside Arabic text
When you write an Arabic sentence containing a Latin number, the browser decides display order with complex rules called BiDi. The common result: 1,250 renders reversed or jumps to the end of the sentence. The technical fix is simple and well known, yet most tools skip it: isolating the number so it does not mix with the surrounding text direction. We apply it to every number on our platform.
Problem two: charts do not flip
When switching to RTL, text flips but chart axes keep their English direction. You end up with a paradox: the table reads right to left while the chart beside it reads left to right. The right call is not flipping everything, but knowing what should flip: text and tables flip, while time sequence in charts stays as readers expect it.
Problem three: fonts
The default font in most BI tools does not support Arabic properly, so letters appear disconnected or inconsistently weighted. You need an Arabic typeface designed for screens with multiple weights, and you need to test it with your actual numbers rather than placeholder text, because problems surface when letters and digits sit together.
What to ask for so the dashboard comes out right
Ask for the dashboard to be built Arabic from the first line, not translated at the last step. Practically: test on your real data with your branch names and figures, open it on a phone before relying on it, and confirm dates use the calendar your team reads. The five dashboards in our demo are built on these rules and you can open them now and judge for yourself.
Frequently asked questions
Does this mean tools like Power BI are unfit for Arabic?
They are usable, but with extra effort and workarounds, and some details stay off. The decision depends on who sees the dashboard: an internal analysis team can cope, while a screen managers watch daily deserves a proper Arabic build.
We have a working English dashboard, do we rebuild from scratch?
Not necessarily. The common pattern is keeping English for the analysis team and building an Arabic version for the screens the wider team watches, since the two needs differ anyway.
Our numbers render reversed in reports, is that fixable?
Yes, and it is a display problem rather than a data problem. It is fixed by isolating numbers from the surrounding text direction, and the effect is immediate once applied.