How can an Amman deli handle a busy shift with Nexara?

What does the deli set up before service?

The deli in this walkthrough takes orders through a branded website and by phone. It uses a kitchen printer with a configured backup. That combination requires Pro: Nexara's call center is a Pro-plan feature, and Pro supports multiple printers. Nexara sits beside the till as the order and operations layer.

Before opening, the manager checks the menu's modifiers and marks unavailable products at the branch. Nexara supports modifier groups and per-branch availability. For a deli, the useful test is a sandwich with a bread choice and an extra filling: the customer must be able to select the intended combination.

The manager then places a test order and compares the submitted items with the paper ticket. Keep that printout at the preparation station during setup. It gives the cook something concrete to assess: whether quantities stand out and whether an Arabic modifier belongs visibly to the correct sandwich.

Nexara founder Issa Al-Dalu built the platform in Amman and answers support himself. A year went into the printing engine. For your setup conversation, have the printer model and a sample of your menu ready.

What happens when evening orders arrive?

A website pickup order arrives while the phone agent enters a delivery order. Both appear on the same branch order board, with their order types recorded. The shift lead checks the items and moves the orders into preparation while the cook works from the printed tickets.

Nexara also supports installable-app orders, table QR and Talabat and Careem intake. Talabat and Careem activation depends on partner approval. The table shows what to check for each channel you choose to enable.

Open dashboard screens receive live updates. Statuses include preparing and ready for pickup, so the person handing over a bag can check its progress. The Talabat and Careem order intake page explains the supported aggregator connections.

How does the ticket reach the kitchen?

Nexara printing uses a Windows PC and standard ESC/POS thermal printers connected over USB or network. Compatible existing printers can stay in use. Test from the PC that will remain at the branch during service, using the actual printer connection.

Each printer receives its assigned menu categories. Food can go to the kitchen while the cashier receives a customer receipt. Templates are assigned per printer, allowing the preparation ticket and customer receipt to use different layouts.

```mermaid flowchart LR A["Website pickup order"] --> C["Branch order board"] B["Phone delivery order"] --> C C --> D["Assigned menu categories"] D --> E["Arabic kitchen ticket"] E --> F["Cook prepares order"] ```

Website and phone orders share the branch board before assigned items print for preparation.

Arabic item names and modifiers print readably, and English can appear on the same ticket. In the deli's test, the cook checks a sandwich's Arabic modifier against the submitted order. A readable ticket at the cashier is still in the wrong place if the kitchen needs that paper to begin.

Automatic duplicate prevention stops a delivered ticket from printing again through automatic recovery. Manual reprints remain available when staff need another copy. The kitchen printing engine guide explains category routing and ticket recovery.

What if the printer or connection stops?

During the rush, the kitchen printer stops responding. The order remains on the board and its ticket waits in the print queue. Staff can re-route categories from the dashboard, or automatic failover can select a backup printer where one is configured.

Orders continue arriving in the cloud while the branch connection is down, and printing catches up after reconnection. Keep a phone hotspot beside the printer PC and test it before you need it. A paper or power fault still needs someone at the printer.

1. Before service, print an Arabic ticket with modifiers on the actual kitchen printer.
2. Confirm which categories go to the primary printer and the configured backup.
3. In a controlled test, interrupt the printer connection and inspect the waiting ticket.
4. Restore the connection and check the paper at both destinations before requesting a manual reprint.
5. Test the printer PC on the phone hotspot and confirm that printing resumes.

Assign one person to check recovered tickets. Otherwise, two staff members can each request a manual copy of the same order. Nexara's printing and connectivity FAQ covers queued tickets and recovery.

What happens when the phone rings?

A returning customer calls for delivery. The agent enters the phone number, and Nexara retrieves saved addresses and past orders when a customer record exists. The agent asks which address applies tonight and reads it back before submitting.

Order history helps the agent find the customer's usual sandwich. The agent still confirms the current quantities and modifiers, then checks pickup or delivery. A caller who usually collects may want the order sent to a different address this evening.

The call-center screen supports drafts and warns about unsaved work. If the caller raises a problem with an earlier delivery, the agent can log a complaint from the same screen rather than leave it on a loose note beside the phone.

After submission, the delivery order appears beside website orders on the branch board and its assigned items print for the kitchen. The call-center order-taking guide explains customer lookup and order entry.

What explains a discrepancy the next morning?

The deli's shift log lists 120 submitted orders, but the manager's completed-order tally is 116. The gap is 4 orders. Rather than treat that as missing business, the manager opens Orders and searches Order History for the previous evening.

In this example, checking individual records finds 3 cancelled orders and 1 delivery still marked out for delivery. That explains the count: 120 submitted minus 3 cancelled minus 1 unfinished equals 116 completed. The remaining delivery needs a staff follow-up before anyone changes its status.

Use the same branch and service hours for both checks. Then open Channels to examine where the orders came from. If a discrepancy concerns phone orders, the Call Center report is another place to investigate. These checks use the available reports and individual records; the arithmetic above is the manager's comparison.

Money needs a separate check. At close, the cashier records the day's net sale for reconciliation. Review End of Day and Cashier Reconciliation, then inspect cancelled or refunded orders where a total needs explanation. A difference in order counts alone cannot establish a cash shortage.

Reports are available in the dashboard; scheduled email reports are unavailable today. For a business adding locations, the shawarma and fast-casual chain workflow explains branch-level operations. Nexara keeps a separate live order board for each branch.