Menus demand analysis
Stage 2 · Analysis
The operator jobs behind Menus searches
Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.
- 1
Compose a clear offer
Create menus, sections and ordered item placements for a service, channel or audience.
Menu owns composition and presentation. Dish and Drink remain the authoritative sellable-item records.
Evidence: restaurant menu builder · manage restaurant menu online
- 2
Turn existing material into structured drafts
Extract sections, items, descriptions and prices from a document, image or URL without retyping everything.
Extraction is a reviewable proposal. It cannot silently create authoritative Dishes, overwrite prices or publish itself.
Evidence: restaurant menu import PDF · AI menu import restaurant
- 3
Keep price and availability current
Review which items appear, where they appear, their displayed price and whether they are currently offered.
Menu availability is an offer decision. Inventory may supply evidence but must not silently mutate a published Menu.
Evidence: restaurant menu update software · multi location menu management
- 4
Publish one reviewed Menu to useful channels
Make the approved Menu available on the web, through a stable link or QR code, and later through supported ordering channels.
Publishing projects a reviewed Menu. QR is a doorway to that publication, not a separate Menu record or capability.
Evidence: digital menu for restaurant · restaurant QR menu
- 5
Review commercial performance
Compare item popularity and contribution margin to support an accountable Menu decision.
Engineering requires authoritative sales and cost evidence. Missing cost or sales data stays visibly unknown rather than becoming an estimate presented as fact.
Evidence: restaurant menu engineering · menu item popularity contribution margin
Record map
Evidence the capability owns, references, or derives
kitchen.menus.menu
Kitchen Menu
Owner: Menus
Menu owns offer identity, content structure, placements, displayed prices and publication configuration.
- Menu identity and role
- sections and item placements
- captured prices and availability
- publication state and source
kitchen.menus.performance-evidence
Menu performance evidence
Owner: Dishes, Drinks, Costs and Sales
Menu engineering reads canonical item, cost and bounded Sales evidence and does not store invented profitability.
- Dish and Drink identity
- supported direct cost
- KitchenSale quantity and value
- period and coverage
Required record questions
What must Menus make knowable?
- Which Kitchen owns the Menu and what service, audience or channel is it for?
- Which version is draft, approved, published, scheduled or retired?
- Which sections exist and in what order?
- Which Dish or Drink record does each placement reference?
- Which displayed name, description, price and availability are Menu-specific presentation choices?
- Which dietary or allergen statements resolve from authoritative Ingredient, Recipe, Dish or Drink evidence?
- Which source document or URL produced an imported proposal and what has a human reviewed?
- Which publication targets use this approved version and when were they updated?
- Which authoritative sales and cost measures support any engineering conclusion?
- Which missing evidence or stale publication must remain visible?