Merge flowers

Merge only when saved flower records refer to the same flower and you want one reusable record. It is a data-cleanup action, not a way to turn one flower into a different flower.

Select the duplicates

1. From Core Data, open Flowers and use search or filters to find the duplicate records.

2. Select the checkbox beside each duplicate. You must select at least two records before Merge is available.

3. Select Merge to open the merge dialog.

Check the names, variety, grade, colors, and thumbnails first. Two records that look similar may have different seasonality, units, or planning prices, so do not merge them solely because their category names match.

The Flowers table shows the reusable records, selection boxes, price information, and row actions to check before opening a merge.

Choose the final information

The merge dialog lets you choose which record supplies each retained detail, including names, colors, Individual Name, processing estimate, Floral Category, seasonality, and thumbnail. Review each field instead of assuming the first record contains the best value. For example, retain a correct photo from one record while retaining the current vendor price and unit from another.

Review the impact and confirm

Review the impact summary before confirming. It identifies affected recipes, events, orders, item prices, palette items, proposal items, and Inventory records. FlowerBuddy updates linked records to use the merged flower, combines duplicate linked rows that share the same flower, and marks the source records deleted.

Because the source records are deleted, confirm the retained information and affected record count before you select Merge. Use the normal edit control instead when you only need to correct one flower's shared details.