Pickup, delivery and dine-in: one order board, three different flows

What stays the same across all three order types?

Every order enters the branch's Live Orders queue, whether it came from the call center, your website or app, a table QR code, Talabat or Careem. Order type and status are available with the order, while order history lets the team search and filter past orders.

The kitchen receives a printed ticket through Nexara's printing setup. Arabic and English can appear on the same ticket, and ordinary ESC/POS thermal printers can be used over USB or a network. Tickets wait in the print queue if a printer is unavailable and can be re-routed from the dashboard or sent to a configured backup printer.

The shared flow includes statuses such as awaiting_payment, pending, confirmed, preparing, ready_for_pickup, out_for_delivery, delivered, cancelled and refunded. Their meaning depends on the order type, so the final handoff determines which status matters.

How does pickup differ from delivery?

A pickup order ends when the customer collects it from the branch. The key status is ready_for_pickup, not out_for_delivery. The ticket needs the customer's name or phone and collection details, but it does not need a delivery zone, driver assignment or courier tracking.

On Nexara's branded storefront, customers can choose cash on pickup or pay online by card when the restaurant enables HyperPay. A phone order can also use the payment choices shown to the call-center agent, including cash, card and a CliQ option stored as online.

The staff flow is short:

1. Confirm the pickup order and payment choice.
2. Print the kitchen ticket and prepare the items.
3. Move the order to ready_for_pickup.
4. Hand it to the customer and complete the collection.

A customer-facing tracking link can show pickup progress. At close, the cashier records the day's net sale so the branch can complete cash reconciliation.

What changes when the order is delivery?

Delivery has an extra handoff between the kitchen and the customer. The order may move from preparing to ready_for_pickup, then out_for_delivery and delivered. Here, ready_for_pickup means ready for the driver or courier to collect.

Delivery orders carry the address and delivery details needed for dispatch. For the restaurant's own orders, Nexara can send delivery to Careem Express, TopDeliver or Nashmi, or assign it to the restaurant's own driver. Growth includes one delivery provider, while Pro allows unlimited providers. Delivery zones can be set by radius, area or polygon.

Talabat and Careem orders enter through their respective integrations, and those platforms keep their own commissions. Nexara's 0% commission applies to the restaurant's own website, installable app and call-center orders.

The order board keeps both types together while the order type identifies the handoff before the ticket reaches the pass.

How does dine-in work differently?

Dine-in starts with a table, not a delivery address or collection time. A guest scans the table's QR code, views the branch menu and places the order from a phone. The printed ticket includes the table number, so the kitchen and service team know where the food belongs.

Nexara supports dine-in sessions with per-guest claims. Guests can claim their own items, allowing a shared bill to be split by claimed items plus tip. Cash claims hold for 45 minutes, while online claims hold for 15 minutes.

The dine-in tab is pay-at-the-table. Pay-at-counter is the dine-in-specific option alongside pay-at-the-table. Online card payment is hidden for dine-in to avoid double payment on a shared bill. The service board gives the branch a place to follow table service while the order remains visible in Live Orders.

• Pickup needs a collection status and a branch handoff.
• Delivery needs an address, dispatch and a driver handoff.
• Dine-in needs a table number, service context and a shared-bill payment flow.

The board is shared, while the ticket and final action follow the order type.

Which customer messages and tickets fit each flow?

A tokenised tracking link can show pickup progress. Use collection readiness for pickup, courier movement for delivery, and table service progress for dine-in.

Nexara does not send WhatsApp order notifications. Its WhatsApp module is a conversation inbox for call-center roles. For customer communication, use the storefront tracking link and the contact method your branch operates.

For a closer look at the shared queue, see the live order board. The order statuses explained guide covers the status names in more detail.

How should a branch set up the three flows?

Start with the branch's real handoffs, then configure the menu, printers, payment choices and delivery settings around them.

1. Confirm each channel's default order type and adjust it per branch.
2. Assign the correct order type to each channel and confirm the available statuses.
3. Set printer groups and templates so kitchen tickets include the details staff need.
4. Configure cash on delivery or pickup, card online via HyperPay when enabled, and pay at the counter for dine-in.
5. Set delivery zones and connect an available dispatch provider if the branch delivers.
6. Print a test order for each flow before the first service.
7. Train the team on the final handoff: collection, driver transfer or table service.

QR dine-in ordering is available from the Growth plan. The free plan has one branch and caps website and QR orders at 30 a month. Nexara has a free plan plus paid plans per branch in JOD; current rates are available on request.

Nexara is built in Amman and its live deployments are in Jordan. Its dashboard, storefront and printed tickets support Arabic and English. Setup information is available on Nexara features, the Nexara FAQ and the guide to QR dine-in ordering.