Products & prices

Documentation Index

Fetch the complete documentation index at: https://docs.hyperline.co/llms.txt

Use this file to discover all available pages before exploring further.

In Hyperline, a product represents anything you sell to your customers. This can be a software, a capability, a service, etc. These products are managed in a products catalog, an interface allowing you to have a complete overview of your offering and manage in a single place the associated and reusable prices based on various parameters (currency, location, market, interval, duration, etc). Setting up products enables the creation of pre-configured plans, subscriptions, or one-time payments for your customers.

​

Types of product

Hyperline enables you to represent a variety of products for sale by leveraging four product categories.

​

Fee

A “flat fee product” refers to a product or service for which the cost is a fixed, a consistent charge. It means that the customer or client pays a predetermined, flat fee, regardless of usage, quantity, or time duration. This contrasts with usage periods where the cost may fluctuate based on factors like usage, consumption, or time. This product can be used for subscription fees, fixed-rate services, addon items, or additional fixed costs. This provides predictability for your customer, as they know exactly how much they will pay without unexpected variations in costs. This type of product can be:

• included in subscriptions using the Allow product to be added to a subscription option
• billed separately using the Allow this product to be charged as a one-time payment option

Pricing model This product supports flat fee prices.

​

Seat

A “seat product” refers to a type of licensing where the cost of a software application or service is based on a number of items also named “seats” (users, accesses, licenses, etc). This kind of product allows scalability, where customers can add or remove seats as needed, making it flexible for businesses with changing requirements. This type of product can be included in subscriptions with the ability to link to product data for automatic adjustment of billable items or manual configuration. Seat products also support connected seats, where the seat count is automatically tracked via an aggregator (count operation). This enables automated metering with background updates and customized payment terms, such as yearly pro-rated charges based on peak user counts. Pricing models This product supports volume, bulk, and bundle prices.

​

Usage

An “usage-based product” refers to a type of product where the cost is directly tied to how much your customer uses or consumes the product. In this model, customers are typically charged based on their actual usage, rather than a flat fee. This kind of product offers flexibility, allowing customers to pay for what they actually use with a cost varying with the amount or extent of usage. It enables “pay-as-you-go” or “pay-per-use” model where customers are billed periodically based on their usage during that period. This type of product is related to usage data measured using events representing specific occurrences or happenings that needs to be billed during a specific period. Detailed usage reports are also provided, making billing transparent and providing clarity on how charges are calculated. Pricing models This product supports volume, bulk, and basis points (BPS) prices.

​

Metering configuration

A usage-based product must be linked to an aggregator that defines how events are transformed into a billable metric. Aggregators support two operations: count (number of events) and sum (total of a numeric property). Additional filters can be configured on the aggregator to narrow down eligible events based on custom fields (strings, numbers, or booleans) from your system. Price metering filters In addition to configuring metering for the product, you can set metering filters for each price. This allows you to define pricing based on specific criteria, enabling complex pricing matrices and price points based on specific usage parameters and values. For example, if you offer cloud computing services, you can apply different prices based on compute instance type or region. Similarly, if you process banking transactions, you can apply specific fees depending on the scheme or card configuration.

​

Credit

A “credit product” represents a granted quota that customers can pay for upfront and consume over time. Each customer has a single shared balance that is automatically debited as eligible usage events come in — so credits act as a pre-paid layer on top of your usage data. This kind of product is useful when you want to decouple purchase from consumption: customers buy credits in packages, and any combination of metered actions draws from the same balance until it is exhausted or topped up. A credit product is linked to one or more aggregators, each with a weight that defines how many credits one unit of usage consumes. All aggregators draw from the same balance. Pricing model This product supports bundle prices — you sell credits in predefined packages (e.g. 1,000 credits for €50, 5,000 credits for €200). For the full setup flow, customer-level balance management, expiration rules, and auto-topup, see Set up credits on your account.

​

Bundle

A “bundle product” groups several existing products into a single offering, sold to your customers as one logical unit. This is useful when you want to package complementary products together — for example, a base subscription combined with a quota of API calls and a number of seats — and bill them as a single item. Components and revenue allocation A bundle is composed of one or more components, each pointing to an existing product in your catalog (any type — fee, seat, or usage). Each component carries a percentage that defines how the bundle’s revenue is allocated to that product. The percentages of all components must sum to 100%. This allocation drives revenue recognition (each component’s share is recognised against the underlying product) and, when configured, the per-line breakdown shown to your customers on the invoice. Display mode Bundles support two display modes that control how they appear on invoices:

• Single line — the bundle is shown as one line item on the invoice. The component breakdown is tracked internally for reporting and accounting, but the customer only sees the bundle as a whole.
• Ventilated — each component is shown as its own line item on the invoice, with amounts split according to the configured percentages. Use this when your customers expect to see exactly what is included in the bundle and at which value.

Exclusive components Bundles offer an option to mark their components as exclusive to the bundle. When enabled, the underlying products can only be sold as part of this bundle and won’t appear on their own in quotes or subscriptions. Disable this option if you also want to sell the same products independently outside of the bundle. Pricing models This product supports volume, bulk, packaged, and bundle prices.

---

​

Pricing models

Products in Hyperline support a variety of pricing models: flat fee pricing, volume pricing, bulk pricing, bundle pricing, and basic point (BPS) pricing.

​

Parameters

Each product can also contain multiple prices (of different models) depending on different parameters: currency, country, interval, and commitment period. This enables you to represent all the cases you propose with fine granularity, depending on the specific characteristics of the markets you operate in, or how you wish to adjust pricing based on your customers’ engagement with your service. In the example above, the product costs 200€ per month except for UK customers where it’s 220£ per month, or 2200€ per year except for customers committed 2 years where the price is reduced to 2000€ per year.

​

Flat fee

Predetermined, fixed and unchanging price.

​

Volume

Cost per unit or item is adjusted proportionally to the quantity of items purchased or consumed. Usually, the more a customer buys, the lower the cost per unit becomes. Volume pricing often involves multiple price tiers, which can be used to change the price depending on certain volume thresholds. In the example above, the customer is billed 50€ per unit between 0 and 10 then 40€ per unit between 10 and 50, then 20€ per unit, so 2360€ for 63 units. We offer you a preview of the price evolution depending on the quantity which can help you have an overview of the trend a price can have; and a preview of the rendering of the price for your customer (e.g. on their checkout page).

​

Pay tier in full

The “Pay tier in full” option can be activated on a per-tier basis. This option allows you to charge the full price of the tier (i.e. price per unit ⨉ to value) if the consumption is contained in this tier range. In the example above, the customer is billed 250€ for this product between 0 and 5 units regardless of their consumption, then a progressive price for higher levels (e.g. 370€ for 9 units).

​

Packaged

As per a volume pricing, a packaged pricing adjusted proportionally to the quantity of items purchased or consumed, usually involving multiple price tiers. The difference is that you can define packages of units, allowing you to define a price for a quantity of items inside a specific tier. In the example above, the customer is billed 6€ per 20 units if less than or equal to 200, then 4€ per 20 units if more than 200 (e.g. so 100€ for 400 units).

​

Bulk

The total number of units determines the tier used and therefore the cost of all units. Reaching a higher tier value will decrease the price per unit. In the example above, the customer is billed 50€ per unit if less than or equal to 10 or 30€ per unit if more than 10, so 1020 for 34 units. As with volume pricing, the “Pay tier in full” is also available, and we offer an overview of the price evolution and final rendering on the customer’s checkout page.

​

Bundle

Bundle pricing allows you to configure predefined bundles with specific quantity/price combinations. This model is particularly useful for seat-based products where you want to offer only specific package options to customers. With bundle pricing, customers can only select from the predefined bundles you configure when creating quotes and subscriptions, rather than choosing any arbitrary quantity. This pricing model is also used for credit products, where you can define packages of credits at fixed prices (e.g., 1000 credits for $50, 5000 credits for$200).

​

Basis Points (BPS)

Method used to calculate prices based on a given percentage applied on the number of items considered in the computation (i.e. usage billed for the period). Tiers can be defined to vary this percentage. As with volume pricing, the “Pay tier in full” is also available, and we offer an overview of the price evolution and final rendering on the customer’s checkout page.

​

Translating product names

If you have an international audience, it’s important to have your products correctly translated on invoices and hosted pages. On the product page, you can add translations for the name and the public description by clicking on the globe icon. Once saved, we will update the portal, checkout and new invoices will use the translations when appropriate.

​

Hosted pages rules

On hosted pages, the translations being used are, by order of priority:

• Customer’s browser language (if the customer has defined Italian as their primary language, that’s what we will use)
• Customer’s language set on Hyperline
• Customer’s country (if the customer’s address is in Italy, we’ll use Italian translations)
• English
• Default product name