Multi-branch restaurant management in Jordan: one menu, one screen
A price change should not become a round of calls to every branch. Neither should finding out which kitchen has stopped selling an item.
Nexara gives you a shared menu, branch-specific controls, company reports and NexaraFlow tasks in one dashboard. It is a restaurant order and operations platform built in Amman, Jordan. It sits beside your till rather than replacing it. Start by mapping your central catalogue to each branch's availability, printers and staff access.
What should head office control, and what stays local?
Central control should stop duplicate work while leaving each kitchen control over local availability. Nexara supports a franchise, company and branch hierarchy, with user-to-branch assignments and permissions. That gives the business a shared structure while preserving branch-level operating settings.
Product names belong in the shared catalogue. Whether a branch can sell that product tonight belongs in availability. Printer destinations belong to the kitchen that will prepare the order. A shortage at one branch can be handled through its availability setting while the product remains available elsewhere.
| Area | Shared control | Branch-level control |
|---|---|---|
| Menu | Products, categories and modifier groups | Item availability |
| Orders | Common dashboard and order history | One live order queue per branch |
| Printing | Receipt and kitchen-ticket templates | Printer assignments and category routing |
| Staff access | Users, roles and permissions | User-to-branch assignments |
| Daily tasks | NexaraFlow templates and schedules | Branch assignments and role-scoped queues |
The dashboard brings these controls into a common workspace. Each branch keeps its own live order queue, and staff access follows the configured roles and branch assignments.
How do you centralize the menu without hiding local shortages?
Nexara holds products, categories and modifiers in one catalogue, with menu lists and settings for which menu appears on each ordering channel. You maintain the menu centrally instead of keeping separate copies for each ordering route. Per-branch availability lets a kitchen stop selling an unavailable item while other branches continue selling it.
Separate catalogue editing from availability updates when assigning responsibility. Changing a product name changes the shared record; marking it unavailable handles a local shortage. This gives head office control of the menu while branch staff report what their kitchen can actually prepare.
Talabat and Careem catalogue push are supported. Talabat uses SKU and outlet mapping to connect catalogue items and outlets. Careem supports availability and opening-hours updates. Activation depends on partner approval, so include the connected catalogue setup in the rollout plan.
- Agree the product names and modifier groups in the central catalogue.
- Set which menus appear on which channels.
- Check availability separately for each branch.
- Verify connected catalogue mappings before accepting live orders.
The guide to one menu across ordering channels covers the shared catalogue and channel setup.
How do orders reach the right branch printer?
Nexara puts phone, website, installable app, table QR, Talabat and Careem orders into one live queue per branch. Updates are pushed to open dashboard screens. Kitchens receive printed tickets; kitchen display screens are not offered today. Call-center ordering requires Pro.
Each branch uses a desktop print agent connected to standard ESC/POS thermal printers over USB or network. Routing selects printers by branch, printer group, product category and location. Per-printer category toggles keep drinks off the hot-food printer and send each category to its preparation station.
The agent renders Arabic text as bitmap images, so printing works without Arabic fonts installed on the thermal printer. Tickets can carry Arabic and English. A branch routing test should include an Arabic item and modifier, with the physical ticket checked at the intended station.
See Talabat and Careem order intake for the distinction between incoming marketplace orders and dispatching your own deliveries.
Can managers work without access to every branch?
Nexara has named roles including company owner, area manager, branch manager and cashier, alongside operational roles such as call center and inventory manager. User-to-branch assignment works with the permissions module. For dine-in payments, waiter, cashier and branch-manager roles are bound to their own branch.
Map each person's work to a role and branch assignment. A waiter taking payment at one branch has a different access requirement from an area manager overseeing several kitchens. Individual user accounts let you configure those assignments separately.
The setup record should identify the employee's role and assigned branch, then specify the actions their job requires. Catalogue editing and local availability updates need separate consideration because they affect different parts of the operation. Nexara provides users, branch assignments and permissions for configuring that access.
The guide to branch and franchise roles explains the franchise, company and branch structure and the roles used within it.
What should restaurant chain reporting show you?
Company reporting should let you review the business together, then examine differences between branches. Nexara includes Product by Branch alongside reports for orders, channels and financial activity. End of Day and Cashier Reconciliation cover closing work; Failed Orders and Complaints support investigations into service problems.
Product by Branch is the starting point for comparing what kitchens sell. Channels shows where orders originate. Closing work has its own reports because the day's net sale and the cash counted answer different questions. The cashier records the day's net sale at close for reconciliation.
- Use Product by Branch to compare what different kitchens are selling.
- Review Channels to understand where orders originate.
- Check Failed Orders and Complaints when investigating service problems.
- Use End of Day and Cashier Reconciliation for the closing review.
Nexara supplies operational and reconciliation reports beside the till; JoFotara e-invoicing and accounting or ERP connectors are not offered today.
The companion guide to restaurant reports that matter connects report tabs to the questions owners ask during a branch review.
How do you make daily branch work visible?
NexaraFlow assigns recurring, timed work through templates, schedules and branch assignments. Tasks have stages, queues restricted by role and SLA clocks that track deadlines. Available templates include Morning Inventory and Daily Inspection. Workflows require Pro.
For a morning count, the branch assignment identifies where the task belongs and the role-scoped queue identifies who receives it. Schedules control recurrence. Managers can review task statistics and export PDFs. NexaraFlow checks SLA escalation every 5 minutes.
A rollout can begin with Morning Inventory or Daily Inspection using an existing routine. Configure its stages and schedule, assign it to the relevant branches, then check that it appears in the responsible role's task queue. This tests the same assignment mechanism that recurring work will use after launch.
Validate the central menu and staff access first, then test each branch's printing route before adding recurring tasks. Nexara has a free plan plus paid plans per branch in Jordanian dinar, with current rates on request. Branch capacity, printing requirements and Pro features determine the setup to discuss.
Message Nexara founder Issa Al-Dalu on WhatsApp through nexaratech.io to map your branch setup and request current rates.
What to remember
- Keep one catalogue, with availability controlled separately for each branch.
- Give each kitchen its own order queue and tested printer routing.
- Assign staff access by role and branch.
- Use Product by Branch to compare sales patterns and NexaraFlow to assign recurring work.
Questions people ask
Can I change the menu once for all my restaurant branches?
Yes. Nexara provides a shared catalogue, lets you choose which menu appears on each ordering channel, and supports per-branch availability. Talabat and Careem catalogue push use the connected catalogue setup.
Can one branch mark an item sold out without affecting the others?
Yes. Availability is controlled per branch, so staff can mark a local shortage while the product remains in the central catalogue.
Can I compare what sells at each branch?
Yes. Nexara includes a Product by Branch report, alongside company report tabs covering orders, channels, money and operations.
Can each kitchen use its own printers?
Yes. Each branch uses a print agent, with routing by branch, printer group, category and location. Supported thermal printers use ESC/POS over USB or network.
Does the dashboard keep working if a branch loses internet?
A backup connection, such as a phone hotspot near the printer computer, lets staff keep using the dashboard during a branch internet outage. Queued print jobs catch up when the print agent reconnects.
Can I assign opening checks to every branch?
Yes. NexaraFlow supports recurring schedules, branch assignments and task queues restricted by role, including a Daily Inspection template.