#connie-subscription-planchange

1 messages · Page 1 of 1 (latest)

signal pawnBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

void needle
#

@sharp plank What's your real exact question? I read all the words you wrote but I don't really get what you're trying to do or answer?

void needle
#

I'm a bit worried as I've seen you type for over 20 minutes now 😅
I can help but it needs to be a clear/concise questions. I'm worried this is so complex and involved that you'd have a way better experience with our support team 1:1 with all the context during the back and forth

sharp plank
#

We charge customers upfront for their upcoming billing cycle, but they can purchase additional usage during their cycle for a prorated amount.

Let's say that a customer's billing day is the 1st of every month, and I'll use users as an example of a usage type we offer.

The flow is:

  1. Jan 1: subscription is created and customer is billed for Jan 1 - Feb 1. Let's say they have 3 users included in their plan
  2. Jan 7: Customer purchases 1 additional user (prorated) and we update the subscription
  3. Jan 14: Customer removes a user, but we don't update the subscription because they have an unused seat they can fill during their billing cycle.
  4. Feb 1: They are billed for the next cycle, but the user's subscription item quantity is still 4, when the number of active users is 3, which should be the correct quantity.

The problem I'm having is making sure that the quantity of the usage items are updated before a customer is charged for their next billing cycle.

void needle
#

Use SubscriptionSchedule for this

#

Basically when you know you want to downgrade the quantity at step 3 you need a SubscriptionSchedule that controls the next "phase" to a lower quantity.
and if they change their mind you can undo that phase/release the Schedule

#

connie-subscription-planchange

sharp plank
#

Ah thanks! I can definitely look into that

#

Also, is this not a common billing structure for Saas companies? I thought this structure was straightforward, but I was having a pretty difficult time figuring out the best way to implement this

void needle
#

it's fairly common yes

sharp plank
#

Is using subscription schedules the best solution for this? Or do you happen to have other suggestions I can explore?

void needle
#

it's the right/best solution yes, so that's what you should build

sharp plank
#

Thanks, I will look into this!

For future reference, is there a way to re-open our previous threads in this channel (apologies if this has been answered somewhere)? Or do we have to create a new thread once it's closed?

void needle
#

we don't reopen threads. This Discord server is for "transactional support" in real time with whomever on my team is helping at that time. It's "ephemeral" and we don't reopen old threads, you just start a new question hopefully with a clear summary (as we help a lot of people in parallel and can't read all the history of past threads)

#

Definitely not something you could have guessed yourself though 🙂

sharp plank
#

I just feel bad for creating 3 similar threads, but that's totally fair. Thanks again for your help!

void needle
#

no worries about this it's totally fine especially with a clear summary. I got worried when I saw you type for a long time, but that was a stellar summary you gave. I was able to answer you in seconds because you gave such a clear example of the lifecycle of the Subscription. That usually takes 20 back and forth to get this out of the person 🙂

sharp plank
#

Haha glad I could make your life easier! That can definitely be frustrating.

void needle
#

it's hard for us to help without a clear understanding of the ask. But it's also hard for you to know what we need. Your summary was perfect because it focused on a clear example of the lifecycle and then it's easy for me to map that to our API features!

sharp plank
#

That's great! And feel free to close out this thread, I will take some time to look into subscription schedules 🙂