Tourists order in English and pay by card. Is your restaurant ready?

What should a tourist see before ordering?

Your Google Business Profile should show the restaurant name, exact location, opening hours, phone number, photos, price level and a link to the current menu. Check the profile from an English-language browser and from a phone outside the branch.

The menu should use the same item names and prices in Arabic and English. Translate ingredients that affect the order, especially nuts, dairy, meat, seafood and spicy sauces. Keep the English readable rather than copying a literal translation that a visitor cannot understand.

How should English and Arabic menus stay accurate?

Start with one menu catalogue. Each item needs a name, price, description, modifier choices and availability. When a price or item changes, update the source menu before opening service. A printed tourist menu with yesterday's price creates a problem at the cashier.

Set Arabic and English names, availability by branch and the menu shown on each channel. Publish the storefront on its subdomain, or use a custom domain from the Starter plan. Visitors can install the storefront from their browser as an app. The free plan allows 20 products; paid plans allow unlimited products.

Use the same spelling everywhere. If the menu says mansaf in one place and lamb rice in another, the visitor may wonder whether these are separate dishes. Keep local names, then add a short explanation in English.

See the practical guide to Arabic and English menu translation before publishing your tourist menu.

Can QR tables capture orders from visitors?

Yes, when dine-in is enabled. A guest scans the table code, chooses items on the phone and submits the order. The ticket includes the table number, and guests can claim items when a shared bill is split. QR dine-in starts on the Growth plan.

Put the QR card where a guest can see it without moving plates or glassware. Add a short instruction in both languages, such as “Scan to view the menu and order.” Keep a staff member ready to help visitors who prefer to order by phone or at the counter.

Table QR orders join the same live order queue as website, app, call-center, Talabat and Careem orders. Tickets print in the kitchen on standard ESC/POS thermal printers.

How do card payments work for tourists?

Visitors often expect to pay by card, but the restaurant must first activate an online card provider and test the checkout. Nexara supports card checkout through HyperPay when the company enables it. HyperPay support includes 3-D Secure and refunds.

The storefront can accept cash on delivery or pickup, and pay at the counter for dine-in. A card payment is useful when the branch knows which payment status to check before preparing an order.

1. Create or confirm the restaurant's HyperPay setup.
2. Enable card payment for the relevant storefront.
3. Place a small test order before service.
4. Confirm the order status and refund path.
5. Tell staff which orders are paid online and which are pay-at-counter.

Read how to enable card payments with HyperPay for the setup sequence and the limits that apply.

What should the kitchen and cashier receive?

A tourist order should arrive with the branch, table or delivery details, item names, modifiers, payment choice and customer contact information. The kitchen needs an unambiguous ticket. The cashier needs to know whether the guest paid online or will pay at the counter.

Nexara prints Arabic and English on ordinary ESC/POS thermal printers. Tickets from the order board can be reprinted, and a ticket waits in a queue if a printer is unavailable. The branch can re-route a printer's categories from the dashboard, or use a configured backup printer.

The order board itself needs a connection. If the internet drops, orders remain in the cloud queue and the printer catches up when the connection returns. A phone hotspot beside the printer computer is the sensible backup during service.

The restaurant still closes the day's net sale at the till. Nexara provides cashier reconciliation and operational reports.

What should a Jordan restaurant check this week?

Use this short audit before the next busy service. The numbers below are an illustrative example, not a client's actual figures.

• Open the Google profile in English and verify the map pin, hours and phone number.
• Scan every table QR code from a phone that is not connected to the staff Wi-Fi.
• Order one item with an English name and one modifier, then check the kitchen ticket.
• Check that sold-out items are unavailable on the public menu.
• Print a sample receipt and kitchen ticket in Arabic and English.

Illustrative example: a branch handling 120 orders in a day could receive 20 from its own website or table QR channel. If the menu, payment path and kitchen ticket are ready, those orders can be handled without a phone call or manual re-entry. The example shows a check to run, not a Nexara result.

Nexara is built in Amman and live deployments are in Jordan today. It offers a free plan plus paid plans per branch in JOD; current rates are available on request. HyperPay, Talabat and Careem activation depends on the relevant setup and partner approval. Issa Al-Dalu founded Nexara in Amman and answers support.