#rstocker99-customer-portal

1 messages · Page 1 of 1 (latest)

rocky hare
#

hello @glad urchin, could you share why you understood the Customer Portal as expecting multiple products each with a single price? Generally, a product can support multiple prices also, but the prices should be for that particular product only. As an example, you can offer a subscription for product A and offer the following prices : $10/month, $20/6 months, $30/year

glad urchin
#

I got that impression from watching this video: https://www.youtube.com/watch?v=u8H6awDJVpM

YouTube
Stripe Developers
Integrating the customer portal

In this edition of Stripe Developer Office Hours, Theodora Chu shares an overview of the Customer Portal and CJ Avilla demonstrates integration into a simple Ruby on Rails application.

Resources

▶ Play video
#

I'm thinking more like this:

#

Plans

#
  • SMB
#
  • Growth
#
  • Scale
#

(logical customer plan) Each plan would have two prices monthly and annual

#

vs. One Product with prices SMB, Growth and Scale which is what our current code does and what our existing subscriptions use

#

It seems like the customer portal would want Products: SMB (Prices X/m Y/year), Growth (Prices X/m Y/year), Scale (Prices X/m Y/year).

#

Maybe the video has steered me in the wrong direction.

rocky hare
#

This seems fine to me - SMB (Prices X/m Y/year), Growth (Prices X/m Y/year), Scale (Prices X/m Y/year) and would work well with the customer portal

#

hmmm, oh, you're using this right now - One Product with prices SMB, Growth and Scale

glad urchin
#

My concern isn't the above which I think will work it's that I've got a bunch of existing subscriptions that aren't like that. My goal is to kill off our custom code but all of our existing subs are like this ProductX (price1, price2, price3, price4...) i.e. one product many prices. What happens when someone launches the customer portal and the sub has a product like that?

#

Basically how do I migrate

rocky hare
#

aaaah, so you can migrate customers by cancel their current subscription (remember to include proration) - https://stripe.com/docs/api/subscriptions/cancel. Then immediately start your customers on a new subscription with the new product/price with the saved payment method.

glad urchin
#

Ok, that's what I was afraid of. As you can imaging canceling ever sub and recreating subs is... a bit scary. At least I know that "the answer".

rocky hare
#

definitely try it out in test mode first

#

to get over the big 'scary', you can also do it in tiny batches

glad urchin
#

Hahaha... yup will def be doing that.

rocky hare
#

that way if something goes wrong, at least you haven't broken the world

glad urchin
#

Ok, thanks for confirming that's "the way"

rocky hare
#

feel free to reach out if you have other questions or run into issues along the way

glad urchin
#

Will do, thanks for your help. Appreciate it!

rocky hare
#

@glad urchin actually on second thought, you can just update the subscription too

glad urchin
#

i.e. like change the Product/price it's linked to?

rocky hare
#

yep!

glad urchin
#

Do you happen to know what happens to the billing cycle in that case? i.e. if you are 18 days into your billing cycle and I switch you what happens?

rocky hare
#

If both prices have the same billing periods—combination of interval and interval_count, the subscription retains the same billing dates. If the prices have different billing periods, the new price is billed at the new interval, starting on the day of the change.

glad urchin
#

Ok, I'll give that a review. Basically there isn't an "easy way". We need to change our product setup and write some migration code.

rocky hare
#

yes

glad urchin
#

Ok, got it :). Thanks again!