Why Restaurant Technology May Win in Jordan

Why do delivery apps and restaurants end up opposed?

The conflict is structural. A delivery app wants to own the customer journey, control discovery, set commercial terms and make its marketplace useful to the customer. A restaurant wants a direct relationship, predictable costs, control over its menu and a clear view of what happens after an order is placed.

Both sides can benefit from the same order, yet they measure success differently. The app looks at marketplace activity and order completion. The restaurant also has to absorb food cost, packaging, labour, rent, refunds, mistakes and the next customer's experience.

That does not make delivery apps the enemy. They solve a real acquisition and dispatch problem. The mistake is asking one channel to become the restaurant's entire operating layer.

What fills the gap between marketplace and kitchen?

The missing layer is the restaurant's order and operations layer. It receives orders from each channel, gives the branch one working view, sends the right information to the kitchen and keeps the restaurant's own customer records connected to its own channels.

That layer should handle more than order intake. Menu availability, Arabic printing, customer lookup, delivery dispatch, inventory, promotions, feedback, complaints and branch reports all affect whether an order becomes a profitable repeat customer.

Nexara is one Jordanian example. It is built in Amman and live deployments are in Jordan today. The company is deliberately small and Jordan-first. On the platform today, tens of thousands of orders a month run through the board across dozens of branches in Jordan.

Why does ownership of the order matter?

As an illustrative example, a Jordanian ticket averaging 4 to 12 JOD can leave 25% to 30% of its value with a delivery marketplace before food, packaging, labour and delivery costs are counted. A 10 JOD marketplace order at a 25% commission leaves 7.50 JOD before those costs.

A direct website, installable app or call-center order carries 0% commission to the marketplace. The restaurant still pays its normal operating costs, including delivery where it chooses to use a courier. Talabat and Careem keep their own commission on the orders they bring. Nexara connects their order intake with the branch board.

A direct order gives the restaurant a customer record, address history and a reason to contact that customer through its own service. Nexara attaches orders to customer records and supports customer reviews, feedback calls and complaint cases.

Direct ordering also gives the restaurant a place to explain its menu in its own words. Nexara storefronts support cash on delivery or pickup, card payment online through HyperPay when enabled, and pay at the counter for dine-in. See the details of Talabat and Careem order intake.

What does the restaurant need to run this layer?

A branch needs a menu that stays accurate, a printer that produces readable tickets, a person who can resolve exceptions and a process for closing the day.

1. Put every product, modifier and price in one menu catalogue.
2. Set availability by branch and channel before service begins.
3. Connect ordinary ESC/POS thermal printers over USB or network.
4. Route kitchen, bar and cashier tickets to the correct printer groups.
5. Use the live order board for phone, website, QR, Talabat and Careem orders.
6. Review customer records, complaints and branch reports after service.

Nexara's printing engine has had a year of work behind it. Arabic lines render correctly on standard thermal printers, and English can appear on the same ticket. If a printer stops responding, the ticket stays on the board and can be re-routed from the dashboard, with automatic failover to a configured backup printer.

Can Jordan build a large food technology company this way?

A company can start by solving specific operational problems: inconsistent menus, duplicated entry, unreadable Arabic tickets, disconnected branches, lost customer context and weak follow-up.

The product opportunity is practical: Arabic and English menus, JOD pricing, Arabic thermal tickets, one queue for each channel and branch-level availability. A restaurant can check each of these during setup and service.

Nexara's honest limit is geographic maturity. It is built in Amman for restaurants and multi-branch chains in Jordan and the Arabic-speaking Middle East, but live deployments are in Jordan today. Local aggregator activation depends on the market and partner approval. Nexara does not offer JoFotara, Jahez or DHUB as live integrations today.

Nexara is a small company in Amman. A year went into the printing engine, and I, Issa Al-Dalu, answer support through WhatsApp and email on Amman hours.

What should founders and restaurant owners watch next?

Founders should watch whether restaurants will pay for control around the channels they already use. Owners should check whether a platform reduces retyping and keeps the kitchen informed without demanding new hardware.

Every Nexara restaurant storefront is orderable by AI agents that speak ACP (2026-04-17), UCP or MCP. The agent reads the live menu, receives a server-priced delivery quote, verifies an anonymous customer's Jordanian phone by SMS code, then places a cash-on-delivery or pay-at-counter order. The kitchen prints it, and the board shows an AI agent badge.

Restaurants still need a clear entity sentence, an accurate Google profile, reviews, current hours and a phone that answers. Read the full Nexara agentic commerce guide.

For the wider argument, see what a restaurant operating system means and own delivery versus aggregators.