#rob-subscription-enddate

1 messages · Page 1 of 1 (latest)

jaunty snowBOT
earnest lance
#

rob-subscription-enddate

#

@crisp lark I recommend SubscriptionSchedules with the right number of iterations. I wouldn't set an exact end date because it can cause weird proration issues at the end

crisp lark
#

thanks!
I see. so a subscription schedule with 1 iteration

earnest lance
#

hmmm not really

#

I guess what are you really trying to do? 😅

#

is this a yearly Price specifically?

crisp lark
#

oh, just to have a customer "subscribe" to our subscription, which is yearly, and it will end in a year
For them to "renew", we will create a second subscription that will start at the end of the current one.

earnest lance
#

why?

#

Like this feels really strange honestly to do something like this

jaunty snowBOT
crisp lark
#

it does?
sorry ... we are trying to model a yearly subscription but where our customers must renew manually

#

we have monthly, quarterly and yearly payment plans, however our contract is always for a year

#

30 days before the end of the subscription they are going to be prompted to renew

#

our plan was to create a NEW subscription that starts in the future, and when an even on the existing subscription is 'cancelled" due to reaching end date, we would then receive the activation event for the new subscription.

hallow helm
#

👋 Taking over this thread

#

Thanks for sharing the details

crisp lark
# earnest lance is this a yearly Price specifically?

No. Basically our contracts are all a year
customers can however pay monthly, quarterly or yearly.
we track the billing cycle locally, but need to allow them to renew ahead of the end of their contract, but for the "next" contract.

crisp lark
hallow helm
#

Instead of creating the new subscription when customer manually renew the subscription, one recommendation will be just releasing the subscription schedule

#

So that the existing subscription won't be cancelled and it will remain

crisp lark
#

right ... so a single subscription but with a subscription schedule ?

#

my colleague and I were trying to run our scenarios via the admin portal, and the best we'd come up with was having a subscription, then creating a new subscription that started at the end date of the one we currently had for the customer.

#

is that how it would be modelled?

hallow helm
#

I'd recommend the following steps:

  1. Create a subscription
  2. Create a subscription schedule on the subscription in step 1 and update it to cancel after one iteration
  3. Before 30 days of the expiry, prompt the customer for renewal
  4. If the customer decides to renew the subscription, you can release the subscription schedule in Step 2 and create a new subscription schedule with next due iteration
  5. Repeat step 3 and 4 until customer decides to stop subscription
crisp lark
#

sweet ... now ... if they DON'T renew within that time, can we still follow the same process when the cancellation occurs ...
replace the expired schedule with another ...
I take it there is only one schedule for a subscription ... ?

hallow helm
#

Yes, correct!