Background

There are a number of unique conditions that are true of the Keebo usage based pricing business model. We plan on shipping a number of updates to our usage based pricing to make these models easier to manage, so the Keebo team does not have to build the software to manage these.

Features

Transaction amounts will not be less than prepaid amounts on a pricing plan

Currently, if a transaction is for a shorter period than the pricing plan covers, the transaction amount can get pro-rated to less than the prepaid amount. We will update this so the transaction amount always reflects at least the prepaid amount.

Edits to prepaid transaction amounts will persist

Currently, prepaid transactions are managed entirely by the usage based pricing engine, which means that edits to transactions (for example, product, book date, etc) are overridden because the transactions are owned by the usage based engine. We will add a feature to allow overriding the defaults and to persist those overrides.

Multiple prepaid tiers will be allowed on a single pricing plan

This will allow “top ups” - where a customer can prepay for more credits, on top of what was initially prepaid.

Additionally, this will create multiple transactions - one for each prepaid tier. This will allow managing start and end dates of the transactions separately to achieve the desired state for ARR and revenue recognition calculations.