Price bundles with coverages and subscriptions

Pricing administrators can price coverage and subscription components that are included in pick-to-order (PTO) model bundles. This support helps pricing teams define bundle-specific coverage and subscription pricing while preserving standard pricing behavior when no model-specific override is available. 

You can:

  • Include coverage and subscription components in PTO model structures. 
  • Price coverages within a model separately from standalone coverage prices. 

  • Use model-specific coverage pricing when a coverage and covered item are both inside the bundle. 

  • Use relationships defined in Oracle Fusion Product Management to determine which model components a coverage can cover when cascade behavior isn’t used. 

  • Use cascade behavior to apply a coverage to all coverable ATO items in the model. 

  • View coverage and subscription component lines from the model structure, and open the related pricing detail pages.

Try it out

  1. Open a price list. 
  2. Add or select a PTO model. 
  3. In the model and components view, review the coverage and subscription components in the structure. 
  4. Open the coverage or subscription details from the component line. 
  5. Review standard prices. 
  6. Add or update model-specific prices where needed. 
  7. Price an order that includes the PTO model with coverage or subscription items. 
  8. Note that you’ll have to supply override pricing for model components of the ATO. 

Enable selling of bundles containing subscriptions and coverage items. Allow setting of bundle-specific pricing for all items.

Steps to enable and configure

Prerequisites 

Make sure these tasks are already done: 

  • Create the PTO model in Product Management. 

  • Add coverage or subscription items as child components in the PTO model where supported. 

  • Set up Product Management relationships for coverage items when coverage should apply only to related model components. The Product Management relationships are set up on the covered items. 

  • Use cascade behavior on the ATO root when you want to apply coverage to all coverable ATO items in the model. 

Steps to enable and configure 

  1. Set up the PTO model and related coverage or subscription items in Product Management. 

  1. Set up bundle prices in Oracle Fusion Pricing. 
    a. Review standard coverage or subscription prices. 
    b. Define model-specific prices when the bundle requires prices that differ from standalone pricing. 
    c. Use coverage UOM, covered UOM, charge, price, frequency, start date, and end date details as needed. 

  1. For subscriptions, review standard and model-specific charges or rate plans. 

  1. For coverages, review standard coverage pricing and define model-specific coverage prices where needed. 

  1. Use the cascade setting on the ATO model root when coverage should apply to all coverable ATO items in the model.

Model view of root and options

Model view of root and options

Set model-specific pricing 

  • From the model and components tab in the price list, search for the model item and select the structure icon to navigate to the model view 

  • Click the Select All icon at the top of the column and select Enter Prices Manually to add prices for model components. This has already been done for this screenshot. 

  • Note that the component path designates the exact place in the model hierarchy for each item 

Model view with additional components - subscriptions and coverages

Model view with additional components - subscriptions and coverages

Scroll down to view additional components of the model. Note that for subscriptions and coverage products, there are pricing details on additional pages. Select View details. 

Model-specific rate plans

Model-specific rate plans

Rate plans are supported for subscriptions that are components of a model. They’re also supported for subscriptions at the root of a model. Note that only active rate plans are available at run time. 

If an active rate plan is set up for the subscription that’s used when the subscription is ordered outside of the model, then it can be used within the model. However, a model-specific rate plan can be set up only for use within the model. In that case, the model-specific rate plan always takes precedence over the standard rate plan. 

Note that a subscription can be set up with standard charges or a rate plan, but not both. 

Select the active rate plan name to see the rate plan details. 

Rate plan details

Rate plan details

Rate plans can contain both charges and entitlements. 

Charge types include one-time charges, recurring charges, and usage charges. Multiple charges of each type are supported.

Model-specific subscription pricing

Model-specific subscription pricing

Subscriptions can be priced with recurring and non-recurring (one-time) charges without setting up a rate plan. In this case, the charges set up for the subscription that’s sold stand-alone (outside of the model), if they were set up, are displayed in the Standard tab. You can also set up model-specific charges, as shown here, that override any standard charges when the subscription is purchased as part of the model.

Model-specific coverage pricing

Model-specific coverage pricing

Coverages are supported as components of a model.  You can use coverages to cover other components of the model and also the model root. Product Management relationships are used to identify which items in the model may be covered by each coverage item. 

Coverages can be priced with recurring and non-recurring (one-time) charges. The charges set up for the coverage that’s sold stand-alone (outside of the model), if they were set up, are displayed in the Standard tab. You can also set up model-specific charges, as shown here, that override any standard charges when the subscription is purchased as part of the model.

Standard coverage pricing

Standard coverage pricing

Here’s the view of the standard pricing of the coverage item, as seen from the model view. In this case, there’s model-specific pricing, so at runtime, the standard pricing isn’t used. But the standard pricing is displayed for reference. 

 Hybrid bundle sales order

Hybrid bundle sales order

Here’s a sales order for a hybrid bundle containing an assemble-to-order (ATO) item plus a subscription and coverage items.  Each charge type is displayed separately on the sales order. You can click the link on each charge to see the charge breakdown, or you can scroll to the structure icon to bring up the configuration summary to view the pricing for each component. Rate plans are displayed on the configuration summary page. They can be negotiated before the order is submitted. 

Configuration summary view for sales order – root level

Configuration summary view for sales order – root level

The configuration summary shows the hierarchy of the model, beginning with the root. Price types and pricing are displayed along with supporting attributes. This is the same view that’s presented when exiting the product configurator. 

Configuration summary view - coverage and subscription

Configuration summary view - coverage and subscription

This section of the configuration summary shows the individual instances of the coverage items and the subscription item.   

There are 2 coverage items – Big Computers Standard Support and Warranty, priced at $100/year, and Big Computers Critical Support and Warranty, priced at $300/year. Both are model-specific prices. 

At the bottom of the list is the subscription, Vision DNA Essentials – 3 Years. There’s a recurring price of $50/month and an activation fee of $25 for this item. 

Configuration summary view - rate plan access

Configuration summary view - rate plan access

Scrolling to the right in the configuration summary view provides access to the rate plan attributes. The two fees for this subscription are associated with the C-SFTWR-SUB-3 Standard Plan. The icon to the right of the plan name provides the link to negotiate the plan during order creation. 

Tips and considerations

  • You can set up hybrid model pricing only on Pricing and Order Management pages that were redesigned.    

  • You don’t have to set up standard pricing for subscriptions and coverages to set up model-specific pricing. Standard pricing is set up under the subscription and coverages tabs in the price list page, if desired. 

  • You have to set up model-specific pricing for any ATO and its components that are included in the hybrid bundle. Second-level model pricing isn’t supported. 

  • Note that discounts applied to components of the bundle aren’t applied to any coverage items in the bundle. This is consistent with pricing behavior for coverages outside of bundles.

Key resources

Manage Price Lists

Access requirements

Privileges

Privilege status Privilege names and codes
Existing Manage Pricing Rules (QP_MANAGE_PRICING_RULES)
Existing View Price Lists (QP_VIEW_PRICE_LISTS_PRIV) 
Existing Manage Price Lists (QP_MANAGE_PRICE_LISTS_PRIV)
Existing Approve Price Lists (QP_APPROVE_PRICE_LISTS_PRIV)
Existing Generate Price Book (QP_GENERATE_PRICE_BOOK_PRIV) Generate a price book from user-selected parameters.
Existing View Price Books (QP_VIEW_PRICE_BOOKS_PRIV) Allows viewing of price books. 
Existing Manage Price Books (QP_MANAGE_PRICE_BOOKS_PRIV)  Allows creation, update, deletion, and viewing of price books.
Existing Delete Price Books (QP_DELETE_PRICE_BOOKS_PRIV)  Allows deletion of price books.
Existing Publish Price Books (QP_PUBLISH_PRICE_BOOK_PRIV)  Publish a price book that was previously generated.