---
schema_version: "1"
id: 4c9bcc924c85122bd400b38e83dffc76540bbcffca67762ca5062b77ead16900
title: Create Offerings in the Product Designer
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_create_offerings_in_the_product_designer.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_create_offerings_in_the_product_designer.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 01d99be9fccdb40a3c804a66d328c5532171c9b89cdfd8586bcae71933d77665
description: After you define product specifications, you can associate them with prices, promotions, and context rules to create offers or commercial products that customers can purchase.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Create Offerings in the Product Designer

After you define product specifications, you can associate them with prices, promotions, and context rules to create offers or commercial products that customers can purchase.

![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

- In the **Edit Attribute** section, you can clear any value regardless of whether the attribute is marked as required. While a red asterisk indicates required fields (excluding Checkbox, Picklist, Multi-select Picklist, or Runtime Configurable attributes), the system allows blank entries. Additionally, the **Configurable** checkbox remains uneditable.
- In the **Details** tab, all fields are editable; however, the system validates all required attributes during the save process. If a required attribute is missing—indicated by a red border—you cannot save the record. This validation applies to all required fields except for Checkbox, Picklist, Multi-select Picklist, and Runtime Configurable attributes.
- In the **Structure** tab (Attribute Override), you can clear any value regardless of whether the attribute is marked as required. Additionally, the **Configurable** checkbox is uneditable in this view.
- While the system permits blank required attributes during design time, you should always assign default values. This prevents validation errors and transaction failures during runtime.

1. From the Vlocity Product Designer app, click the down arrow button, and select **Products**.
    
    ![Vlocity product designer app](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/resources-product/images/epc_select_products_upc.png)
2. If the view isn’t **All Products**, click the menu, and select **All Products** from the list.
    
    ![Tip](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_tip.png)
    
    Tip
    
    We recommend that you make **All Products** the default view. After you select **All Products**, click the pin icon to make it the default view.
    
    ![all products as default view](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/resources-product/images/epc_spec_prod_view_upc.png)
3. Click **Create New Product**.
4. In the New Product: Product page, enter the following information.
    
    <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
            <colgroup>
              <col>
              <col>
            </colgroup>
            <thead class="slds-text-title_caps ">
              <tr class="">
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d324083e156">
                  <p style="margin-bottom:0;">Field</p>
                </th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d324083e162">
                  <p style="margin-bottom:0;">Description</p>
                </th>
              </tr>
            </thead>
            <tbody>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Product Name</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>Enter a name for the product. Product names appear to customers in the product catalog.</p>
                  <p>Example: iPhone 6S Plus</p>
                  <p style="margin-bottom:0;">Example: Fixed Energy</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Product Code</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>A unique code for the product.</p>
                  <p>Example: VLO-MOB-0003</p>
                  <p style="margin-bottom:0;">Example: PD_FIXED_ENERGY</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Product Description</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">Enter a description that is shown at runtime in the Product Details window of Industries Cart. It's also searchable in the Search dialog.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Product Family</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>Select a group of products that this specification belongs to.</p>
                  <p>Leave this field blank if this offer doesn't fit into a product family or if you don't use product families.</p>
                  <p style="margin-bottom:0;">If the Product Family list doesn’t show all active values, click <strong class="uicontrol">Refresh Tab </strong>from the tab menu for a product.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Specification Type</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">Select <strong class="uicontrol">Offer</strong>. See <a href="https://help.salesforce.com/s/articleView?id=ind.comms_configuration_for_offer_specification_realization.htm&amp;release=264.0.0&amp;type=5" title="Product specifications and offers can be simple (stand-alone) or part of a bundle. Offers can be associated with object types or product specifications.">Configuration for Offer Specification Realization</a>.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Product Spec</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>This field is reserved for the Offer Specification Realization functionality.</p>
                  <p>See <a href="https://help.salesforce.com/s/articleView?id=ind.comms_configuration_for_offer_specification_realization.htm&amp;release=264.0.0&amp;type=5" title="Product specifications and offers can be simple (stand-alone) or part of a bundle. Offers can be associated with object types or product specifications.">Configuration for Offer Specification Realization</a>.</p>
                  <p style="margin-bottom:0;">Select a product specification for an offering. You can only select this option if Specification Type is set to Offer.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Object Type</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>Select the object type you have previously created.</p>
                  <p>Example: Smart Phone type</p>
                  <p style="margin-bottom:0;">Example: Commodity Offer</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Specification Sub Type</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>This field is reserved for the Offer Specification Realization functionality.</p>
                  <p>Select one of the following types or leave it blank for backward compatibility. If blank, the product is treated as a bundle and can have child specifications.</p>
                  <ul>
                    <li>
                      <p>Simple — The product doesn’t have child specifications and can’t be associated with another product specification. It can be a child of a bundle product specification and can refer to an object type. In the Structure view, it can’t be set as a <strong class="uicontrol">Virtual Item</strong>.</p>
                    </li>

                    <li>
                      <p>Bundle — The product can have child specifications and refer to an object type. In the Structure view, it can be set as a <strong class="uicontrol">Virtual Item</strong> when the specification is a child of a parent specification. But it can’t be virtual when the specification is a root product in a bundle.</p>
                    </li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Help Text</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">Enter the text that displays at runtime in the Industries Cart if users hover over the information icon (lowercase letter “i”).</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Status</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">This field is a customer-defined.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Orderable</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">Enable the offering to be ordered. This setting is typically enabled for offerings and not the product specifications that the offerings are based on.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Type</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">This field is customer-defined. Use it to classify products.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Version Label</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>This field is reserved for Versioning functionality. See <a href="https://help.salesforce.com/s/articleView?id=ind.comms_product_versioning_start_and_end_dates.htm&amp;release=264.0.0&amp;type=5" title="A product version’s Versioning Start Date Time and Versioning Start End Time fields are key for runtime use. The version of a product is picked during runtime, and the available version is derived from these fields.">Product Versioning Start and End Dates</a>.</p>
                  <p style="margin-bottom:0;">Enter a value to indicate a new version, such as v2.0. You can only set this field if Specification Type is set to Product or Offer.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Version Start and End Date</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>This field is reserved for Versioning functionality. See <a href="https://help.salesforce.com/s/articleView?id=ind.comms_product_versioning_start_and_end_dates.htm&amp;release=264.0.0&amp;type=5" title="A product version’s Versioning Start Date Time and Versioning Start End Time fields are key for runtime use. The version of a product is picked during runtime, and the available version is derived from these fields.">Product Versioning Start and End Dates</a>.</p>
                  <p style="margin-bottom:0;">Enter a date or date range when the new version is available. The dates for different versions of a specification can’t overlap. You can only set this field if Specification Type is set to Product or Offer.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Lifecycle Status</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>This field is reserved for Versioning functionality. See <a href="https://help.salesforce.com/s/articleView?id=ind.comms_product_versioning_start_and_end_dates.htm&amp;release=264.0.0&amp;type=5" title="A product version’s Versioning Start Date Time and Versioning Start End Time fields are key for runtime use. The version of a product is picked during runtime, and the available version is derived from these fields.">Product Versioning Start and End Dates</a>.</p>
                  <p>Set and track the lifecycle status of the specification. You can only set this field if Specification Type is set to Product or Offer.</p>
                  <p>When releasing a hierarchy of products, start releasing products in a bottoms-up approach: Release the leaf nodes first and release going up the product hierarch to the top of the hierarchy.</p>
                  <div class="slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium">
                    <div class="slds-media slds-media_responsive">
                      <div class="slds-media__figure"><span class="slds-icon_container slds-icon_container_circle slds-icon-note-error"><img style="margin-bottom:0;" src="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_warning.png" alt="Warning"></span></div>
                      <div class="slds-media__body" style="padding-top:.5rem;padding-bottom:.5rem;" id="comms_create_offerings_in_the_product_designer__note_a51c3b7e71e22489cdedf94ed987a195"><a name="comms_create_offerings_in_the_product_designer__note_a51c3b7e71e22489cdedf94ed987a195"><!-- --></a><span class="slds-text-title_caps">Warning</span>
                        <p>Don’t use the Released value in Fall '20 because it can have undesirable effects.</p>
                      </div>
                    </div>
                  </div>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Active</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p>Indicate that the offering is active and in use.</p>
                  <div id="comms_create_offerings_in_the_product_designer__uuid-782d3fdf-f56c-953e-3e55-c21c9419ba17_uuid-31ef007f-079d-8827-7ee6-bac4f392ff76"><a name="comms_create_offerings_in_the_product_designer__uuid-782d3fdf-f56c-953e-3e55-c21c9419ba17_uuid-31ef007f-079d-8827-7ee6-bac4f392ff76"><!-- --></a>
                    <div>
                      <p>Deactivating a product after it's Active and available to sales channels can have multiple impacts, such as product hierarchies, rules, and existing orders. For example, a deactivated product is removed from the Industries Cart, but the Cart price isn’t changed.</p>
                    </div>
                  </div>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Selling Start and End Date</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">Enter a date or date range when a commercial product can be ordered and sold.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">Fulfillment Start Date</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">Enter a date when a commercial product is ready to be fulfilled. By default, this date is the same as the selling date, but it can be a future date to support pre-orders.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e156 ">
                  <p style="margin-bottom:0;">End of Life Date</p>
                </td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d324083e162 ">
                  <p style="margin-bottom:0;">Enter a date when a commercial product is no longer available to be fulfilled.</p>
                </td>

              </tr>
            </tbody>
          </table>
5. Click **Done**.

The offering is saved, and you can add attachments, set attribute rules, or add context rules.

[Create Product Bundles in the Product Designer](https://help.salesforce.com/s/articleView?id=ind.comms_create_product_bundles_in_the_product_designer.htm&release=264.0.0&type=5 "Creating a product bundle as an offer involves creating the structure of the bundle, including the main product and the product child items that comprise the bundle offer.")

- **[Configure Attribute Rules for Offerings in the Product Designer](https://help.salesforce.com/s/articleView?id=ind.comms_configure_attribute_rules_for_offerings_in_the_product_designer.htm&release=264.0.0&type=5)**  
    If you create a new simple product offering from a simple product specification using Offer Specification Realization, only attribute assignments are available for the simple product offering from the product specification. The attribute rules, prices, and costs of the product specification are not available to the simple product offering. If you create a simple offer realizing a composite product specification, the attribute rules, prices, and costs on the child product specification are honored at runtime. Upon adding the simple offer to the cart, each child product specification manifests as a separate line item and all the rules, pricing and cost defined on the child product specification are executed/applied.
- **[Add Attachments in the Product Designer](https://help.salesforce.com/s/articleView?id=ind.comms_add_attachments_in_the_product_designer.htm&release=264.0.0&type=5)**  
    You can upload files for an offering or specification, including images and documents. On the Attachments tab, you can indicate the product image to show across different channels. Previews of images and videos are shown in the Details tab for a product.
- **[Apply Context Rules to an Offering in the Product Designer](https://help.salesforce.com/s/articleView?id=ind.comms_apply_context_rules_to_an_offering_in_the_product_designer.htm&release=264.0.0&type=5)**  
    With a qualification rule, you can control whether an offering appears in the Qualified or Disqualified tab in the industries CPQ Cart. A qualification rule determines a customer's eligibility to receive a product or promotion before it is added to the cart. You can assign a rule to a product specification or offering.