> 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/offer-optional-recipes.md).

# Offer optional recipes

An optional recipe lets a client turn an offering on or off through the Client Portal. This reduces back-and-forth when the client is choosing among clearly priced additions, while the florist retains control of the recipe and its price.

An optional choice can be an individual recipe or a whole recipe group. A recipe inside a group is controlled by the group and cannot become a separate optional choice.

The expanded recipe card places **Optional** beside the recipe's other client-facing choices. Turning it on reveals **Selected**, which tells you whether the client currently wants that item included.

<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-402654e7c181d9860705974c41559aa8f63c54d1%2Frecipe-optional-choice.png?alt=media" alt="FlowerBuddy expanded Bridal Bouquet recipe with Optional and Selected enabled beside Sales Tax, with the recipe name, quantity, price, and other recipe sections visible for context." width="550"><figcaption></figcaption></figure></div>

## Mark a recipe or group as optional

1. Open the event and select **Recipes**.
2. Expand the top-level recipe or group.
3. Change **Not Optional** to **Optional**.
4. Review the **Selected** state that appears.

**Optional** means the client is allowed to choose. **Selected** means the choice is currently included. These settings answer different questions.

## Set the current selection

Use **Selected** when the option should begin in the event. Use **Not Selected** when it should be offered but excluded until the client chooses it.

An optional item that is not selected does not contribute to event totals. Selecting it adds its quantity and price back into the event. For a group, its recipes and fixed costs follow the group's selection.

For example, a client could receive a proposal with an optional ceremony arrangement shown as **Not Selected**. Selecting it in the Client Portal includes that arrangement and updates the event price without requiring the florist to edit the proposal for that choice.

## Prepare the option for the Client Portal

Before sharing the Client Portal, check the option as a client would see it:

* Use a clear client-facing name.
* Add useful **Proposal Notes** and an image when they help explain the choice.
* Confirm the quantity and selling price.
* For a group, decide whether its recipes and their prices should be visible.
* Confirm whether the choice should start **Selected** or **Not Selected**.

The option changes what is included and the event total. It does not change the underlying recipe ingredients or create a payment by itself.

## Change or remove an option

Turn **Optional** off when the item should become a normal included line. Review **Selected** first so the resulting event includes or excludes the line as intended.

Deleting an optional item that was never selected removes it directly. After a contract is signed, a selected contracted item follows the amendment process when it is removed or deselected. Review the event's pending amendments before publishing an updated proposal.
