One menu record — updates can reach the POS, online ordering, or print/QR systems configured for your engagement. Confirm every connected destination got the update.
The menu record is where item names, prices, availability, and dietary details live — the source for whichever POS, online ordering, and print or QR systems are configured and mapped for your engagement, when a destination supports the changed fields. With Business AI Ops configured, a verified supplier cost change surfaces the affected items so your operator can decide the response. Every destination is confirmed separately, not assumed.
The Menu Record Contract
One menu record for the change. Separate proof for every connection.
01
Keep the menu record current
Manage item names, descriptions, categories, selling prices, availability, dietary details, allergens, and internal menu status.
02
Verify cost context separately
Supplier cost, inventory, recipe mapping, and margin context require configured source data and an explicit item mapping. The native menu record stores selling prices; it does not calculate margin by itself.
03
Confirm every destination
An internal save or active menu status does not prove a POS, website, ordering channel, cost view, or team surface changed. Each configured target needs its own result.
Verified Change To Confirmed Targets
Know. Decide. Approve. Then inspect every result.
You run the shift. Our team configures the menu, cost, mapping, and destination connections so the operator can focus on the decision—not a setup weekend.
Sample numbers — not a live account. When a cost changes, you see which menu items move. You approve what happens next.
01
Verify the change
Confirm the supplier or cost input before it becomes decision context.
02
Map affected items
Use the configured ingredient and item mapping to identify the relevant menu records.
03
Prepare the response
Review item-level context and consider price, portion, substitute, availability, or hold.
04
Owner decides
A named operator approves the consequential change or leaves the menu unchanged.
05
Send to named targets
Only applicable configured systems receive the approved fields.
06
Verify each target
Confirm success or surface failure and retry separately for every configured destination.
Everyday Menu Depth
Keep the source record useful between cost events.
Price response is one moment. The menu record also supports the daily facts your team needs to find, edit, mark unavailable, activate, archive, bulk update, or export.
- Menu state
- Internal draft, active, or archived status, with optional effective and expiration dates.
- Item truth
- Name, description, category, price, currency, image, order, and availability.
- Guest context
- Dietary tags, allergens, calories, and preparation time.
- Operator actions
- Search, bulk price or availability edits, selected deletion, and CSV export.
Scoped AI Assistance
AI can read and prepare. Consequential changes stay governed.
Within configured access, AI Agents can list and retrieve permitted menu records independently. AI Agents can also prepare a draft menu item for review without changing the stored menu.
Approval Boundary
Create + add + update + bulk import + publish → permission check → approval
The current registered AI mutation actions require approval. Direct authorized operator actions follow their own capability checks. Neither path proves an external destination accepted the change.
Menu-management questions, answered.
What the menu stores, how configured margin workflows work, and what each destination still needs to prove.
The enabled module manages menus, categories, and items inside your organization’s workspace. It supports item details, selling price and currency, availability, dietary and allergen context, internal draft, active, and archived status, bulk operator edits, and CSV export. Seasonal records can also be listed when configured.
With Business AI Ops configured, a verified supplier or cost input can be mapped to affected menu items and presented as decision context. Your operator chooses whether to reprice, resize, substitute, mark unavailable, or hold. The native menu record alone does not calculate ingredient cost or margin.
No universal propagation is implied. After the required approval, selected fields can be sent only to applicable systems configured and mapped for the engagement. Each destination must be checked separately; the engagement defines what acknowledgement, failure, or retry evidence is available.
The internal menu record changes to unavailable. A configured channel integration may send that state to a named destination, but the source update is not proof that every customer-facing surface changed or that ordering was blocked. Verify the target result.
Within configured access, AI Agents can list and retrieve permitted menu records independently. AI can also propose a draft item without writing it. Creating menus, adding or updating items, bulk importing, and publishing through the current registered AI actions are permission-scoped and require approval.
The connected verified-cost-to-menu decision workflow is configured with Business AI Ops and above. Exact data sources, item mappings, target systems, fields, approval boundaries, verification evidence, exception handling, and transfer terms are defined for the engagement.
Continue The System