Assistants don't know your menu
Without a direct source, AI assistants rely on scraped or outdated menus and can suggest items, prices or combos that don't exist.
Agentic Ordering
Guests are starting to ask AI assistants what to eat. menuOS lets them order your menu there, with accurate items, modifiers and availability for their chosen store, then hands the cart to your checkout so the customer stays yours.
Where it breaks today
Without a direct source, AI assistants rely on scraped or outdated menus and can suggest items, prices or combos that don't exist.
A real order depends on the store, the time of day, what's in stock and which modifiers are allowed. A general-purpose assistant can't see any of that.
Brands want the new channel without giving checkout, loyalty or first-party data to another intermediary.
How it works
The guest describes what they want in their own words. menuOS interprets it against your actual menu.
Items, sizes, modifiers and combos are resolved for the chosen store and daypart, including what's available right now.
Recommendations and add-ons follow brand rules, so the assistant never offers what you wouldn't.
The finished cart opens on your website or app, where the guest pays, earns loyalty and stays your customer.
What's in the module
Agentic Ordering opens new channels such as AI assistant apps and messaging, and brings conversational ordering to the web and app channels you already run.
Put your menu inside assistants such as ChatGPT, built on open standards like the Model Context Protocol.
Every answer comes from your published menu, prices and availability, not from the open web.
Carts reflect the chosen location's menu, hours and 86s at the moment of ordering.
Control what the assistant suggests, how it describes items and which requests it declines.
A structured link carries the cart to your existing checkout, with attribution for the channel it came from.
The same ordering capability can power conversational ordering in your own app and website.
Where it sits in menuOS
Agentic Ordering reads the published menu from Menu Management, store details from Store Management and nutrition and allergen data from Product Lifecycle.
Because it sits on the same data as every other channel, what a guest orders in an assistant matches what the store can make, at the price the brand approved.
What you'll see move
Assistant-built carts that reach checkout without corrections.
Share of assistant-built carts that complete purchase.
Orders attributed to AI channels, tracked like any other channel.
Time from kickoff to a live assistant experience.
Common questions
It's ordering carried out by an AI agent on the guest's behalf: the guest says what they want and the agent turns it into a valid order. menuOS provides the menu knowledge and ordering rules that keep those orders accurate.
menuOS is open by default. It isn't tied to any one assistant, so it works with any agentic commerce framework or protocol your guests' assistants use, and extends to new ones as they emerge.
Answers are grounded in your published menu and checked against it before a cart is built. Items, modifiers or prices that aren't on your menu can't be added.
No. Agentic Ordering works on its own with your existing menu data, onboarded as part of setup. Menu Management is a natural next step, since it keeps every store's menu accurate at the source, but it isn't a requirement.
Agentic Ordering
We'll scope a pilot around your menu, your stores and your checkout, and show what an assistant-built order looks like before you commit.