POS System in Bahrain — Bilingual, VAT-Ready at 10%, Built for Manama Retail

Bahrain's 10% VAT, and what "VAT-ready" actually means

1. 2022

   Value-added tax comes into force at 10%.

2. August 2026

   The e-invoicing framework is under development.

Bahrain has applied value-added tax at 10% since 2022, administered by the National Bureau for Revenue. As of August 2026 that is the standard rate. Confirm your own registration threshold, filing frequency, and sector treatment with the NBR at nbr.gov.bh — a software vendor is not a tax adviser, and that includes us.

This is worth spelling out because "VAT-ready" is the vaguest phrase in this category, and it is usually doing a lot of work in a sales deck. Here is the concrete version — what the system actually does, so you can check it against what you need:

VAT readiness, stated concretely

• The rate is a configuration value, not a hardcoded assumption baked into the receipt renderer. It is set on the tax profile. That is what makes a rate change an edit rather than a release.
• The tax registration number field exists on the merchant profile and prints in the receipt header when populated.
• Line-level breakdown prints in Arabic and English, so a receipt shows net, tax, and gross per line rather than a single tax figure at the foot.
• Reports separate net, tax, and gross per branch, which is the shape an accountant wants and the shape a filing needs, rather than a single consolidated number you then have to pick apart.
• Zero-rated and exempt items are handled as their own treatment, not as a 0% hack on a standard-rated product — the distinction matters on a return.

Bahrain's e-invoicing framework, as it stands

On e-invoicing: as of August 2026 Bahrain's e-invoicing framework is under development, with a voluntary phase being prepared. It is not mandatory. We are deliberately not shipping a submission-format feature against a specification that is not final, and we would treat any vendor selling you one today with some suspicion. Track the NBR's own announcements rather than a roadmap slide; when a format is published, it becomes an integration and we will say so plainly at that point rather than implying it now.

What we do not do: file on your behalf, generate a signed submission document, or connect to a government portal. Those are real capabilities and we would rather name their absence than let "VAT-ready" quietly imply them.

What POS software actually costs in Bahrain

The Bahrain results do not answer this question. The micro-sites holding the head term quote "contact us"; the reseller listings bundle software into a per-terminal hardware price so you cannot see either number. So, plainly: Sandooq is 29 US dollars per month for a single store, and 79 for up to 5 stores. Billed annually those become 24 and 66. That is the whole price.

What sits inside the published figure

Larger chains are quoted individually. Three things are worth saying out loud about that price.

• It is charged in US dollars, not Bahraini dinars, and there is no local markup. A shop in Manama pays what a shop anywhere else pays. The dinar is a strong currency and it is tempting for a vendor to quote a BHD number that is quietly above their home-market rate; we would rather show you the dollar figure and let you do the conversion yourself.
• What is included is the whole back office, not a starter tier that upsells: inventory with stock counts and transfers between branches, purchasing and supplier orders, customer accounts and on-account balances, staff permissions per branch, and the sales and closing reports your accountant needs. The plan boundary is scale — stores, staff, products — not features you discover are missing in month two.
• Hardware is yours, not ours. Sandooq runs in the browser on tablets and standard computers, works with commodity ESC/POS receipt printers and USB or Bluetooth barcode scanners, and does not require a proprietary terminal. If you already have counter hardware, the likely outcome is that it works; confirm the specific models during setup rather than taking a compatibility promise on trust.

Selling when the network drops

Bahrain's connectivity is among the best in the region, and that is exactly why this section is short and specific rather than dramatic. The failure you will actually meet is local and occasional: crowd load around a major event, or the older fabric of the souq where the signal is thinner than the map suggests. The counter experience is the same either way — a reader thinking, a queue building, a customer waiting. Here is precisely what Sandooq does and does not do about that.

What continues through a dropped connection

• What keeps working. The checkout loop: building a cart, attaching a customer, and taking a cash sale. Those are captured on the terminal and queued locally. When the connection returns the queue replays in order, with deduplication on the server, so queued sales aren't lost and nothing gets double-counted from a retry.
• What needs the network. Signing in, manager and device PIN checks, opening and closing a cash session, looking up an earlier receipt, voids, exchanges, and card payments. These are online-only by design — each one either moves money through a third party or changes control state that the server has to arbitrate between terminals.
• The practical shape of that, for a shop in a Manama mall: open the session before doors, and a drop mid-shift does not stop cash checkout. Reloading the browser tab while offline will sign the cashier out, so don't. Take card payments and process returns when the connection is back.

Causeway traffic, mixed staff, and multi-branch retail

Bahrain's retail shape is specific enough that generic Gulf POS content misses it. The market is small, which means customer relationships are closer and repeat trade is a larger share of revenue. And weekend demand arrives over the King Fahd Causeway rather than building locally, which produces a weekly peak most systems are not configured for.

The shape of Bahraini retail, and what it asks of a till

• For multi-currency counters, that Causeway flow is the whole reason it matters: you will be handed Saudi riyals and US dollars against dinar-denominated prices. Sandooq records BHD alongside both at a daily rate set centrally from the dashboard, frozen onto each transaction so later reporting uses the rate that applied at the time of sale. Receipts show the dinar total and the tendered amount separately.
• For tender tracking, cash, card-style tenders, and on-account payments are broken out separately in the daily report, so Manama and Riffa teams can reconcile the drawer and hand clean numbers to accounting. We do not name acquirer integrations that are not product-backed, and you should be sceptical of any Bahrain page that lists a wall of processor logos without saying what "supports" means.
• For retail operations, the parts that decide whether a system survives contact with a real shop are inventory accuracy and multi-branch control: barcode-driven checkout, stock counts that reconcile without closing the shop, transfers between Manama, Riffa, and Muharraq with an audit trail, and purchase orders that land back in stock levels rather than in a spreadsheet.
• On bilingual operation, which in Bahrain is an operational requirement rather than a preference: retail floors here routinely run Bahraini, Filipino, Indian, and Western staff on the same shift. Staff read the interface in whichever language they think in, switching per session without restarting. Receipts print in Arabic, English, or both depending on whether the buyer is local or visiting. A layout that reads right to left is the default the product was built around, not a mirrored afterthought.