---
schema_version: "1"
id: 5b0cbd99b9d21d81c6bf9c0d01ea6c034d420ff6d4f5575ef47420741977cb2a
title: Create a Product Relationship
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_create_a_product_relationship.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_create_a_product_relationship.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1467808060a1a10c1636e5c3a49b9da379f6c94061997cfe76574d850c57c2d3
description: You create product relationships to relate products to one another.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Create a Product Relationship

You create product relationships to relate products to one another.

For example, you may want to recommend that, when a customer orders an iPhone, he also orders an iPhone case. To do so, you create a product relationship for the iPhone.

1. Go to the Products tab.
2. Search for and go to the product on which to base the relationship.
3. Scroll down to the Product Relationships related list.
4. Click **New Product Relationship**.
5. On the Product Relationship Edit page, enter the following information:
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/images/icon_note.png)
    
    Note
    
    If you're using product versioning, you can’t create two product relationships based on the versions that have the same **Relationship Type** and the same **Add Mode**. The same product relationship is used for all versions of a product. See [Versioning and EPC Entities](https://help.salesforce.com/s/articleView?id=ind.comms_versioning_and_epc_entities.htm&release=264.0.0&type=5 "When you create a version of an object, commercial product, or picklist, the related entities for each are either automatically cloned or reused across the versions.").
    
    - **Product Relationship Name** describes what this relationship is, for example **Sonic Screwdriver recommends Psychic Paper**.
    - **Product** is a lookup to the product.
    - **Relationship Type** defines the action that occurs, for example, **Recommends**.
    - **Related Product** is a lookup to the product to act upon, for example, **Psychic Paper**.
        
        Use this field to specify the product for a rule to act upon. Let's say you create a rule that automatically removes a product. In this field, specify the product that you want to remove.
    - **Description** describes the relationship.
    - **Max Quantity** is the maximum number of the related product a customer can add to the original product.
    - **Min Quantity** is the minimum number of the related product a customer can add to the original product.
    - **Is Conditional** specifies if a relationship is or is not conditional.
        
        This option is only applicable if the UnconditionalProductValidation custom action is include in the Validation flow.
    - **Message** is the custom message that appears when the product is added to the cart. For more information, see [Create a Custom Product Configuration Message](https://help.salesforce.com/s/articleView?id=ind.comms_creating_a_custom_product_configuration_message.htm&language=en_US).
    - **Default Quantity** is the number of products to add, delete, recommend, and so on, for example, **1.00**.
    - **AddMode** indicates how the product should be added in relation to the original product.
    - **Context** is the context of the defined relationship, **Bundle** or **Cart**.
    
    For detailed field descriptions, see [Product Relationships Overview](https://help.salesforce.com/s/articleView?id=ind.comms_product_relationships_overview.htm&release=264.0.0&type=5 "Products can be related to one another. For example, a product may require, exclude, or recommend another product. You can define relationships between products using Product Relationship objects. Product Relationship objects are then used in compatibility rules to ensure that the correct combination of products is ordered. For example, if a customer orders Product A, the interface may recommend Product B.").
6. Click **Save**.