> 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/locations/manage-locations.md).

# Manage locations

Locations are reusable named places and addresses. They can be used again when your team plans events, but they do not replace an event's own timeline entry, timing, notes, or proposal visibility.

## Add a reusable location

1. From **Core Data**, open **Locations** and select **Add Location**.
2. Enter a nickname when it helps your team recognize the place, then search for or enter the address.
3. Add a point of contact, phone number, website, and notes when they will help the team work at that location.
4. Review the display preview and select **Add**.

For example, a saved venue can use a short nickname and its full address, with the loading contact and parking notes stored alongside it. The nickname helps distinguish a venue from another location at the same address.

<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-8c3dcc4f52ed5b506d35194fb69b49db77400f3c%2Fadd-location-dialog.png?alt=media" alt="FlowerBuddy Add Location dialog with nickname, address, point-of-contact, website, and notes fields." width="550"><figcaption></figcaption></figure></div>

The dialog shows a display preview when it has enough information to form one. Review that preview before saving so the location is recognizable in event planning. Correct the address or nickname before saving when the preview would be ambiguous to a teammate.

## Update shared details or one event

Open the **Events** count before changing a location when you need to see where it is used. Select the edit icon to update the reusable location. Updating a saved location changes the shared record, while an event's date, timeline notes, and proposal visibility belong to that event's location entry. Change those event-specific details from the event rather than overwriting the Core Data location.

## Delete a location

Select the delete icon only when the saved location is no longer needed. Deleting the shared location does not delete an event's location entry, but that entry is no longer linked to the saved location. Use **Inventory** for stock-storage locations and addresses. A Core Data location helps plan event places, while Inventory locations describe where stock is held.