---
schema_version: "1"
id: 53fca2cf834053f68deb2a178c861f59a7018a103f7952ac54bd000a2280fa60
title: Configuration for Offer Specification Realization
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_configuration_for_offer_specification_realization.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_configuration_for_offer_specification_realization.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8919a2861915830586295726aab779a85fe3bf235d0428a5ea13bcab3cd68805
description: Product specifications and offers can be simple (stand-alone) or part of a bundle. Offers can be associated with object types or product specifications.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Configuration for Offer Specification Realization

Product specifications and offers can be simple (stand-alone) or part of a bundle. Offers can be associated with object types or product specifications.

You can configure product specifications and offerings with these settings:

- **Specification Type** — Set what type of specification you’re creating: Offer, Product, Resource, or Service. For offer specification realization, configuring this setting is required, and it is required to add any child to a product.
- **Specification Subtype** — Select whether the specification is Simple or Bundled. Configuring this setting is strongly recommended but not required.
- **Product Specification ID** — Select the associated product specification. The **Product Specification** field is available only with simple offers.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d350880e77">
              <p style="margin-bottom:0;">Specification Type</p>
            </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d350880e83">
              <p style="margin-bottom:0;">Specification Subtype</p>
            </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d350880e89">
              <p style="margin-bottom:0;">Product Specification ID</p>
            </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Specification Type" class="slds-cell-wrap" rowspan="3" style="vertical-align:top;" headers="d350880e77 ">
              <p style="margin-bottom:0;">Offer</p>
            </td>

            <td data-label="Specification Subtype" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e83 ">
              <p style="margin-bottom:0;">Simple</p>
            </td>

            <td data-label="Product Specification ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e89 ">
              <ul>
                <li>
                  <p>Can be associated with a product specification (not resource or
                    service) or an object type, but can't be associated with both. If an
                    offer is not associated with a product specification, then it’s a
                    blended offer.</p>
                </li>

                <li>
                  <p>Cannot have child offers.</p>
                </li>

              </ul>
            </td>

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

            <td data-label="Product Specification ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e89 ">
              <ul>
                <li>
                  <p>Cannot be associated with a product specification but can have an
                    object type.</p>
                </li>

                <li>
                  <p>Can have child offers (not child product specifications).</p>
                </li>

                <li>
                  <p>Can be virtual (when the offer is a child of a parent offer) or
                    non-virtual (when the offer is a root product in a bundle).</p>
                </li>

              </ul>
            </td>

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

            <td data-label="Product Specification ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e89 ">
              <ul>
                <li>
                  <p>For backward compatibility.</p>
                </li>

                <li>
                  <p>This is the default, and the offer is treated as a bundle so it
                    can have child offers.</p>
                </li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Specification Type" class="slds-cell-wrap" rowspan="3" style="vertical-align:top;" headers="d350880e77 ">
              <p>Product</p>
              <p>Service</p>
              <p style="margin-bottom:0;">Resource</p>
            </td>

            <td data-label="Specification Subtype" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e83 ">
              <p style="margin-bottom:0;">Simple</p>
            </td>

            <td data-label="Product Specification ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e89 ">
              <ul>
                <li>
                  <p>Cannot be associated with a product specification.</p>
                </li>

                <li>
                  <p>Cannot have child product specifications (not child
                    offers).</p>
                </li>

                <li>
                  <p>Can be a child of a bundle specification.</p>
                </li>

                <li>
                  <p>Can refer to an object type.</p>
                </li>

              </ul>
            </td>

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

            <td data-label="Product Specification ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e89 ">
              <ul>
                <li>
                  <p>Cannot be associated with a product specification.</p>
                </li>

                <li>
                  <p>Can have child specifications. Can be virtual (though child
                    specifications cannot be).</p>
                </li>

                <li>
                  <p>Can refer to an object type.</p>
                </li>

                <li>
                  <p>Can be virtual (when the specification is a child of a parent
                    specification) or non-virtual (when the specification is a root
                    product in a bundle).</p>
                </li>

              </ul>
            </td>

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

            <td data-label="Product Specification ID" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e89 ">
              <ul>
                <li>
                  <p>For backward compatibility.</p>
                </li>

                <li>
                  <p>This is the default, and the specification is treated as a bundle
                    so it can have child specifications.</p>
                </li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## Rules for Configuring Offers and Specifications

When you’re configuring products with the above settings, consider the following rules.

<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="d350880e332">
              <p style="margin-bottom:0;">Type</p>
            </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d350880e338">
              <p style="margin-bottom:0;">Restrictions</p>
            </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e332 ">
              <p style="margin-bottom:0;">Associated Specification or Object Type</p>
            </td>

            <td data-label="Restrictions" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e338 ">
              <ul>
                <li>
                  <p>A product specification can be associated with an offer.</p>
                </li>

                <li>
                  <p>An offer can have only one product specification. But a product
                    specification can be associated with multiple offers.</p>
                </li>

                <li>
                  <p>A product specification cannot be associated with another
                    product specification.</p>
                </li>

              </ul>
            </td>

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

            <td data-label="Restrictions" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e338 ">
              <ul>
                <li>
                  <p>The Specification Type of a parent and a child must match for
                    bundled specification or bundled offers.</p>
                  <ul>
                    <li>
                      <p>An offer can have only child products whose
                        <strong class="uicontrol">Specification Type</strong> is set to
                        <strong class="uicontrol">Offer</strong>. An offer cannot have child product
                        specifications.
                      </p>
                    </li>

                    <li>
                      <p>A product specification can only have child products whose
                        <strong class="uicontrol">Specification Type</strong> is
                        <strong class="uicontrol">Product</strong> .
                      </p>
                    </li>

                    <li>
                      <p>Resource and Service specifications can have only child
                        products that have <strong class="uicontrol">Specification Type </strong>set
                        to the same value as the parent product.</p>
                    </li>

                  </ul>

                </li>

                <li>
                  <p>To have child products, a product must have a value set for the
                    Specification Type.</p>
                </li>

              </ul>
            </td>

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

            <td data-label="Restrictions" class="slds-cell-wrap" style="vertical-align:top;" headers="d350880e338 ">
              <ul>
                <li>
                  <p>Pricing adjustments and overrides for the products with
                    Specification Type in (Offer, Product, Null) are allowed.</p>
                </li>

                <li>
                  <p>Pricing adjustments/overrides for the products with
                    Specification Type in (Service, Resource) are allowed.</p>
                </li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## Example: Simple Offer and Simple Specification

In this example, a 4G LTE SIM card offer sells a 4G LTE SIM product specification.

![Example of the offer, product specification, and object for a SIM card](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/simple_offer___specification_sim.png)

Both the offer and the product specification have Specification Subtype set to Simple. Neither has child offers or specifications. The SIM product specification is based on a SIM card object type. The specification inherits the fields and attributes assigned to the SIM card object type. You can customize the product specification’s layout. An offer inherits the layout of its associated product specification.

## Example: Bundled Offer with Child Offers and Simple Specifications

In the following example, the Gold Mobile Bundle is a bundled offer. Because its **Specification Subtype** is set to **Bundle**, it is not associated with a product specification. It has child offers for voice, text, and data. Each of these child offers has **Specification Subtype** set to **Simple** and is associated with a product specification. The product specifications are based on different object types, each of which has defined fields and attributes that the specification inherits.

![Example of the Gold Mobile Bundle](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/bundle_offer___simple_spec_example.png)