What does a shawarma chain need beside its till?

What belongs beside the till?

An agent takes a phone order while another order arrives from Talabat. Both need to reach the correct branch queue and kitchen printer without someone copying details between screens. If you are comparing “shawarma restaurant POS” products, assess that order flow separately from billing: the till and the order queue have different jobs.

Nexara puts phone, website, installable app, table QR, Talabat and Careem orders into one live queue per branch. Open dashboard screens receive live updates. Delivery, pickup and dine-in are supported order types, so staff can see how an order will leave the pass.

Keep the cash-register decision separate, including any fiscal requirements. Nexara handles incoming orders and kitchen tickets, while the cashier records the day's net sale at close for reconciliation. Nexara does not provide JoFotara e-invoicing today.

How do you assess throughput without trusting a sales claim?

Take a branch handling 240 orders a day, with 60 arriving during its busiest hour. Of those peak-hour orders, 24 come by phone. Compare total call-handling time, measured from answering the call until the order is submitted, the call ends and any associated notes are finished. An average of one order per minute can hide clustered arrivals.

An address change or complaint during an order call belongs inside total call-handling time. Record unanswered ringing separately because it occurs before the agent answers. Log complaint-only calls separately too: they occupy agents without producing an order. The table covers only the 24 calls that produce orders.

Measure total call-handling time separately from submission-to-print time and food handoff. Nexara has a Call Center report tab and records abandonment reasons. Pair those records with direct observation at the pass. Cooking capacity needs its own measurement: a faster phone desk can feed a kitchen faster than that kitchen can cook.

What should the phone agent see before confirming?

Nexara's call-center screen retrieves saved addresses and past orders when an agent enters a customer's phone number. The agent can use those records to enter a repeat order and confirm the delivery location with the caller. A regular customer may be ordering from a different address.

1. Look up the caller by phone number and confirm who is ordering.
2. Confirm the delivery address or pickup branch before entering the basket.
3. Read back the items and modifiers, especially exclusions such as no garlic.
4. Confirm the payment choice, then check that the submitted order appears in the intended branch queue.

The call-center screen includes unsaved-order warnings and complaint logging. When an agent is interrupted, the warning flags an unfinished order; complaint logging gives the agent somewhere to record the caller's problem.

The call-center order-taking guide covers the desk workflow in more detail. Staff take the calls and enter orders through Nexara's screen. Include someone who is still learning the menu when assessing whether the desk procedure is clear.

How should tickets reach each branch and station?

Each branch uses Nexara Printing with standard ESC/POS thermal printers connected by USB or network. Windows is the primary desktop setup; Linux and macOS builds are also available. Routing can use the branch, printer group and product category. Per-printer category toggles determine which items each printer receives.

For a shawarma menu, a sandwich and a drink can go to separate station printers. The branch assignment comes first; category routing then determines the station tickets. At the pass, staff bring the prepared items together for handoff.

```mermaid flowchart LR A["Phone order entry"] --> B["Branch assignment"] B --> C["Branch order queue"] C --> D["Sandwich station printing"] C --> E["Drinks station printing"] D --> F["Assembly at pass"] E --> F ``` A phone order reaches its assigned branch before station tickets guide preparation and assembly at the pass.

Arabic item names and modifiers print on ordinary thermal printers, and the same ticket can carry English. Receipt and kitchen-ticket templates are assigned per printer, so the pass and cashier can each have a layout suited to their work. Use branch and station names that staff can distinguish, especially when branches have similar printer names.

The printer category-routing guide explains the routing controls. Nexara provides printed kitchen tickets; kitchen display screens are not available today. Include that requirement in your buying checklist if your kitchen depends on screens.

What happens when the connection or printer fails?

A printer outage and an internet outage need different responses. If a printer fails, the order remains on the board and the ticket waits in a queue. Staff can re-route its categories from the dashboard, or automatic failover can use a backup printer where one is configured.

When the branch loses internet, orders keep arriving in the cloud queue and printing catches up after reconnection; the live board itself needs a connection. Keep a phone hotspot beside the printer PC as a backup.

Tickets wait in the branch's print queue and print once when the printer answers. Manual reprinting is also available. Agree how staff will mark a deliberate replacement ticket so the kitchen can recognise an order it has already started preparing.

Assign responsibility before service: the shift manager should know who checks waiting tickets and who authorises a manual reprint. Write the recovery procedure around the branch's configured backup printer and internet connection, using the acceptance results below.

What should a chain prove before rollout?

Start with a representative branch and its actual menu structure. Nexara supports modifiers and per-branch availability, so an item can be unavailable at one kitchen and still sold elsewhere. Talabat and Careem intake depends on partner approval; confirm activation before setting the rollout date.

Use one acceptance checklist with the shift manager present. Set acceptable timing targets for your operation before testing clustered orders on the proposed hardware.

Record each failure in a shared test log with the branch, order reference and time. Attach the ticket photo or screen evidence, describe the expected result, and name the person responsible for correction. Note the menu setting, equipment or staff procedure changed. Repeat the failed test and any affected routing checks; keep the new evidence beside the original failure before approving another branch.

See Talabat and Careem order intake and dispatch providers for the distinction between incoming marketplace orders and dispatching your own deliveries. Nexara charges no commission on its own website, app and call-center orders. Talabat and Careem retain their own commissions on the orders they bring; payment processing and delivery costs are separate.

Nexara has a free plan plus paid plans per branch in JOD, with current rates on request. Base the rollout scope on the branches and printing arrangements that passed acceptance.