#.brolala
weak ether
lethal abyss
Hi 👋 can you share the ID of the Subscription? How did you make the request to update the Subscription? What were you hoping would happen?
spare dust
Hi ! Here's is the subscription id :
sub_1OfQZ5FotBUbrdlcqs2JIJHF
In my needs, my business deliver each week some goods to customer, each customer can change his basket any time, so each monday we update the subscription price to the amount of previous week basket delivered.
If I'm good, each monday at 2:00 AM we set all subscriptions prices to previous week amount, and the charge will be the updated amount right ?
I'm confused about the 3:00 AM charge of the old amount.
lethal abyss
Hm, I'm trying to figure out where the downgrade came from. Right now the only request I'm readily spotting that updated that Subscription, only changed the default payment method.
spare dust
It's an automatically downgrade
lethal abyss
Oh, I see, you updated the Subscription Item directly
spare dust
yes
lethal abyss
Not automatic
spare dust
Yes, automatically in our system *
lethal abyss
Yup, we refer to that as something your system explicitly does, when we refer to automatic it's things our system does with no interaction from your system.
Found it
It's because you're changing them from a free Price to a paid Price:
https://docs.stripe.com/billing/subscriptions/upgrade-downgrade#handling-zero-amount-prices-and-quantities
so the behavior described here is kicking in
spare dust
Okay, it's a bit clearer, but how I'm supposed to avoid billing date change ?
cloud zephyr
Hi toby, I am a collegue to Brolala.
We update subscription items of subscriptions every monday at 2am based on the delivery of the past week, but subscriptions can be paused or free for the first delivery.
But then, as I understand it, both sub item price update and billing happen at the same time, which causes bugs.
How to avoid this ?
lethal abyss
Two options come to mind.
I believe you could include a trial period as part of your update, to push back when the next payment will be processed.
Or you could look into leveraging a Subscription Schedule, which would allow you to schedule your changes to occur at the appropriate/desired time to avoid this behavior.
spare dust
I'm reading the doc, and watch the pause payment collection part : https://docs.stripe.com/billing/subscriptions/pause
Could we use this to stop the collection for few hours and bring it back when all subscriptions are updated ?
lethal abyss
I think that may work, but you can test in testmode to confirm.
Test clocks can be used to make that testing much faster if you haven't already seen and used those:
https://docs.stripe.com/billing/testing/test-clocks
