Menu items overview

A menu item is a sellable thing — a dish, a drink, a side — paired with a price and a recipe. Once you have menu items linked to recipes, four features unlock:

• Food cost percentage for each item (recipe ingredient cost ÷ selling price).
• Food cost target alerts — Standard+ tier; flags items whose cost drifts above a target you set.
• Variance report — Standard+ tier; compares theoretical ingredient usage (sales × recipes) against actual consumption.
• Demand forecasting — Pro tier; predicts per-item sales and converts those into ingredient-level prep needs.

You can manage menu items even without enabling all of those features, but the value compounds once you do.

Fields on a menu item

1. Recipe (required) — the recipe whose ingredients power this menu item. Recipes can be either output-producing (e.g., a prepped sauce + plated dish) or inline (made-to-order). See recipes overview.

2. Name (required) — the customer-facing name. Can differ from the recipe name.
3. Description (optional) — a one-liner for menus and receipts.

4. Selling price (required, in dollars) — what the customer pays. Used as the denominator in food cost percentage.

5. Menu category (optional) — Appetizers, Entrees, Desserts, etc. Used to group menu items in reports and on the menu items page.

6. Target food cost % (optional, Standard+ tier) — the percentage you want food cost to stay below. Drift alerts trigger when actual exceeds this.

7. Portion size (optional, default 1.000) — how much of the recipe's output product is consumed per sale.

Portion size

Most menu items consume one unit of the recipe output per sale. But sometimes one batch of a recipe serves multiple plates or one plate uses a fraction of a batch.

• Half-loaf sandwich: the recipe produces a full loaf; one sandwich uses 0.5.
• Half-dozen donut box: the recipe produces a single donut; one box sale uses 6.
• Dish that uses the whole batch: default 1.0.

Variance, forecast, food cost, and prep-list math all multiply expected sales by this value before computing ingredient demand.

How food cost is computed

food cost % = recipe cost ÷ selling price

Recipe cost is the sum of the recipe's ingredient costs at their weighted-average cost from receipts. See how cost is computed.

Food cost percentage updates as receipts land — the same menu item's percentage moves as supplier prices change.

Inline vs output-producing recipes

A menu item can point at either kind of recipe:

• Output-producing recipe. Selling the item consumes a portion of the prepped output (and the prep step deducted ingredients separately). Examples: a marinara pasta dish, a margherita pizza using prepared dough.
• Inline recipe. Selling the item deducts raw ingredients directly. Examples: a salad assembled to order, a burger built from raw patty + bun.

Both are fully supported. Pick whichever matches how the kitchen actually operates.

Archiving a menu item

Use the On the menu toggle in the edit modal (or swipe the row on mobile) to archive a menu item. Archiving is for seasonal items, retired specials, and weekend-only dishes — anything you want off the menu without erasing what it did while it was on.

An archived menu item stops driving anything forward-looking:

• Demand forecasts skip it.
• The order list's Sales expectation mode orders nothing for it.
• Prep list generation ignores it.
• Food cost drift alerts stop firing for it.
• It can't be added as a new component of a combo.

A combo that already contains it is the exception, and deliberately so: the combo is still on the menu, so it's still selling, and Rinvy keeps ordering and prepping its components — archived or not. You can still edit that combo normally; the archived component shows up in its ingredient list marked (archived).

Its history is untouched. Variance, sales depletion, the menu item report, forecast accuracy scoring, and cost calculations all still see it — so a combo that already contains an archived component keeps costing correctly, and last quarter's numbers don't change.

The Menu page splits the list into Active and Archived chips; restoring an item is the same toggle in reverse.

Related

• Food cost targets and drift alerts
• Recipes overview
• Create a recipe