beastboy_best-practices

[lusty oyster]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1272980308458868779

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[dusty gyro]

Stripe would functionally see that as an "upgrade", so this guide might be the best place to start: https://docs.stripe.com/billing/subscriptions/upgrade-downgrade

I would recommend reading through that first, then coming back with follow-ups so I can help from there

[sand helm]

So it looks like I need to create a new product and update them all onto this new product?

By just updating the subscription

Or maybe adding a trial period to each subscription? But then that doesnt solve the problem for the next subscription cycle

[dusty gyro]

That would certainly work, yes. I would really recommend testing this out before making changes to production though. Billing can be complicated and the default behavior isn't always obvious, so testing is imperative.

We built Test Clocks for scenarios like this, where you can simulate the passage of time and inspect different Subscription objects and how they change over time: https://docs.stripe.com/billing/testing/test-clocks