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.

Specification Type	Specification Subtype	Product Specification ID
Offer	Simple	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. Cannot have child offers.
	Bundle	Cannot be associated with a product specification but can have an object type. Can have child offers (not child product specifications). 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).
	null	For backward compatibility. This is the default, and the offer is treated as a bundle so it can have child offers.
Product Service Resource	Simple	Cannot be associated with a product specification. Cannot have child product specifications (not child offers). Can be a child of a bundle specification. Can refer to an object type.
	Bundle	Cannot be associated with a product specification. Can have child specifications. Can be virtual (though child specifications cannot be). Can refer to an object type. 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).
	null	For backward compatibility. This is the default, and the specification is treated as a bundle so it can have child specifications.

Rules for Configuring Offers and Specifications

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

Type	Restrictions
Associated Specification or Object Type	A product specification can be associated with an offer. An offer can have only one product specification. But a product specification can be associated with multiple offers. A product specification cannot be associated with another product specification.
Bundles	The Specification Type of a parent and a child must match for bundled specification or bundled offers. An offer can have only child products whose Specification Type is set to Offer. An offer cannot have child product specifications. A product specification can only have child products whose Specification Type is Product . Resource and Service specifications can have only child products that have Specification Type set to the same value as the parent product. To have child products, a product must have a value set for the Specification Type.
Pricing and Promotions	Pricing adjustments and overrides for the products with Specification Type in (Offer, Product, Null) are allowed. Pricing adjustments/overrides for the products with Specification Type in (Service, Resource) are allowed.

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

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.