#mikewilliams-subschedules

1 messages · Page 1 of 1 (latest)

naive verge
#

hello, can you share the sub ID and I can have a look

vocal garnet
#

sub_1Jn4IrBFqTKIU0a7zA1rr7bQ

#

Some of the code I was using

nocturne zinc
#

Sorry for the delay! Quick question for you - is your goal here to create subscriptions immediately but just have them anchored to a specific date, or do you want to create subscriptions that start at a later date/have future changes scheduled for them?

vocal garnet
#

Doing it in the future seemed to not have any issues @nocturne zinc . We just were looking at the scenario of like, someone signs up Oct 15 (this is metered usage btw), so we want to basically make that first period Oct 1 - Oct 31, and do monthly going forward

#

I got this to work by creating a subscription and then converting it to a schedule, but needed a few different phases and didn't realize if there was a simpler way

#

When using the regular create subscription api, we're able to anchor the billing fine, I was just trying to think of ways to convert existing subscriptions

nocturne zinc
#

Just to make sure I have this straight:

  • In the scenario where someone signs up on Oct 15 and the first period is Oct 1 - Oct 31, you currently do this with just the plain subscriptions API and billing cycle anchor
  • Your remaining issue is how to manage this for subscriptions that have already been created in the past, and you now want to correct them
#

Do I have this right?

vocal garnet
#

Yes

#

They have subs being created through checkout and stuff where they're not controlling the dates

#

Again, I think I have this working with the schedule conversion but not sure why I needed three phases

#

Although I just made this update and it seems to work:

nocturne zinc
#

Yeah I misinterpreted your initial ask - I thought you were having trouble with creating new subscriptions with a billing cycle anchor. With existing subscriptions the approach your using (schedules) is fine, but you can definitely do it with 2 phases instead of 3. Based on your screenshots it looks like you've already figured it out though 🙂

vocal garnet
#

Yeah I guess I kinda did, just wanted to really understand it. I'm unsure why it wouldn't just work with the first phase?

#

Cant you just say like 'end this phase at the end of the month and release'

nocturne zinc
#

The missing piece with that is the the billing cycle anchor - you can only reset the billing cycle anchor on a subscription schedule by setting billing_cycle_anchor: phase_start, which you would need to do on the second phase

vocal garnet
#

Gotcha, and I can't just put that in the default settings

nocturne zinc
#

Correct

vocal garnet
#

Thanks! Learn something new every day

#

And the difference between create prorations vs none is? They get charged Nov 1 vs immediately or something?

nocturne zinc
#

none will not create any prorations that may happen for an update, create_prorations will create the prorations and only invoice them immediately when required (otherwise they'll just be rolled in to the next schedule invoice), and always_invoice will immediately invoice the prorations