> 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/core-data/flowers/add-and-manage-flowers.md).

# Add and manage flowers

The **Flowers** tab is for reusable flower and foliage records, not an event's temporary palette. Add a record here when the information should be available the next time your team builds a recipe.

## Add a flower from the available list

1. From **Core Data**, open **Flowers** and select **Add Flower**.
2. Search or filter the list by **Category**, **Color**, **Function**, or **Season**.
3. Select the checkbox for a matching flower, then select **Add**.

Choosing an existing flower starts from the standard flower information already available in FlowerBuddy. Review the resulting shared record before using it in a recipe, especially its colors, unit, and planning price. The selected flower is added to your workspace catalog, so later changes can affect its use across the workspace.

<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-f0be990bb5ca3ff1269b29299e68b578b1e805d2%2Fadd-flower-dialog.png?alt=media" alt="FlowerBuddy Add Flower dialog with a selected Alstroemeria record and filters for finding other flowers." width="550"><figcaption></figcaption></figure></div>

## Create a flower record

Select **Add New Item** from the **Add Flower** dialog when no listed flower is the right starting point. Enter the required **Category** and choose **Individual Name**, which defines the unit for one recipe quantity. Add **Variety**, **Grade**, colors, **Floral Category**, **Seasonality**, and **Processing Time Estimate (minutes)** when those details help your team select and prepare the flower correctly.

Use category and variety nicknames only when they make the record easier for your team to recognize. For example, "Garden Rose" and a variety name can distinguish a specific rose from another saved rose without creating a vague duplicate. Set colors and seasonality based on the information you want planners to use while filtering the catalog.

## Update or remove a flower

Select the edit icon beside a flower to update its shared information. Before selecting **Save Flower**, review the warning: changes apply throughout your account wherever the flower is used, including past events and proposals. This makes the record useful for consistent maintenance, but it also means an edit is not limited to one event.

Select the delete icon only when the flower is no longer needed. The confirmation explains that deletion removes the item from Core Data, Inventory, and the inventory log. It does not replace a duplicate record or preserve two names for the same flower. Use [Merge flowers](/reference/core-data/flowers/merge-flowers.md) when two saved records represent the same flower.