What happens when a Talabat order reaches Nexara?
On a Thursday at 21:00, the cashier has enough on her hands. A Talabat ticket should print, not be typed twice.
Nexara is a restaurant order and operations platform built in Amman, Jordan, for restaurants and multi-branch chains in Jordan and for the Arabic-speaking Middle East. A Talabat order enters one branch queue, prints in the kitchen, and sends status updates back. Talabat approval and assisted WhatsApp setup are required.
What happens when a Talabat order arrives?
Nexara receives the Talabat order through the integration and places it in the branch's live order queue. The same board also handles call center, website, app, table QR and Careem orders. Staff can search the order in Order History and filter past orders.
The first staff action is acceptance. The restaurant confirms that it will prepare the order. Nexara records the order and sends the relevant status back through the Talabat connection. The cashier does not create a duplicate order by typing the items again.
Where does the kitchen ticket come from?
After the order enters Nexara, the branch's configured printing setup sends the order to the kitchen printer. The kitchen receives a ticket in Arabic, with English available on the same ticket. Nexara drives standard ESC/POS thermal printers over USB or a network.
Tickets wait in the print queue if the printer cannot answer. They print in order when the printer is available. Staff can re-route that printer's categories from the dashboard, or a configured backup printer can receive the ticket. If the branch connection is down, orders keep arriving in the cloud queue while the printer catches up after reconnection. The order board itself needs a connection.
The kitchen ticket prints from the order. The cashier records the day's net sale and follows the branch's normal till process.
- Talabat sends the order details once.
- Nexara places the order in the branch queue.
- The kitchen receives a printed ticket.
- Staff work from the printed ticket and live order board.
- No one retypes the customer's items into a second order.
What changes when staff start preparing?
Once the order is accepted, the branch moves it into preparation. Nexara's order statuses include confirmed and preparing. The live board shows the current status so staff can see which orders are waiting and which are being made.
Nexara does not include kitchen display screens; the kitchen works from the printed ticket and the live board. If a manager needs to check an earlier order, Order History provides search and filters for past orders.
The order remains connected to its customer record when customer information is available. Nexara customer records can include addresses and order history, helping a restaurant recognise repeat customers across its own channels and marketplace intake.
| Stage | Restaurant action | Nexara outcome |
|---|---|---|
| Arrived | pending | The order appears in the branch queue |
| Accepted | confirmed | The accepted status is recorded and sent back |
| Preparing | preparing | The live board shows preparing |
| Ready | ready_for_pickup | The order status moves to ready_for_pickup |
| Rider pickup | out_for_delivery | The order moves into delivery |
| Delivered | delivered | The order is recorded as delivered |
How do ready and delivery statuses reach Talabat?
When the kitchen finishes the order, staff mark it ready for pickup. Nexara uses the status ready_for_pickup for this point in the order. The rider can then collect the packed order from the branch.
After pickup, the order can move through out_for_delivery and delivered. Nexara records provider statuses and sends order status updates back to Talabat. Its Talabat module also supports inbound order receipt and inbound cancellation.
If Talabat cancels an order from its side, Nexara applies that inbound cancellation to the order. Staff should still follow the branch's food-safety and handover procedure for an item already being prepared.
For the full integration scope, see Talabat order intake and integration and the related guide on Talabat order integration.
What does the staff member actually type?
For the order itself, staff do not re-enter the items, modifiers or customer order details. Talabat sends the order into Nexara, and the kitchen receives a printed ticket from the order.
Staff still act at the operational points: accepting the order, preparing it, marking it ready, handing it to the rider and completing the relevant delivery status. Those actions are different from rebuilding the order manually.
Nexara keeps orders from the phone, website, app, table QR, Careem and Talabat in one queue per branch. Staff can check incoming work in one place while each channel keeps its own customer and provider rules.
- Watch the branch's live order queue.
- Accept the incoming Talabat order.
- Check the printed kitchen ticket.
- Prepare the food and update the order to preparing.
- Mark the packed order ready for pickup.
- Hand it to the rider and complete the delivery step.
How is Talabat activation handled?
Talabat activation requires partner approval. Once activated, the same menu, prices and availability can be connected to the Talabat outlet from Nexara, while orders and status updates move between the two systems. Reconciliation helps the restaurant check the connected orders. Confirm the correct Talabat outlet and menu before relying on the flow during service.
The setup path is assisted. Send founder Issa Al-Dalu, who built Nexara in Amman, a WhatsApp message with the restaurant name, branch details and Talabat outlet information. He can guide activation. Support is available in Arabic and English during Amman hours.
The platform has a free plan plus paid plans per branch in JOD. Current rates are available on request. Talabat keeps its own commission on the orders it brings; Nexara's 0% commission applies to the restaurant's own website, app and call-center orders.
If you also receive Careem orders, the Careem order flow guide covers that separate partner connection. The live order board guide explains how channels meet inside the branch queue. You can also read about Issa Al-Dalu and Nexara or use the Nexara contact page.
What to remember
- Watch one live queue for Talabat and the branch's other order channels.
- Accept, prepare, mark ready and hand over the order without retyping its items.
- Use Arabic kitchen printing, status updates, inbound cancellation and reconciliation in the Talabat flow.
- Ask Nexara's founder to guide partner activation before the branch relies on it during service.
Questions people ask
Does Nexara automatically receive Talabat orders?
Yes. After partner activation, the Talabat integration receives orders into the correct branch's live Nexara queue, where staff can accept and prepare them.
Do staff have to retype a Talabat order?
No. Talabat order details, items and modifiers arrive in Nexara, and the kitchen receives a printed ticket. Staff update the order instead of creating it again.
Does Nexara print Talabat orders in Arabic?
Yes. Nexara supports Arabic kitchen and receipt printing on standard ESC/POS thermal printers over USB or a network, with English available on the same ticket.
Can Nexara send order statuses back to Talabat?
Yes. The Talabat module records provider statuses and sends updates back through the integration, including ready_for_pickup, out_for_delivery and delivered.
What happens if the kitchen printer is unavailable?
The order remains on the board and the ticket waits in the print queue. Staff can re-route categories from the dashboard, or a configured backup printer can receive the ticket.
Does Nexara replace the restaurant's cash register?
Nexara sits beside the till as the order and operations layer. It brings orders into one queue and prints kitchen tickets, while the cashier handles the branch's normal till process and records the day's net sale.