Resources | Resources |



Price plan structure elements

A price plan includes the price method, price basis, and price points (value billing and developer application price [DAP]). The price plan is defined and maintained by the developer but must be approved by the operator using the price plan against the application. Other points follow.

  • A price plan associated with an application that uses the A-VB iBilling extension (microtransactions) includes the value billing (VB) price method, VB price ID, VB price description, and the associated price points (DAP).
  • A price plan is associated with the item’s part number.
    • For each part number, the developer must create a price plan for each operator. Price plans can be cloned so you can create a price plan as a foundation for all operators and modify the DAP for each operator.
    • For part numbers associated with public (priced) extensions, the developer must create currency-specific price plans corresponding to the target operator’s currency.
    • A single item maps to one or more part numbers. A part number can be associated with multiple items being offered based on a single price plan.
    • Developers associate items with part numbers.
  • Price plans are versioned.
  • Price plans are given an effective date to indicate an item’s availability in an operator’s catalog.
  • An operator can have only one active price plan version per part at any point in time.
  • The list price is set by the operator and defined in the operator catalog. The same part number can span multiple operator catalogs, but each operator will have a specific operator price plan for that part.
  • Make sure the individuals responsible for creating and maintaining price plans on the Distribution Extranet are assigned the Developer Extranet Administrator role.