Choosing an ERP for a Growing Saudi Business

An ERP project is a business change project

Most ERP problems are not caused by the software. They come from unclear processes, poor data, and an implementation that tries to copy every old habit into a new system. Treat selection and rollout as a business project with a technology component, not the other way round.

Write down requirements first

Ask vendors to demonstrate your scenarios instead of their standard demo.

• The processes that must work on day one: finance, sales, purchasing, inventory, HR
• Reports leadership actually uses
• Integrations: e-commerce, payments, banks, CRM, and existing tools
• Users, branches, entities, and currencies
• What is unique to your business and genuinely needs customisation

Saudi-specific checks

Confirm compliance claims with references and, where needed, your tax advisor.

• E-invoicing that meets ZATCA requirements for your phase, including integration where required
• VAT handling and Arabic invoices
• Arabic interface and reports for the people who will use them
• Local support and an implementation partner with references in Saudi Arabia
• Hosting and data location that match your sector’s expectations

The partner matters as much as the product

The same ERP can succeed or fail depending on who implements it. Ask who will be on your project, speak with clients whose systems have been live for at least a year, and make sure configuration and data migration are documented and handed over.

Common mistakes

An independent advisor can review the shortlist, the contract, and the implementation plan before you commit.

• Heavy customisation that makes every upgrade expensive
• Migrating years of messy data without cleaning it
• No internal owner after go-live
• Training only a few people and expecting adoption