This topic contains information about the settings for both basic and compound bundles.
Service Design Center uses a change management process to track and approve all changes to any product. All of these changes, including additions, edits, and deletions, must go through the promote-approve-deploy process before they become available.
Any changes you make (change a name, change a price, add or delete a product from a bundle, etc.) to any product do not affect any users that already have the product.
The General tab contains most of the settings you will configure to determine how a bundle looks, acts, is priced, and more.
These settings define how information about a product will appear to customers.
| Setting | Description |
|---|---|
| Name | Required. The name serves 2 primary purposes: it's what you see in product lists and it's what customers see as a descriptor when they are making purchase decisions. The name is limited to 115 characters. |
| Short Description | Brief plain-text information about the bundle that sometimes appears with the bundle name. |
| Marketing Message |
The Marketing Message setting is available only in compound bundles.
Descriptive rich-text information about the bundle that appears on only the pre-purchase detail page above the content you add in the Description field. You can format the content you enter in several different ways using the functions in the toolbar. This field is best for a small amount of marketing information that will help drive purchase decisions, such as offers customers will receive with purchase. Use the Description field for larger amounts of additional product information.
|
| Description |
Detailed and descriptive rich-text information about the bundle that appears on bundle detail pages. The content you enter here is seen on the product detail page both pre- and post-purchase. You can format the content you enter in several different ways using the functions in the toolbar. This field is best for providing additional details about the product, for adding details to the brief marketing message, for legal boilerplate content, and so on.
|
| Fulfillment Type |
Required. This defines the system process by which customers receive the product or fee. Currently, ItsOn Digital Delivery is the only option that is supported. Selecting any other option may produce unpredictable results.
|
Depending on what types of plans and fees are in the bundle, you may also want to provide short summaries of each. For example:
| Setting | Description |
|---|---|
| Pricing Model |
Required. Determines how the bundle price is calculated. Select from:
|
These settings determine who can receive the bundle and how a bundle's allotment can be allocated.
| Setting | Description |
|---|---|
| This compound bundle can be purchased for |
Required. Determines who can receive a compound bundle when it is purchased by a customer. Select
Gifted products cannot have more than one cycle, because when you purchase a compound bundle, you are purchasing only the first cycle, and gifting a compound bundle with more than 1 cycle would require the gift recipient to either pay for subsequent cycles or cancel the compound bundle before it renews. So if you choose
A compound bundle can be gifted only at purchase time. The purchase process of a gift requires a phone number to be input by the purchaser to identify the gift recipient. There are several issues that could occur and that would prevent the completion of a gift purchase, issues that include:
|
| Allocation |
Required. Determines how the plans in a compound bundle are allocated to subscribers. Select
The Assignable and Shareable options are viable only when the tenant offers more than one subscriber per account.
|
| Share Method |
When Shareable is selected as the Allocation setting, determines how that sharing occurs. Available only when the Allocation setting is Shareable. Select:
|
| Share Type |
Determines how allowance of products in the compound bundle can be shared by subscribers. Available only when the Allocation setting is Shareable.
Limited is considered a "hard allocation," which means that once a subscriber is allocated an amount from a product, no other subscriber can use that allocated amount of that product unless there is an explicit reallocation. The total of the subscriber allocations cannot exceed 100%. For Limited, the following is true:
Piñata is like a large glass with each subscriber having a straw. Each subscriber can consume as much of the total plan allocation as they are allocated, each allocation can be any value up to the plan allocation, and the total of all allocations can be more than 100%. The amount each subscriber actually consumes each cycle is defined only by their usage pattern. For example, you have a shared 100MB data plan. An account with 2 subscribers purchases the plan and gives each subscriber 100%. The first day of the first cycle, subscriber A uses 100MB. Subscriber B's allocation for the rest of the cycle becomes 0MB. In the second cycle, subscriber B uses 100MB in the first day. Subscriber A's allocation for the rest of the cycle becomes 0MB. For both Limited and Piñata, the total allocation to subscribers can equal less than 100%, so there could be an unallocated amount in a cycle. See Sharing Examples for information on how sharing and allocation works. The Share Type option is viable only when the tenant offers more than one type of sharing.
|
| Assignment Method |
When Assignable is selected as the Allocation setting, determines how that assignment occurs. Select:
|
There are a number of ways that customers receive bundles where sharing, assigning, and gifting settings will not be available to them. In those cases, default bundle sharablility and assignability occurs.
Some sharing and assigning is done by the bundle purchaser as part of the purchase process. In fact, some settings require sharing, assigning, or gifting selection at purchase time. But when a bundle is mandatory to be received, is received via the complimentary or provisioning API, or is received as a benefit, it is not included as a part of such a purchase flow, so sharing and assigning selections that are required within that flow cannot be made.
A specific example of this is if a bundle's Allocation setting is Assignable and the Assignment Method setting is Assignable at purchase only. If the bundle is received as a benefit, it doesn't go through that customer-facing purchase flow, and so cannot be assigned. Another example is if a bundle's This product can be purchased for setting is Gift recipient only. If this bundle was being purchased, the only option at purchase time would be to enter a phone number of a subscriber outside the account to receive the bundle. But again, if the bundle is received as a complimentary bundle, the screen to enter a phone number isn't shown, so there's no way to gift the bundle.
The general rule is that if a bundle is received outside of the customer-facing purchase flow, like when a bundle is received automatically, and has a combination of settings that require decisions only in that customer-facing purchase flow, then the bundle is assigned to the subscriber designated to receive the bundle, and if that subscriber is not known, the bundle is assigned to the first subscriber in the account.
These settings determine how and when a compound bundle is available in the store. See Plan Behavior Settings Examples for some scenarios on how these settings combine to produce desired product behavior.
Several of the behavior settings relate to aspects of the plan cycle, aspects that include:
| Setting | Description | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Recurring |
Required. Defines whether the bundle is a multi-cycle subscription, lasts for only one cycle, or lasts for one cycle with the option for customers to renew. If you selected Giftable only in the This product can be purchased for setting, the only option here is No. This is because bundles that are gifted can have only one cycle because when you purchase a bundle, you are purchasing only the first cycle, and gifting a bundle with more than 1 cycle would require the gift recipient to either pay for subsequent cycles or cancel the bundle before it renews.
Select:
Any segmentation rules that include this setting, including restrictions and offers, will treat both Yes and Optional as the same. That is, if a rule is defined to match a recurring product, the rule will match if this setting for the product is either Yes or Optional.
|
|||||||||
| Number of Cycles |
Required. This defines the number of cycles a subscriber can receive the compound bundle. The options determine if a compound bundle repeats at the end of its duration. (The duration is defined either as the account cycle, if Aligned to account cycle is Yes, or as the compound bundle's Cycle Duration value.) If so, the customer is grandfathered the compound bundle rate and attributes when it is renewed, even if you have made significant changes to the compound bundle or even deleted it from your catalog. Select from:
Compound bundles renew when they are set to an unlimited number of cycles or when they are "limited" to more than one cycle, that is, the number in the Limited to option is greater than 1. Renewing means that at the end of a compound bundle cycle's duration:
If you are going to make the compound bundle giftable, then it cannot renew and you must select the Limited to option and enter 1. This is because when you purchase a compound bundle, you are paying only for the first cycle. If gifting a compound bundle with more than 1 cycle was allowed, the recipient would be responsible for either paying for subsequent cycles or canceling the compound bundle before it renews. |
|||||||||
| Aligned to account cycle | Required. This is the alignment, and it defines when renewals occur and are billed. Available only when Number of Cycles is set to Unlimited or is set to Limited to and its value is greater than 1. Defines whether the compound bundle is billed when the account cycles or when the compound bundle is purchased. | |||||||||
| Cycle Duration |
Required. This defines how long a compound bundle cycle is. Available only when Aligned to account cycle is set to No. Select from:
|
|||||||||
| Prorated on first cycle |
Required. This is proration, and it defines how much is billed and allotted for the first cycle. Available only when Aligned to account cycle is set to Yes. Best Practice: When you have a compound bundle that has more than 1 cycle and is aligned to the account cycle, you'll almost always want to set this to Yes. If you set it to No, a customer will be charged full price for the compound bundle even if they buy it on the last day of the account cycle. While that may be OK for compound bundles with a fixed amount of consumption, your business needs may dictate otherwise, especially for compound bundles with unlimited plans For example, if if a plan in a compound bundle offers 30MB of data for $30/month and a customer whose account cycle begins on the 1st buys the plan of the 20th, they will get a prorated amount of 10MB for a prorated cost of $10. But if you offer an unlimited amount of data for $30/month and a customer whose account cycle begins on the 1st buys the plan on the 30th, they will get an unlimited amount of data for $1. So if you have unlimited plans in he compound bundle, you may want to consider setting this option to No. Even when a compound bundle is prorated normally, when it is offered in an exchange category in a carousel and a customer receives the compound bundle through the exchange category in the carousel, no proration occurs. The customer receives the full allotment for the remainder of the cycle in which it is received and is charged the full cycle price. |
|||||||||
| Terminates when all product usage allowances run out |
Available only when Number of Cycles is set to Limited to and its value is 1 because this setting is used only for one-time compound bundles. Determines if a compound bundle is terminated when the usage allowance of all the plans in the compound bundle run out. The choices are:
Note: A reason why you might want to choose No here is so that customers can upgrade one-time compound bundles if the usage allowance of all its plans run out before the expiration of the compound bundle. Once a compound bundle terminates, it can't be upgraded.
The choice here can also affect when intercept notifications are triggered. One of the intercept notification rule options is a reason, and the two choices are Plan Capped and Plan Not Present. If a bundle terminates, then it would match the Plan Not Present option in the notification. If a bundle is not terminated when the usage allowance of all the plans in the bundle run out (the No option of this setting), the bundle would still be considered active until its duration expires. This matches the Plan Capped intercept notification option, and you could design an intercept notification to provide easy upgrade options. |
|||||||||
| Visibility |
Determines whether or not the compound bundle is visible to customers. If this is set to Hide, the bundle is not visible for purchase in the store nor is it visible in a customer's account information. It is not shown as part of a bundle when included in another bundle, and usage notifications are not triggered by plans within a hidden bundle, regardless of the visibility setting of the plans. A bundle cannot be hidden unless its price is equal to 0 (zero). This is because at checkout, a non-zero priced bundle in the cart will result in a total price that is different from the sum of the prices of the visible products, which could cause customer confusion. So this setting is unavailable until a price value greater than 0 (zero) has been entered for the bundle.
|
|||||||||
| Usage Display |
This setting defines how bundle usage information is viewed on devices. Each bundle has a default set of usage information that is displayed to users that is based on other bundle behavior settings, but you can override the default and specify different usage information to be displayed on devices for that product. Select:
Custom Usage Display Options
Summary of Usage Display Option DefaultsUsage display defaults depend on your usage and duration choices:
Bar and Label Direction and PositionThe direction of bar movement and the position of labels in relation to the bar (to the right or left of the bar) depend on tenant settings and/or language (left-to-right or right-to-left) settings. First, whether the bars are count up (for example, Day 7 of 15) or count down (for example, 8 days remaining) depends on a tenant setting. Then, the direction that the bar moves (or fills) depends on a tenant setting. Finally, if there is a label, its location depends on language settings. If the language setting is left-to-right, the label will be to the right of the bar. If the language setting is right-to-left, the label will be to the left of the bar. |
| Setting | Description |
|---|---|
| Retail Price | Defines the default, standard price for the bundle. This is the price customers will see unless overridden by the Sale Price field or other available offer mechanisms. If no value is entered, 0 is used. |
| Sale Price |
Overrides the Retail Price while allowing you to keep a record of the retail price. To return to the Retail Price, delete the contents of this field. A Sale Price can affect whether customers qualify for offers (benefits and discounts), depending on the value of the Apply to sale price setting in the offer.
When a customer is viewing the catalog, both the sale price and the retail price are visible in the product listing. The exact appearance will depend on your branding. The following graphic is an example of what customers might see in a product where the Retail Price is 1.00 and the Sale Price is 0.80:
Some research suggests that consumers believe prices with more syllables are higher than the same prices with fewer syllables, and this is seen in both spoken and printed prices. Both commas and decimal points add to the "syllables," so, for example, $1,199.00 is viewed as more than $1199. ItsOn provides a client-side branding setting that can present catalog prices without the decimal and the digits after the decimal for whole number prices. If this setting were used for the example above, the values seen in the catalog presentation would be $1 and $0.80. This setting does not affect the amounts you enter in the Retail Price Price or the Sale Price fields, nor the amounts shown during checkout, in customer invoices, and in customer service records.
|
This is where you manage the products in a bundle. You can:
| Setting | Description |
|---|---|
| Sku | The product name. |
| Quantity | How many of the product are in the bundle. |
| Item Sale Price | The price of the product when it is sold as part of the bundle. |
| Options | Not used. |
Certain product types can and cannot be added to different types of bundles. The following table illustrates this.
| Basic Bundle | Compound Bundle | |
|---|---|---|
|
OK to add
|
||
|
Do not add
|
|
|
If you attempt to promote a change that includes a bundle that contains an ineligible product, the promotion will fail and you will see an error message.