> 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-templates/editor/details/event-flowers.md).

# Set event flowers for a template

**Event Flowers** is the reusable flower palette for the template. It is a starting selection of flowers and foliage for the future event's recipes. It is not a purchase order and it does not replace the ingredients inside an individual recipe.

Open the template's **Details** tab and expand **Event Flowers**. Select **Add Event Flower**, choose the flower or foliage item, and add the items that should commonly be available when the template is used.

This empty-state view shows the control in its owning section. A populated template lists its selected palette items in the same area.

<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-3f31f9a8026a05a48000122d19d6c67e91ef7df6%2Fevent-template-editor-event-flowers.png?alt=media" alt="FlowerBuddy Event Template Details tab with Event Flowers expanded. The empty section displays Add Event Flower as the control for defining a reusable palette." width="550"><figcaption></figcaption></figure></div>

Choose a palette that is useful across the events that will use the template. Remove an item when it should no longer be part of the starting selection. After creating an event from the template, review the event's palette and recipes together because the new event may need different flowers, quantities, or substitutions.

When applying a template to an existing event, **Event flowers** has its own **Add**, **Replace**, or **Keep existing** choice. [Apply an event template](/reference/event-page/details/apply-event-template.md) explains that one-time update separately from editing this saved palette.
