> 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/set-flower-units-and-prices.md).

# Set flower units and planning prices

The unit and price information on a flower record provide a reusable planning starting point. They are not an instruction to buy the same amount for every event, and they do not replace a vendor's actual purchase-order price.

## Choose a unit for a workspace-created flower

1. From **Core Data**, open **Flowers** and select **Add Flower**.
2. Select **Add New Item** when you need a workspace-created flower rather than a catalog flower.
3. Choose **Individual Name** for the unit one recipe quantity represents, such as a stem.
4. Set **Processing Time Estimate (minutes)** when the unit needs a preparation estimate, then select **Create Flower**.

A flower added from FlowerBuddy's catalog keeps the catalog unit. Its **Individual Name** field says, **This flower matches the core catalog. To use a different unit, create a new flower.** Do not try to change that catalog flower into a differently measured workspace record. Create a new flower instead, then choose the needed unit as part of its setup. See [Add and manage flowers](/reference/core-data/flowers/add-and-manage-flowers.md) for the catalog and workspace-created paths.

The catalog restriction appears in the flower editor beside **Individual Name**.

<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-a73df78d6c72f06ae330b69928be7ab0304fa74a%2Fedit-flower-dialog.png?alt=media" alt="FlowerBuddy Edit Flower dialog with the Individual Name field and a message that a flower matching the core catalog needs a new flower record for a different unit." width="550"><figcaption></figcaption></figure></div>

## Change an eligible shared unit

For a workspace-created flower whose **Individual Name** has an edit icon, select the icon and wait for FlowerBuddy to load the recipe and price counts. Review the number of recipes and prices, including templates and saved event versions. Choose **New individual name**, select **Use selected unit**, then select **Save Flower** in the editor.

Changing an eligible shared unit changes its meaning everywhere that flower is used. FlowerBuddy does not convert existing quantities or prices. A bunch price and a stem price can both be valid for the same flower, but the recipe unit must match how quantities are planned and the associated pricing needs review.

## Add or update a planning price

1. In the **Flowers** table, select the price count or price control for the flower.
2. In the pricing dialog, add a price or select the edit control for an existing price.
3. Enter the vendor information when it is known, then set the price amount, the group name, and the number of individual units in that group.
4. Save the price after checking that the group quantity matches the amount you entered.

A planning price estimates what you expect to spend while building recipes. It is different from a purchase-order price and from an event-specific price, which applies only in that event and does not become a Core Data price. For example, a price for a bunch must include the number of stems in the bunch so FlowerBuddy can estimate the cost of a recipe that calls for individual stems.

Use [Purchasing](/reference/purchasing.md) when you are ready to review order needs or record the actual amount on a purchase order.