The error pattern
The most consistent error in Gulf ERP selection is not choosing the wrong product. It is choosing the right product for the wrong version of the business.
Organisations that make ERP selection decisions based on their current operating model — their current entity structure, their current process design, their current regulatory position — and then spend two years implementing the selected system, arrive at go-live with a system configured for a business that no longer exists. Vision 2030 participation, regulatory change, organisational restructuring, and expansion into new markets have all shifted the business during the implementation period. The ERP they selected is a good fit for where they were, not for where they are.
This is not primarily a technology problem. It is a requirements definition problem. The requirements used to select the system described the current state. They did not describe where the business would be when the system went live.
What a robust ERP selection process looks like in the Gulf context
Start with a three-year business model projection, not a current-state requirements document. The right question is not “what does our business need from an ERP today?” It is “what will our business need from an ERP when this implementation goes live, and for the five years after that?” For a Saudi enterprise participating in a Vision 2030 programme, that means accounting for the regulatory reporting requirements that will apply as the programme matures, the organisational scale the business is targeting, and the integration requirements that new business lines or subsidiaries will introduce.
Separate must-have from wish-list with genuine discipline. ERP selections in the Gulf consistently produce requirements documents where 80% of the requirements are weighted as high priority. When everything is high priority, nothing is — and the selection evaluation cannot differentiate between products on the basis of what genuinely matters. A proper requirements definition exercise forces the business to distinguish between requirements that are genuinely critical, requirements that are important but adaptable, and requirements that represent preferences rather than functional necessity.
Assess total cost of ownership including integration, customisation, and local compliance. Gulf ERP selections frequently produce commercial comparisons that undercount the total cost of ownership by excluding three specific cost categories: the integration cost of connecting the ERP to existing and planned ancillary systems; the customisation cost of adapting the system to local regulatory requirements that standard configurations do not cover; and the ongoing cost of maintaining compliance as regulatory requirements — ZATCA, PDPL, IFRS 18, sector-specific regulations — continue to evolve. A commercial comparison that excludes these costs consistently underestimates the true cost of implementation by 30 to 50 percent.
The specific Gulf considerations that change the equation
ZATCA Phase 2 integration is now a baseline ERP requirement for Saudi Arabia operations. Any ERP under evaluation for a Saudi enterprise should be assessed against its current, certified ZATCA integration capability — not its roadmap capability.
Arabic-language operation is not the same as Arabic-language support. Most enterprise ERP systems support Arabic character rendering. Very few are designed for an organisation where the primary working language for financial operations is Arabic. The difference between the two matters for user adoption and for the quality of data entry — which is the foundation on which every other ERP and EPM output depends.
Multi-jurisdiction operation is common in the Gulf in a way that is not common in Western markets. An enterprise with operations in Saudi Arabia, the UAE, and Egypt is managing three different tax frameworks, two or three different GAAP requirements, and potentially multiple currency regimes. The ERP must handle this natively, not through workarounds.
Loop Wise Solutions provides independent ERP and enterprise technology selection advisory for organisations across Egypt and the GCC — covering requirements definition, vendor evaluation, and implementation readiness.
Contact: Contact@loop-wise.com | www.loop-wise.com
