ERP Selection Consultant, Iraq

When partner coverage is thin, judge the partner first

For many platforms, the number of firms able to implement and support them inside Iraq is small. Some are based in Baghdad or Erbil; others deliver from Amman, Dubai or Istanbul and send consultants in for workshops and go-live. Any of these models can work, but the risks differ, and they should be weighed before the software is chosen, not after.

I ask every partner on the shortlist to answer the same questions in writing:

• Which named people will design, configure and train, and where will they physically be during the project?
• Can they support sites in the south, the center and the Kurdistan Region, or only one area?
• Who delivers training in Arabic and in Kurdish, and who answers support calls after go-live?
• What happens if the lead consultant leaves or cannot travel?
• Which comparable Iraqi clients, or clients in similar conditions, can we speak to?

Reference calls then test those answers. I ask former clients whether the team they were promised actually turned up, how quickly issues were resolved once the partner's consultants had gone home, and how changes were handled. Where only one credible partner exists for a platform, the scoring sheet records that dependency as a risk in its own right.

Shortlists for contractors, service companies and importers

Shortlists in Iraq depend heavily on what kind of business is buying.

• Contractors and engineering firms need costs by contract, site and cost code, subcontractor payments with retentions and progress billing. Odoo, ERPNext and Dynamics 365 Business Central typically appear here, each tested on the same project scenarios.
• Oil and gas service companies working for international operators need job tickets, rate schedules, timesheets and documentation that client auditors expect. The platform must produce that evidence cleanly.
• Import traders and distributors focus on landed costs, multi-warehouse stock, customer credit and sales collected in cash. Zoho and Odoo often feature for smaller traders, with ERPNext or Business Central for larger operations.
• Groups with international parents or partners may need to evaluate a platform the parent already uses, checking local fit rather than running an open comparison.

I describe every option neutrally, with its strengths and limits, and I do not rank platforms in general. A system that suits a Baghdad trader may be wrong for a contractor with remote camps. For background, the ERP for construction comparison and Zoho and ERPNext compared are useful, and my Odoo notes for Iraq cover one candidate in more depth.

Testing offline tolerance and slow connections in demos

A demo on fast office internet tells you little about a store at a remote yard or a timesheet entered at a camp. Iraqi sites can have limited, shared or intermittent connectivity, and grid power is not always stable. I therefore make connectivity a scored part of every demo.

Each vendor is asked to show:

• Data entry on a deliberately slowed connection, including attachments such as delivery notes or photos.
• Offline capture on mobile devices for site tasks like goods receipts, timesheets or stock counts, and how records synchronize when the link returns.
• What happens to a half-saved transaction if the connection drops.
• How conflicting edits from two locations are resolved.
• Whether a local server option exists and what it requires in power protection, backups and administration.

Some systems handle these conditions well out of the box, some need a separate mobile app or add-on, and some simply expect a stable connection. None of those answers disqualifies a product automatically, but the effort and risk must be visible. Process owners from your sites score this part of the demo, because they know the conditions best. The Iraq ERP consultant page discusses hosting choices more broadly.

Demo scripts for dinars, dollars, entities and projects

Beyond connectivity, the demo scripts follow the transactions that carry the most risk for an Iraqi company. Scripts and an extract of your own records go to all vendors ahead of time; each then performs them live while your team marks every step.

Typical scenarios include:

• A contract priced in US dollars with progress invoices, an advance payment and retention, while some site costs are paid in Iraqi dinars.
• A subcontractor invoice checked against measured work, with retention held and released later.
• An import shipment with freight, customs and clearing costs spread across items as landed cost.
• Two companies, one registered in federal Iraq and one in the Kurdistan Region, each with its own ledger, numbering and users, plus a consolidated group report.
• Invoices and delivery notes printed in Arabic or Kurdish, checked by your bilingual staff.

Which rate applies to which transaction is decided by your finance team and accountant, and tax or statutory treatment for each entity is confirmed by local advisors. For every scenario, the notes say whether it ran out of the box, needed setup, or depended on development. My ERP evaluation page explains the scoring approach in general terms.

Licensing, payment routes and contract terms

Ownership cost covers implementation effort, customization, connectors, data migration, hosting, training and support, not just the subscription. I set these drivers side by side for each option so owners can compare like with like.

Iraq adds a practical question that is easy to overlook: how will licenses and services actually be invoiced and paid? Some vendors bill only by card or international transfer, some sell through regional distributors, and partners may invoice from another country. I ask each vendor and partner to confirm the billing entity, currency and payment method in writing, and you should check those arrangements with your bank and finance advisor before signing. The same applies to renewals and to adding users later.

Hosting terms need written answers too: where data is stored, how backups are tested and whether a full data export is possible if you change partner. In the statement of work, I look for gaps such as Arabic and Kurdish templates left out, migration covering only master records, site training left vague, and support terms without response commitments. I take nothing from any vendor or partner, so the markup is written for your side only.

The work runs remotely. If requirements are not yet documented, start with the Iraq ERP business analyst work. After choosing, my client-side implementation role in Iraq follows delivery, and the Iraq hub lists the rest. My ERP vendor selection service sets out the method in full.