Drinks demand analysis

Stage 2 · Analysis

The operator jobs behind Drinks searches

Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.

  1. 1

    Maintain the sellable Drink

    Define the beverage offered by the Kitchen, whether packaged, poured or mixed, and connect its operational references.

    Drink owns sellable beverage identity and specification. A bottle Ingredient, cocktail Recipe and Menu placement remain separately authoritative.

    Evidence: beverage menu management · cocktail specification sheet

  2. 2

    Know what beverage stock is available

    Count bottles, containers or measured quantities and understand movements, variance and replenishment needs.

    Inventory owns stock observations and movements. The Drink capability provides a beverage-focused doorway and never stores a second stock truth.

    Evidence: bar beverage inventory software · bar stock count app

  3. 3

    Standardise mixed drinks

    Record ingredients, measures, method, glassware, garnish, yield and batch conversion for a cocktail.

    Recipe owns method, measures and yield. Drink references the approved Recipe used to produce it.

    Evidence: cocktail recipe management software · cocktail batch calculator

  4. 4

    Calculate evidenced cost per serve

    Roll Ingredient prices and Recipe measures into a per-Drink direct cost or pour cost.

    The calculation must preserve units, effective prices, yields and missing evidence. Suggested price is a proposal, not canonical Menu price.

    Evidence: cocktail cost calculator · liquor pour cost calculator

  5. 5

    Review the beverage offer

    Compare Drink availability, displayed price, placement and bounded sales or contribution evidence.

    Menu owns placement and displayed price; Finance owns sales measures. DrinksAI can assemble a review but cannot mutate either silently.

    Evidence: drink menu engineering · cocktail menu profitability

Record map

Evidence the capability owns, references, or derives

kitchen.drinks.drink

Drink

ownedavailable

Owner: Drinks

The canonical Dish record with item kind drink owns the Kitchen-local sellable beverage identity.

  • stable Drink identity
  • drink item kind
  • name, description and image
  • lifecycle and audit stamps

kitchen.drinks.operational-evidence

Drink operational evidence

referencepartial

Owner: Inventory, Recipes, Ingredients, Menus and Sales

Drinks coordinates beverage work through owner records rather than storing stock, Recipe, Menu or Sales copies.

  • Inventory observations
  • Recipe measures and yield
  • Ingredient acquisition evidence
  • Menu placement and price
  • KitchenSale lines

Required record questions

What must Drinks make knowable?

  • Which Kitchen owns the Drink and is it packaged, poured, mixed or non-alcoholic?
  • Which stable Ingredient or product identity represents the stocked beverage?
  • Which Recipe defines a mixed Drink, measures, method, garnish and yield?
  • Which unit connects purchased container, counted stock, Recipe measure and served portion?
  • Which Inventory observation or movement supports current availability?
  • Which effective Ingredient prices and conversions support cost per serve?
  • Which Menu placement and displayed price reference the Drink?
  • Which bounded KitchenSale lines support a beverage review?
  • Which jurisdiction-specific alcohol, allergen or serving facts require identified authority?
  • Which proposed Inventory, Recipe or Menu change must be handed to its owning capability?
Analysis conclusion
Drinks owns the sellable beverage specification and coordinates beverage work. Inventory owns stock, Recipe owns mixed-drink production, Menu owns the offer, and Finance supplies sales evidence; DrinksAI must cross those boundaries through explicit evidence and tools rather than duplicate them.
Review proposed Tools