HungerStation, Jahez, Noon Food: Nexara's integration limits

Which delivery integrations does Nexara support today?

Separate incoming marketplace orders from outgoing delivery jobs. An intake integration brings an order placed on a delivery app into Nexara. A dispatch integration sends a restaurant's own order to a courier partner for delivery. Those are different connections, even when the provider names look similar.

The supported list is not a promise of availability in every country. Talabat and Careem activation is per market and subject to partner approval. Courier coverage and branch activation also need checking before you include dispatch in a launch plan.

What do Talabat and Careem orders actually bring in?

Talabat sends incoming orders through webhooks. Nexara supports incoming cancellations, status updates back to the provider, and catalogue work with SKU and outlet mapping. Mapping matters: the provider's item identifier needs to point to the right product, and its outlet needs to point to the right branch.

Careem intake supports incoming orders and auto-accept, along with status changes, driver information, item replacements and cancellations. Nexara also supports scheduled-order handling and updates to the Careem catalogue, trading hours and availability. These are food-order functions, separate from booking a Careem Express courier.

Supported marketplace orders join the branch's live queue alongside orders from the restaurant's website, installable app, phone order screen and table QR. Open dashboard screens receive live updates. HungerStation, Jahez, Noon Food and Deliveroo orders do not join that queue through a native integration.

The guide to Talabat and Careem order intake explains how that order layer fits beside the till. Connecting intake does not remove the marketplace's commission: Talabat and Careem keep their own charges on the orders they bring.

What if HungerStation or Jahez integration is your main requirement?

If your buying requirement is automatic HungerStation, Jahez, Noon Food or Deliveroo intake, Nexara does not meet it today. Keep that requirement separate from whether you like the ordering website or Arabic printing. A useful feature elsewhere does not fix a missing connection at the counter.

Nexara has a public API for external orders, menus and webhooks. That is not evidence of a working connection to any of those apps. API access alone does not establish provider permission, correct menu mapping or reliable cancellation handling.

A provider that can demonstrate your required app connection in your market is the better pick when replacing that app's separate order workflow is the main job. Judge the demonstration by an order reaching the correct branch and by what happens when the customer cancels, not by the number of logos on a slide.

How could a Gulf restaurant use Nexara beside those apps?

Nexara is built in Amman, Jordan, and its live deployments are in Jordan today. A Gulf restaurant can evaluate its own-channel ordering and kitchen workflow without assuming local marketplace integration. The platform uses a browser, with a Windows print agent for kitchen printing; the dashboard and storefront support Arabic and English.

• Own ordering: publish a branded ordering website that customers can install from their browser as an app. Nexara takes no commission on these orders. Subscription, payment-processing and delivery costs remain separate.
• Phone orders: on Pro, the call-center screen retrieves saved addresses and past orders when an agent enters the customer's phone number. The agent places the order into the branch queue.
• Table ordering: QR dine-in starts on Growth. Guests scan the table code and order from their phones; printed tickets carry the table number.
• Kitchen tickets: the branch print agent drives standard ESC/POS thermal printers over USB or network. Printing starts on Growth, rather than being included in every plan.

In this arrangement, unsupported delivery apps keep their existing workflow. Do not assume their orders, menu changes or cancellations appear in Nexara. Write down who watches each app and how its tickets reach the kitchen. Running own-channel orders through Nexara does not make the remaining app tablets redundant.

Nexara sits beside the till as the order and operations layer. It is not a POS or cash register, and it does not provide ZATCA certification. A Saudi restaurant still needs an appropriate checkout and invoicing setup. The current Nexara feature limits cover other boundaries that matter before purchase.

What happens to Arabic tickets and a dropped connection?

For orders already in Nexara, Arabic printing does not depend on the thermal printer having an Arabic font. The print agent reshapes Arabic text and renders it as images before sending it to the printer. A ticket can carry English too, and routing can send product categories to their assigned printers.

When the branch connection drops, orders keep arriving in the cloud queue and printing catches up after reconnection. The live order board itself needs a connection. A phone hotspot beside the printer PC is a sensible backup; this is not an offline till.

If a printer fails, the ticket waits in the queue. Staff can re-route its categories from the dashboard, and automatic backup routing is available where a backup printer is configured. These printing functions do not create an intake connection for an unsupported delivery app.

What should you verify before committing a branch?

A supported integration still needs a branch-specific check. Talabat and Careem use partner APIs, and activation depends on the market and partner approval. A working demonstration for a Jordan branch is not proof that your Gulf outlet is approved.

1. Record your country and required delivery apps. Mark each as incoming marketplace orders or outgoing courier dispatch.
2. Confirm partner approval and outlet mapping for every supported intake connection you intend to use.
3. Test an order with modifiers, then a cancellation. Check the branch queue, provider status and printed ticket.
4. Print Arabic item names on your actual printer model. Test the backup procedure with the person who will use it during service.
5. Confirm the plan includes the required phone, QR, printing and dispatch functions. Keep unsupported apps outside the proposed automatic workflow.

Nexara has a free plan plus paid plans per branch in JOD, with current rates on request. Support is by WhatsApp and email on Amman hours, in Arabic and English; the founder answers.

For a fit check with Nexara at nexaratech.io, send your country, required apps and printer model through the WhatsApp button below. Start with the connections you cannot operate without.