How to Choose an ERP: Cloud or On-Premise, Off-the-Shelf or Custom

How to Choose an ERP: Cloud or On-Premise, Off-the-Shelf or Custom

In part three we opened the system from the inside and walked its six modules through concrete Saudi sectors. Now you know what you want to run; the harder decision is which system to run it on. Here the choice is not settled by the vendor's slogan or the number of features in the demo, but by five practical criteria: where your data lives, how closely the system matches your process, what it integrates with, whether you can leave it, and whether it complies with e-invoicing. We walk them one by one.

Cloud or on-premise: where your data lives

The first decision is where the system runs, and it has two faces:

• Cloud: the vendor hosts it and you reach it over the internet on a monthly or yearly subscription. No servers to buy, updates and backups are the vendor's responsibility, the upfront cost is lower, and you reach it from any branch or device.
• On-premise: you run it on your own servers inside the company. You hold full control, but you carry the cost of the hardware and an IT team that manages security, backups, and updates, and the upfront cost is higher.

Between them sits a common middle option: private cloud hosting inside a data center in Saudi Arabia. The governing question here is not price but data residency: where is it actually stored? The Personal Data Protection Law overseen by SDAIA sets controls on personal data and its transfer outside the Kingdom, and some sectors require their data to stay inside Saudi Arabia. Before you sign, ask the vendor plainly: in which country do your servers sit, and who holds access.

Off-the-shelf or custom: how closely it matches your process

The second decision is the degree of tailoring:

• Off-the-shelf: a pre-built system with fixed modules. Faster to install, lower cost, proven elsewhere — but you bend your work to the system, not the other way around.
• Custom: built on your exact process, so it matches perfectly, but it is more expensive and slower, and you carry its maintenance and development alone.

The reality is that most good systems are configurable: off-the-shelf at their core, with a bounded space for customization. The practical rule: customize the part that genuinely sets you apart from competitors, and adopt the ready standard for everything routine and shared. Heavy customization looks attractive, but it freezes your system into a shape that is hard to upgrade later, and ties you to whoever wrote it.

Integration and the freedom to exit

A system does not live alone, and you must know before signing what it connects to and how you leave it:

• Integration: does it link with your bank, payment gateway, online store, shipping company, and invoicing platform? Documented APIs mean you can add tools later without rebuilding everything.
• Freedom to exit: many overlook this question until it is too late. If you decide to move after three years, can you export all your data in a readable format? Or is it locked in a vendor-specific format? Ask for a data-export clause written into the contract before you begin, not after you are stuck.

Being tied to a vendor is not bad in itself, but a tie you cannot undo is what turns a system from a tool into a constraint.

E-invoicing: a requirement, not a nice-to-have

One last criterion precedes all the above because it is not a preference but a legal obligation: any system that issues sales invoices in Saudi Arabia must comply with e-invoicing (Fatoora) and its second phase of integration with the Zakat, Tax and Customs Authority. This is not an extra feature to defer; it is a pass-or-fail condition. Before any other comparison, confirm the vendor is actually integrated and certified with the Authority, not merely planning to be. A system that fails this condition drops off the list no matter how attractive it looks on the other criteria.

The Origami view

We are a technology company, and we do not push you toward cloud or on-premise out of a ready template but by reading your sector and its regulatory requirements. For most small and medium businesses, the practical answer is cloud hosting inside a Saudi data center, with a configurable off-the-shelf system and light customization that touches only the part that sets you apart. We insist on two non-negotiables: data you can export at any time without lock-in, and full e-invoicing compliance from day one. Our measure is not the system with the most features, but the one that matches your process and leaves you free to move.

Conclusion

Choosing a system is not a contest between two brands but a balance of five criteria: where the data lives, the degree of customization, integration, freedom to exit, and e-invoicing compliance as a pass condition. But behind each of these choices sits a number on the invoice, and the licence price is the smallest of them. In part five we open the real cost of an ERP beyond the licence price: implementation, data migration, training, and maintenance, and where budgets actually blow up across three years.

Sources

• Zakat, Tax and Customs Authority — E-invoicing (Fatoora) and the second phase of integration, as a condition in choosing any system: https://zatca.gov.sa
• Saudi Data and Artificial Intelligence Authority (SDAIA) — the Personal Data Protection Law and controls on data residency and transfer: https://sdaia.gov.sa
• Saudi Vision 2030 — digital transformation and enabling small and medium enterprises: https://www.vision2030.gov.sa