Subscription bundles with one-off amounts

A bundle combined the purchase of several subscriptions and optional one-off amounts in checkout. The bundle was a shared purchase experience; the subscriptions created from it each had their own price, periods, trial, and lifecycle.

Historical retrospective: May–June 2026; changed since June 2026

This article was written afterwards and describes the feature as it worked during the stated periods. Bundles later behaved as independent subscriptions with their own trial and invoicing rules. See the subscription lifecycle guide (Markdown file, AI agent-friendly).

A bundle combined the purchase of several subscriptions and optional one-off amounts in checkout. The bundle was a shared purchase experience; the subscriptions created from it each had their own price, periods, trial, and lifecycle.

Build the bundle

Choose the plans the bundle should contain and check the shared interval, currency, and payment method. Add one-off amounts separately. A fixed subscription price, one-off amount, and usage price mean different things and should be shown separately in the review.

Checkout shows the customer the combined order. A one-off amount or first fixed period may be paid at purchase, while trials, future start dates, and usage move other amounts. A bundle therefore does not promise one common invoice date.

After purchase, each subscription can be changed or cancelled separately. Changing one subscription does not automatically change the other parts of the bundle.

Can a bundle have a setup fee? Yes, as a separate one-off amount when the setup allows it.

Why is not everything paid today? Each part follows its own start date, trial, usage, and invoicing.

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.