> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/event-page/recipes.md).

# Recipes

The **Recipes** tab is where an event's floral designs become a practical and priced plan. Each recipe can bring together the flowers, hard goods, quantities, direct labor, images, and notes needed to sell and build one design.

The tab can also contain recipe groups, other costs, and recipe proposal sections. These serve different purposes:

* A **recipe group** presents one client-facing offering while preserving the individual recipes and fixed costs needed to produce it.
* An **other cost** accounts for a service or expense that is not a floral recipe, such as delivery or setup.
* A **recipe proposal section** is a heading that organizes line items, such as Personals or Reception. It does not combine their prices.

This populated Recipes tab is organized with a **PERSONALS** recipe proposal section. Each collapsed recipe shows its event quantity and its total Cost, Price, and Profit, so the florist can compare designs without opening every card.

<div data-with-frame="true"><figure><img src="https://2616748322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtdSEPutB4SrRwwUMOIx%2Fuploads%2Fgit-blob-b77c31c4908c06717e1e7c8adf2883d825b2d17c%2Fevent-recipes.png?alt=media" alt="The Recipes tab for the Amelia and Noah Garden Wedding, showing a Personals recipe proposal section followed by Bridal Bouquet, Bridesmaids Bouquet, Corsage, and Boutonniere recipe cards. Each recipe card displays an event quantity and total Cost, Price, and Profit, while Generate Recipes, Templates, and Add Item controls appear above the list." width="550"><figcaption></figcaption></figure></div>

## Plan each design

Expand a recipe to work with its **Inspiration Photos & Notes**, **Flowers & Hard Goods**, **Labor**, and **Design Fee & Overheads** sections. The recipe quantity tells FlowerBuddy how many of that design the event needs. The quantities inside **Flowers & Hard Goods** describe what one recipe uses, unless a recipe group changes how its quantities are interpreted.

You can start with a blank recipe, add a saved recipe template, duplicate a similar recipe, or create a first draft with FlowerBuddy AI. These starting points all lead to an event recipe that should be reviewed for the event's actual flowers, quantities, costs, labor, and selling price.

## Understand cost, price, and profit

**Cost** is what the design is expected to cost the business. **Price** is what the client is charged. **Profit** is the difference after the costs FlowerBuddy knows about are included.

FlowerBuddy calculates a suggested price from the recipe and the event's pricing settings. That suggestion can include flower and hard-good pricing, direct labor, an optional Design Fee, selected overhead, and applicable fee settings. You can choose a different selling price. A warning appears when a recipe is priced below its suggested price or contains a flower or hard good with no cost.

Accurate overhead information makes the profit estimate more useful and can move it from a gross-profit view toward net profit. It is still an estimate based on the costs entered in FlowerBuddy, not a complete accounting statement.

## Present choices without losing production detail

A recipe group is useful when the client should see one offering but the florist still needs individual production detail. For example, a client can see 12 tablescapes while the florist plans the centerpieces and bud vases required for those tables.

An optional recipe or group lets the client select or deselect an offering through the Client Portal. Its **Selected** state determines whether it is currently included in the event total.

Recipe images and **Proposal Notes** can help explain the design to the client when the proposal's Scope of Services displays images and notes. **Florist Notes** are for you and your team and do not appear in the proposal. Both note fields can be shared through Build to help the people preparing the designs. See [Add recipe notes and Build information](/reference/event-page/recipes/add-recipe-notes-and-build-information.md).

## Use this section

When an event needs a new design, create its recipe first, then use the detailed articles below for ingredients, pricing, groups, client choices, proposal organization, media, production information, and other costs.

## In this section

* [Create, reuse, and manage recipes](/reference/event-page/recipes/create-reuse-and-manage-recipes.md)
* [Add flowers and hard goods to a recipe](/reference/event-page/recipes/add-flowers-and-hard-goods.md)
* [Set recipe quantities, pricing, and labor](/reference/event-page/recipes/set-recipe-quantities-pricing-and-labor.md)
* [Use recipe groups](/reference/event-page/recipes/use-recipe-groups.md)
* [Offer optional recipes](/reference/event-page/recipes/offer-optional-recipes.md)
* [Organize recipes for the proposal](/reference/event-page/recipes/organize-recipes-for-proposals.md)
* [Use images and FlowerBuddy AI with recipes](/reference/event-page/recipes/use-images-and-flowerbuddy-ai.md)
* [Add recipe notes and Build information](/reference/event-page/recipes/add-recipe-notes-and-build-information.md)
* [Add and manage other costs](/reference/event-page/recipes/add-and-manage-other-costs.md)