Products & Pricing
Products consist of Data Sources that are sold as a package to customers. Products have associated subscription terms and fees, overage rates, quotas, SLAs, and more attached to them.
Last updated
Products consist of Data Sources that are sold as a package to customers. Products have associated subscription terms and fees, overage rates, quotas, SLAs, and more attached to them.
Last updated
Products are used to apply pricing and billing rules to usage created via . Once a product is built, you can assign one or more Subscribers to the product by creating a .
When configuring a product, the default options allow you to define a recurring charge, determine the invoicing periods (i.e. how often invoices are generated), define pricing for different volumes of usage, whether you wish to invoice in advance or arrears, and how Subscribers will pay for the product.
Basic pricing rules are established by creating pricing tiers as shown below. In Plan 1, subscribers to this product will pay a Recurring Charge of 100 per invoice period, and usage charges will vary depending on the number of transactions. In addition, you can choose whether each transaction is charged based on the tier it falls in or whether a Subscriber receives the price of the highest tier for all transactions once a higher tier is reached.
In Plan 2 below, customers are charged per 'group' of transactions. For the first $100 transactions, customer are charged a flat fee of $100, then $90 for the next 100, $80 for transactions 201-300, and .70 / transaction after that.
These models can be mixed & matched as needed to create the plans that match your business model.
Lastly, tf you wish to create a price model without price tiers, you could also create just one tier. In this model, each transaction would be charged a flat fee regardless of volume.
Plans 1 & 2 are some of the most basic pricing structure supported by Revenium. Many additional complex pricing configuration options are explained below.
Product Name
Shown in storefronts to display the name of your product to end subscribers
Invoicing Period
Determines how often an invoice is generated and when usage counters and charges reset. In addition to the standard options like monthly & annual, the following options are supported.
5 Minutes (no synthetic transactions) - for one hour, this will open and close an invoicing period every 5 minutes for every active Subscription you create for this product. This will generate subscriber notifications and invoices each five minutes so that you can test that everything is working as expected without waiting for actual settlement periods to close.
5 Minutes (randomized synthetic transactions) - this option behaves identically to the previous option, but in addition, a randomized number of transactions will be simulated for sources included in the products throughout the one-hour period so you can check how charges are applied to randomized usage scenarios and ensure your product's payment model is configured as you intended.
Custom - this selection allows you to define non-standard invoicing periods (i.e. every 2, 3, or 6 months)
Invoice Schedule
In Advance
- this will send an invoice for setup fees and recurring fees at the beginning of each invoice period. Because usage can only be charged for after it occurs, usage fees are still billed in arrears.
In Arrears
- this invoices all charges at the end of each invoice period.
Payment Options
Invoice Only
- Revenium sends invoices to customers to be paid manually.
Invoices with External Payment Updates
- Same as ‘Invoice Only,’ but Revenium also tracks invoice payment status based on updates from your financial system to Revenium. (this allows you to track overdue invoices and suspend subscriptions for subscribers with overdue payments)
Send invoices to Subscription owners
By default, this option is selected. In general, only unselect this box if you are set up to provide your own invoicing based on usage data exported from Revenium.
Automatically resend unpaid invoices
if you are updating Revenium when your invoices are paid in an outside system (often Oracle, SAP, etc.), checking this option will resend your subscribers invoices on a monthly basis if they are unpaid. This will occur for up to four times if an invoice remains unpaid before stopping. Each invoice will be titled differently (i.e. second notice, third notice, final notice)
Allow immediate cancellations and pro-rated invoices
By default, Subscriptions that are deactivated will remain valid until the end of their current invoicing period. This means that a subscriber with monthly invoicing who cancels a Subscription in the middle of the month will continue to have access to their products through the end of the month (and pay for the entire month).
However, if you select the 'allow immediate cancellations' option, as soon as an associated Subscription for this product is canceled, it will take effect immediately, and a pro-rated invoice will be created to charge only for the time of the subscription prior to cancellation.
Metering Elements allow you to modify the amount charged based on key value pairs received in the transactions sent to Revenium (i.e. to enable usage-based charges that scale based on metrics other than transaction counts).
When adding Metering Element charges to a product, you can choose from the following charge models.
Average of All Values Received
Element Description
Element Charge
Average all values received for a given element in a period and multiply that value by a defined charge.
Maximum of All Values Received
Element Description
Element Charge
Find the maximum of all values received for a given element in a period and multiply that value by a defined charge.
Sum Element Values Received
Element Description
Element Charge
Sum all values received for a given element in a period and multiply that value by a defined charge.
Count Element Occurrences
Element Description
Element Charge
Count the number of times a given element is observed (with any value) in a period and multiply the count by a defined charge.
Count Unique Values Received
Element Description
Element Charge
Count the number of unique values received for a given element and multiply the count by a defined charge.
On each occurrence of specific value
Element Description
Element Charge
Element Value
Count the number of times a specific value is received for a defined element and multiply the count by a defined charge. (Example: match every time the value "Germany" is received in an element named "Country" and charge $2 / occurrence)
On first occurrence of specific value
Element Description
Element Charge
Element Value
Count the first time a specific value is received for a defined element and charge a defined amount. (Example: match the first time the value "Germany" is received in an element named "Country" and charge $2 / occurrence)
It is also possible to create products with no associated pricing. This is sometimes useful in scenarios like this:
for internal reporting purposes
to generate the additional analytics that come from products versus from API Sources alone.
to limit usage of a Product in a free tier by enforcing quotas without costs
To create a free product, you simply do not enter pricing for usage and configure all other options as you normally would. Depending on your use case, you may wish to disable the option to "Send Invoices to Subscription Owners" for free products.
The product configuration form also includes a number of that can be added by checking the appropriate box in the creation form.
Stripe-Enabled Payments
- external will display here as options to automatically collect payment via credit card (the payment status of stripe-enabled payments is automatically tracked in Revenium)
must be created prior to adding them to a product.
The Product Quota field defines a limit on the number of transactions to be enforced. Depending on the payment model chosen, the behavior of this field differs (either to absolutely block traffic once the quota is reached or to begin rating transactions at the average rate once the quota is reached). Note that quota enforcement is dependent on the type of Revenium type chosen. Please contact us for questions on how to enable quotas for a specific connector.
Default Quota Notification Threshold allows you to set a percentage of the maximum transactions when a notification will be sent to the configured e-mail addresses chosen in the Provider Notification Addresses field on page 2 of the product creation process. Note that end subscriber notifications can be configured for each that is created for a product.
Custom allow you to select a previously configured Pricing Rule that will apply for Subscriptions issued under this product.
Revenium supports that are created to API Gateways. This allows you to publish products that are created in Revenium to supported gateways and API storefronts for purchase by end subscribers.
Create a linked gateway product: Select from a previously configured . Using a linked gateway will allow API product owners to choose from Sources that have been synchronized from that gateway and allow for the automatic creation of products in a supported gateway once saved in Revenium.
External ID: this field allows you to manually link this product to an external gateway so that it can be dynamically displayed in a supported commerce portal like Anypoint Community manager from MuleSoft. More information .
: choose the data sources that are bundled into this product. If you created a linked gateway product above, this list will automatically filter the correct Sources from your gateway environment that are available for product bundling. If not, you can manually choose from any configured Sources in Revenium.
: Allows you to choose a previously created SLA to associate with this product.
Named Subscribers: if selected, only commerce portal subscribers with a compatible, pre-configured in Revenium will be able to view this product. Named subscribers are matched either to the client owner of a subscription or the array of Named subscribers on a subscription. If the end user logged into the commerce portal matches either of these lists, a product configured for a named subscriber audience will be visible to them, otherwise, it will not be visible.
Named Customers: Named Customers audiences work the same was as Named Subscribers in terms of requiring a compatible, pre-configured Subscription, though the matching is done against an array of listed in the Product License. The match is done in two ways:
AcmeSoft, Inc. is set up as an in Revenium with a list of "associated domains" that includes acmesoft.com and acmesoft.inc. These are the two domains used by AcmeSoft for email and they want all internal Subscribers to have access automatically.