AI Menu Management: Edit Your Menu by Talking to It

Tuesday morning. Your fish supplier just called — snapper's out, but they've got halibut at a good price. You grab your phone, open the chat, and type: "Replace the pan-seared snapper with pan-seared halibut, same price, update the description to mention lemon-butter sauce and roasted fingerlings."

Done. No laptop. No logging into a dashboard. No clicking through four screens to find the item, edit three fields, save, then double-check it actually published. You just told your menu what to do, and it listened.

That's AI menu management. Not a futuristic concept — something I built and shipped at Deally, and something restaurant operators are using right now to cut what used to be a 20-minute task down to a single sentence.

I want to walk through what this actually looks like in practice. The version we built is closer to having a really sharp assistant manager who knows your menu inside out, never forgets a spec sheet, and works at 6am when you're prepping and at midnight when you're doing next-day planning.

Why Menu Management Is Broken

Here's the dirty secret of restaurant technology: the people building menu dashboards have never worked a service. They've never had to 86 the braised short rib mid-rush while simultaneously adding a last-minute special because the chef scored a case of beautiful heirloom tomatoes from a farmer who showed up unannounced.

Traditional menu management systems are database forms wearing a restaurant costume. Add item: fill out name, description, price, category, tags, options, modifiers, availability, image. Want to change the price on everything in a category because your food cost just shifted? Click, edit, save. Click, edit, save. For every single item.

I've watched operators spend 45 minutes updating a seasonal menu. Forty-five minutes of pointing, clicking, and typing into tiny text fields when they could've been on the line, talking to staff, or — radical idea — actually running their restaurant.

Menu management shouldn't require a computer science degree. Or even a laptop.

The broader shift toward AI in restaurant operations is real, but menu management is where the friction is most absurd, because the people who need to make changes are the busiest people in the building.

How Natural Language Menu Editing Works

The Menu Agent we built at Deally has 13 tools under the hood. You don't need to know what they are. You just talk to it.

You open the menu agent in your dashboard — a chat interface — and start typing the way you'd talk to a sous chef:

"Add a pumpkin spice latte for $5.95 in the Fall Specials category."

The agent creates the item, sets the price, files it under Fall Specials (creating the category if it doesn't exist), and confirms what it did. No mandatory fields blocking you from getting the item live.

"Update all prices in the Appetizers category — bump everything up by a dollar."

The agent finds every item in Appetizers, adds $1.00 to each price, and shows you the before and after. One command, twelve items updated.

"86 the lobster bisque and change the soup of the day to French onion, $8.95, add a note that it's vegetarian."

Two operations in one sentence. The agent marks lobster bisque as unavailable, then either updates the existing soup-of-the-day item or creates a new one — depending on how your menu is set up. It handles the ambiguity because it knows your menu structure.

That's the difference between a form and a conversation. Forms are rigid. Conversations handle context, intent, and the messy, shorthand way real operators actually communicate changes.

What 13 Tools Actually Means

When I say 13 built-in tools, I don't mean 13 buttons. I mean 13 distinct capabilities the AI chains together to accomplish what you're asking for:

Item creation and editing. Create new items with all the details or update any field on existing ones. "Make the burger description more appealing" — it rewrites it. "Mark the pad thai as contains peanuts" — allergen tag added.

Category management. Create categories, reorder them, move items between them. "Move all the seasonal items into a new category called Spring Menu" just works. So does "put the Spring Menu right after Appetizers on the board."

Modifier and option management. Modifiers — the required and optional add-ons that make restaurant menus complex — are painful to manage in any traditional UI. The agent handles them conversationally: "Add a size option to the poke bowl — regular for $14.95, large for $18.95, make it required." It creates the option group, sets it as mandatory, and attaches it to the item. Extra charges, required versus optional, nested modifier groups — all handled without ever seeing a nested form.

Bulk operations. Update prices across a category, toggle availability for a group of items, apply a tag to an entire section. Fifteen minutes of clicking becomes one sentence.

Item reordering. "Put the wagyu burger at the top of the Burgers category." Done. No drag-and-drop jankiness on a phone screen.

Menu analysis. This is the one that surprises people. Ask the agent to review your entire menu and it'll give you strategic feedback — pricing gaps between categories, descriptions that all sound the same, missing dietary options you could build from existing inventory. It told one operator: "Your appetizer category has seven items between $12 and $14 with no premium option — you're potentially leaving money on the table." That's not a command execution. That's a second opinion from something that's looked at your actual data.

If you're already tracking your AI tools' performance in a dashboard, you'll see the Menu Agent's activity right alongside your ordering and upselling data.

The Memory Problem (And How We Solved It)

Here's something that bothered me about every AI tool I tested before building ours: they forget everything. Every session starts from zero. You tell the AI that your restaurant does Thai-Mexican fusion and your price point is mid-range, and the next time you open it, it has no idea.

The Menu Agent has persistent memory. It remembers your preferences — how you format descriptions, that you never capitalize "and" in item names, that you started a seasonal rotation last Tuesday. When you come back and say "add the next round of seasonal items," it knows the context.

It also tracks its own actions. Every change is logged — what changed, the before and after values, when it happened. So when your chef asks "who changed the salmon price?" you've got a record. Operators I've talked to are consistent on this: "I don't trust anything I can't audit." Fair. Now you can.

A Real Day With the Menu Agent

Here's how this fits into an actual shift, not a demo.

6:30 AM — Prep. You're reviewing what came in from suppliers. Short on arugula, baby spinach looks great. You pick up your phone: "Swap arugula for baby spinach on the harvest salad and the steak salad. Update the descriptions." Two items fixed before you've finished your first coffee.

10:15 AM — Pre-service. Chef wants to run a special. "Add a lunch special — grilled swordfish with mango salsa, choice of two market sides, $24, only available today until 3pm." The agent creates it, sets the time window, slots it into Specials.

2:45 PM — Between services. Half the dessert descriptions are from two years ago. "Review the dessert category and suggest better descriptions for anything that sounds generic." The agent proposes rewrites. You approve the ones you like, skip the rest. Ten minutes instead of an hour.

9:30 PM — Post-service. "86 the duck confit, the tuna tartare, and the chocolate soufflé for tomorrow." They'll show as unavailable when the menu goes live in the morning.

Four interactions. Maybe five minutes total. No laptop.

Who This Is For (And Who It Isn't)

I'll be direct. This is built for operators who are hands-on with their menu — owner-operators, chef-owners, GMs who keep the board updated and the POS current. If you're running one to five locations and you're the person making menu changes, this saves real time every week.

It's also built for restaurants that change their menu frequently. Seasonal rotations, daily specials, market-price items — the more dynamic your menu, the more this pays off.

Who it's not for: multi-unit chains with a centralized menu team and a dedicated CMS. If you have three people whose entire job is managing the menu across 200 locations, you've already solved this differently.

For everyone in between — and that's most restaurants — the conversation-based approach removes enough friction that menu changes actually happen when they should, instead of being put off because "I'll update the system later."

Frequently Asked Questions

Can the AI agent make changes without my approval?

It confirms what it's about to do before executing. You see a summary of every change — what's being created, updated, or removed — and you approve it. Nothing goes live without your sign-off. The action tracking log gives you a full audit trail.

Does it work with modifiers and complex option groups?

Yes — that's actually one of its strongest features. You can create required size options, optional add-ons with extra charges, nested modifier groups, and everything in between through natural language. "Add a required temperature option to all steaks — rare, medium rare, medium, medium well, well done" handles the entire modifier setup in one command.

What if I say something ambiguous or make a mistake?

The agent asks for clarification rather than guessing. If you say "update the chicken" and you have four chicken items, it'll ask which one. If you realize a change was wrong, tell it to undo — the persistent memory means "actually, put the price back" works.

How is this different from just using a regular menu dashboard?

Speed and flexibility. A dashboard requires navigating to the right section, finding the item, clicking into the right field, making the change, and saving. The agent lets you describe what you want in plain English — including multiple changes in a single sentence. The gap is biggest with bulk operations and complex modifier setups, which take ten times longer through a form-based interface.

The Menu Shouldn't Fight You

I built this because I kept watching operators battle their own software. They'd have the change in their head — they knew exactly what needed to happen — but the tool made them translate that knowledge into clicks, dropdowns, and form fields.

Your menu is the most important piece of marketing your restaurant has. If your current system makes you dread updating a price or adding a special, something's fundamentally wrong with the tool, not with you.

The Menu Agent is available on all Deally plans that include AI features. It pairs well with our AI upselling system — the menu agent keeps your items sharp, and the upselling engine makes sure customers see the right ones at the right time. Different tools, same menu data.

Your menu changes every day. Your tools should keep up.