
- How a customer gets charged Products can either be usage-based, composite (derived from usage-based products), subscription-based, or fixed (for example, a platform fee).
- Invoice line item display Each product (or grouping of products) becomes a line item on generated invoices.
PRODUCTS DON’T HAVE PRICESProducts determine how a customer is charged (for example, which billable metrics impact a charge), but they don’t dictate how much a customer pays. For usage-based, composite, and subscription products, prices are set on a rate card, which you can modify on a contract. Prices on fixed products are set on a contract.
Product types
Metronome supports four types of products:- Usage , variably priced based on reported customer usage for the period. With usage products, you must set up billable metrics beforehand. Associate each product to a single billable metric. The same billable metric can be associated with multiple products.
- Composite , percentage charge on a group of applicable products.
- Subscription , a recurring fee billed on a schedule. Use subscription fees for seat billing models, platform fees, or other recurring charges.
- Fixed , used to power scheduled charges, commits, and credits.
Create products
To define products in the Metronome app, go to Offering -> Products -> click + Add new product :- Give the product a meaningful name; this will appear on customer invoices.
- Optionally enter any product tags.
- Select the product type.
- For usage-based products, select a billable metric.
- (Optional) Add presentation and pricing group keys. Presentation and pricing group keys can only be added if they have been defined as group keys on the underlying billable metric. This field is only applicable for usage products.
- (Optional) Add a quantity conversion. Multiply or divide by a conversion factor. This field is only applicable for usage products.
- (Optional) Add rounding. Round up, down, or half up to the specified number of decimal places. This field is only applicable for usage products.
- Click Save.
Update products
Within Metronome, you can edit products even when they’re actively in use for customer billing. Changes to products are scheduled to take effect at a specifiedStarting at
time, which you can define when changing a product. This date can be set in the future to schedule out product changes ahead of time. If set in the past, it will be retroactively applied at the time specified.
The following fields are available to edit:
- Name
- Tags
- Billable metric
- Quantity conversion
- Rounding
- Pricing and presentation group keys (only editable with the API)
- Click on the product to edit.
- In the product details pane, click the overflow action -> Edit product…
- In the resulting modal, set the Starting at value to specify when the product edits should take effect and update the desired product fields.
- Click Save.
Product tags
Metronome supports adding one or more tags to products. Consistent use of tags helps you select products more easily, whether when creating a composite product or adding products to a commit or discount. Product tags are also useful for adding your company’s internal identifying information to your products in Metronome. For example, you may have internal product codes that you want to store in Metronome to maintain a consistent integration pattern across your systems.Group keys
You can set two types of group keys on your new product: pricing group key and presentation group keys. To set a group key on a product, you must use a billable metric with the relevant group keys. You can use these group keys to encode your price book and customize the display of invoices in Metronome.Pricing group keys
Many AI and infrastructure companies opt to price their products differently across dimensions like region and cloud provider. This approach aligns COGS and revenue, allowing for consistent margins across SKUs within a product catalog. Pricing group keys allow you to set different prices for the same product based upon a set of variables you can choose during product creation. For example, you have two products (P1 and P2), priced per hour of uptime. To support this pricing model, set theregion
and cloud_provider
fields as pricing group keys on the products. The unique rates for each key-value permutation are then defined on the Metronome rate card:
Region 1, AWS | Region 1, AZURE | Region 2, AWS | Region 2, AZURE | |
---|---|---|---|---|
Product 1 | $0.12/hr | $0.14/hr | $0.16/hr | $0.18/hr |
Product 2 | $0.18/hr | $0.22/hr | $0.20/hr | $0.24/hr |
Presentation group keys
You may want to override the display of information on an invoice by grouping across certain properties. Do this with presentation group keys, which will group a set of line items together. Pricing and presentation group keys can be the same property if desired. For example, you have two products, two regions, and two orgs. The pricing group key in this situation isregion
, while the presentation group key will be org
. This allows you to split out region
level usage by org
. The resulting invoice contains:
Region 1, Product 1 | Region 2, Product 1 | Region 1, Product 2 | Region 2, Product 2 | |
---|---|---|---|---|
Org 1 | 15 units | 10 units | 10 units | 5 units |
Org 2 | 10 units | 0 units | 6 units | 3 units |
CONFIGURATION NOTEUsing multiple pricing and presentation group keys with many possible values for a given customer can increase latency when calling the Metronome API. If you anticipate the cardinality of these possible values reaching one thousand, contact your Metronome representative to discuss your configuration.