ERP selection in the UAE usually runs as a features comparison. A spreadsheet with vendors across the top and modules down the side, ticks in boxes, a weighted score, a decision. The problem is that every serious system does inventory, every serious system does purchasing, and the tick tells you a module exists rather than whether it fits how you work.
The projects that go badly rarely fail because a module was missing. They fail on data quality, on processes nobody wrote down, and on the belief that go-live is the end of the work.
Start with what you are actually buying
An ERP is a shared source of truth. Its value comes from everybody using the same records, which means its cost comes from everybody changing how they work. The software is the smaller half of that trade.
Before looking at vendors, write down the handful of questions the business cannot currently answer quickly. What did we actually make on that project. What is really in the warehouse. Which customers are past terms and by how much. How long does an order take from confirmation to delivery. Those questions are your requirements. A demonstration that does not answer them has not told you anything.
The UAE-specific requirements that are not optional
Some regional requirements are genuinely hard constraints, and a global product that handles them through a partner add-on is a different proposition from one that handles them natively.
VAT is the obvious one, and most systems handle standard cases. Fewer handle the awkward ones cleanly: reverse charge, designated zones, disbursements passed at cost, mixed supplies.
E-invoicing is the requirement that has just become urgent. The UAE mandate runs on the Peppol network with the PINT AE specification, structured XML and an Accredited Service Provider in the path. Businesses above AED 50 million in revenue appoint a provider by 30 October 2026 and go live on 1 January 2027, with everyone else following on 1 July 2027. If you are buying an ERP in 2026, ask specifically how it emits PINT AE compliant XML and which accredited providers it already connects to. An answer about being on the roadmap is a real answer, but plan around it.
Payroll and end of service are the third. WPS file generation, gratuity calculated to UAE labour law, leave accrual and air ticket entitlements are all things a system either does properly or turns into a spreadsheet somebody maintains beside the ERP.
Then multi-currency and multi-entity, which almost every Gulf group needs. Trading in AED, buying in USD, a free zone entity and a mainland entity, and consolidated reporting across both. This is where mid-market products often reveal their limits.
Arabic support is the last, and it is worth testing rather than accepting. There is a wide difference between a system with an Arabic interface and one that handles Arabic properly on printed and electronic documents, in customer names, and in right to left layouts that do not break.
Cloud, on-premise and what the licence actually costs
Most UAE businesses land on cloud, and for most it is correct. The reason is not cost, it is that somebody else runs the upgrade. On-premise still makes sense where connectivity is genuinely unreliable or where a specific contractual obligation requires it.
Whichever you choose, build the five year number rather than the licence number. Licences or subscription. Implementation, which frequently exceeds first year licence cost and sometimes exceeds it several times over. Data migration. Training, including the second round after the people you trained leave. Customisation, and then the cost of carrying that customisation through every future upgrade. Integration to the systems you are keeping. Support.
The customisation line is the one that quietly grows. Every modification you make is a modification you own forever, and heavily customised systems get stranded on old versions because upgrading means redoing the work.
Data is the project
Whatever the vendor says, migration is where the schedule goes. Your customer master has duplicates. Your item codes have three conventions from three eras. Your opening balances need someone with authority to decide what is real and what is a historical artefact nobody wants to write off.
None of that is the software's fault and none of it can be skipped, because an ERP loaded with bad data produces confident wrong answers, which is worse than the spreadsheets it replaced. Budget real time for it and put a named person from the business in charge, not the implementer.
How to run the selection
Give every vendor the same three scenarios from your own operation, including one awkward one, and ask them to demonstrate those rather than present a standard demo. Insist that the consultant who would actually run your implementation is in the room. Ask for a reference from a project that went badly as well as one that went well, and call both. Ask what happens if you stop after phase one.
If you are not yet sure an ERP is the right answer at your size, when ERP is worth it for a GCC business is the prior question, and custom against off the shelf covers the build alternative. The e-invoicing requirement above is set out in full in the UAE e-invoicing deadlines and penalties. For the payroll side specifically, see HR and payroll systems and WPS.
