Running 5 branches in Amman from one dashboard
Five branch managers send you five different versions of the same Thursday. You need to see which kitchen has waiting orders and who still owes a customer a call.
Nexara lets you see each branch's orders and unfinished work, with shared menus and reporting in one dashboard. It is a restaurant order and operations platform built in Amman, Jordan, sitting beside your till. The board requires an internet connection. Start by assigning branch responsibilities and testing each kitchen's ticket routing.
Figures in this post are illustrative examples, not a client's actual results.
08:30: Who owns each branch's opening checks?
Picture a restaurant with branches in Sweifieh, Khalda, Shmeisani, Jubeiha and Abdoun. You start the morning away from all of them. Before looking at sales, establish who owns today's opening work and which branch each person belongs to.
Nexara supports user-to-branch assignments and permissions, with roles including area manager and branch manager. NexaraFlow supports recurring tasks assigned by branch and role, with schedules, stages and escalation clocks. Workflows are a Pro-plan feature.
| Illustrative branch | Morning check | What the owner should establish |
|---|---|---|
| Sweifieh | Morning inventory | Whether the count is complete before prep decisions |
| Khalda | Daily inspection | Which unfinished inspection needs a manager's attention |
| Shmeisani | Branch stock request | What stock the branch is asking for |
| Jubeiha | Kitchen printer test | Whether the intended kitchen receives the ticket |
| Abdoun | Open complaint review | Who owns the next customer follow-up |
Use this as a management checklist. A named person counts stock and checks the printed ticket, then records the work as complete. The multi-branch restaurant management guide covers the wider branch setup.
11:00: How do you change availability for just one branch?
Khalda runs out of a sandwich filling while Sweifieh still has stock. The correct response is a Khalda availability change, not removing the sandwich from the whole business.
Nexara has a shared catalogue with products, modifiers and menu lists, plus per-branch availability. Menu channels control which channel sees which menu. Talabat and Careem catalogue push is supported, with mapping needed between your catalogue and the provider's items.
- Confirm whether the shortage belongs to one branch or the whole company.
- Change availability for the affected branch rather than deleting the product.
- For a planned price change, update the shared catalogue and check the affected channel menus.
- Verify the customer-facing item and its modifiers on the relevant ordering channel.
Check outlet and item mapping when verifying an external listing. The branch receiving the order must match the branch whose menu you changed. The Talabat and Careem order intake details explain those connections; activation depends on partner approval.
13:30: Keep each kitchen's orders and printers separate
One dashboard does not mean one undifferentiated queue for the entire chain. Nexara brings phone, website, installable app, table QR, Talabat and Careem orders into one live queue per branch. Open screens receive live order updates.
These two example branches show how each channel's orders reach the assigned branch queue and its kitchen printer.
Each branch uses Nexara Printing on a Windows PC. Standard ESC/POS thermal printers connect over USB or network. Routing considers the branch and printer group, and category controls let a printer receive only its assigned categories. Kitchen tickets print in Arabic, with English available on the same ticket.
In this example, test Jubeiha's food and drink categories before lunch. Confirm both the destination and the ticket contents. A ticket printed successfully at the cashier is not evidence that the kitchen received its copy.
If a printer fails, the ticket waits in a queue. You can re-route its categories from the dashboard, or use automatic failover where a backup printer is configured. If branch internet drops, orders continue arriving in the cloud queue. Keep a phone hotspot beside the printer PC as a backup.
16:00: Who acts when a branch task becomes overdue?
Shmeisani has requested stock, but the afternoon inspection is still unfinished. Calling the branch may resolve today's issue. A repeatable task makes tomorrow's responsibility clearer.
NexaraFlow provides templates, schedules and branch assignments, with task lists organised by role. Available task templates include Morning Inventory for stock counts, Daily Inspection for branch checks and Branch Orders for stock requests. Tasks can move through stages with SLA clocks and escalation.
Set a deadline that reflects the actual work. An opening count due after the lunch rush cannot help the kitchen prepare for lunch. Decide which role performs the check and who receives an escalation if it is late.
Managers can review unfinished tasks and their SLA clocks in NexaraFlow, with overdue work escalated to the designated role. The manager assigned to that escalation is responsible for following up with the branch and checking completion. The NexaraFlow timed tasks guide explains how to organise that routine.
19:30: How do you keep a complaint from being forgotten?
An Abdoun customer calls about a missing item. The call-center agent should not have to reconstruct the order from messages forwarded between managers.
Nexara's call-center screen looks up saved customer addresses and past orders by phone number, and supports complaint logging. The call center is a Pro-plan feature. Feedback-call tasks can also be populated from delivered orders, with item summaries for the person making the follow-up call.
Complaint cases support photos, SLA minutes and a routing ladder, with linked workflow tasks. Case statuses include open, breached, escalated and resolved. These give the owner a specific case to inspect rather than a verbal assurance that someone is handling it.
For this complaint, agree on the next customer contact and check the case again after that contact. Staff decide whether to replace the missing item or arrange a refund, then record what happened so the next person handling the case has the full account.
23:00: Which reports should you check at close?
At close, use the same reporting period for every branch. A lunch-only view for one location and a full-day view for another will send you after the wrong problem.
Nexara has report tabs across orders, products, customers, channels, delivery, money and operations. Product by Branch helps examine product performance across locations. Complaints and Failed Orders provide different checks from the Financial report.
- Use Product by Branch to investigate whether the unavailable sandwich affected Khalda's product mix.
- Review Failed Orders and order history before attributing a weak result to low demand.
- Check complaint cases for unresolved service work that must carry into tomorrow.
- Review End of Day for each branch. Then use Cashier Reconciliation with the cashier's recorded net sale to investigate closing differences.
Have the cashier record the day's net sale at close so you have a figure to reconcile. The restaurant reports that matter guide explains which reports to use for the daily review.
Nexara has a free plan plus paid plans per branch in JOD, with current rates on request.
To assess your five-branch setup, start a WhatsApp conversation with Issa Al-Dalu, founder of Nexara at nexaratech.io. Send your branch locations and printer models so you can discuss ticket routing and branch responsibilities together.
What to remember
- Keep orders and printer routing specific to each branch.
- Use shared menus with local availability changes.
- Assign recurring work and complaint follow-up to clear owners.
- Compare the same reporting periods before deciding which branch needs help.
Questions people ask
Can I manage five restaurant branches remotely with Nexara?
You can manage branch assignments, menus, reporting and timed tasks through the dashboard. Each branch keeps its own live order queue, and staff on site still handle physical checks and kitchen work.
Can one branch mark an item unavailable without affecting the others?
Yes. Nexara supports per-branch availability, so a shortage at one location does not require removing the product across the company.
Will orders print in the right branch's kitchen?
Yes, when branch routing, printer groups and category assignments are configured correctly; verify them with a test ticket at each location.
What happens if one branch loses its internet connection?
The affected branch's printing catches up when its connection returns.
Can I see which branch tasks are overdue?
NexaraFlow provides timed tasks with branch assignments, task lists by role and escalation. Managers can review unfinished work and follow up with the assigned staff.
Does Nexara send the closing reports by email automatically?
Nexara does not offer scheduled email reports. Use the dashboard's report tabs for your closing review.