The live order board: every channel, one queue, one status

What belongs in one restaurant order management screen?

A delivery app shows the orders it brings. Your website receives orders separately, but the same kitchen prepares both. A branch queue brings that incoming work together so the cashier can follow orders across supported channels.

Nexara calls this screen Live Orders. It receives orders from the call center, branded website and installable app, table QR, Talabat and Careem. Updates appear on open dashboard screens without staff repeatedly refreshing the page.

Each branch has its own queue. Order type is separate from source: Nexara supports delivery, pickup and dine-in. A website order can be for pickup; a phone order can be for delivery. Staff need the order type to arrange the handover, whichever channel brought the customer.

The shared queue gives staff a common set of statuses. The handover still follows the order type: a pickup customer collects at the restaurant, while a delivery order needs a driver.

How should staff read statuses and order age?

Nexara supports the nine statuses below. Use them to record what has happened to the order, with the checks in the second column as a suggested staff routine.

For an order that seems late, check its current status and speak to the station responsible. Before comparing waiting times across orders, agree which event your team measures from. That keeps a payment delay and a cooking delay from being treated as the same problem.

Use Order History to find an earlier order through search and filters. Keep Live Orders open for incoming work while another staff member investigates a past handover or cancellation.

What does the cashier do with the queue?

Assign someone to watch incoming orders during service and agree who reports preparation and readiness. Nexara records statuses; the person watching the queue needs a clear handoff with the person running the pass.

1. Read the incoming order and its type before promising a handover. For phone orders, Call Center retrieves saved addresses and past orders by phone number.
2. Check that the kitchen received its ticket. If work has stalled, speak to the responsible station before changing the recorded status.
3. Mark an order ready for pickup when the packed food is ready to leave the pass.
4. Log a caller's complaint directly from the call screen, then use Order History to investigate the earlier order while someone watches new arrivals.

Call Center also includes a blacklist and warnings about unsaved orders. These help the agent handle the phone order itself, while the branch queue carries the placed order into service.

At close, the cashier records the day's net sale for reconciliation in Nexara's Cashier Reconciliation report tab. The guide to restaurant reports that matter explains how order review and end-of-day checks fit together.

What does the kitchen see, and what does printed mean?

Each printer receives only the menu categories enabled for it. Nexara routes printing by branch and printer group, with product-category routing. A station gets the items it is responsible for preparing.

Kitchen work arrives on printed tickets through Nexara Printing on the branch PC; Nexara does not offer kitchen display screens today. Standard ESC/POS thermal printers connect over USB or network. Tickets can carry Arabic and English together, and table QR tickets carry the table number. The ticket gives the kitchen its instruction; staff record Preparing after the station confirms work has started.

If a printer fails, the order stays on the board and its ticket waits in a queue. Staff can reroute categories from the dashboard, or use automatic failover to a backup printer where one is configured. Manual reprinting is also available. The kitchen printing engine explains routing and recovery.

During a branch internet outage, orders continue arriving in the cloud queue and printing catches up after reconnection. Keep a phone hotspot beside the printer PC as a backup connection.

Which delivery apps feed the queue?

Talabat and Careem feed Nexara's branch queue alongside the restaurant's own ordering channels. Talabat intake includes incoming cancellations and status exchange. Careem intake also handles driver information, item replacements and scheduled orders. Activation depends on partner approval.

If you are looking for one screen for all delivery apps, match your actual channels against that list. Nexara does not offer Jahez, DHUB or Deliveroo today. The Talabat and Careem order intake guide covers the supported marketplace connections.

For orders placed directly with your restaurant, Nexara supports dispatch through Careem Express, TopDeliver and Nashmi. Staff can book, track and cancel a delivery from the order.

Talabat and Careem keep their own commission on the orders they bring. Nexara charges no commission on your website, app and call-center orders.

WhatsApp is a conversation inbox for call-center roles, with chat history and lookup by phone; it does not send order notifications. Customers can follow an order through a private customer-facing tracking link.

What should a branch walkthrough demonstrate?

Follow an order from arrival in Live Orders to its kitchen ticket, then find it again in Order History. Use a channel your branch actually runs and compare the printed items with the categories assigned to that station.

Include a controlled printer interruption. Watch the ticket wait in the queue, reroute the affected categories, and check the paper at the receiving station. This tests the handoff your staff will depend on during service.

Match the demonstration to the plan. Call Center requires Pro. QR dine-in and kitchen printing start on Growth, which allows one printer; Pro allows unlimited printers. Count the stations that need separate tickets before choosing the setup.

Founder Issa Al-Dalu answers Nexara support himself, in Arabic or English on Amman hours. Have your ordering channels and printer models ready for the conversation so it starts with your branch's actual setup.