POS Systems for Retail and Restaurants in Oman: Buying a Till That Survives 2027

If you sell to people standing in front of you, the point-of-sale system is not the cash drawer. It is the place where your revenue is recorded, your stock is decremented, and — from 2027 — your tax invoice is legally issued. Choose it as a cash drawer and you will replace it within two years. Choose it as the front end of your accounting and inventory, and it may last a decade.

This article covers what a POS actually does, what changes for Omani retailers and restaurants because of e-invoicing, the differences between retail and food service that vendors gloss over, and the specific questions that separate a system you will keep from one you will regret.

The short answer

• A POS is worth buying the day your till stops telling you what sold, not the day it stops telling you how much came in.
• In Oman, the deadline that matters is 1 October 2027 for taxpayers at or below OMR 5 million in annual supplies. Retail is not exempt and is not on a later clock.
• Restaurants and retail need different systems. The overlap is smaller than the demos suggest.
• The two features nobody asks about and everybody eventually needs: offline mode and data export.

The one thing that changed for retail in 2026

Retailers have generally assumed that e-invoicing is a B2B problem — that structured electronic invoices are for companies billing other companies, and that a supermarket handing over a printed receipt is a different world.

That assumption is now wrong in Oman, and the reason is a single amendment.

Tax Authority Decision No. 189/2026 rewrote Article 143 of the VAT Executive Regulations to require tax invoices in an approved, secure electronic format. Article 143 already required that a tax invoice be issued no later than fifteen days from the date of supply, the deemed supply, or receipt of consideration in advance. The amendment also revised Article 146 so that the simplified tax invoice sits on the same timeframes as Article 143.

The simplified tax invoice is the retail instrument — the one used for supplies to non-taxable persons and for low-value supplies, subject to Tax Authority approval. Putting it on the same clock means point-of-sale invoicing is not being left behind for a later phase. It arrives with everything else.

Practically: the till you buy this year is an e-invoicing device by October 2027. Not the accounting package behind it — the till itself, or whatever it feeds within fifteen days. That is one procurement question you should put to every POS vendor, in writing, before you sign anything: what is your plan for Fawtara, and on what date will it ship? A vendor with no answer in 2026 is a vendor you will be migrating away from in 2027. The detail of what compliance actually requires is in what Fawtara requires from your systems.

There is a second, quieter obligation attached. Article 70 of the VAT Law, promulgated by Royal Decree 121/2020, requires tax invoices and accounting records to be retained for ten years after the end of the tax year in which the return was filed — fifteen for real estate. A POS whose transaction history you cannot get out of it in a readable form is a ten-year problem wearing a one-year price tag.

What a POS is actually for

Strip the marketing and there are four jobs. A system that does the first two and not the last two is a cash register.

1. Take the money. Cash, card, and whatever else you accept, reconciled to a shift and an operator.
2. Record what sold. Not the total — the line items. This is the entire difference between a till and a system.
3. Move the stock. Every sale decrements something, or the number in your inventory system is fiction by Thursday.
4. Hand the data on. To accounting, to the tax invoice, to whatever reporting you do.

Job 2 is why you buy one. A business that knows its daily takings but not its item mix cannot answer the only questions that matter: what makes money, what sits, what to reorder, what to stop stocking.

Retail and restaurants are not the same purchase

Vendors sell “POS” as one category. Operationally the two are different products, and buying the wrong one produces daily friction that never quite resolves.

	Retail	Restaurant
The unit sold	A stock item with a barcode	A recipe made of stock items
Stock movement	One-to-one, at the till	One-to-many, via recipe consumption
The transaction	Opens and closes in seconds	Stays open for an hour, with additions
Where orders originate	The counter	The table, the phone, the aggregator app
The hard part	Variants, barcodes, supplier prices	Modifiers, course timing, the kitchen display
Peak failure mode	Queue length	Wrong item to the wrong table

The two features that decide a restaurant purchase have no retail equivalent at all:

Recipe-level stock consumption. If selling one chicken shawarma does not deduct bread, chicken, garlic sauce and pickles in the quantities your recipe specifies, you have a sales report, not a food-cost system — and food cost is where restaurant margin lives or dies.

Modifiers that reach the kitchen. “No onion” has to arrive legibly at the person cooking, in the language they read. This is a genuine Arabic-and-English problem in Omani kitchens and it is worth watching a live demonstration rather than accepting a claim. The general shape of that problem is covered in building bilingual Arabic-English software.

Retail’s equivalent decider is variants. A shop selling shirts in five sizes and four colours has twenty stock items, not one, and a POS that treats them as one product with a dropdown will eventually let you sell a size you do not have.

Offline mode: the question to ask first

Almost nobody asks it during a demo, and almost everybody discovers it during a power cut or an internet outage on a Thursday evening.

Ask precisely this: when the internet is down, can I still take a sale, and what happens to it when the connection returns?

There are three honest answers, and they are not equally acceptable:

• Full offline. Sales are written locally and synchronise when connectivity returns. This is what you want.
• Read-only offline. You can see prices but cannot complete a transaction. This means closing the shop until the connection returns.
• Nothing. The screen is blank. Surprisingly common in cloud-first products, and rarely mentioned unprompted.

The follow-up matters as much as the answer: what happens to card payments offline? Card authorisation genuinely requires connectivity, so a shop with full offline POS and no offline card fallback still cannot complete most transactions. Knowing that in advance means you plan for it — a mobile hotspot on a second network, or a documented cash-only procedure — rather than improvising in front of a queue.

Hardware: the tablet question

The market splits into two shapes, and the right answer is usually not the cheaper one.

Tablet-based. A consumer tablet, a mobile app, a Bluetooth printer, a card reader. Cheap to start, quick to set up, easy to replace. It genuinely suits a small café, a market stall, a service counter. Its weakness is duty cycle: a consumer tablet used twelve hours a day in a hot room with sticky hands does not have a long life, and when it fails you are not down one component but the entire till.

Dedicated terminal. Purpose-built, sealed against spills, with a cash drawer and printer that are separate replaceable parts. Higher cost, longer life, serviceable when one part fails.

The deciding factor is transactions per day and environment, not budget. A kitchen or a busy grocery is hardware-hostile in ways an office is not. And the real cost of a failure is not the device — it is the hour you spend not selling.

One thing to insist on regardless: the printer and drawer should not be proprietary to the software. If the vendor’s own hardware is the only hardware that works, the cost of leaving them is the cost of re-equipping the shop.

Taking cards

POS and payment acceptance are sold together and are separate decisions. The system records the sale; the acquirer moves the money and takes a cut of it.

The cut is not one number. Domestic debit routed over the national network and an international scheme card carry different economics, and a terminal that routes everything through the international schemes costs you more per transaction than one with direct domestic acquiring. So the question to a POS vendor is not “do you take cards” but which acquirer, on which network, and at what rate for a domestic debit card specifically. Get that in writing with the rate, the cap if there is one, and the settlement period — the number of days between the sale and the money arriving in your account, which is a working-capital question, not a fee question.

The same terrain online is covered in payment gateways and integration in Oman.

What actually goes wrong

Four failures account for most of the regret, and none of them is about features.

Staff work around it. The commonest and most expensive. If ringing up an item takes four taps too many, staff will use a generic “miscellaneous” button, and within a month your item-level data — the reason you bought the system — is worthless. Test this by having an actual member of staff, not the owner, complete twenty sales during the trial.

The item list is never finished. A POS is only as good as its catalogue. Someone has to enter every product with its correct price, barcode, cost and category, and keep it current. Budget real time for this before go-live. Systems are usually abandoned during setup, not after it.

Nobody counts the stock. Perpetual inventory drifts. Without periodic physical counts reconciled against the system, the numbers diverge quietly until nobody trusts them, and once nobody trusts them the system is decoration. This is the same failure described in inventory systems and when a spreadsheet stops working.

The data never reaches accounting. If closing the day means someone typing yesterday’s totals into a separate package, you have bought a system and hired a human integration to go with it. Ask what the accounting export looks like and whether the destination system can read it — before you buy, not after.

Before you sign

1. What is the plan for e-invoicing, and on what date does it ship? In writing. This is the question of 2026.
2. Can I export every transaction, with line items, to a file I can open? If not, your ten-year record obligation belongs to your vendor rather than to you.
3. What happens when the internet drops? And separately, what happens to card payments.
4. Which acquirer, and what is the domestic debit rate?
5. Is the hardware standard or proprietary?
6. What does month two cost? Licence per till, per user, support, hardware replacement, payment processing. The monthly figure on the brochure is rarely the monthly figure on the statement.
7. Does it work in Arabic on the printed receipt? Not the screen — the receipt, and the kitchen ticket.
8. Who fixes it at 8pm on Thursday? Support hours that end at 5pm on a weekday are a real limitation for a retail business, not a detail.

If several of these answers are unsatisfying and no product fits, that finding is worth testing rather than acting on immediately — signs your business needs custom software sets out how to tell a genuine gap from an incomplete search.

Questions people ask

Do I need a POS if I only take cash? The payment method is not the reason to buy one. The reason is item-level records — knowing what sold rather than how much came in. A cash-only business with a hundred products has exactly the same problem as a card-accepting one.

Can I use a normal tablet as a till? Yes, and for a low-volume business it is often the right answer. The trade is durability and single-point failure. Consider what your Thursday evening looks like if the tablet dies, and whether you have a second one.

Will my POS handle e-invoicing automatically? Only if the vendor builds it. There is no automatic compliance. Because Decision 189/2026 put simplified tax invoices on the Article 143 timeframes, retail is in scope on the same dates as everyone else — 1 October 2027 for taxpayers at or below OMR 5 million in annual supplies. Ask your vendor now.

How much of a POS do I need on day one? Sales, item catalogue, and a clean export. Loyalty programmes, customer displays and advanced promotions are the features that sell systems and the features least used a year later. Buy the ones you will use in month one and confirm the others can be switched on later without a migration.

What is the penalty for getting invoicing wrong? Tax advisers report penalties in the range of OMR 500 to 5,000 for failing to issue valid tax invoices within the required timeframes. The figure is worth confirming with your own adviser against the current text, because the amounts and the article references have both moved recently.

Should the POS or the accounting system be the master of my product list? Whichever one you will actually maintain. What matters is that there is exactly one, and that the other receives from it. Two independently edited product lists diverge within weeks, and reconciling them becomes somebody’s permanent job.