Scheduled subscription changes are removed if I update the subscription.
M
Michael Elsdörfer
started a topic
about 2 years ago
I guess what I want is not supported, but I'd like to describe my use case anyway and solicit some input.
My user can switch between two plans, say, Basic and Pro. If the user upgrades Basic -> Pro, I let chargebee prorate. If the user downgrades from Pro -> Basic, I update the subscription with "end_of_term", such that Chargebee "schedules" the changes for the end of the billing term. That is, my customers can cancel to the end of the term.
So far so good. What complicates this is that for a Pro subscription, the plan has a"quantity" that factors in. If the user schedules a downgrade to "Basic", and that downgrade is scheduled for two weeks from now, in those two weeks the user still would have the ability to downgrade the quantity of his Pro plan.
I expected Chargebee to handle this for me. In particular, since the docs for a subscription update state "Only the parameters that are passed are modified for the subscription. Rest will reflect the existing values".
However, what happens when I run the UpdateSubscription API call, even when I do not give ANY data to change, the existing "scheduled changes" are always removed entirely.
Best Answer
L
Lakshmi Narayanan G
said
about 2 years ago
Hi Michael,
In this scenario, the best approach for you would be to use the retrieve with scheduled changes API before calling the update subscription to see if there any scheduled changes to the subscription, store these temporarily on your end, update the quantity, and then schedule the changes again.
With the current workflow in our system, when you update the plan quantity, you're also including the current plan's ID, in which case the update a subscription API would update the subscription with the current plan and quantity, removing the scheduled changes.
1 Comment
Lakshmi Narayanan G
said
about 2 years ago
Answer
Hi Michael,
In this scenario, the best approach for you would be to use the retrieve with scheduled changes API before calling the update subscription to see if there any scheduled changes to the subscription, store these temporarily on your end, update the quantity, and then schedule the changes again.
With the current workflow in our system, when you update the plan quantity, you're also including the current plan's ID, in which case the update a subscription API would update the subscription with the current plan and quantity, removing the scheduled changes.
Michael Elsdörfer
I guess what I want is not supported, but I'd like to describe my use case anyway and solicit some input.
My user can switch between two plans, say, Basic and Pro. If the user upgrades Basic -> Pro, I let chargebee prorate. If the user downgrades from Pro -> Basic, I update the subscription with "end_of_term", such that Chargebee "schedules" the changes for the end of the billing term. That is, my customers can cancel to the end of the term.
So far so good. What complicates this is that for a Pro subscription, the plan has a"quantity" that factors in. If the user schedules a downgrade to "Basic", and that downgrade is scheduled for two weeks from now, in those two weeks the user still would have the ability to downgrade the quantity of his Pro plan.
I expected Chargebee to handle this for me. In particular, since the docs for a subscription update state "Only the parameters that are passed are modified for the subscription. Rest will reflect the existing values".
However, what happens when I run the UpdateSubscription API call, even when I do not give ANY data to change, the existing "scheduled changes" are always removed entirely.
Hi Michael,
In this scenario, the best approach for you would be to use the retrieve with scheduled changes API before calling the update subscription to see if there any scheduled changes to the subscription, store these temporarily on your end, update the quantity, and then schedule the changes again.
With the current workflow in our system, when you update the plan quantity, you're also including the current plan's ID, in which case the update a subscription API would update the subscription with the current plan and quantity, removing the scheduled changes.
Lakshmi Narayanan G
Hi Michael,
In this scenario, the best approach for you would be to use the retrieve with scheduled changes API before calling the update subscription to see if there any scheduled changes to the subscription, store these temporarily on your end, update the quantity, and then schedule the changes again.
With the current workflow in our system, when you update the plan quantity, you're also including the current plan's ID, in which case the update a subscription API would update the subscription with the current plan and quantity, removing the scheduled changes.
-
EU VAT Support?
-
How do I accept check or bank transfer payments?
-
Can a customer change from one plan to another?
-
How is Chargebee different from a payment gateway?
-
What time zone does ChargeBee use to record transactions?
-
How does ChargeBee handle changes in quantity in the middle of a billing period?
-
How to cancel or void an invoice once it is generated in ChargeBee?
-
How to test webhooks locally during the development phase?
-
Payment gateway options for Indian companies
-
How to create subscriptions to pay by invoice, credit card and other offline methods (paypal, wire transfer, bank transfer).
See all 178 topics