> ## Documentation Index
> Fetch the complete documentation index at: https://docs.petakopi.my/llms.txt
> Use this file to discover all available pages before exploring further.

# Recipes

> Sellable drinks built from items — per-cup COGS plus two pricing paths

A Recipe is a sellable drink (or pastry, or anything you ring up at the till). You build it by adding lines — each line is `{Item, quantity}` — and the app sums the line costs to give you per-cup COGS.

## Two prices

Each recipe surfaces two suggested prices, and they answer different questions:

<CardGroup cols={2}>
  <Card title="Quick price" icon="bolt">
    On the Recipes form. Set a target food-cost % (e.g. 25%), the app shoots back a suggested sell price. Fast — but doesn't account for rent or wages.
  </Card>

  <Card title="Calculator price" icon="calculator">
    On the [Calculator](/manage-shop/costs-and-pricing/calculator) page. Full P\&L number — covers rent, wages, target margin, and your actual volume.
  </Card>
</CardGroup>

Use **Quick price** when you're sense-checking a single recipe ("does RM 12 for this latte make sense at 25% food cost?"). Use the **Calculator** when you're pricing the menu seriously ("at this volume, with this rent and these wages, what does each cup need to charge to leave 10% margin?").

## Menu price (optional, recommended)

Each recipe also has a **Menu price (RM)** field — the actual price you charge on your menu today. It's optional, but filling it in unlocks two things:

* The [Calculator](/manage-shop/costs-and-pricing/calculator)'s **Unit economics check** card, which compares your real menu prices against your fixed costs and tells you whether the plan breaks even at planned volume.
* The recipe-derived target line on [Pulse's revenue burn chart](/manage-shop/pulse/summary#revenue-burn-chart). With menu prices set, the target reflects what you actually charge — not just what the Calculator suggests.

If you leave it blank, nothing breaks; the Calculator's suggested price is used as the fallback for any recipe without a menu price set.

<Tip>Fill in menu prices for your top sellers first. The Unit economics check averages across whatever recipes have one set — so even a handful of mapped prices is enough for a useful read.</Tip>

## Example: Hot Coffee Latte

Using the [items defined on the Items page](/manage-shop/costs-and-pricing/items), the Hot Coffee Latte recipe has three lines:

| Item         | Quantity | Per-unit cost    | Line cost   |
| ------------ | -------- | ---------------- | ----------- |
| Whole milk   | 150 ml   | RM 0.008 / ml    | RM 1.20     |
| Coffee beans | 18 g     | RM 0.0889 / g    | RM 1.60     |
| Paper cup    | 1        | RM 0.30          | RM 0.30     |
|              |          | **Per-cup COGS** | **RM 3.10** |

### Quick price for this recipe

If you set a target food-cost of 25% on the Recipes form, the Quick price comes back as:

`RM 3.10 ÷ 0.25 = RM 12.40`

That's the minimum sell price to keep food cost at or below 25% of revenue. Round to a clean menu number (RM 12.50, RM 13) for the till.

For the full P\&L picture — what to charge once rent, wages, and target net margin are factored in — feed this same recipe through the [Calculator](/manage-shop/costs-and-pricing/calculator). The Calculator surfaces a different price because it's solving a different equation (margin on revenue, not food cost as a % of revenue).

## Per-recipe sales (after Loyverse linkage)

If you map Loyverse variants to recipes (see [Loyverse Items](/manage-shop/costs-and-pricing/loyverse-items)), the Recipes index gains three columns: **Sold this month**, **Revenue**, **Gross margin**.

Without mapping, the Recipes index still works for setup and pricing — you just don't see per-recipe sales numbers. Mapping is incremental: cover your top sellers first, leave rare items unmapped. They'll still count in your overall [Pulse](/manage-shop/pulse/overview) revenue.

## What's next

With your top recipes built and per-cup COGS computed, head to the [Calculator](/manage-shop/costs-and-pricing/calculator) to factor in your fixed costs (rent, wages, utilities) and target margin. That's where the full P\&L picture lands — and where your monthly revenue target gets set.