"How much does an ERP cost?" is the first question almost every Saudi business asks us, and the honest answer is: it depends on a handful of decisions you can control. The licence price on a vendor's website is only one line of the budget, and often not the biggest.
This guide walks through every line of a typical ERP budget in Saudi Arabia, what makes each line bigger or smaller, and the questions that let you compare quotes fairly. We implement ERPNext and Odoo as an official partner and provide services for Microsoft Dynamics 365 and Infor, so the lines below apply to all four.
We do not quote prices here. Every project is scoped against your processes, and a number without that context does more harm than good. What we can give you is the structure, so the quotes you receive make sense.
The seven lines of an ERP budget
| Line | What it covers | One-off or recurring |
|---|---|---|
| 1. Licences or subscription | The right to use the software | Recurring (or none) |
| 2. Hosting | Cloud or your own servers | Recurring |
| 3. Implementation | Workshops, configuration, testing, go-live | One-off |
| 4. Data migration | Moving masters and opening balances | One-off |
| 5. Saudi compliance | ZATCA Phase 2, VAT, Zakat, Arabic documents | One-off + small recurring |
| 6. Integrations and customisation | POS, HRMS, banks, e-commerce, your own rules | One-off + upkeep |
| 7. Training and support | Users, key users, ongoing help | One-off + recurring |
1. Licences: the line that varies most between platforms
This is where the platforms differ most.
- ERPNext is open source. There are no per-user licence fees, so adding a warehouse team or a new branch does not change this line at all.
- Odoo has a free Community edition, but the Saudi ZATCA Phase 2 module is in Odoo Enterprise, which is a subscription priced per user.
- Microsoft Dynamics 365 and Infor are licensed by subscription, typically per user and per application.
The question to ask is not "what is the price per user" but "how many users will we have in three years, including occasional ones?" A per-user model that looks cheap for ten users can become the largest line in the budget at a hundred. This is the main reason we usually recommend ERPNext to growing Saudi businesses. We compare the two open platforms in ERPNext vs Odoo for Saudi businesses.
2. Hosting
You can run your ERP in the vendor's cloud (Frappe Cloud for ERPNext, Odoo Online or Odoo.sh for Odoo, Microsoft's cloud for Dynamics 365) or on your own servers. Cloud hosting is a predictable monthly or yearly fee and removes server management. Self-hosting suits organisations with an IT team or data rules that require it; the cost moves to servers, backups and someone to look after them. ERPNext can be self-hosted with no licence strings attached.
3. Implementation: usually the biggest one-off line
Implementation is the work of turning software into your system: process workshops, configuration of the chart of accounts, items, warehouses, approval rules and print formats, then testing and go-live. Its size depends on:
- Number of modules you start with (accounting only, or accounting + stock + sales + buying + manufacturing).
- Number of companies, branches and warehouses.
- How standard your processes are. Every "we do it differently" is configuration or development time.
- How fast your team can decide. Waiting for sign-offs is the hidden cost in most projects.
A phased plan (finance and stock first, then manufacturing or projects) spreads this line out and gets you live sooner.
4. Data migration
Customers, suppliers, items, opening balances and open documents have to move from the old system. Clean data in spreadsheets is quick; years of duplicate items in an old system are not. Decide early how much history you really need. Most businesses bring masters and opening balances, and keep the old system read-only for reference.
5. Saudi compliance: ZATCA, VAT, Zakat and Arabic
Every ERP sold in the Kingdom needs to handle:
- ZATCA Phase 2 e-invoicing: invoices generated in the required format, cryptographically stamped and reported or cleared through FATOORA. With ERPNext this is done with KSA compliance apps (one is free and open source); with Odoo it is the Saudi module in Enterprise; any ERP can also connect through a specialist platform such as Taxilla. See how to connect your ERP to FATOORA.
- VAT and Zakat reporting set up on your chart of accounts.
- Arabic invoices, print formats and, usually, an Arabic interface for some users.
If your business is in ZATCA's Wave 25 (VAT-able revenue above SAR 187,500), this line has a deadline: integration by 1 February 2027. Read who must join FATOORA in Wave 25.
6. Integrations and customisation
Integrations are where budgets most often grow after signing. Typical Saudi connections are a point-of-sale system, an HRMS and payroll, bank files, e-commerce, and attendance terminals. Each one is scoped separately: which data moves, in which direction, how often, and what happens when it fails.
Customisation should be the last resort. Every custom feature has to be maintained through upgrades. A good partner will first show you how the standard system does it.
Payroll is a common example. Saudi payroll needs GOSI, Mudad/WPS salary files and labour-law rules for leave and end of service. Many businesses pair the ERP with a dedicated HRMS rather than customising payroll. Our own HR Works integrates with Mudad/WPS, GOSI, Qiwa and Muqeem and connects to ERPNext, Odoo or any ERP. We have already delivered the ERPNext–HR Works integration; see the system integrations we have delivered.
7. Training and support
Plan for key-user training (the people who will own the system), end-user training per role, and a support agreement after go-live. Support is usually a yearly contract or a block of hours. Ask exactly what it includes: bug fixes, small changes, upgrades, and response times.
Five things that push the total up
- Underestimating users on a per-user licence.
- Custom development instead of adapting a process to the standard.
- Dirty data discovered during migration.
- Integrations added after signing, without scope.
- Slow decisions that stretch the project timeline.
Five ways to keep it down
- Choose a licence model that does not grow per user (ERPNext) if your headcount will grow.
- Start with the core modules and phase the rest.
- Clean your masters before migration: items, customers, suppliers.
- List every integration in the first quote, even the ones planned for later.
- Name one decision-maker per department for the project.
How to compare two ERP quotes
Put the quotes side by side on the seven lines above and check:
- Are licences counted for all users, for the full contract period?
- Is ZATCA Phase 2 included, and for which invoicing systems?
- Are Arabic print formats included?
- Which integrations are in scope, and which are "to be discussed"?
- How many training sessions, and for whom?
- What does support cover after go-live, and at what cost from year two?
A quote that is lower because it leaves out one of these lines is not cheaper.
Get a quote built on your processes
Tell us your users, branches, modules and the systems you need to connect, and we will build a quote line by line, usually with ERPNext as the starting point and Odoo, Dynamics 365 or Infor where they fit better. Request a quote, read about ERPNext in Saudi Arabia, or compare platforms in the best ERP software for Saudi Arabia.
Licence and edition details reflect each vendor's published offering at the time of writing. They change, so confirm with the vendor.
