#shastasanu

1 messages · Page 1 of 1 (latest)

jagged shellBOT
steady jetty
#

Just to be clear, are you hoping to keep the same billing cycle? Do you want to cut an invoice for the existing usage when you make the update?

fast wind
#

Preferably I'd like to keep the existing billing cycle, but if I had to cut an existing invoice for the update I might be able to make that work. Some additional info is that I also have a flat fee on the subscription in addition to the usage based prices and I have around 15 different products each with per unit prices that the user can switch between. The current implementation just has 1 product with many different prices but we are reaching a limit on the amount of prices we can add to a product which I believe is 20.

steady jetty
#

Hm, I think you likely need to cut a new invoice in this case. I assume you don't want to keep the Subscription Item for the $1 price if a customer has upgraded to the $2 price, right?

fast wind
#

Yeah, I wouldn't want to keep the $1 price if the customer did upgrade. For example, I wouldn't want them to move into the next billing cycle still subscribed to that price on their subscription object. Rather, the usage for that price would have shown up on their next invoice and then wouldn't show up again on the following invoice unless they changed again.

steady jetty
#

Gotcha

#

Sorry for the delay. I recommend testing this out but another way you can handle this is to add a new Subscription Item for the new $2 price (leave the existing Subscription Item as is), stop reporting usage for the old Subscription Item and continue reporting usage for the new Subscription Item. Once the new billing cycle starts, delete the original Subscription Item (this should have 0 usage in the new billing cycle)

fast wind
#

Awesome, I'll take a look into that. Thanks for the help!