Product Administration Guide > Customizable Product User Interface >

About Pricing Integration

Siebel ePricer works in conjunction with Siebel eConfigurator to provide updated pricing information during a configuration session. There are two methods for obtaining updated pricing information: automatic and manual. You select which method to use when you select a base theme.

Automatic price updates is the default method and is the method used by the default base theme. Base themes that provide manual price updates are labeled as such when displayed in the dialog box where you select the base theme. Unless labeled otherwise, base themes use the automatic price update method.

With automatic price updates, the pricing of the entire customizable product is updated when the session starts, each time a new solution is created during the session, and when the session ends. When the user picks a product, the price of the product displays automatically.

With manual price updates, the pricing of the entire customizable product is updated when the session starts, when the user clicks the Check Price button, and when the session ends. During the session, prices are not updated automatically when the user picks a product. The user must click the Check Price button to obtain the prices of the products they select.

When a price update occurs during a configuration session ePricer pricing elements trigger in the following order:

1. Component-based pricing adjustments
2. Attribute-based pricing adjustments
3. Customizable product pricing factors (single, bundle, matrix, and script-based only). Aggregate and volume discount pricing factors do not trigger.
4. Price List pricing factors (single, bundle, matrix, and script-based only). Aggregate and volume discount pricing factors do not trigger.

When the session ends, ePricer pricing elements trigger in the same order. Volume discount and aggregate pricing factors also trigger for Quotes, Orders, and agreements.

If a customizable product contains other customizable products, only the pricing model for the parent customizable product is triggered during a price update. For example, customizable product CP1 contains customizable product CP2. During a configuration session for CP1, the pricing factor models for CP2 are not triggered during a price update.

When building a customizable product, use automatic price updates. Switch to manual price updates only if performance becomes too slow. The sequence of events after the user selects a product is as follows:

• eConfigurator engine computes a new solution
• eConfigurator engine forwards the solution to ePricer
• ePricer returns pricing for all items in the solution
• eConfigurator redisplays the selection page

If you do not need interactive pricing, consider switching to manual price updates.