ERP implementation cost in Jordan: what you really pay for, and common mistakes
A breakdown of what an ERP project in Jordan really costs beyond the licence: implementation, data migration, training, customisation, integrations and internal time, with the mistakes that most often blow the budget.
"How much does an ERP cost?" is the first question every owner asks, and the honest answer is that the licence is often the smallest part of it. The total depends on how many people use the system, how many modules you need, how clean your data is, how much you want to change the software, and how much of your own team's time you can give the project. This guide breaks the cost into its parts so you can compare quotes properly, without invented averages that would not apply to your company. If you are still deciding whether you need one at all, start with what ERP is and when a company needs it, and see our ERP system for companies in Jordan for what a ready-made Jordanian setup includes.
The six parts of ERP cost
| Cost item | What it covers | What drives it |
|---|---|---|
| Licence or subscription | The right to use the software, one-off or monthly/yearly | Number of users, modules, companies or branches, hosting |
| Implementation | Analysis, configuration, chart of accounts, approval rules, permissions, project management | Number of modules and processes, how many decisions are already made |
| Data migration | Customers, suppliers, items, opening balances, open invoices and cheques, employees | Quality of existing data, number of sources, history required |
| Training | Teaching each role to use the system, plus documentation | Number of users and roles, staff turnover |
| Customisation | Changing screens, reports or workflows beyond configuration | How far your process differs from the standard |
| Integrations and hardware | JoFotara, bank salary files, attendance devices, POS printers and scanners | Number of external systems and devices |
On top of these come two costs that rarely appear on a quote: your team's time (the accountant who cleans data and tests payroll is not doing their normal work) and ongoing support after go-live.
Licence models and what they hide
Subscription per user
Most cloud ERPs charge per user per month. Odoo's public pricing page is a clear example: a free plan limited to one app, then Standard and Custom plans billed per user per month, with Odoo Studio, the external API and on-premise or Odoo.sh hosting reserved for the Custom plan. Ask who counts as a user, whether occasional users (a manager who only approves, an employee who only views a payslip) are cheaper, and what happens to the price when you add a branch or a company.
One-off licence
Local desktop and on-premise systems are often sold with a one-off licence plus annual maintenance. The licence looks cheaper over five years, but servers, backups, updates (including JoFotara changes) and remote access become your costs.
"Free" open-source editions
Open-source editions remove the licence fee, not the work. Someone still has to install, host, configure, secure, update and support them, and Jordan-specific features may need paid modules or a partner.
Implementation is usually the biggest variable
Odoo's pricing page states plainly that implementation services are not included in any plan, and lists project management, data import, customisation and training as separate services; it points small companies to its Success Packs and mid-size companies to partners. That is normal across the market: a system that has to be shaped to your business costs more to implement than one that already speaks your local rules. For a Jordanian company, localisation is where effort hides: social security with the yearly ceiling, income tax exemptions per employee, JoFotara, post-dated cheques, Arabic documents and bank salary files. Our page on Aspirations vs Odoo compares the two approaches in detail.
Costs after go-live
The project does not end on go-live day. Budget for the subscription or maintenance fee, support hours, training for new staff, changes in rules (a new social security ceiling each January, tax changes, JoFotara updates) and the occasional new report or branch. Ask whether rule updates are included or charged as change requests: in a system where local rules are part of the product, they usually arrive with normal updates; in a heavily customised one, each change may be a small project.
Common mistakes that raise the cost
- Comparing licence prices only. A cheap subscription with an expensive implementation can cost more than the reverse. Ask for the total for the first year and for years two and three.
- Migrating dirty data. Duplicate customers, items with three names, opening balances that never reconciled. Cleaning before migration is cheaper than cleaning inside the new system.
- Customising before learning the standard. Many requests disappear after a month of use. Customisations also have to be maintained through every upgrade.
- No internal owner. A project led only by the vendor drifts. Name one person in your company who decides and is given time to do it.
- Going live with everything at once. Starting with accounting, sales and inventory, then adding payroll and CRM, spreads the cost and the risk.
- Skipping a parallel payroll month. Running one month in both the old and new system catches errors before employees see them on a payslip.
- Forgetting JoFotara and the banks. E-invoicing credentials and bank file formats take time to obtain and confirm; leave them to the last week and go-live slips.
- Underestimating training. A system people do not know how to use ends with them going back to spreadsheets.
How to get comparable quotes
- Give every vendor the same written list: users by role, modules, branches, companies, devices and the integrations you need.
- Ask for the price split into the six items above, plus support after go-live.
- Ask what is included in implementation in days or deliverables, and what happens if it runs over.
- Ask which Jordanian requirements work out of the box and which need customisation or a paid module.
- Ask how you export your data if you leave.
- Ask for a demonstration with your own example: an invoice to JoFotara, a bounced cheque, a payroll with a salary above the social security ceiling.
The point is not to pick the cheapest line in each column but to see the whole picture. A vendor who cannot split the price this way is telling you something about how the project will be run.
Aspirations is a cloud ERP with Jordanian and Saudi rules already in the product: accounting with JoFotara and post-dated cheques, payroll with social security and income tax, inventory, POS, HR and CRM. Setup is done with our team using import templates, a review of rates, bank and government file formats confirmed with you, and a parallel payroll month. It is less customisable than Odoo. Plans are being finalised, and a free trial is available.
General information; costs depend on your company and each vendor's current terms, so get written quotes and check e-invoicing requirements with the Income and Sales Tax Department.
