ERP Selection Consultant, Jordan

Shortlists for Jordanian companies, by size and sector

There is no single right shortlist for Jordan. The one that makes sense depends on what you sell, how much stock you hold and whether a parent company sets the rules.

• IT, outsourcing and professional services firms that bill foreign clients usually compare suites strong in projects, timesheets and multi-currency invoicing. Zoho and Odoo often appear here, sometimes alongside a dedicated professional services tool.
• Pharmaceutical suppliers, medical distributors and FMCG traders need lot and expiry control, approvals and traceable stock movements. Odoo, ERPNext and Dynamics 365 Business Central are typical candidates, each tested on the same batch scenarios.
• Manufacturers and larger groups may add SAP Business One or NetSuite where an implementer proposes them, and regional groups may need to evaluate a platform already chosen by head office.

I describe each candidate's strengths and limits in writing, without ranking platforms in general. A product that suits a software exporter can be a poor fit for a warehouse full of short-dated stock. For side-by-side context, the ERPNext and Dynamics 365 comparison and the ERP for distribution comparison are useful background, and my Odoo notes for Jordan go deeper into one option.

Making e-invoicing a test rather than a promise

Jordan's tax department operates a national electronic invoicing system, and every vendor pitching in the market will say they support it. That sentence alone is worth very little. What you need to know is how the connection works, who owns it and what happens on a bad day.

During screening and demos I ask each vendor and implementer to answer in writing:

• Is the connection a standard feature of the product, a connector built by this implementer, or a third-party service with its own subscription?
• Can they show a submission working in a test environment, including the response that comes back?
• How are rejected or failed submissions shown to users, corrected and resent?
• How are credit notes and cancellations linked to the original invoice?
• Who updates the connector when the authority changes its specifications, and is that covered by support or charged separately?

Which of your invoices fall in scope, and what fields they must carry, is a question for your tax advisor, and I do not interpret the rules. My role is to make sure their guidance becomes a demo scenario and later a test script. If e-invoicing support depends on a small connector maintained by one person, the scoring sheet should say so.

Comparing implementers in Amman and across the region

In Jordan, the implementer often shapes the outcome more than the platform. Two firms selling the same product can differ widely in team depth, sector knowledge and how they treat a client after go-live. Some Jordanian buyers also receive bids from Gulf-based partners serving a regional group, which widens the field but makes comparison harder.

I assess each implementer on the same terms. I want to know which named consultants will run your design workshops and configure the system, whether they have delivered batch-controlled inventory or project billing before, who maintains any e-invoicing connector and customization, and how users raise issues once the project team moves on. Arabic training and support usually come from the implementer, so I ask how that is staffed.

Reference calls follow the demos. I ask for clients of a similar size and sector, then run structured conversations about scope changes, support response and whether the promised team turned up. Those calls are often where a polished proposal and a realistic one separate.

If you already have proposals on the table, my vendor proposal review covers that narrower job. For the wider picture of independent work in Jordan, see the freelance ERP consultant page for Jordan.

Demo scenarios for pharma, distribution and exported services

Scripted demos are where I learn most about fit. Each vendor receives the same scenarios and a sample of your data before the session, then works through them live while your process owners score what they see.

For Jordanian companies the scripts usually draw on cases such as these:

• Receiving a shipment with several lots and expiry dates, then picking the earliest-expiring stock for a hospital or pharmacy order.
• Tracing every customer who received a given batch, as you would during a recall.
• Raising an invoice in US dollars to a client abroad while the books are kept in dinars, then receiving payment at a different rate.
• Recording consultant timesheets against a project and billing them under a fixed-fee or time-and-materials contract.
• A local sale with sales tax, its e-invoice submission and an Arabic printout checked by your staff.

I record whether each scenario was handled as standard, with configuration or only through custom development. Dinar amounts are checked for rounding along the way, since the currency is subdivided into fils. The resulting notes feed the weighted scoring, so the decision rests on evidence rather than on which presenter was most persuasive. My ERP evaluation page explains the scoring method in general terms.

Licenses, hosting and the contract you sign

Ownership cost is broader than the subscription quote. I compare per-user subscriptions, open source software paired with paid hosting and services, and suite bundles, then add the drivers that move the total: implementation effort, connectors, customization, data migration, training and ongoing support. Some subscriptions are billed in foreign currency, so ask how pricing is set and invoiced to a Jordanian entity.

Hosting questions go into writing as well. Where will the data be stored, how are backups tested, can you export everything if you leave, and how do Jordan's personal data protection rules apply to the arrangement? Your legal counsel interprets the law; I make sure the vendor's answers are on file for them.

Before signature I mark up the statement of work. Typical gaps include e-invoicing described as an assumption rather than a deliverable, migration limited to master data, Arabic templates missing from scope and support terms that start vaguely. I take no fee or commission from any vendor or implementer, so the markup serves only you.

The work is remote, with workshops scheduled in hours Jordan and India share. If requirements still need writing, start with the Jordan ERP business analyst work; after the decision, the ERP implementation consultant role in Jordan keeps delivery tied to what was evaluated. The Jordan overview lists everything else.