ERP and CRM Development in Saudi Arabia: ZATCA, Arabic and What to Ask
What a custom ERP or bespoke CRM for a Saudi business has to be built around — ZATCA e-invoicing, Arabic-first screens and documents, PDPL and hosting, local integrations — and the questions to put to a developer.
Invoice first · Arabic firstFIG.01
Short answer
An ERP or CRM built for a Saudi business starts from three fixed points: invoices generated to ZATCA's e-invoicing rules with the required fields and QR code, an Arabic-first interface and documents, and personal data handled under the Personal Data Protection Law. Modules, workflows and integrations are designed around those rather than added to them afterwards.
Key takeaways
- In Saudi Arabia the invoicing module is designed first, because ZATCA's rules decide how invoices are generated, stored and reported.
- Arabic is the main language of the system and its documents, with English alongside for staff who need it.
- Customer and employee records are personal data under the PDPL, which makes hosting a design decision.
- A bespoke CRM earns its cost when selling is tied to your quotations, stock or contracts — not for a simple pipeline.
- Plan reviews and support around the Sunday-to-Thursday working week.
Businesses in Riyadh, Jeddah and Dammam ask for much the same systems as businesses anywhere: orders, stock, purchasing, a sales pipeline. What differs is the ground the system stands on. Three requirements are fixed before any workflow is discussed, and a quotation that does not mention them has not understood the project.
The service itself is described on ERP and CRM development for Saudi Arabia. This article is the checklist to read first.
The invoice comes first
VAT is charged at a standard rate of 15% and administered by ZATCA. E-invoicing, known as FATOORA, is mandatory: invoices have to be generated electronically with the required fields and a QR code, and businesses are brought into direct integration with ZATCA's platform in waves.
For an ERP that puts the invoicing data model ahead of everything else. How an invoice is numbered, what it stores, how a correction is issued and how it is reported are settled by the rules, not by preference. A system that treats invoicing as one module among many usually has that module rebuilt.
Arabic-first screens and documents
Arabic is the working language for most Saudi customers and for many of the staff who will use the system. Screens are designed right to left from the first wireframe — forms, tables, dates and numbers included — with English available alongside.
Documents matter as much as screens. Quotations, invoices, delivery notes and statements each need an Arabic layout, and confirming the language requirements for tax invoices is part of the conversation with your adviser. Ask to see an Arabic document produced by a system the developer built, not a translated screenshot.
CRM: bespoke or packaged
A packaged CRM is the right answer for a straightforward pipeline: leads, stages, follow-ups, reports. Bespoke CRM software earns its cost when selling is tied to things a package does not know about — your quotation format, your stock, contracts and renewals, or the ERP that runs the rest of the business.
Two details are specific to Saudi Arabia. Leads and replies arrive on WhatsApp and SMS more than by email, so those channels have to feed the CRM rather than sit beside it. And search has to work on Arabic names, with their spelling variations, or staff create a duplicate customer every time. CRM vs Excel covers whether you need a CRM at all.
Personal data and where it is hosted
The Personal Data Protection Law (PDPL), supervised by SDAIA, places conditions on collecting and processing personal data and on transferring it outside the Kingdom. A CRM is a database of personal data, and an ERP holds customer and employee records.
So the hosting location is decided per project with the law in mind, not by picking the cheapest region. List what personal data the system will hold before the build starts, and take legal advice where it is sensitive.
What the system has to connect to
| Connection | Common in Saudi Arabia | Why it is decided early |
|---|---|---|
| Accounting | Zoho Books, Qoyod, Wafeq | It decides whether the ERP keeps the ledger or feeds one |
| Payments | mada, STC Pay and Apple Pay through HyperPay or Moyasar | Receipts have to match invoices automatically |
| Delivery | SMSA Express, Aramex, SPL | Tracking attaches to the order |
| Marketplaces and stores | Noon, Amazon.sa, Salla, Zid | Stock sold there comes off the same count |
| Messaging | WhatsApp, SMS | It is how customers are actually reached |
If what you need is invoicing and books, a local accounting package may be the whole answer, and cheaper. A custom ERP is for the operations around it — and it can post into that package. ERP vs accounting software explains the boundary.
The working week
The Saudi week runs Sunday to Thursday. With a team that works Monday to Friday, Monday to Thursday overlap fully, so reviews belong on those days, and Sunday cover has to be arranged in the support agreement rather than assumed.
Where we stand
We deliver from Karachi, two hours ahead of Saudi Arabia, and have no office in the Kingdom. We also have no published Saudi case studies yet, and would rather say so. What we can show is the ERP work itself — for example the Sea Keepers procurement ERP, which runs operations across Pakistan, the UAE and China — and how it maps to a Saudi requirement.
Questions to ask any developer
- How does the system generate invoices to ZATCA's e-invoicing rules, and what happens when my integration wave begins?
- Is the Arabic interface designed first, and can I see Arabic documents from a system you built?
- Where will customer and employee data be hosted, and why there?
- Which accounting package and payment gateway will it connect to?
- What is delivered first, and when will it be in daily use?
- Who owns the source code, the hosting account and the data?
- Who answers on a Sunday?
The fifth question matters as much as the first: an ERP delivered one module at a time is in use sooner and fails more cheaply. The ERP implementation roadmap shows the usual order. To have these answered for your own business, send us a sample invoice and describe how an order moves.
Frequently asked questions
Does an ERP in Saudi Arabia have to support ZATCA e-invoicing?
If it issues invoices, yes. E-invoicing (FATOORA) is mandatory in Saudi Arabia: invoices are generated electronically with the required fields and a QR code, and businesses are brought into direct integration with ZATCA's platform in waves. Confirm your wave with your tax adviser.
What is bespoke CRM software?
A CRM built around one company's sales process rather than configured from a package. It is worth the cost when selling depends on your own quotation format, stock, contracts or ERP, and unnecessary when a standard pipeline of leads and follow-ups is all you need.
Should we buy a Saudi accounting package or build an ERP?
If the need is invoicing and books, a local accounting package is usually enough and cheaper. An ERP is for the operations around the accounts — orders, stock, purchasing, projects — and can post invoices into that package.
Can our ERP or CRM data be hosted outside Saudi Arabia?
It depends on the data. The PDPL places conditions on transferring personal data outside the Kingdom, so hosting is decided per project with that in mind, and sensitive data calls for legal advice.
Do you have ERP clients in Saudi Arabia?
No published case studies yet. Our ERP work is for clients in Pakistan, the UAE and elsewhere, and Saudi projects are delivered remotely from Karachi with reviews scheduled Monday to Thursday.
/Services in this article
/ERP & CRM Systems by country
Keep reading
All articlesWhat Is a Basic ERP System? The Minimum a Small Business Needs
What a basic ERP system contains, how it differs from accounting software and from a full ERP, and how to tell whether a small business needs one yet.
ERP vs Accounting Software: Which One Does Your Business Need?
The real difference between accounting software and an ERP, where an accounting package stops, the signs you have outgrown it, and why most businesses end up keeping both.
CRM vs Excel: When a Spreadsheet Stops Being Enough for Sales
An honest comparison of running sales from a spreadsheet and from a CRM — what each does well, five questions that show which you need, and how to move without losing your list.
ERP Development in the UAE: What to Get Right Before You Build
The decisions that shape an ERP project in the UAE — VAT and phased e-invoicing, English and Arabic documents, mainland and free zone entities, integrations, and where the team sits — with the questions to ask a developer.