> 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. It includes events that associate the place directly or use it in their timeline. Select the edit icon to update the reusable location. Updating a saved location changes the shared record. [Event-specific location notes and the primary designation](/reference/event-page/details/manage-event-locations.md) belong to the event's Locations list; activity times, timeline notes, and proposal visibility belong to its [timeline items](/reference/event-page/details/plan-event-timeline.md). Change those details from the event rather than overwriting the Core Data location.

## Find and export locations

Use **Search Locations** to narrow the table by saved location information. Select the **Name**, **Location**, or **Events** column heading to change the sort order.

Select the checkbox beside one or more locations to open the bulk actions. **Export** downloads the selected locations as a CSV file. The checkbox in the table heading selects all locations currently visible after searching, rather than every hidden search result. Use **Clear** when you want to remove the selection without changing any locations.

## Merge duplicate locations

Merge locations when two or more saved records describe the same place and their event uses should point to one shared record.

1. Select at least two location rows.
2. Select **Merge**.
3. For each field, choose the value to keep in the merged location. You can keep the name from one record and the address, contact, or notes from another.
4. Confirm that you understand the selected locations will be combined.
5. Select **Merge Locations**.

Timeline entries, event-location associations, and recipe assignments move to the merged location. If one event used more than one of the selected locations, its Locations list keeps one combined entry, combines distinct event-specific notes, and retains a primary designation when one of those entries was primary. The selected source records are replaced by the combined saved location, so review every field before confirming.

## Delete a location

Select the delete icon for one location, or select several rows and choose **Delete**, only when the saved locations are no longer needed. Timeline entries and recipes remain, but their location assignments are cleared. The deleted place is also removed from each event's separate Locations list, including its event-specific location notes and primary designation. Bulk deletion reports how many locations were deleted, skipped, or failed.

Use **Inventory** for stock-storage locations and addresses. A Core Data location helps plan event places, while Inventory locations describe where stock is held.