Pricing and Rating
Product Item Rate (or Product line item price) is the rate you associate with a Product Item.
Amberflo provides full range of rate types ranging from the traditional fixed and recurring to usage-based.
In addition to creating flexible usage-based pricing plans, you can also further customize plans with fixed-rate add-ons. These add-ons can be recurring like a subscription or platform fee, or restricted to one-time (or X billing periods) to handle startup costs or other time-restricted offers.
By combining usage-based and fixed rate elements, Amberflo allows you to create pricing plans that are:
-Usage-based
-Hybrid (include usage-based and fixed charges)
-Fixed charges only (subscription)
![](https://files.readme.io/ff04204-Screenshot_2023-07-07_at_9.25.58_AM.png)
Usage-based rate models we support out-of-the-box include:
- Per unit
- Per unit with dimensions
- Per block
- Per block with dimensions
- Tiered
- Tiered with Dimensions
- Volume
Per Unit
A usage-based model where a per-unit price is set. For this model, you can also specify a number of 'Included Units' which will be free of charge; after the included units are consumed, the rate you define will be applied automatically. The bill amount is calculated by multiplying the amount of each unit consumed with the per unit price point(s), taking into account any included units.
Example -
100 support hours consumed
$50 per support hour
Bill amount = 100 hours x $50 per hour = $5000
Per Unit with Dimensions
A usage-based model where the per-unit price is set according to any combination of dimension values. For this model, you can also specify a number of 'Included Units' for each dimension-value combination which will be free of charge; after the included units are consumed, the rates you define will be applied automatically. The bill amount is calculated by multiplying each group of units having the same dimension values with their respective per unit price points and then summing the totals for each group, taking into account any included units.
Example -
10 support hours consumed in USA
40 support hours consumed in EMEA
50 support hours consumed in APAC
Per unit rates defined according to the table below:
Product Item | Dimension: Value | Per Unit Rate |
---|---|---|
Support hours | region: USA | $30 |
Support hours | region: EMEA | $40 |
Support hours | region: APAC | $50 |
Bill amount = (10 hours x $30 per hour)+(40 hours x $40 per hour)+(50 hours x $50 per hour) = $300 + $1600 + $2500 = $4400
Per Block
A usage-based model where the price is set per block of units. You define the block size and the per-block price. For this model, you can also specify a number of 'Included Units' which will be free of charge; after the included units are consumed, the rate you define will be applied automatically. The bill amount is calculated by dividing the billable usage by the block size - this gives the number of blocks consumed (round up any decimal values to next whole number).
Example -
5900 API calls made
Block size = 500
Price per block = $10
Blocks consumed = 5900/500 = 11.8 -> 12
Bill amount = 12 x $10 = $120
Per Block with Dimensions
A usage-based model where the price is set per block of units according to any combination of dimension values. For this model, you can also specify a number of 'Included Units' for each dimension-value combination, which will be free of charge; after the included units are consumed, the rates you define will be applied automatically. The bill amount is calculated by applying the appropriate per block price to each group according to the dimension values, then sum the totals for all the groups.
Example -
300 API calls in USA
750 API calls in EMEA
1000 API calls in APAC
Per block rates defined according to the table below:
Product item | Dimension: Value | Block Size | Per Block Rate |
---|---|---|---|
API calls | region: USA | 250 | $5 |
region: EMEA | 500 | $7 | |
region: APAC | 500 | $9 |
Blocks consumed (USA) = 300/250 = 1.2 -> 2
Bill for API calls in USA = 2 x $5 = $10
Blocks consumed (EMEA) = 750/500 = 1.5 -> 2
Bill for API calls in EMEA = 2 x $7 = $14
Blocks consumed (APAC) = 1000/500 = 2
Bill for API calls in APAC = 2 x $9 = $18
Bill amount = $10 + $14 + $18 = $42
Tiered
Per unit/per block price points are grouped into tiers based on the quantity of units consumed. Users can charge per unit or define block sizes for each tier. The bill amount is calculated by multiplying the amount consumed in each tier with that tier's rate. Summing the totals for each tier gives the total amount.
Example -
500,000 API calls made
Tiered rates defined according to the table below:
Product Item | Quantity Consumed | Rate | Block size |
---|---|---|---|
API calls | 0 - 999 | $0 | 1 |
1,000 - 9,999 | $2 | 250 | |
10,000 - 99,999 | $1 | 500 | |
100,000 - 999,999 | $0.50 | 1000 |
First tier = ($0 x 999) = $0
Second tier: (8999/250) = 35.9 -> 36
36 x $2 = $72
Third tier: (89999/500) = 179.9 -> 180
180 x $1 = $180
Fourth tier: (899999/1000) = 899.9 -> 900
900 x $0.50 = $450
Bill amount = $0 + $72 + $180 + $450 = $702
Tiered with Dimensions
Per unit/per block price points are grouped into tiers according to any combination of dimension values associated with that meter/product item. Users can define the tiers according to dimension-value combinations, and select whether to charge per unit or define block sizes for each tier. A new tiered scheme can be created for each dimension-value combination. The bill amount is calculated by multiplying the amount consumed in each tier with that tier's rate then summing the totals for each tier to give the total amount.
Example -
500,000 API total calls made:
-100,000 calls made in USA
-200,000 calls made in EMEA
-200,000 calls made in APAC
Tiered rates defined according to the table below:
Product Item | Dimension: Value | Quantity Consumed | Rate | Block Size |
---|---|---|---|---|
API calls | region: USA | 0 - 9,999 | $0 | 1 |
10,000 - 99,999 | $2 | 250 | ||
100,000 - 499,999 | $1 | 500 | ||
region: EMEA | 0 - 9,999 | $0 | 1 | |
10,000 - 99,999 | $2.50 | 250 | ||
100,000 - 499,999 | $1.25 | 500 | ||
region: APAC | 0 - 9,999 | $0 | 1 | |
10,000 - 99,999 | $2.25 | 250 | ||
100,000 - $499,999 | $1.10 | 500 |
Bill for API calls in USA -
First tier = ($0 x 9999) = $0
Second tier: (89999/250) = 359.9 -> 360
360 x $2 = $720
Third tier: (2/500) = .004 -> 1
1 x $1 = $1
Total for API calls in USA = $0 + $720 + $1 = $721
Bill for API calls in EMEA -
First tier = ($0 x 9999) = $0
Second tier: (89999/250) = 359.9 -> 360
360 x $2.50 = $900
Third tier: (100002/500) = 200.004 -> 201
201 x $1.25 = $251.25
Total for API calls in EMEA = $0 + $900 + $251.25 = $1151.25
Bill for API calls in APAC -
First tier = ($0 x 9999) = $0
Second tier: (89999/250) = 359.9 -> 360
360 x $2.25 = $810
Third tier: (100002/500) = 200.004 -> 201
201 x $1.10 = $221.10
Total for API calls in APAC = $0 + $810 + $221.10 = $1031.10
Total bill amount = Bill for USA + Bill for EMEA + Bill for APAC = $721 + $1151.25 + $1031.10 = $2903.35
Volume
This is very similar to tiered pricing, except only one rate is used to calculate the bill amount. Per unit/per block prices are calculated entirely according to the rate set for the tier containing the quantity consumed. This rate model is typically used to incentivize higher usage; as usage increases, the per-unit price decreases.
Example -
100,000 API calls made
Rate tiers defined according to the table below:
Product Item | Quantity Consumed | Rate | Block size |
---|---|---|---|
API calls | 0 - 9,999 | $5 | 500 |
10,000 - 49,999 | $2 | 500 | |
50,000 - 99,999 | $1 | 500 | |
100,000 - 499,999 | $0.50 | 500 |
Since the customer made 100,000 calls, we use the tier which includes that quantity -
Blocks consumed = (100,000/500) = 200
Use the rate from tier 4 -
Bill amount = 200 x $0.50 = $100
Updated 9 months ago