How to choose POS software in the Gulf: shops and restaurants

Start with the failure case

The question that separates a Gulf POS from a demo is not what it does on a good day. It is what happens at seven o’clock on a Thursday when the line reaches the door and the connection drops.

An offline-first till keeps the catalogue, prices, open bills and the current cash session on the device. It sells, prints the receipt and the kitchen ticket, and opens the drawer with no network at all, then queues the sale and syncs it later — after which it posts through the same stock, cash-session and accounting flow as any online sale. There is one set of books, not an offline pile to reconcile on Saturday.

Most cloud products describe themselves as working offline and mean something weaker: a read-only cache, a small queue, or a degraded mode where discounts and returns stop working. The distinction is worth an article of its own — offline POS: why your till should work without internet — and the test in a demo is one sentence long: disconnect the network now, and sell me something.

VAT-inclusive shelf prices, tax still split

Gulf retail prices are shown inclusive of VAT. A shopper expects a round number on the shelf and the same number on the receipt. Your accountant expects the tax portion in its own ledger.

Both are satisfiable, and the requirement is precise: pricing inclusive or exclusive should be a setting per price list, and the settlement must post a balanced double-entry voucher with the tax split out regardless. If the POS calculates tax for display but the accounting is done later from a daily total, the tax summary and the trial balance will not agree, and you will find out during a filing.

Rates differ by state, and country defaults should ship ready rather than being typed in by an implementer.

Rates as of September 2026; they change, and your accountant confirms what applies to you. Note also the three-decimal currencies: the Kuwaiti and Bahraini dinar and the Omani rial use three decimal places, and a till that rounds them to two produces a real cash variance by the end of the day. Ring up a three-decimal amount on any system you are shown — ours included — and compare the printed receipt with the posted voucher before you buy.

If you run outlets in more than one state, see the multi-country GCC guide — different rates per branch, one set of books.

Receipts people can read

A receipt in the Gulf is read by an Arabic-speaking customer and, when it comes back as a return or an expense claim, by an English-speaking accountant. The right answer is paired Arabic and English labels on one printed receipt, from the same template system as your invoices and quotations, so a bilingual policy applies to everything rather than to the tax invoice alone. Branding should be configurable per branch, so each outlet’s receipt is its own without maintaining separate templates. The bilingual documents guide has the print test.

Counters, cash sessions and branches

Three practical requirements that owners tend to raise only after the first bad month:

• Cash sessions per counter. Open with a float, record the day’s tenders, close with a count and a variance that someone signs for. Without sessions, a shortfall is an argument rather than a number.
• Branch scoping enforced by the platform itself. Each outlet sees its own sales; head office reads across all of them and compares. A dropdown filter is not scoping.
• Sessions that survive a restart. A power cut should not log the device out of your business. The till stays signed in, each cashier unlocks with their own PIN, and permissions follow the person whether the device is online or not.

Restaurants: the kitchen is the other half

A restaurant POS is a different product from a retail till, not a retail till with a menu. Kitchen order tickets must route to the right station — grill, bar, cold section — from the item’s own configuration, and must keep routing when the network is down, because that is exactly when a floor falls apart. Tables, several bills on one table, and modifiers as structured data rather than free text are the rest of the shape.

Retail counters want the opposite emphasis: barcode scanning at speed, multiple barcodes and pack sizes on one product, and a shelf price that matches the receipt. Flowyana’s POS ships as two editions, retail and restaurant, against the same stock and accounts. There are twelve restaurant-specific questions in how to choose restaurant POS software.

What not to assume

This is where Gulf POS buying goes wrong most often. Delivery-aggregator integrations, online ordering, and loyalty programmes are assumed from a logo on a website or a line on a feature grid, and turn out to be a roadmap item, a third-party connector you pay for separately, or a manual re-keying job. The same applies to e-invoicing: mandates and filing formats differ by country and are changing across the region right now.

So ask, in writing, of every vendor: which aggregators, under what contract, live today, and what happens when one of them changes its interface? And apply it to us — Flowyana claims no delivery-aggregator integration, no online ordering, no loyalty programme, and no e-invoicing clearance integration. We would rather be plainly out of scope than let an assumption close a sale.

The demo, in ten minutes

1. Pull the network cable. Sell, discount, print a receipt, open the drawer, fire a kitchen ticket.
2. Restart the device, still offline. Is the cashier still signed in?
3. Reconnect. Show the stock movement, the cash-session line, and the accounting voucher with tax split.
4. Show a shelf price inclusive of VAT and the same sale posted with the tax separated.
5. Print a receipt with paired Arabic and English labels, branded for that outlet.
6. Close the cash session with a deliberate variance. Read the report.

To run those six against Flowyana on your own catalogue, book a demo.