A shawarma chain's Nexara shift: an illustrative workflow

Where does this shawarma-chain shift start?

Picture a shawarma chain in Amman preparing for Thursday evening. The shift lead reviews the pickup menu while the phone agent confirms which branch serves each delivery address. Nexara keeps availability by branch, so a sold-out item at one location can remain available at another.

At the sandwich station, the team reads an Arabic modifier on the next ticket. Nexara supports Arabic and English tickets, with categories assigned to individual printers. The instruction belongs beside the person preparing that item, rather than on a receipt waiting at the till.

Nexara serves dozens of branches across Jordan and handles tens of thousands of orders a month. The background on Nexara and its founder explains who builds and supports the platform.

At 21:00, where do the orders go?

The example branch handles 180 orders over Thursday. That total becomes the starting point for Friday's review: the owner will inspect how those orders ended, including any cancellations or orders still awaiting action. At 21:00, the immediate job is getting each new order to the right branch.

A website pickup order arrives while an agent enters a delivery order over the phone. Both reach the intended branch's Live Orders queue, carrying their order type and current status. Nexara supports call-center orders alongside website, installable app, table QR, Talabat and Careem intake.

Updates appear on open dashboard screens. Staff move orders from confirmed to preparing, then ready for pickup or out for delivery. When the shift lead marks an item unavailable, the selected branch matters: the other locations may still have stock. Menu channels control which menu each ordering channel sees.

Talabat and Careem activation depends on partner approval. Their commissions still apply to orders they bring; Nexara charges no commission on the restaurant's own website, app and call-center orders. The Talabat and Careem order intake page covers the supported connections.

What happens between the board and the printer?

The next ticket includes an Arabic item name and a modifier. Nexara prints readable Arabic on standard ESC/POS thermal printers, with English available on the same ticket. The branch can use compatible USB or network printers through the Windows printing app.

Tickets go to printers according to branch, printer group and assigned product categories. In this example, the sandwich station receives the categories assigned to its printer, while the cashier receipt uses its own template. The kitchen reads preparation instructions; the cashier handles the customer's receipt.

Website and phone orders reach the branch board, then print at the assigned station or a configured backup.

Mid-service, the kitchen printer stops answering. The order remains on the board and the ticket waits in the branch's print queue. Staff can re-route its categories from the dashboard, or automatic failover can select a configured backup printer. A manual reprint is available when staff need another copy.

During an internet interruption, orders keep arriving in the cloud and printing catches up after reconnection. A phone hotspot beside the printer PC provides a backup connection. The kitchen printing engine guide explains routing and recovery.

A year went into Nexara's printing engine. Automatic reconnection does not print a completed ticket again. The shift lead follows the waiting tickets as the printer recovers, while the kitchen continues preparing orders from the tickets it has received.

When the phone rings, what does the agent see?

A returning caller asks for the usual delivery. The agent enters the phone number in Nexara's call-center screen. Saved addresses and past orders appear, so the agent can confirm the delivery address and read back the previous order's items.

1. Enter the caller's phone number and open the matching customer record.
2. Confirm the delivery address, including any changed building or entrance details.
3. Use the previous order as a reference and confirm today's items and modifiers.
4. Place the order in the intended branch's queue.

If the caller also reports a missing item from yesterday, the agent can log the complaint from the call screen. Unsaved-order warnings flag unfinished work when the agent switches tasks. Complaint cases support routing and escalation, so the issue can move to the person responsible for following up.

Call center is a Pro-plan feature. The call-center order-taking guide covers customer lookup and order entry. The saved record gives the agent a starting point; the caller confirms what belongs in this order.

What does the owner check on Friday morning?

At Thursday's close, the cashier records the day's net sale for reconciliation. Nexara provides End of Day and Cashier Reconciliation reports beside its order records. On Friday, the example chain's owner opens those records with the area manager.

Start with the branch's 180 Thursday orders. Filter Order History to that branch and date, then inspect cancelled orders and any still marked preparing or out for delivery. Resolve the status of unfinished records with the shift lead before using the day as a comparison for another branch.

Next, open Channels and Product by Branch to compare channel activity and product sales between locations. A branch selling fewer meal combinations gives the manager a reason to inspect its menu availability. Orders and customer records can also be exported as CSV.

Bloub, Nexara's assistant, can answer questions about channel breakdowns and branch performance from the company's own numbers, with citations. The owner can follow those citations back to the records while discussing the shift with the area manager.

The stock lead reviews branch stock requests and inventory counts. NexaraFlow's Morning Inventory and Branch Orders templates assign that work to responsible staff with schedules and stages. Managers can review overdue work and escalations. NexaraFlow is a Pro-plan feature.

What should the chain check before rollout?

Start with one branch's complete order path. Nexara's ordering link is available the day you sign up, and an existing compatible printer usually prints the same day. Give the setup session a clear finish: an order reaches the intended branch and produces a readable ticket at the right station.

1. Confirm the menu and branch availability, then place a pickup order with Arabic modifiers.
2. Inspect category routing and receipt templates on the actual kitchen and cashier printers.
3. Test the backup-printer procedure and identify who can re-route tickets.
4. Enter a returning caller with more than one saved address, confirm the selected address and inspect the resulting ticket.
5. Review branch assignments and permissions for order-taking staff and managers.
6. Open the close-of-day reports and confirm who records the cashier's net sale.

Issa Al-Dalu, Nexara's founder, answers support himself. Support runs through WhatsApp and email on Amman hours, in Arabic and English.

Nexara has a free plan, then paid plans per branch in Jordanian dinar, with current rates on request. Free and Starter include no printers; Growth includes one, and Pro supports unlimited printers.

Message Nexara's founder through the WhatsApp contact for nexaratech.io with your printer models and branch arrangement to discuss a first-branch setup.