A Riyadh distributor wants its salesmen to book orders in a browser. A Jeddah clinic group wants patients to book and pay online. Both need a web application, not a website: software that people log into and work in every day. Before anyone draws a screen, a few decisions shape the whole project.
What is the difference between a website and a web application?
A website mostly shows information and collects enquiries. A web application handles work: logins, roles, records, approvals, payments and reports. That makes it closer to an ERP or CRM than to a brochure site, and it should be planned that way. Our website development guide for Saudi Arabia covers the simpler case.
Who are the users, and in which language?
List every role: staff, managers, customers, suppliers. Decide which language each one works in. Arabic is the main language in the Kingdom and is laid out right to left, which changes navigation, tables, forms, number entry and printed documents. Designing both directions from the first screen costs far less than flipping an English app later. Our guide to Arabic and English websites explains the details.
Does it issue invoices?
If the application sells or bills, ZATCA's e-invoicing rules (FATOORA) apply: invoices are issued electronically with a QR code, and businesses are brought into integration with ZATCA's platform in waves. VAT is 15%. Decide early whether the app issues invoices itself or passes sales to an accounting system that already does. Confirm your obligations and timing with your tax adviser. Our guide to ERP software in Saudi Arabia covers the same question for back-office systems.
What else must be decided first?
| Decision | Options | Why it matters |
|---|---|---|
| Payments | mada, STC Pay, Apple Pay, cards | Each needs a provider and changes the checkout flow |
| Personal data | Where it is stored and who can see it | The PDPL governs personal data; confirm specifics with a lawyer |
| Devices | Desktop, phone browser, or both | Field staff work on phones; offices on screens |
| Integrations | Accounting, ERP, delivery, SMS, WhatsApp | Each connection adds work and testing |
| Support hours | Sunday to Thursday cover | Problems must be answered in your working week |
How should the build run?
Discovery
Map users, workflows, invoices, payments and data rules into a written scope.
Design both languages
Approve Arabic and English screens before any building starts.
Build in releases
Ship the core workflow first and test it with real users.
Connect the outside systems
Add payments, invoicing and integrations one at a time, each tested.
Train and support
Train each role and agree support hours that match your working week.
Can Operix build it from Karachi?
Yes, remotely. Karachi is two hours ahead of Riyadh, so calls fit the working day. We have no office in Saudi Arabia and no published Saudi project yet, and we say that upfront. Read about our web development for Saudi Arabia, compare contract options, then contact us with your scope.
Questions people ask
Does a Saudi web application have to be in Arabic?
Not always, but most customer-facing apps should offer Arabic, and staff apps often need it too. Plan both languages from the first design so right-to-left layouts work properly.
Does my web app need ZATCA e-invoicing?
If it issues invoices to customers, it likely does, either itself or through connected accounting software. The rules and integration timing depend on your business, so confirm with your tax adviser.
Which payment methods should a Saudi app accept?
mada is the local debit network and should usually be included. STC Pay, Apple Pay and cards are also common. The payment provider you choose decides which methods are available.
Can an offshore team build a Saudi web application?
Yes, if the team plans Arabic, e-invoicing and data rules from the start and offers support in your working week. Ask for a small paid first phase to test the fit.
