Learn about the different types of product items
Product items are the building blocks of your products. Each item defines what customers are allowed to use when they purchase the product, and how they should be charged for it.
There are 3 types of product items: Features, Prices and Priced Features.
Features are the parts of a product that your users get access to when they enable a product. You can model these as either metered or boolean.
These are any features that require you to keep track of a usage count, and defined with 2 key fields.
Example
You have an AI chatbot that allows users to send 10 messages per month. Included Usage is 10
and Reset Interval is per month
.
You also have a 3 seat limit per organization. For this, Included Usage is 3
and Reset Interval is No Reset
.
With these two fields defined, Autumn can track what your users have access to and enforce these limits. From your application:
You can learn more about how Autumn handles metered balances, usage and reset intervals on the Balances page.
Boolean features are for your features that can be either enabled or disabled. Think of them like feature flags to gate specific parts of your application based on what product a user has (eg, access to a premium analytics dashboard).
For these features, there is no configuration needed to be set. If you add them to a product, users on that product will be granted access to the feature.
Prices are a fixed amount a user will be charged for a product. They can be either a one-time payment or a recurring payment.
You can select whether to create a one-time or subscription price through the “Billing Interval” dropdown.
Priced features can be used to model usage-based pricing, where the price of the product is variable and tied to how much of a feature a user consumes. This combines the configuration options of a feature with a price.
When creating priced feature items via API, the interval
field is the
billing interval.
You can use the reset_usage_when_billing
flag to control
whether the usage count should reset when the feature is billed (eg, for
credits, API calls and other consumable resources), or not reset (eg, for
seats, workspaces etc).
You can use priced features to model a number of different pricing models: