Case study: bilingual QR ordering in Aqaba

What did the Aqaba restaurant need?

Imagine Coral Steps, a small seafood restaurant near Aqaba's waterfront. Its guests include Jordanian families, British holidaymakers, Gulf visitors and European divers. The team had one printed Arabic menu and one English menu. Staff carried the wrong version to tables, then retyped handwritten orders at the counter.

The owner wanted QR cards on the tables, a menu that guests could read without waiting for a waiter, and receipts that made sense in both languages. The restaurant also wanted card payment online where enabled, while keeping cash and pay-at-counter options for guests who preferred them.

The practical requirement was simple: one catalogue, one order path, one kitchen ticket and one record of the customer. Nexara fits beside the till as the order and operations layer. It is not a POS or a cash register.

How does one bilingual menu serve both guests?

The owner enters each product once with Arabic and English names, descriptions, prices, modifiers and availability. For example, the menu can show صيادية سمك alongside Fish Sayadieh, with the same price and the same selectable sides. When a price or availability status changes, the restaurant updates the shared menu rather than editing separate paper lists.

The storefront can open from a table QR code in a phone browser. Guests choose their language, browse the available items and send the order from their own device. The restaurant can use a Nexara subdomain or a custom domain, and the storefront can be installed from the browser as an app.

For dine-in, Nexara supports pay-at-the-table sessions and shared bills. Guests can claim their own items, so a group can divide the bill by selected dishes. Online card payment is hidden for dine-in shared bills, which keeps the table payment path clear.

What happens after a tourist scans the table?

The guest scans the code fixed to the table and selects Arabic or English. The live menu shows current availability. After the guest confirms the items, the order appears on the branch's live order board with the table number.

The kitchen receives a ticket through the branch's configured thermal printer. Nexara supports standard ESC/POS printers over USB or network. Arabic text is printed correctly, and English can appear on the same ticket. Receipts can also carry both languages.

If a printer stops answering, the ticket stays on the order board and waits in a queue. The team can re-route that printer's categories from the dashboard, or use automatic failover to a configured backup printer. The board itself needs a connection, so a phone hotspot beside the printer computer is the sensible backup.

What changed for the fictional branch?

In this illustrative example, Coral Steps has 12 tables and receives 120 dine-in orders on a busy day. Before the change, staff manually carried a bilingual menu, wrote orders on paper and retyped them at the till. The owner counted an illustrative 18 minutes of re-entry during the lunch and evening peaks.

After the QR cards were placed on the tables, guests could read the menu in their chosen language and send orders directly. The kitchen ticket included the table number and item details. In the illustrative example, re-entry fell from 18 minutes to 4 minutes across those two peaks.

Those figures describe the fictional case only. A real branch should compare its own order-entry time, cancelled items, missing modifiers and guest requests before deciding whether QR ordering is worthwhile.

What should the owner check before launch?

1. Write every item in Arabic and English. Check seafood names, allergens, portion sizes and modifiers with the kitchen.
2. Set availability by branch before printing the QR cards. A guest should not order an item that is already unavailable.
3. Create a test table and place a small QR card on it. Scan with an Arabic phone and an English phone.
4. Send one order in each language. Check the table number, modifiers, tax and receipt text.
5. Confirm the payment path. Nexara storefronts support cash on delivery or pickup, card online through HyperPay when enabled, and pay at the counter for dine-in.
6. Train the floor team to read the service board and help guests who prefer a waiter.
7. Keep a readable printed fallback menu for guests whose phones are unavailable.

QR dine-in starts on the Growth plan, while the free plan does not include QR dine-in. Nexara has a free plan plus paid plans per branch in Jordanian dinar; current rates are available on request.

Nexara is built in Amman and live deployments are in Jordan. Support is available in Arabic and English through WhatsApp and email during Amman hours, and the founder answers support questions.

How does Nexara fit beside a restaurant till?

Nexara handles the order and operations work around the cashier: the branded website, installable app, table QR orders, call-center orders, Talabat and Careem intake, menu, customer records, printing, delivery dispatch, inventory, promotions and reports. The cashier still records the day's net sale at close for reconciliation.

For a tourist-facing restaurant, the useful test is whether one order reaches the right table, branch and printer without staff translating or retyping it. Start with five tables, test both languages, then expand the QR cards after the kitchen has approved the ticket.

For the practical setup, read Nexara's guide to QR table ordering and review the Nexara printing features. The Nexara features page lists the other order and operations areas available to a branch. To discuss the setup, visit nexaratech.io or use the WhatsApp link below.