Extend Expiry date when upgrading to different plan

Hello,

We have four plans created, giving membership for four levels of time:
-- 1 year
-- 6 mos
-- 3 mos
-- 1 mo

We have just spotted an error, whereby when someone changes plans, it essentially erases the credit they previously had, and replaces it with the new one.

That is to say:
-- if I sign up for the 3 mo plan, it gives me credit through 10/31/16.
-- BUT if I then "upgrade" to the monthly plan (to pay one additional month), it removes the previous expiry and replaces it with the new one == 08/31/16.



...What they WANT to happen is that the expiry date keeps being extended when people switch plans, so that they do not lose any amount of time for which they have already paid.

(I understand WHY this is happening, because the system just switches plans and gives them the new date, but it's not what we want to happen.)


I have reviewed the "upgrade" and "workflow" options, but cannot figure out how to make this happen.

I have the Manual Renewal setting as "Renewal extends expiration date (without gap or overlap)" but this doesn't apply when switching between plans.

How can I set it up to make this happen as we want?


Thank you for your help!!

CBSubs doesn't work how you're trying to make it work. You can't have say 4 plans and have their durations add up. That's just not how it works. You're replacing 1 plan with another and if you replace a 6 month plan with a 1 month plan then it's time and money lost. By default CBSubs shouldn't let you downgrade to a cheaper plan like that to avoid such scenarios. The only parameter applying for plan to plan is Prorating which is configured under the Pricing tab of your plans.

Best I can suggest is probably to use CBSubs SQL Actions and extend their expiration date based off their previous subscription (you should be able to find that easily since their database row should contain what they upgraded from). This likely however will not work correctly with recurring payments usage.

krileon wrote: Best I can suggest is probably to use CBSubs SQL Actions and extend their expiration date based off their previous subscription (you should be able to find that easily since their database row should contain what they upgraded from). This likely however will not work correctly with recurring payments usage.

Can you please tell me specifically how to do this?

Or... if you can think of any other alternatives, i would very much appreciate it!!

You need to write a custom database query for that. Specifically on the database table _cbsubs_subscriptions. The subscription they upgraded from should have its ID stored in the replaces_subscription column. The [subscription_id] substitution in your SQL action would be used to grab the subscription they just activated. So with that info you'd grab their active subscription, check if it has replaced anything, if it has you'll then need to do date range comparisons and add remaining duration to the new subscription row.

I'm really not comfortable suggesting anything more specific unless you're very experienced with SQL. Tampering with the subscription row can cause all kinds of problems.

thank you.

i am not comfortable tampering with any of that.

i will leave it as is, and hope they accept my suggestions to add explanations or restrict the upgrades.


that would be possible, right?

== to not allow upgrade until their current subscription expires, and they choose a new one?

thanks again,

== to not allow upgrade until their current subscription expires, and they choose a new one?

Yup, you can add conditions to upgrade under the Workflows tab of your plans. So for example hide Plan B if Plan A is active.