Combine Pricing Models
Aria Allegro lets you create custom pricing models by combining one or more monetization capabilities using the Composite pricing model. Refer to the 4. Pricing Models section for details on the Composite pricing model.
The following example combines Progressive Tier pricing with Day of Week (Weekend/Weekday) and Time of Day (Peak/Off-Peak).
| Time of Day | Day of Week | Tier Set |
|---|---|---|
| PEAK | WEEKDAY | Tier Set 1 |
| OFFPEAK | WEEKDAY | Tier Set 2 |
| ANYTIME | ANYDAY | Tier Set 3 |
Expected Result
Based on the evaluated Time of Day and Day of Week for each usage record, the system applies the corresponding tier set and its rates.
Variants
You can combine and create custom models using any of the following:
- Usage attribute-based pricing
- Transaction attribute-based pricing (Day of Week, Time of Day, or Holiday calendar)
- Tier pricing: Quantity, Progressive, Prospective, or Volume (two-pass rating) using quantity, amount, or expression-based accumulator resources
- Any combination of allowances and accumulators in pricing
- Shared allowance or accumulator in a master plan instance hierarchy
Setup
- Add an accumulator resource for tier pricing for the usage type.
- Pre-configure the Time Model under Configurations > Models > Time Model. Select weekdays and peak hours; offset values for WEEKEND and Off-Peak are set automatically.
- Set up the plan, plan rate schedule, and plan services in core Aria.
- For the usage service, select the price offer based on the plan or rate schedule.
- Set Pricing Model to Composite.
- Select the Transaction Attribute and Tiers checkboxes. The Transaction Attributes and Tiers sections appear, and an Add Tier button becomes available.
- In the first transaction attribute group, set Day of Week to WEEKDAY and Time of Day to PEAK. Leave other fields unselected. Use Add Tiers to add tiers and rates for Tier Set 1. Refer to UC006 for Progressive Balance-based tier configuration using the accumulator from step 1. When adding rates, also add the accumulator impact for the same accumulator.
- Repeat step 4 for the remaining groupings shown in the table above.
- The rest of the setup and processing remains unchanged.

