Point of sale software that meets Saudi tax, payment and data rules in every region.

Devices are onboarded through ZATCA's process to obtain their cryptographic stamp identifiers. Invoices are produced as structured XML with the required QR code, unique identifier and invoice hash chain. Simplified invoices are reported, standard business invoices are cleared before issue, and credit and debit notes follow the same rules. Rejected or warning responses from the platform are logged with the exact reason, so finance can correct and resubmit.

Phase 2 has been rolled out in waves based on taxable turnover, with ZATCA notifying each group in advance. We check where your entities stand, test against ZATCA's sandbox and simulation environments, and plan onboarding so every device is live before your deadline. Certificate renewals and replaced devices are tracked centrally after go live.

The POS connects to terminals from your acquiring bank or licensed payment provider, sending amounts and receiving results automatically. We support the integration methods offered by Saudi acquirers for mada, international cards and wallets such as Apple Pay, plus tap on phone acceptance where your provider offers it. Where a group uses different banks in different regions, a single internal payment layer keeps the cashier screen identical.

Where customers want to pay through a SAMA licensed wallet or a buy now pay later provider such as Tabby or Tamara, we integrate those flows at the counter by QR code or link and record each one as a distinct payment method. Refunds follow each provider's own process and are linked back to the original invoice.

Groups with several commercial registrations or VAT numbers can run them from one back office, with each branch issuing invoices under the right entity. Regions, cities and store formats share master data but keep their own price lists, taxes where relevant and approval rules. New branches inherit settings from a template, so opening a store in a new city starts from a known baseline.

Stores on highways, in smaller towns or in buildings with poor coverage keep trading without internet. Invoices are stamped locally and queued, then reported or cleared when connectivity returns, with head office alerted to any device whose backlog grows.

Opening floats, cash drops, paid outs and blind closing counts are recorded per cashier and drawer. Variances surface to supervisors and regional managers, and shift data flows into payroll or attendance systems if you need it. Thresholds for acceptable variance can differ by store format.

Cashier screens, receipts and reports are designed in Arabic from the start with proper right to left layouts, and English is available alongside. Reports can show Hijri and Gregorian dates, which helps when planning around Ramadan and the Hajj season. Product names, modifiers and receipt lines are stored in both languages.

Customer profiles, points and purchase history are captured only with consent, with a clear purpose, retention rules and a process for access or deletion requests. Hosting and data transfer decisions are documented against SDAIA's requirements. Marketing messages respect each customer's consent choices.

Sales, VAT, payment mix and margins roll up by branch, city, region and entity, and post to your ERP or accounting platform as journals. Regional managers see their stores; executives see the whole Kingdom. Common targets include Dynamics 365, Odoo and SAP, connected through their published interfaces.