ERP Selection in Jordan: Questions to Ask Before You See a Demo
A polished demo tells you what a system can do, not whether it fits you. These are the questions to answer, and to ask vendors, before you sit through the first presentation.

An ERP (enterprise resource planning) demo is designed to impress. The presenter knows the product well, the sample data is clean, and every screen works first time. Two hours later, the management team is excited and has learnt almost nothing about whether the system fits their business.
The most useful part of ERP selection in Jordan, as anywhere, happens before the first demo. A set of questions, some for yourselves and some for vendors, turns the demo from a show into a test.
Questions to answer internally first
Vendors can only show you what you ask to see. If you have not agreed internally what you need, every product will look suitable. Work through these as a leadership team, with operations, finance and IT (information technology) in the room.
- Which problems must the new system solve? Name the top five, in business terms. “We cannot see stock across our three branches in real time” is useful. “We need a modern system” is not.
- Which processes will it cover in the first phase? Sales, purchasing, inventory and finance are common. Manufacturing, payroll, customer relationship management (CRM) and maintenance may come later, or stay in specialist tools.
- How do those processes work today, and how should they work? If you buy software before agreeing the target process, the vendor’s default setup becomes your process by accident.
- What data will move across? Customers, suppliers, products, open balances, and how many years of history.
- Who will own the system internally? Someone must make decisions during the project and manage it afterwards. If there is no realistic candidate, factor that into your choice of partner.
- What is the realistic budget, including people’s time? Licences are only part of the cost. Implementation, data cleaning, training and the hours your own staff spend on the project all count.
Questions about local fit
Many international ERP products are used successfully in Jordan, but local fit varies between products and, just as much, between implementation partners. Ask specifically:
- E-invoicing. How does the system connect to JoFotara, the national e-invoicing system run by the Income and Sales Tax Department? Is the integration built in, provided by the partner, or a third-party add-on? Who maintains it when requirements change? If you also trade in Saudi Arabia, ask the same about e-invoicing with the Zakat, Tax and Customs Authority (ZATCA).
- Arabic. Is the interface available in Arabic for staff who prefer it? Can invoices, statements and delivery notes print in Arabic, with right-to-left layout and correct number formatting? Can customer and product names be stored in both languages?
- Tax and currency. How is general sales tax configured, including different rates and exempt items? Does the system handle multiple currencies if you buy in dollars or euros and sell in dinars?
- Payroll and human resources. If payroll is in scope, how does the system handle local requirements such as social security contributions and income tax deductions? Many companies keep payroll in a local specialist system and integrate it, which is a perfectly sensible choice.
- Banking. Can bank statements from your banks be imported, and can payment files be produced in a format your bank accepts?
Requirements in these areas change from time to time, so treat vendor answers as a starting point and confirm tax and compliance questions with your own adviser.
Questions about the implementation partner
In practice you are choosing a partner as much as a product. The same ERP can succeed with one partner and fail with another. Useful questions include:
- How many implementations similar to ours, in size and industry, has this team delivered in the region? Can we speak to two of those clients without the partner on the call?
- Who exactly will work on our project, and how much of their time is committed? Will the people in the sales meeting be the people doing the work?
- What is your method for requirements, data migration, testing and training? What do you expect from us at each stage?
- How is support provided after go-live, in what hours, in which languages, and with what response times?
- What happens to our customisations when the product releases a new version?
Questions about cost, data and exit
Pricing models differ widely. Some products charge per user per month, others per module, others through a perpetual licence with annual maintenance. Ask for a five-year view of total cost at your expected number of users, including implementation, support, hosting and any add-ons such as e-invoicing connectors or reporting tools. Ask what triggers extra charges, such as more users, more companies or more storage.
Ask too where your data will be hosted, who can access it, how backups work, and how you would export your data if you ever left. Jordan’s Personal Data Protection Law of 2023 adds weight to these questions where customer or employee data is involved. A vendor that answers them clearly and in writing is easier to trust.
Turning the demo into a test
Once you have answers, write a short demo script and send it to every shortlisted vendor in advance. Consider a consumer goods distributor with branches in Amman, Irbid and Aqaba. Its script might ask each vendor to show a customer order taken at Irbid for stock held in Amman, a credit limit block and its approval, a transfer between branches, a sales tax invoice submitted to JoFotara, and the month-end stock valuation by branch. Ask vendors to use sample data you provide, including a few awkward cases, such as a partly delivered order or a return.
Score every vendor against the same script. The difference between products becomes much clearer when each one has to walk through your reality rather than its own showcase.
Choosing a system that fits how you work
Before booking any demo, hold one internal session to answer the six questions in the first section, then turn the answers into a demo script of five or six scenarios. Vendors who decline to follow the script, or ask to show their standard presentation instead, have told you something useful.
Our Enterprise Systems service supports each step, from mapping your processes and writing requirements to scripting demos, scoring vendors against your own scenarios and overseeing implementation.



