To avoid duplicate Golden Records for the same product, the Central Product Database (CPD) supports automatic merging based on shared barcodes. When two Golden Records are linked to variants with the same barcode, the system will merge them according to predefined rules.
When automatic merging happens
Automatic merging is triggered during Golden Record matching, at the end of the autocreate and autolink process for new products.
- CSV import
- UI creation
- M Connect
- API
Before a new Golden Record is created, the system checks if the barcode already exists in another Golden Product. If a match is found, and the variant or advert points to a different Golden Record, the system triggers a merge.
If vetting is enabled, the merge occurs during the vetting stage.
How the system decides which record to keep
The Golden Record with the most linked variants is retained. If both records have the same number of variants, the oldest record is kept.
What gets merged
- Variants and adverts from both records are reassigned to the retained Golden Record.
- Product data (such as title, description, and attributes) is kept from the retained product only. Differences are not resolved or combined.
- The duplicate Golden Record is deleted after the merge.
How to enable automatic merging
- Log in to the Operator portal.
- Go to Configuration > Product Settings > Golden Product Settings in the left nav dashboard.
- Check the Enable merging of Golden Products box.
- When enabled, Golden Products merge if they share a variant. The one with more variants (or the older one, if tied) is kept. You can also merge manually in the CPD UI.
- Click Submit.
Notes:
- Merging is permanent and cannot be undone.
- Only shared barcodes trigger automatic merging.
- Operators are not notified when automatic merges occur.
- All merge events are tracked in the activity log.
Related articles