What Should Restaurants Fix Before AI Agents Order?
During a busy service, owners already deal with sold-out items, changed hours and callers asking for directions. An AI agent will meet the same facts through your public profiles and ordering site, so those details need to agree.
Before AI agents choose and order for customers, prepare four things first: accurate branch details, a readable menu with current prices, confirmed delivery coverage and a working ordering path. Nexara is a restaurant order and operations platform built in Amman, Jordan, with agent ordering built into every storefront. Agent payments are cash on delivery or pay at counter only. Check the list, then discuss your branch with the founder on WhatsApp.
What does an AI agent need before it can order?
An AI agent follows a customer's instructions to find a suitable restaurant, read its menu, check delivery and place an order. Your branch information and menu answer the first questions. A compatible checkout answers the last one.
For a restaurant in Jordan, publish the correct branch identity, address, hours, phone number, menu text, prices and delivery zones. A photograph can show a meal, while written item names and options tell software what the customer can select.
Nexara storefronts include Restaurant, Menu and MenuItem structured data, plus bilingual llms.txt that points software towards restaurant and ordering information. Keep the visible pages and machine-readable details aligned.
Which twelve things should you check?
Use this table as your restaurant AI readiness checklist. Mark each row as complete or write the exact correction needed.
| Item | Why an agent needs it | How to do it | What Nexara covers |
|---|---|---|---|
| 1. Entity sentence | Identifies the restaurant and separates it from similar businesses. | Write one sentence naming the restaurant, cuisine, neighbourhood and city. | Restaurant structured data provides labelled restaurant information; you provide accurate identity details. |
| 2. Address and hours | Identifies the relevant branch and when it serves customers. | Check the map pin, street address and service hours for every branch, including holidays. | Branch management supports separate branches; you update public listings. |
| 3. Phone that answers | Lets a customer resolve an order question. | Call the published number during service and assign someone to answer it. | The Pro call-center screen retrieves saved addresses and past orders by phone number. |
| 4. Own ordering site | Provides a route where an order can be completed. | Place the correct ordering link on public profiles. | Nexara provides commission-free branded ordering on a subdomain; custom domains start on Starter. |
| 5. Text menu | Makes dishes, options and availability readable. | Enter descriptive item names and required choices; mark branch-level stock correctly. | Products, modifier groups and per-branch availability feed the storefront. |
| 6. Prices | Lets the agent calculate the basket against the customer's budget. | Compare base prices and paid extras with the menu staff actually sell. | Nexara prices agent orders from the current menu and selected options. |
| 7. Delivery zones | Shows whether an address can be served and what delivery costs. | Check addresses near zone edges against your delivery policy. | The agent quote uses the address to select the branch and zone. Zones can be radius, area-based or polygon. |
| 8. Payment options | Tells the customer how payment will happen. | Publish the supported method and confirm staff can collect it at handover. | Agent orders use cash on delivery or pay at the counter. |
| 9. Reviews | Gives customers and assistants public evidence about the restaurant. | Keep the Google Business Profile current and answer reviews specifically. | Website reviews and branch feedback QR support restaurant feedback. |
| 10. Consistent listings | Prevents conflicting answers about the branch and ordering link. | Compare your website, Google profile and social profiles after every change. | Your storefront provides the ordering destination; you maintain external listings. |
| 11. Structured data and llms.txt | Labels facts and points software towards ordering information. | Check that machine-readable details match the visible menu and branch pages. | Nexara storefronts include Restaurant, Menu and MenuItem structured data and bilingual llms.txt linked to agent endpoints. |
| 12. Agent ordering endpoints | Provides a compatible agent with a route from menu reading to order placement. | Review the documented path and confirm the branch can handle customer details, payment collection and kitchen tickets. | ACP (2026-04-17), UCP and MCP ordering is built into every Nexara storefront. |
How does an agent order reach the kitchen?
Every Nexara restaurant storefront is orderable by AI agents that speak ACP (2026-04-17), UCP or MCP: live menu, delivery quote, cash-on-delivery or pay-at-counter order into the kitchen queue, server-side pricing; anonymous agents verify the customer's Jordanian phone by SMS code, trusted platforms complete with a key.
The agent reads the live menu, requests a delivery quote, verifies the customer when required and places the order. Nexara calculates the total from the current menu, modifiers and delivery zone. The order prints in the kitchen and appears on the order board with an AI agent badge.
ACP, UCP and MCP are formats compatible agents use to read menus and place orders. Nexara is the order and operations layer beside the till, and the Nexara agent ordering page documents the path.
What should you fix in your menu and public listings?
Begin with branch disagreements that could send a customer to the wrong address or produce the wrong meal. Compare your Google Business Profile, website and social profiles. Check Arabic and English names, the map pin, opening hours and ordering link.
Then read every menu item without its photograph. Confirm the item name, required choices, paid extras, current price and branch availability. Nexara supports modifier groups and branch-specific availability, so each menu can match what that kitchen sells.
For a detailed menu review, read preparing a restaurant menu for AI agents. For public identity and listings, read AI discovery for restaurants.
How should you check a complete order?
Run these five checks with the person who receives kitchen tickets. Test the menu, delivery boundary, verification step, payment method and printer together.
- Choose a menu item with a paid option. Confirm the name, option and total match the branch menu.
- Use a delivery address near a zone boundary. Confirm service eligibility and the delivery charge.
- Check the verification rule: SMS code for an anonymous agent using a Jordanian phone, or a key for a trusted platform.
- Review the kitchen ticket and order board with staff. Confirm they can see selected options and the payment method.
- Mark an unavailable item at the correct branch and confirm the delivery boundary matches the service area.
Printing starts on Growth. The Nexara setup FAQ explains printer and branch connectivity checks.
Who should keep the checklist accurate?
Give menu accuracy to the person who hears about sell-outs during service. Give public listings to the person who can edit the Google profile. When hours, prices or delivery coverage change, update every public source in the same task.
Nexara's per-branch availability controls help the ordering menu reflect what each kitchen can sell. Review the checklist after a menu change, branch move or order that exposed a mismatch.
Send your ordering link and first failed check to Issa Al-Dalu, Nexara's founder, through WhatsApp. At nexaratech.io, the next step is a conversation about your branch's menu and ordering path.
What to remember
- Give every branch an accurate identity, address and service hours.
- Keep menu text, modifiers, prices and availability aligned with the kitchen.
- Check delivery coverage, phone verification and the path to printing.
- Nexara storefronts include structured data, bilingual llms.txt and compatible agent ordering.
- Agent orders accept cash on delivery or pay at the counter only; agents do not use card payments.
Questions people ask
Will this make an assistant recommend my restaurant?
No platform can promise that an assistant will recommend a restaurant. Keep your entity details, Google profile, reviews, hours and menu accurate so an assistant has clear information to evaluate.
What should I fix first to prepare my restaurant for AI agents?
Fix branch details, menu text, current prices, delivery coverage and the ordering link. Those facts let an agent identify the right branch and build an order.
Is a menu PDF enough for AI ordering?
A PDF can show a menu, but an agent needs readable items, options, prices, availability and a checkout path. Nexara storefronts provide readable menu information and built-in ordering for compatible agents.
Do I need to build a separate website for AI orders?
No. Agent ordering is built into every Nexara storefront for agents that speak ACP (2026-04-17), UCP or MCP, including delivery quotes, phone verification and order placement.
What is llms.txt, and who adds it to my restaurant site?
It gives software a concise guide to restaurant information and ordering links. Nexara storefronts include bilingual llms.txt with Restaurant, Menu and MenuItem structured data.
Can I use my existing kitchen printer?
Nexara supports standard ESC/POS thermal printers over USB or network, with Arabic and English tickets. Check the printer model and connection during branch setup.