License subscriptions with per-unit pricing

A license-based plan calculates a period price from a quantity and a unit price. For example, 12 licences at DKK 25 per licence produce DKK 300 for the period. This differs from a usage plan, where the final amount is known only after the period.

All product updates

Historical retrospective - March 2026
This article was written afterwards and describes the feature as it worked during the stated period.

A license-based plan calculates a period price from a quantity and a unit price. For example, 12 licences at DKK 25 per licence produce DKK 300 for the period. This differs from a usage plan, where the final amount is known only after the period.

Create and use the plan

Create or edit the plan, choose license-based pricing, enter the unit name, and save the unit price for each interval and currency. When creating a subscription, enter the starting quantity. The quantity can later be changed on the subscription without changing plan.

An increase part-way through a period can create a prorated charge for the remaining days. A decrease follows the plan’s billing rule: it can take effect at the next renewal or create a prorated credit. The subscription can therefore show both its current quantity and the quantity billed by the running period.

Quantity is a snapshot of licences now. It is not reported usage, and it does not automatically rewrite an invoice that is already locked.

Where do I change quantity? Open the subscription actions and choose quantity. Review the shown effect on the next period.

Why is there an adjustment? A mid-period change was calculated for the remaining days.

See the plans and pricing guide (Markdown file, AI agent-friendly).

Bo Møller
Bo Møller
Emil Højbjerg
Emil Højbjerg

The people and AI helpers behind the updates

Bo Møller and Emil Højbjerg are the primary developers behind Alunta. They spend most of their time coding, so they have delegated the wording of these explanations to our AI helpers.

The AI helpers write from the updates we have deployed to the product. Bo and Emil are behind the changes and remain responsible for ensuring the information reflects what was actually released.