Choosing a bilingual dealer management system for Arabic-speaking markets

Translation is not localisation

Plenty of systems ship an Arabic string file and call it Arabic support. The test is not whether labels are translated — it is whether the interface reverses correctly, whether numbers and dates read naturally, and whether a printed invoice looks like a document a customer would accept.

• Full right-to-left layout, including tables, forms, icons and navigation direction
• Language switching per user, not per installation
• Arabic on printed and PDF documents, not just on screen
• Search that works with Arabic text, including customer names

Currency handling in the Gulf

Currency is where regional systems quietly break. Kuwaiti dinar, Bahraini dinar and Omani rial use three decimal places, not two. Any system that stores money as a floating-point number with two decimals will produce rounding errors on every deal, and those errors accumulate on invoices and accounting exports.

Ask directly how money is stored. The correct answer is integer minor units with an explicit currency code on every amount — 1.250 KWD stored as 1250 fils, never as 1.25.

Multi-branch and permission structure

Dealer groups rarely run one lot. Inventory, users and reporting all need to be scoped by branch, with roles that let a branch manager see their own lot while a group owner sees everything. Check that permissions are enforced on the server, not merely hidden in the interface.

• Per-branch inventory and user assignment
• Roles stored and enforced server-side, not in the browser
• Group-level reporting that rolls up across branches
• An audit trail showing who changed what and when

Ask about leaving before you join

The most important question in any DMS evaluation is how you get your data out. If export is a paid service request or a support ticket, you are locked in and future pricing conversations will reflect that.

Insist on self-service export on every list — inventory, contacts, leads, deals, recon and reporting — in a plain format you can open anywhere.

A short evaluation checklist

• Switch the demo to Arabic and use it for ten minutes, including creating a vehicle and printing a document.
• Enter a three-decimal currency amount and check the invoice total to the fils.
• Create a second branch and confirm a branch user cannot see the other lot's inventory.
• Export every list to CSV yourself, without asking support.
• Change a price and confirm the audit trail records who did it.

How Starcar handles it

Starcar is bilingual English and Arabic throughout with full right-to-left layout, stores every amount in integer minor units with an explicit currency (including three-decimal currencies), scopes inventory and permissions per branch with server-enforced roles, keeps an immutable audit log, and offers one-click CSV export on every list surface. The free plan covers up to 10 vehicles, one branch and three users, so the checklist above can be run on real data.

Frequently asked questions

Does Arabic support require a separate installation?

It should not. Language belongs to the user, so a bilingual team can work side by side in the same workspace with each person in their preferred language.

Why do three-decimal currencies matter?

Kuwaiti dinar, Bahraini dinar and Omani rial are divided into 1,000 subunits. A system that assumes two decimals rounds every deal and produces invoice and accounting discrepancies.

Can Starcar be evaluated for free?

Yes. The Starter plan is free and covers up to 10 vehicles, one branch and three users, with full CSV export.