Included usage on usage-based subscriptions

If you sell, for example, SMS, API calls or GB with a number of units included and a price per unit above that, Alunta can now handle the whole calculation. A usage plan's price can have included usage: a number of units in each billing period that are free. Usage above it is charged at the price per unit.

All product updates
Included usage on usage-based subscriptions

If you sell, for example, SMS, API calls or GB with a number of units included and a price per unit above that, Alunta can now handle the whole calculation. A usage plan’s price can have included usage: a number of units in each billing period that are free. Usage above it is charged at the price per unit.

With 100 SMS included and DKK 0.55 per SMS above that, 180 SMS gives an invoice of 80 × DKK 0.55 = DKK 44.00. If the customer uses 100 SMS or fewer, no invoice is sent and the card is not charged. The invoice line shows both the total usage and the included quantity, for example “180 SMS (100 included, 80 extra)”, and the same text appears on the line in e-conomic, Dinero and Billy.

You turn it on for the plan’s price under Subscriptions. The included quantity is fixed for each subscription when it is created, so later changes to the plan do not change existing agreements. Every billing period gets the full quantity, including a shorter first period. A percentage discount applies to what is charged after the included usage.

If you report usage through the API, you no longer need to subtract the included quantity yourself. GET /v1/subscriptions/{uuid}/usage now shows both the included and the billed quantity for the current period. Included usage can also be used in bundles and custom offers, but not in imports.

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.