A Saudi company should choose an ERP by starting with its own processes, not with vendor demos. Document how the business actually runs, define prioritized requirements, and run a fit-gap analysis to see how well each candidate platform covers them. Then confirm local compliance, including ZATCA e-invoicing, VAT, Arabic documents and local support, and compare the total cost of ownership over several years rather than the license price alone.
Most selection problems come from skipping one of those steps. This guide sets out a practical, vendor-neutral process for executives and IT heads at mid-to-large Saudi companies in manufacturing, oil and gas, logistics and retail.
Start with the process, not the demo
The most common way to choose an ERP is also the least reliable: watch three polished demos and pick the one that looked best. Demos rarely reveal how the system handles your approval chains, your costing method, your project billing or your warehouse layout.
Begin instead with a clear picture of how work flows through your company today:
- Order to cash: quotation, sales order, delivery, invoicing, collection.
- Procure to pay: requisition, purchase order, receiving, supplier invoice, payment.
- Plan to produce: demand planning, bills of materials, work orders, quality checks.
- Record to report: general ledger, cost centers, consolidation, statutory and management reporting.
- Hire to retire: if HR and payroll are in scope.
For each process, capture who does what, which systems and spreadsheets are involved, and where delays, rework or manual reconciliation happen. This is also the moment to ask whether the process itself should change. An ERP project is one of the few times a company has the budget and attention to redesign how it works. Automating a broken process simply makes it fail faster.
This groundwork gives you something every vendor must respond to on your terms.
Define requirements that matter
Once processes are mapped, turn them into requirements. Avoid the trap of long, generic feature lists copied from templates. A list of four hundred items where everything is marked “essential” gives vendors nothing to differentiate on and gives you nothing to decide with.
Use MoSCoW prioritization
Sort each requirement into one of four groups:
| Priority | Meaning | Example |
|---|---|---|
| Must have | The business cannot operate or comply without it | ZATCA-compliant e-invoicing; multi-warehouse inventory |
| Should have | Important, but a workaround exists for a period | Mobile approvals for purchase orders |
| Could have | Useful if it comes at little extra cost or effort | Built-in customer portal |
| Won’t have (this phase) | Deliberately deferred | Advanced demand forecasting |
Write requirements as scenarios
“The system must support multi-currency” is too vague. “A buyer raises a purchase order in euros to a German supplier, goods are received in Dammam, and the supplier invoice is booked with the exchange rate on the invoice date” is testable. Scenario-based requirements make fit-gap analysis and scripted demos far more meaningful.
Separate standard fit from differentiators
Most of your processes, such as accounts payable or fixed assets, are similar to those of other companies and should run on standard ERP functionality. A few processes, perhaps your engineering-to-order workflow or your fleet scheduling, may be genuinely distinctive. Identify those early, because they drive most customization cost and most of the difference between platforms.
Saudi-specific requirements
Several requirements are specific to operating in the Kingdom. Treat them as must-haves and verify them in detail, not by a yes on a questionnaire.
ZATCA e-invoicing readiness
The Zakat, Tax and Customs Authority (ZATCA) e-invoicing program has two phases. Phase 1 covers generating and storing electronic invoices in the required format. Phase 2 adds integration with ZATCA’s platform so that invoices are cleared or reported electronically, with requirements covering invoice structure, cryptographic stamps, QR codes and technical integration. Companies are brought into Phase 2 in waves.
When evaluating an ERP, ask each vendor to show:
- How standard tax invoices and simplified tax invoices are produced, including credit and debit notes.
- How the system connects to ZATCA for clearance or reporting, whether natively, through a certified add-on or through middleware.
- How failed submissions, retries and audit trails are handled.
- Who maintains the integration when ZATCA updates its specifications.
VAT handling
Confirm that the system supports your VAT scenarios cleanly: standard-rated, zero-rated and exempt supplies, reverse charge on imported services, VAT on advances, and the return figures your finance team needs. Ask how VAT rate changes are applied to open documents.
Arabic, bilingual documents and right-to-left interfaces
Many Saudi companies need invoices, delivery notes and statements in Arabic or in bilingual Arabic and English layouts. Check whether the user interface supports right-to-left display properly, not just translated labels, and whether printed and PDF documents render Arabic text correctly. Test with real customer and item names, including mixed Arabic and English content.
Hijri dates where needed
Not every company needs Hijri dates, but some contracts, government interactions and HR records use them. If this applies to you, check whether the system can display or print Hijri dates alongside Gregorian dates, and how it handles conversion.
Local support availability
An ERP runs your business every day. Ask who supports it in the Kingdom, in which time zone and working week, in which languages, and with what response times. A capable partner in Jeddah, Riyadh or Dammam can matter more than the software itself.
Data residency and cloud hosting
Cloud ERP is now common, but where your data is stored and processed matters. Ask each vendor where the relevant data centers are, what options exist for in-Kingdom hosting, and how data is backed up and transferred. Obligations can arise under the Personal Data Protection Law, sector regulations and customer contracts, particularly in oil and gas, defense-related work and government supply. Confirm your current obligations with your legal and compliance advisers before deciding on a hosting model, rather than relying on vendor assurances.
Off-the-shelf platforms vs custom ERP
There is no single best ERP in Saudi Arabia. Each option suits different company profiles. The table below describes typical fit in qualitative terms; your fit-gap results should override any general view.
| Option | Typical fit | Strengths | Points to evaluate |
|---|---|---|---|
| Microsoft Dynamics 365 | Mid-to-large companies, especially those already using Microsoft 365 and Azure | Integration with Office, Teams and Power Platform; broad partner ecosystem; finance, supply chain and business central editions | Choosing the right edition; licensing structure; scope of partner-built extensions |
| Odoo | Small to mid-sized companies and divisions wanting a modular, flexible platform | Modular apps; open architecture; relatively fast to configure; community and enterprise editions | Depth for complex manufacturing or large volumes; quality of third-party modules; upgrade discipline |
| SAP | Large and complex organizations, multi-entity groups, asset-intensive industries | Deep industry functionality; strong controls; scale for high transaction volumes | Implementation effort and duration; need for specialized skills; change management load |
| Oracle | Large enterprises, finance-led transformations, groups needing strong consolidation | Strong financials and reporting; cloud suite breadth; enterprise scalability | Fit for operational processes; integration with shop-floor and legacy systems; skills availability |
| Custom-built ERP | Companies with genuinely distinctive processes that packages fit poorly | Built around your exact workflows; full ownership of code and roadmap | Ongoing maintenance responsibility; documentation; building compliance features yourself |
A few practical observations:
- Hybrid approaches are common. A packaged ERP for finance and supply chain is often combined with custom applications for specialized operations.
- The partner matters as much as the platform. The same product can succeed or struggle depending on the quality of the implementation team.
- Custom is not automatically cheaper or more expensive. It shifts cost from licenses to development and long-term maintenance, and it puts responsibility for compliance changes, such as ZATCA updates, on you.
Total cost of ownership beyond licenses
License or subscription fees are the most visible cost and often not the largest. Build a five-year view that includes:
| Cost area | What to include |
|---|---|
| Licenses or subscriptions | User types, modules, environments (production, test, development), annual increases |
| Implementation | Consulting days for design, configuration, testing and go-live support |
| Customization | Extensions, reports, forms and workflows beyond standard functionality |
| Integrations | Connections to ZATCA, banks, e-commerce, MES, WMS, CRM, HR and legacy systems |
| Data migration | Cleansing, mapping, loading and reconciling master data and open balances |
| Training and change management | End-user training, super-user programs, process documentation |
| Infrastructure and hosting | Cloud fees or on-premises servers, backup, security and monitoring |
| Support and maintenance | Partner support contracts, internal ERP team, bug fixes |
| Upgrades | Effort to retest and adapt customizations with each major release |
Two cost drivers deserve particular attention. First, customization: every change to standard behavior must be maintained through upgrades, so ask whether each gap is truly a must-have or whether the process can adapt. Second, data migration: companies consistently underestimate how much effort it takes to clean customer, supplier, item and bill-of-materials data. Start cleansing before the project begins.
Running a fair selection
A structured selection protects you from being sold to and gives every vendor a fair chance. A practical sequence looks like this:
- Form a selection team. Include finance, operations, supply chain, IT and a senior sponsor with authority to decide. Name one person accountable for the outcome.
- Map processes and agree requirements. Use the MoSCoW approach and scenario-based requirements described above.
- Build a longlist, then a shortlist. Screen platforms and partners against must-haves, industry experience and local presence. Aim for two to four serious candidates.
- Run a fit-gap analysis. For each shortlisted option, classify every requirement as standard fit, configuration, customization or gap. This is the core of an objective comparison.
- Hold scripted demos using your own scenarios. Send vendors your scenarios and sample data in advance. Score each demo against the same criteria with the same evaluators. Do not let vendors substitute their standard demo.
- Check references. Speak to existing customers of similar size and industry, ideally in the Kingdom. Ask about the partner’s delivery, not just the software.
- Run a proof of concept for high-risk areas. Where a requirement is critical and uncertain, such as ZATCA integration, complex costing or a key integration, test it in a limited working environment before committing.
- Compare total cost of ownership. Use the same five-year model for every option so the numbers are comparable.
- Agree contract and scope in detail. Define deliverables, assumptions, acceptance criteria, change-request rules, key personnel, data ownership and post-go-live support. Vague scope is a leading cause of disputes.
- Plan the implementation before signing. Confirm phasing, internal resource commitments and the go-live approach, so the decision reflects what delivery will really require.
Common mistakes
- Choosing on the demo. A good presentation is not evidence of fit. Scripted scenarios are.
- Replicating the old system. Recreating every legacy screen and report inside a new ERP adds cost and removes the benefit of change.
- Underestimating internal effort. Key users are needed for design, testing and training. Plan for their time or backfill their roles.
- Treating compliance as a later task. ZATCA e-invoicing, VAT and Arabic documents should be tested during selection, not discovered during go-live.
- Over-customizing. Each customization adds to upgrade and support effort. Challenge every gap before approving development.
- Ignoring data quality. Poor master data undermines reports and user trust from day one.
- Weak executive ownership. Without a senior sponsor who resolves cross-department conflicts, projects stall.
Frequently asked questions
What is the best ERP in Saudi Arabia?
There is no single best ERP for every Saudi company. Microsoft Dynamics 365, Odoo, SAP, Oracle and custom-built systems each suit different sizes, industries and process complexity. The best choice for you is the option that covers your must-have requirements with the least customization, meets local compliance needs and has a total cost you can sustain.
How long does ERP selection take?
It depends on company size, scope and preparation. Allow enough time for process mapping, fit-gap analysis, scripted demos and reference checks, because shortcuts at this stage tend to cost more during implementation.
Do we need ZATCA Phase 2 integration built into the ERP?
You need a reliable way to meet your e-invoicing obligations. That can be native functionality, a certified add-on or a middleware integration. What matters is that invoices are produced and submitted correctly, errors are handled, audit trails are kept and someone is responsible for updates when specifications change.
Should we choose cloud or on-premises ERP?
Cloud ERP reduces infrastructure management and usually simplifies upgrades. On-premises or private hosting may suit companies with specific data residency, security or integration needs. Review hosting locations and contractual terms, and confirm current data protection obligations with your legal and compliance advisers before deciding.
When does a custom ERP make sense?
Custom ERP makes sense when your core processes are genuinely distinctive, packaged platforms fit them poorly even after process improvement, and you are prepared to own long-term maintenance.
Getting an independent view
AIMLTS is a vendor-neutral consultancy based in Jeddah. We implement and extend Microsoft Dynamics 365, Odoo, SAP and Oracle, and build custom ERP on .NET, Java, Python or Node.js. Before recommending any system, we run fit-gap analysis and process re-engineering so the decision rests on how your business actually works. Learn more about our ERP Solutions, Business Process Consulting, ERP Implementation and ZATCA & E-Invoicing services, or book a discovery call to talk through your selection.