In Oracle Monetization Cloud, you create pricing components that represent your product offerings. Pricing components define how you sell your products and services to customers. For example, you could offer an International VIOP package for a monthly subscription fee plus usage charges. You also create pricing setup components, such as services and rating metrics. Pricing setup components define the data used in pricing components.
For background information, see Overview of Oracle Monetization Cloud.
Pricing components define how to charge for services and how to bundle services together in a package.
Use Offer Design to create pricing components:
Charge offers specify how to charge for your services; for example:
10 cents per minute for mobile phone calls
A $5 monthly fee
A charge offer is associated with a service, so when a customer purchases the charge offer, they're allowed to use the service.
Discount offers specify when and how to reduce the cost of usage charges or to change the balance of elements such as free minutes or loyalty points.
After you create charge offers and discount offers, you package them in the following pricing components:
Bundles contain one or more charge offers, discount offers, and trackers. Each bundle is associated with a single service.
Packages contain one or more bundles. You use packages to offer multiple services to subscribers. For example, you can include two bundles: one for an Internet service and one for a conferencing service.
Package lists contain a group of packages that are offered to a single type of subscriber, such as those in a regional group.
This figure shows how charge offers and discount offers are organized into bundles and packages:
Before you create pricing components, such as charge offers, you need to create pricing setup components:
Services. Services define what you base your charges on. For example, the GSM service definition enables you to charge for usage based on the customer's phone number.
Events. An event is an online action, such as a phone call, an SMS message, or a data download. Data about the event, such as when it occurred, is recorded in the cloud. For example, when a customer makes a phone call, an event is generated that contains information about that phone call, such as the date and time the call was made. Events are also recorded for customer actions such as purchasing a charge offer or inactivating a service.
Balance elements. A balance element is a currency or noncurrency asset, such as U.S. dollars or minutes. For example, for a charge of one dollar per minute, the balance element for the charge is US Dollars. When granting a customer minutes, the balance element is Included Minutes.
Rateable usage metrics (RUMs). RUMs specify how to measure events for rating; for example:
Duration: The length of an event in units such as seconds or minutes
Occurrence: The number of events generated during a specified period