The pattern: review the catalog structure, decide which related-record types should clone, configure the toggles, document the choices, audit when catalog structure evolves. The settings are usually one-time but the audit cadence catches drift.
- Inventory the related-record types on Product2
PricebookEntries, ProductFeatures, ProductAttributes, ProductRelatedComponents, custom related objects. The inventory drives which toggles matter for the org.
- Open Deep Clone Product Settings
Setup, Product Settings (location varies by edition). Find the Deep Clone section.
- Enable PricebookEntry copying for sellable-clone scenarios
Most catalog workflows want clones to be immediately sellable; PricebookEntries are required for that.
- Enable Bundle Children for orgs using Bundle Products
Skip if the org does not use Bundles; enable if Bundles are part of the catalog structure.
- Configure ProductFeatures and Attributes copying per CPQ usage
CPQ-driven catalogs need feature copying; flat catalogs do not have features to copy.
- Set default values on cloned records where source values should not propagate
IsActive = true on cloned PricebookEntries, Required = false on cloned ProductFeatures. Defaults override source values.
- Document the configuration and test with a sample clone
Clone a test Product and verify the cloned hierarchy matches expectation. Adjust settings until the clone is what catalog admins need.
Whether per-Pricebook prices copy to the cloned Product.
Whether configurable feature definitions copy to the cloned Product.
Whether bundle component references copy to the cloned bundle.
Whether ProductRelatedComponent records copy to the cloned Product.
Admin-managed overrides applied to cloned related records.
- Without PricebookEntry copying, cloned Products are not sellable until admins add prices. Enable unless the workflow intentionally requires price restructure.
- Bundle Children copying references existing component Products, not clones them. The cloned bundle and the source bundle share components.
- Default value overrides apply to every clone. Document so admins understand why cloned records do not match source values.
- Settings drift as the catalog evolves. New related-record types or bundling structures need configuration review.
- Deep Clone operations on large bundles can take noticeable time. Test performance with realistic data before declaring done.