Skip to Content

ERP requirements checklist for companies in the Middle East

A practical checklist to write your ERP requirements before you talk to vendors: finance and tax compliance, sales, purchasing, inventory, manufacturing, HR and payroll, integrations, reporting, language, hosting and support, with the questions specific to Saudi Arabia, the UAE and Egypt.
November 7, 2026

The most expensive mistake in an ERP project is made before it starts: choosing a system, or a partner, without writing down what the business actually needs. Demos then show what the vendor wants to show, quotes cannot be compared, and gaps are discovered after the contract is signed. A clear requirements list fixes that. This checklist is built for companies in the region, so it includes the tax, language, labour and data rules that generic templates miss.

FlexCode Middle East is part of FlexCode Systems GmbH, an Odoo Silver Partner. We implement Odoo, so Odoo is the system we describe, next to an honest look at the topic itself.

Key points

  • Write before you shop. Requirements first, then demos and quotes.
  • Compliance is mandatory. E-invoicing, VAT, Zakat or corporate tax, and payroll rules.
  • Must, should, could. Prioritise so vendors are judged on what matters.
  • Script the demo. Ask vendors to show your scenarios, not their slides.

Tax and legal compliance

  • Saudi Arabia: ZATCA Phase 2 e-invoicing integration, VAT returns, Zakat or income tax, withholding tax.
  • UAE: VAT returns, Corporate Tax, upcoming e-invoicing through accredited service providers, free zone treatment.
  • Egypt: ETA e-invoice and e-receipt, VAT, withholding, item coding with EGS or GS1.
  • Bilingual tax invoices with the required fields and QR codes.
  • Audit trail, document retention and locked periods.

Detail per country: Saudi VAT, UAE Corporate Tax and Egypt VAT.

Team writing requirements on sticky notes
Write down what the business needs before anyone shows you a demo.

Operations

AreaQuestions to answer
SalesChannels, pricelists, approvals, quotations in Arabic, credit limits, commissions
PurchasingApproval levels, imports, landed costs, vendor pricelists, three-way match
InventoryWarehouses, bins, lots and expiry, serials, barcode, valuation method
Point of saleBranches, offline, card terminals, loyalty, receipts per country
ManufacturingBoMs, routings, MTO or MTS, quality, costing, subcontracting
Projects and servicesTimesheets, billing models, progress billing, retention

HR, payroll and people

  • Payroll per country: GOSI in Saudi Arabia, WPS files in the UAE and Saudi Arabia, social insurance in Egypt.
  • End of service gratuity calculations and accruals.
  • Leave, attendance, overtime and allowances such as housing and transport.
  • Saudisation or Emiratisation reporting where it applies.
  • Employee self service in Arabic and English.

See GOSI in Odoo, UAE WPS and Egyptian social insurance.

Technology, data and support

  • Languages: full Arabic interface and documents, right to left layout.
  • Structure: number of companies, branches, currencies and countries.
  • Integrations: banks, payment gateways, marketplaces, delivery apps, existing systems.
  • Hosting and data residency: cloud, private cloud or on-premise, and where data must be stored.
  • Security: roles, two-factor login, audit trail, backups.
  • Support: local team, Arabic support, response times, upgrade policy.

Read Odoo hosting options and ERP security and data protection.

Prioritising and scoring vendors

Mark each requirement as must have, should have or could have. Musts are pass or fail: a system that cannot meet ZATCA or ETA requirements, or cannot run payroll in your country, is out. Shoulds and coulds are scored, weighted by how much they matter. Then ask each vendor to demonstrate five or six of your real scenarios, with your products and your documents, rather than a general presentation.

  1. Collect requirements by department
  2. Prioritise: must, should, could
  3. Shortlist systems and partners
  4. Scripted demos with your scenarios
  5. Score, check references, negotiate

Must

Pass or fail requirements

5 to 6

Scenarios for each demo

3

References to call per vendor

1

Written scope before signing

Next steps: how to choose an Odoo partner, our ERP comparison and what an implementation costs. You can also take our ERP readiness quiz.

Turn your requirements into a plan with FlexCode

We run requirement workshops with each department, map them to Odoo, mark the gaps honestly and give you a written scope you can compare.

Book a free call

Frequently asked questions

Why write ERP requirements first?

So demos, quotes and contracts are judged against what your business needs.

What are must-have requirements in the region?

E-invoicing and tax compliance, payroll rules and Arabic documents.

How many requirements should we list?

Enough to cover your key processes; a few hundred lines is common for mid-sized companies.

What is a scripted demo?

A demo where the vendor shows your scenarios with your data.

Who should write the requirements?

Key users from each department, coordinated by a project owner.

Talk to us about how Odoo fits your business. Book a free call

Run invoicing, stock and accounts from one system.

FlexCode Middle East implements Odoo in Arabic and English for companies in Egypt, Saudi Arabia and the UAE.