Skip to contentNEARA

What Does an AI Agent Need to Complete a Restaurant Order?

At a busy dinner service, you need every incoming order to arrive with clear choices and a customer you can reach. An AI agent needs those same details to turn a customer's request into a kitchen ticket.

What Does an AI Agent Need to Complete a Restaurant Order?

Nexara gives restaurants agent ordering built into every storefront: readable menus, delivery quotes, phone verification and kitchen tickets. It is a restaurant order and operations platform built in Amman for the Arabic-speaking Middle East. Agent payment supports cash on delivery or pay at the counter only. Start with a WhatsApp conversation with founder Issa Al-Dalu.

What does an AI agent need before checkout?

An AI agent orders on a customer's behalf by finding a restaurant, checking its menu and completing checkout with the customer's details. Its first requirement is a clear restaurant identity. Nexara storefronts publish discovery files and structured Restaurant, Menu and MenuItem data. Bilingual llms.txt and links to the agent ordering path help an agent identify the business and find its menu.

  • A clear restaurant identity and branch information
  • A readable menu with item IDs, prices in fils and real availability
  • Categories, modifiers and modifier groups
  • Delivery areas, address details and available order types
  • A checkout path that can confirm the order
  • Consistent hours, phone and menu facts across public listings

A menu photo can show the food, but it leaves the agent to interpret prices and options from an image. A phone-only website also makes completion depend on someone answering. Nexara supplies the live catalogue used by the restaurant storefront, including availability and modifiers. The guide to restaurant menus for AI agents explains which menu details to prepare.

How does an agent actually place the order?

This diagram follows an agent's delivery order from restaurant discovery through phone verification to the kitchen ticket and customer tracking.
This diagram follows an agent's delivery order from restaurant discovery through phone verification to the kitchen ticket and customer tracking.

Use an ACP checkout session as the worked example: a basket the agent creates, updates and completes for the customer. Nexara supports ACP version 2026-04-17. Discovery starts at the restaurant domain through https://{store}/.well-known/acp.json, with the product feed at https://{store}/feed/products.jsonl. UCP publishes its business profile at https://{store}/.well-known/ucp. MCP gives agents tools to find restaurants and complete checkout.

  1. Find the restaurant through its discovery files or the platform's restaurant search.
  2. Read item IDs, prices in fils, availability and modifier groups.
  3. Choose products, quantities and options, then select delivery or pickup.
  4. Create the checkout session with the customer's name, phone and delivery address when needed.
  5. Receive Nexara's delivery quote for the selected branch and delivery zone.
  6. Verify an anonymous customer's Jordanian mobile by one-time SMS code; a trusted platform that verified its buyer completes with a key.
  7. Confirm the quoted total and choose cash on delivery or pay at the counter.
  8. Complete checkout so the order enters the kitchen queue and returns tracking details.

Nexara calculates the total from the live menu, selected modifiers and delivery zone. The agent cannot set a lower price by supplying a different number. If the customer changes the basket, the agent updates the ACP checkout session before completing it; ACP also supports cancelling the session.

What happens when the customer address is missing?

For delivery, the agent must collect an address before it can obtain a useful quote. “Near the mall” leaves the destination unclear. Nexara uses the supplied address to select the branch and delivery zone, then prices delivery using the storefront's rules. The agent should also clarify when the customer wants the food and check the restaurant's hours before confirmation.

What must be confirmedInformation the agent supplies or checksWhat Nexara provides
Restaurant and branchRestaurant identity and branch coverageRestaurant discovery and branch information
Items and optionsProduct IDs, quantities and modifiersLive menu prices, options and availability
Delivery requestCustomer name, phone and delivery addressBranch selection, delivery-zone check and a calculated quote
Payment choiceCash on delivery or pay at the counterAn order carrying the selected payment method
Final confirmationPhone verification and accepted checkout detailsA completed order, kitchen ticket and tracking link

Phone verification is part of completing the order. An anonymous agent asks the customer for the one-time SMS code sent to their Jordanian mobile. A trusted platform that has verified its buyer completes with a key. Staff then receive an order attached to the customer's contact details, which they can use if delivery needs clarification.

How is payment handled in an agent checkout?

The payment choice tells the customer when to pay and tells the restaurant how to collect. For a delivery order, the customer pays cash at hand-over. For pickup, the customer pays at the counter. The agent confirms that choice with the order details before completing the checkout session.

Nexara's customer-facing website can also accept online card payment through HyperPay when the company enables it. That is a separate website checkout option. When reviewing your setup, check both the payment choices shown to website customers and the collection instructions on agent orders.

What reaches the kitchen after confirmation?

A completed agent order enters the kitchen queue and appears on the order board with an AI agent badge. It counts like a website order. The kitchen ticket carries the selected items and modifiers. Nexara prints Arabic on ordinary ESC/POS thermal printers, with English available on the same ticket.

The customer receives a tracking link. Platforms registered for signed order webhooks receive order creation and update events, allowing them to follow changes after checkout. Staff work from the same order board used for website, phone, table QR, Talabat and Careem orders.

During setup, check a ticket with modifiers and compare it with the confirmed basket. Check that each food category reaches its assigned printer and that staff can identify the AI agent badge. Nexara supports printer routing by category and Arabic and English ticket templates; these checks connect the checkout details to what the cook actually reads.

What should a restaurant prepare for AI ordering?

Start with the facts customers use to choose your restaurant. Nexara publishes structured menu data and the ordering path from the storefront. You still need to keep your public identity and operating details accurate wherever people find you. Compare your Google Business Profile with your storefront before reviewing checkout.

  • Write one sentence naming your restaurant, describing its food and stating where it serves.
  • Complete your Google Business Profile with the correct location and contact details.
  • Check menu names, prices, required modifiers and branch availability.
  • Keep opening hours consistent across your storefront and public listings.
  • Ask customers for reviews describing their actual food and service experience.
  • Assign someone to answer the published phone during service.
  • Confirm delivery coverage, pickup instructions and payment choices.

Review Nexara's agent ordering details alongside your menu. For your branch setup, start a WhatsApp conversation with founder Issa Al-Dalu at Nexara, nexaratech.io. Issa Al-Dalu can walk through your storefront checkout and the resulting kitchen ticket with you.

What to remember

  • Give agents readable menu items, current availability and a checkout path they can complete.
  • Nexara calculates menu and delivery prices from the restaurant's own catalogue and delivery zones.
  • Anonymous agents verify the customer's Jordanian phone by SMS; trusted platforms complete with a key.
  • Check the kitchen ticket, payment collection instructions and tracking link before relying on the order path.
  • Keep your restaurant identity, Google profile, reviews, hours and answering phone accurate.

Questions people ask

How do AI agents place restaurant orders?

They find the restaurant, read its live menu and build a basket with the customer's choices. They then obtain a delivery quote where needed, verify the phone when required and complete checkout with the supported payment method.

Can an AI agent pay by card?

No. Nexara agent checkout uses cash on delivery or pay at the counter.

What does an anonymous agent need to verify?

It verifies the customer's Jordanian mobile number with a one-time SMS code. A trusted platform that has verified its buyer completes with a key.

Do I need to integrate anything to accept agent orders?

Agent ordering is built into every Nexara restaurant storefront. Prepare your restaurant details, menu, hours and delivery coverage, then check the resulting checkout and kitchen ticket.

What happens after an agent completes the order?

The order prints in the kitchen and appears on Nexara's order board with an AI agent badge. A tracking link gives the customer a status view, and registered platforms can receive signed order creation and update webhooks.

Which agent protocols does Nexara support?

Nexara supports ACP (2026-04-17), UCP and MCP. These give compatible agents a way to read the menu, request a quote and complete an order.

WhatsApp Nexara Founder About Ordering