POS System in Saudi Arabia: ZATCA Requirements, Features and How to Choose

A POS system in Saudi Arabia is the software and hardware a business uses to record sales, take payment and issue receipts. Because those receipts are simplified tax invoices, the POS must also meet ZATCA e-invoicing rules: each receipt carries a QR code and cryptographic stamp, and is reported to ZATCA's Fatoora platform within 24 hours.

This guide is for retail, restaurant and service business owners choosing or replacing a point-of-sale system. It covers what ZATCA requires from a POS as of October 2026, the features that matter in the Saudi market, cloud versus on-premise deployment, off-the-shelf versus custom POS, and how to connect POS to your ERP and online store.

What is a POS system?

A point-of-sale (POS) system is where a sale is completed. Modern POS combines several parts:

• POS software that holds the product catalogue, prices, discounts, taxes and users.
• Hardware: a tablet, touchscreen terminal or handheld device, receipt printer, barcode scanner and cash drawer.
• A payment terminal that accepts mada, credit cards and mobile wallets.
• A back office for inventory, branches, staff, reports and integrations with accounting, ERP and e-commerce.

In Saudi Arabia the POS is also a tax system. Every receipt it prints is a simplified tax invoice under the VAT rules, which puts the POS squarely inside ZATCA's e-invoicing programme.

What does ZATCA require from a POS system?

Simplified tax invoices and the 24-hour rule

Sales to consumers (B2C) are documented with simplified tax invoices. Under Phase 2 of e-invoicing, these are not cleared by ZATCA in advance. Instead, the POS issues the invoice to the customer immediately and must report it to Fatoora within 24 hours of issuance, according to ZATCA's E-Invoicing Detailed Guideline. If a business customer asks for a full tax invoice with its VAT number, that invoice must go through clearance before it is handed over, so a POS used for trade customers needs both flows.

QR code and cryptographic stamp on every receipt

Since Phase 1 (4 December 2021), simplified invoices must carry a QR code. In Phase 2, the QR code expands to nine data tags, including the invoice hash, the digital signature and the public key, and the POS signs every invoice with a cryptographic stamp. Each invoice also carries a unique identifier (UUID), a counter value and the hash of the previous invoice, creating a tamper-evident chain.

Every invoicing device is an EGS unit

ZATCA calls each system that generates invoices an e-invoice generation solution (EGS) unit. Each unit is onboarded on the Fatoora portal with a one-time password and receives its own cryptographic stamp identifier (CSID). In practice:

• If each till generates and stamps invoices itself, each till needs its own CSID.
• If tills send sales to a central server that generates and stamps the invoices, the server is the EGS unit.

This architectural choice determines how many certificates you must issue, secure and renew across branches.

Functions a POS must not have

ZATCA prohibits functions that allow tampering. A compliant POS must not allow:

• Editing or deleting an issued invoice. Voids and returns are handled with credit notes.
• Changing the device date or time used on invoices.
• Multiple invoice sequences or resetting counters on the same unit.
• Anonymous access, default passwords or users without activity logs.
• Exporting the private key used for the cryptographic stamp.

When does Phase 2 apply to my POS?

Phase 2 applies from the date in your wave notification. ZATCA's Wave 25 announcement of 24 July 2026 covers taxpayers whose VAT-able revenue exceeded SAR 187,500 in any year from 2022 to 2025, with integration due by 1 February 2027. For most VAT-registered shops, cafes and clinics, the question is no longer whether the POS must integrate, but whether it will be ready in time. Our e-invoicing guide for Saudi Arabia lists every wave and deadline.

What features should a POS system in Saudi Arabia have?

• Arabic interface and bilingual receipts. The human-readable invoice must be in Arabic; English can sit alongside it. Check right-to-left layout on the screen, the printer and digital receipts.
• Correct 15% VAT handling. VAT-inclusive pricing, rounding, zero-rated and exempt items, and line-level discounts that recalculate VAT correctly.
• Local payment methods. Integrated terminals for mada, Visa and Mastercard, plus Apple Pay, STC Pay and buy-now-pay-later options where your customers expect them. Integration removes manual amount entry and reconciliation errors.
• Inventory management. Real-time stock by branch, purchase orders, transfers, batch and expiry tracking for food and pharmacy, and variants for fashion.
• Multi-branch control. Central price lists and menus, branch-level permissions and consolidated reporting.
• Offline mode. The ability to keep selling, issuing stamped invoices and printing QR codes when the internet drops, then report automatically on reconnection.
• Roles and audit trail. Per-user logins, approval for refunds and discounts, and a full log of actions.
• Integrations. APIs or connectors for ERP or accounting, e-commerce platforms, delivery apps and loyalty programmes.
• Sector features. Kitchen display and table management for restaurants, appointments for salons and clinics, weighing scales for groceries.

How does offline mode work under ZATCA rules?

Because simplified invoices are reported rather than cleared, a POS can legitimately complete a sale without a live connection to ZATCA. A well-built offline mode generates the XML, applies the device's cryptographic stamp, prints the QR code and stores the invoice in a local queue. When the connection returns, the queue is reported to Fatoora automatically, oldest first. The risk is the 24-hour window: if a device stays offline longer, or a device fails, ZATCA's guideline expects the taxpayer to notify it through the e-invoicing failure notification service. Your POS should therefore alert managers to unreported invoices well before 24 hours pass.

Cloud POS vs on-premise POS: which is better?

Factor	Cloud POS	On-premise POS
Set-up	Fast; subscription, runs on tablets	Slower; local servers and installation
Cost profile	Recurring monthly or annual fees per device or branch	Larger upfront licence and hardware cost, lower recurring fees
Multi-branch reporting	Real time by default	Requires synchronisation between sites
ZATCA updates	Applied centrally by the vendor	Your team or vendor must patch each installation
Offline resilience	Depends on the quality of the offline mode	Strong locally, weaker for central visibility
Data location and control	Depends on the vendor's hosting; check where data is stored	Full control on your own infrastructure

Most single-site and growing multi-branch businesses choose cloud POS. On-premise or private-cloud POS still makes sense for large chains with strict data-control policies, complex integrations or high transaction volumes. Whichever you pick, customer data such as names, phone numbers and loyalty history falls under the Personal Data Protection Law (PDPL), so ask vendors how they host and protect it.

Off-the-shelf POS vs custom POS

The Saudi market has mature off-the-shelf options, including Saudi-built cloud platforms for food service and retail, regional accounting suites with POS modules, and international POS products with Saudi localisation. A custom POS, or a custom layer on top of an existing one, is built around your own processes.

Factor	Off-the-shelf POS	Custom POS
Time to launch	Days to weeks	Months, depending on scope
Upfront cost	Low; mostly subscription	Higher; development investment
Fit to workflows	Standard workflows; you adapt to the product	Built around your pricing, loyalty, approvals and operations
ZATCA compliance	Vendor responsibility; verify Phase 2 readiness	Your responsibility; must be engineered and maintained
Integrations	Limited to the vendor's connectors and API	Any system, including legacy ERP and in-house apps
Ownership	Vendor owns the roadmap and data platform	You own the code, data model and roadmap

A useful rule: if a standard product covers about 80% of your needs, buy it and integrate the rest. If your differentiator lives in the checkout, such as complex pricing, a franchise model, a membership scheme or unusual fulfilment, custom or hybrid development usually pays back.

How should a POS integrate with ERP and e-commerce?

POS rarely works alone. The goal is a single version of stock, prices, customers and revenue across every channel:

• POS to ERP or accounting: daily or real-time posting of sales, VAT, payments by method and cost of goods sold, plus purchase orders and stock transfers flowing back. See our ERP guide for Saudi Arabia.
• POS to e-commerce: shared inventory with your Salla, Zid or custom online store, so stock sold in-store is not sold again online. Our comparison of Salla, Zid and custom stores covers the online side.
• Delivery apps and loyalty: orders from aggregator apps landing directly on the POS or kitchen screen, and one customer profile for loyalty across channels.
• Central e-invoicing: when POS, online store and ERP all issue invoices, a central e-invoicing service keeps numbering, stamping and reporting consistent. Our ZATCA e-invoicing integration work focuses on exactly this.

How do you choose a POS system in Saudi Arabia?

1. List your invoice scenarios: walk-in sales, trade customers needing full tax invoices, returns, deposits, gift cards, delivery orders.
2. Verify Phase 2 readiness: ask the vendor to demonstrate onboarding, stamping, the nine-tag QR code, reporting and credit notes in ZATCA's simulation environment. ZATCA's solution providers directory is indicative only, so test rather than assume.
3. Test offline mode: disconnect the internet, sell, reconnect and confirm invoices report automatically.
4. Check payments: confirm integrated mada and wallet acceptance with your acquiring bank.
5. Review integrations: ERP, accounting, e-commerce and delivery apps; ask for API documentation.
6. Assess data protection: hosting location, access controls and PDPL alignment.
7. Model total cost over three to five years: licences, devices, payment fees, integrations, support and future branches.
8. Run a pilot in one branch before rolling out.

What drives the cost of a POS system?

Costs vary widely between vendors and scopes, so compare on drivers rather than headline prices: the number of devices and branches, subscription tier, payment processing fees, hardware, the number and complexity of integrations, data migration from an old system, custom features, training, and ongoing support and compliance updates. For custom builds, the biggest drivers are workflow complexity, offline requirements and integrations with legacy systems.

Next step

If you need a POS that fits your operations, connects to your ERP and stays ZATCA-compliant as rules evolve, Amwaj Solutions designs and builds custom and integrated systems through our ERP and custom software service. Request a consultation and we will respond within 24 to 48 business hours.