How to choose a restaurant POS without buying the wrong one twice

Most owners buy a POS twice. The first time for the cheapest screen that prints a receipt. The second time, a year later, after lost tickets, stock that never matches, and an accountant who still rebuilds the month in Excel.

The second purchase is the expensive one. This is how to make the first one last.

What a restaurant POS actually has to do

A sale is not a receipt. A sale should:

1. Reach the kitchen in the same second, by station.
2. Deduct the recipe from stock.
3. Post a balanced journal to the books.
4. Stay possible when the internet drops.

If any of those four are a separate product — or a promise for “phase two” — you are buying a cash register and hoping the restaurant grows around it.

Eight questions that separate a system from a terminal

Ask them in the demo. A vague answer is an answer.

The demo that actually tests the software

Do not let the salesperson ring up a water. Walk this path yourself:

• A dine-in order with two modifiers and a size change.
• A split bill across two payments.
• A void that needs a manager.
• A promo code and a service charge on the same ticket.
• A delivery assigned to a driver.
• Unplug the router for five minutes and finish a sale.

If any step becomes a phone call to support, it will become a queue on a Thursday night.

Costs that hide in the quote

The licence is rarely the bill.

• Per-device or per-branch fees that double when you add a kitchen screen.
• Payment hardware locked to one acquirer.
• Onboarding sold as a week of consultancy.
• Modules (inventory, KDS, payroll, accounting) priced after you are already live.

Write the 24-month cost: software + hardware + extra modules + the hours your manager will spend reconciling systems that do not talk.

What “Arabic-first” actually means

A translated button is not enough. You need RTL layout that does not break the ticket, receipts your cashier can read at speed, and tax / payroll rules that match the country you operate in. If the product was designed in another market and “supports Arabic”, test a full shift in Arabic before you sign.

A one-week way to decide

• Day 1: List the flows you run every day (dine-in, takeaway, delivery, split, void).
• Day 2–3: Run those flows in two demos. Same script, same person.
• Day 4: Unplug the internet in both.
• Day 5: Ask for the all-in price for two years, including kitchen and a second branch.
• Day 6: Have your accountant look at one sample day of journals and the tax report.
• Day 7: Pick the system that survived the script, not the one with the smoother slide deck.

GoSufra is built as one live database across POS, kitchen, inventory, HR, payroll and accounting — offline included — so those eight questions have a single answer rather than a stack of add-ons. Try the same script on it that you try on everything else.

The right POS is the one you are not shopping to replace next Ramadan.