Short answer: first decide whether a ready-made ERP fits the way you work, or whether you need a custom system. Then talk to at least two providers of the type you chose, ask each one the same questions, and compare written proposals on the same scope. The provider matters as much as the software. The same product can succeed in one company and fail in another because of who set it up, how the data was moved and how the team was trained. This guide does not rank providers. It gives you the questions that separate a careful one from a risky one.
The kinds of ERP providers in Jordan
- Partners of global products. Firms that sell and set up products such as Odoo, SAP Business One, Microsoft Dynamics 365 Business Central or Oracle NetSuite. You pay licences to the product and fees to the partner for setup, changes and support.
- Local vendors with their own product. Jordanian firms with their own ready-made ERP or accounting system, often with local invoicing and payroll already built in.
- Open source implementers. Teams that set up free products such as ERPNext or Odoo Community. There is no licence fee, but setup, hosting and support still cost money.
- Custom software teams. Teams that build an ERP around your process from the start, usually module by module, with the code handed to you.
Each one can be the right choice. The question is which kind matches your business.
Ready-made or custom ERP
| Ready-made ERP | Custom ERP | |
|---|---|---|
| A good fit when | Your process is close to standard practice, and you are willing to adjust to the product | Your process is what sets you apart, or ready-made products force too many workarounds |
| How you pay | Licences per user, monthly or yearly, plus partner fees | A one-off build per phase, plus hosting and a care plan |
| Time to start | Fast for standard modules | Starts with the module that hurts most, then grows |
| Ownership | You rent the software and own your data | You own the code and the data |
| Main risk | Heavy changes that break on upgrades, and licence costs that grow with the team | A weak scope, or a team that cannot maintain what it built |
Our post on Odoo or a custom ERP goes deeper into this choice, and the ERP cost guide compares the money over several years.
Prepare before you call anyone
Providers can only quote what you describe. Before the first meeting, write down:
- How a sale, a purchase and a delivery move through your business today, step by step.
- The modules you need now and the ones that can wait.
- The number of users, branches and warehouses.
- The data you need to move: items, customers, suppliers, opening balances.
- The systems it must connect to, starting with JoFotara, your bank, your online store or your current accounting.
- The ten reports management reads every month.
One page is enough. Give the same page to every provider, so the proposals answer the same question.
Questions to ask any ERP provider
- Can you show us a live JoFotara invoice from the system? Invoices in Jordan go through the national e-invoicing system. A working link means an accepted invoice with the QR code from the tax department, not a slide. See our JoFotara guide.
- Who will set it up, and where are they? Ask for the names of the people on your project and whether they are in Jordan.
- Which clients in our industry can we call? Ask for two, and ask them what went wrong and how it was fixed.
- What grows with our team? Licences per user, storage, modules or support fees. Ask for the cost at today's size and at twice the size.
- Is data migration included? Who cleans the old data, who imports it, and who checks it.
- How do you handle changes? On a ready-made product, ask what happens to your changes when the product is upgraded. On a custom build, ask how changes are priced after launch.
- Who owns the data, and how do we export it? You should be able to take all your data in a usable format at any time.
- What does support look like? Hours, response times, and who answers when the invoices stop on a busy day.
- What is the plan, phase by phase? A clear first phase with a date and a price is a better sign than a promise to switch everything on at once.
- What happens if we part ways? Ask what you keep: data, code, documentation and accounts.
Warning signs in a proposal
- A package price with no list of modules, users or reports.
- A demo made only of slides or screenshots.
- One big go-live for every module and branch on the same day.
- Changes promised for free with no written scope.
- No clear answer on JoFotara.
- Your data stored in an account that belongs to the provider.
- A discount that expires this week, pushing you to sign before you understand the scope.
What different industries need
Distributors and warehouses need stock across several warehouses, transfers, batches and reorder alerts. Many start with an inventory and warehouse system and add accounts later. Factories need bills of materials, production orders and the real cost of each product. Contractors need projects, bills of quantities, subcontractors and progress billing, which many standard products handle only with heavy changes. Companies with field staff need attendance, leave and payroll, see our attendance and HR system. Ask every provider to show the workflow for your industry, not a general tour.
What a careful rollout looks like
- Discovery. The provider maps your process and writes the scope for the first phase.
- Setup or build. Screens are configured or built, then reviewed with the people who will use them.
- Data migration. Items, customers, suppliers and opening balances are cleaned and imported, then checked by your team.
- Testing with real work. Real invoices, purchases and stock moves, including JoFotara, before anyone depends on the system.
- Training per role. Short sessions for each role, not one long demo for everyone.
- Go-live and close support. The provider stays close through the first month end, when most problems appear.
Ask every provider to describe these steps for your project. Vague answers here usually mean the work will land on your team.
Hosting, security and the size of the provider
Ask where the system will be hosted, how often it is backed up, and whether each user sees only what their role allows. A log of who changed what is worth asking for in any system that holds money.
A large provider has more people, but your project may go to its newest staff. A small team gives you direct contact with the people who build, so ask how the work continues if one of them leaves: documentation, access to the code and a second person who knows your system.
How to compare proposals
Put the proposals in one table: the modules, the number of users, the setup fee, licences per year, hosting, support and the cost of the first year of changes. Add up three years, not one. A low setup fee with high yearly licences can cost more than a higher one-off build. Then compare the plan: who does what, in which order, and how your team will be trained.
What the written proposal should state
The modules and reports in scope, the number of users, each phase with its date and price, the payment stages, what is not included, the support terms after go-live, and who owns the data and the code. If any of these is missing, ask for it before you sign.
Where Saree3 fits
We build custom ERP systems for companies in Jordan, in phases, starting with the module that hurts most. A first version of a custom system starts from 4,500 JOD, and each phase is fixed in writing after a short discovery. You own the code and the data. When a ready-made product fits your process better, we say so in the proposal, and we can build the custom part around it.