Owner intent
The owner types or speaks a menu change in normal language.
How it works
Message in. Card prepared. Approval first. Receipt after.
AI can understand the owner request, but MenuList controls what can be prepared and what can be applied.
Daily commands
Menu updates by message
Ask naturally, or choose an item, category, or menu area first when you want tighter control. Every example stays tied to the selected business and menu, and broad work is shown before approval.
Menu operations
Built for menu work, not random chat.
Every supported request maps to a MenuList action. Unsupported external platforms get a clear not-supported card, not a fake done state.
Prices and availability
Prepare single-item, selected-item, category, or bulk price, sold-out, visibility, and status cards from the selected menu.
Notes and publishing
Prepare menu notes, supported MenuList publishing work, and review/handoff cards with the right approval level.
Images and content
Generate drafts and apply them only after the owner chooses to use them on the menu.
Imports and review
Use existing menu import and extraction review paths instead of overwriting live menu data.
Design and theme
Turn style requests into previewable changes using MenuList design controls.
Unsupported platforms
Zomato, Swiggy, Google, Instagram, and similar destinations are not supported by AI Menu Manager.
Owner control
AI prepares the work. You stay in control.
The feature is designed around approval, selected business/menu context, and receipts so important menu details do not change silently.
Approval-safe
Price changes, bulk updates, publishing, generated images, and risky work require explicit owner approval.
Existing MenuList paths
Approved supported work uses existing MenuList save, image, import, publish, and receipt behavior.
Clear manual tasks
Unsupported external posting is shown honestly as a manual step or export handoff.