Deep Clone Product Settings
Deep Clone Product Settings is the Salesforce Setup page that configures the behavior of the Deep Clone feature for Product2 records: which related records (PricebookEntry, ProductFeature, ProductAttribute, related Bundle children, ProductRelatedComponent) are included when an admin clones a Product, what default values are applied to the cloned children, and how the cloned hierarchy preserves relationships from the source Product.
Definition
Deep Clone Product Settings is the Salesforce Setup page that configures the behavior of the Deep Clone feature for Product2 records: which related records (PricebookEntry, ProductFeature, ProductAttribute, related Bundle children, ProductRelatedComponent) are included when an admin clones a Product, what default values are applied to the cloned children, and how the cloned hierarchy preserves relationships from the source Product. The settings page lets admins decide whether Deep Clone is a faithful copy (every related record carries over) or a structured clone (only specific relationships carry).
Deep Clone Product Settings exists because Product catalog management at scale produces near-duplicate Product configurations constantly: new SKUs that share most attributes of existing SKUs, regional variants of a global Product, annual refreshes of a seasonal Product line. Manual recreation of every related record (PricebookEntries across multiple Pricebooks, ProductFeatures, related components) is error-prone and slow; Deep Clone automates the duplication with admin-controlled behavior. The settings page is where the admin defines what Deep Clone copies and what it leaves out.
Why Deep Clone Product Settings matters for any catalog with hundreds of Products
Where Deep Clone Product Settings lives in setup
Setup, Product Settings (or under Industries Cloud configuration depending on edition). The page lists toggles for each related-record category: Include PricebookEntries (yes/no plus per-Pricebook scope), Include ProductFeatures, Include Bundle Children, Include Related Components. Each toggle determines whether Deep Clone copies that relationship type from source to cloned Product. The page is usually configured once during catalog rollout; routine cloning operations consume the configured settings without per-clone adjustment.
The Deep Clone operation and what it produces
Deep Clone copies the source Product record plus the configured related records. The cloned Product is a new Product2 record with a new ID; the related records are new records linked to the new Product. The relationships from source to cloned mirror the source relationships in topology but reference the new Product ID. The user kicks off Deep Clone via a button or action on the source Product; the operation runs server-side and returns the new Product for the user to adjust.
PricebookEntry copying and the price-by-price decision
PricebookEntries are the per-Pricebook prices for a Product. A Product priced in three Pricebooks (Standard, US Retail, Enterprise) has three PricebookEntries. Deep Clone with Include PricebookEntries enabled copies all three to the cloned Product; without the toggle, the cloned Product has no PricebookEntries until admins add them manually. The default usually enables PricebookEntry copying because new Products need prices to be sellable; the override is rare (intentional price restructure on the clone).
Bundle children and the configuration-tree copy
Product Bundles (Product2 with ProductRelatedComponent children that form a sellable package) clone hierarchically when configured. Deep Clone with Include Bundle Children enabled copies the bundle Product plus every component Product reference. The cloned bundle's components point to the same Product2 IDs as the source bundle (the bundle is the parent that cloned; the components are existing Products the bundle references). For deeper hierarchies, the operation respects the configured depth.
ProductFeatures and ProductAttributes
For orgs using the CPQ or Industries Product model, ProductFeatures and ProductAttributes define configurable attributes on a Product. Deep Clone with Include ProductFeatures enabled copies the feature definitions to the cloned Product; without it, the cloned Product has none of the source's features. The decision drives whether the clone is a fully-configurable variant or a flat copy that admins reconfigure manually.
Default values on cloned related records
Some Deep Clone settings let admins specify default values applied to cloned related records (set PricebookEntry IsActive to true on all clones, set ProductFeature Required to false on all clones). The defaults override the source's values; useful when the source has values that should not propagate (Active = false on retired Products). The defaults are admin-managed; document the policy so future admins understand why cloned records appear with overridden values.
Audit, maintenance, and the catalog-evolution question
Deep Clone Product Settings interacts with how the catalog evolves. Settings configured for the catalog of 2024 may not match the catalog of 2026 if new related-record types were added or if the bundling structure changed. The quarterly audit: review Deep Clone settings against current catalog structure, confirm the toggles produce the desired clone behavior, update defaults if needed. The audit prevents surprises when admins clone a Product and find the result missing critical related records.
How to configure Deep Clone Product Settings for catalog management
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.
Trust & references
Cross-checked against the following references.
- Product Settings referenceSalesforce
- CPQ overviewSalesforce
Straight from the source - Salesforce's reference material on Deep Clone Product Settings.
- Product SettingsSalesforce Help
- Products OverviewSalesforce Help
- CPQ Product SettingsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the primary benefit of Deep Clone Product Settings for Salesforce administrators?
Q2. Why is understanding Deep Clone Product Settings important for Salesforce admins?
Q3. In which area of Salesforce would you typically find Deep Clone Product Settings?
Discussion
Loading discussion…