cha5nce_best-practices

[sharp moss]

👋 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/1308315897080975392

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

[midnight siren]

I have a core subscription of just that base subscription + then I created another product called Usage + Add Ons, with multiple prices, covering my usage based SMS and email charges, as well as any add ons. This way, in the no code portal, users can only upgrade/downgrade the base subscription, since the other product containing all of the other usage + add on prices can't be upgraded as the product is composed of multiple prices + is a "Price varies with usage"

I was wondering if this makes any sense at all, or if I'm being a total fool and missing something obvious.

My main priority here is that I'd like to use the stripe customer portal to enable upgrades/downgrades.

I'm fine with having cancellations take place on my site. I just don't want to manage upgrades/downgrades and prorated charges, for example.

[spiral token]

hello! gimme a while to read through and understand!

[midnight siren]

To reiterate, we've got multiple subscription types.

Good/Better/Best base subscription
Usage based charges for SMS and Email
Additional monthly recurring flat charges for add-ons like custom phone numbers

And I want to use as much of the customer portal as possible to avoid dealing with cancellation/downgrade/upgrade

and I'm just wondering what best practice is here

Thank you!

Or maybe it makes no sense to use the customer portal in this context. I'm very open to any recommendations. Thank you very much!

[spiral token]

if I understand this correctly, you only want the customer to be able to upgrade/downgrade the base subscription right? If that's the case, then what you did i.e. creating different product(s) for those that you don't want to allow the customer to upgrade/downgrade is what I would have done too

[midnight siren]

is there a way in the no-code customer portal to prevent customers from upgrading one product vs the other?

Right now, what i've found is as soon as I toggle this one

to be on, the customers not only can switch between the base subscription (good / better / best)

but they can also see the upgrade options on additional monthly recurring flat charges for add-ons like custom phone numbers

[spiral token]

you can configure which specific product to allow upgrades/downgrades from I recall

[midnight siren]

So if for example

I add the good/better/best trio as those products, and

I had a customer subscribed to the better plan, with the phone number add on

They would see 'upgrade subscription' as a button next to

the better plan

AND

The phone number monthly add-on

And upon clicking upgrade, both would show that they could select good/best

[spiral token]

are you saying that even after specifying the specify product, your customers can still see upgrade options for the add ons?

[midnight siren]

I wouldn't want someone to be able to switch the 6.00/month phone number 'add on' to the best plan, for example

yes! I can demo this

So here are the products that I have specified

and here i am in the portal

I can both update the texting base plan (the custom phone number add on) AND the core plan

[spiral token]

hmmm, gimme a while to poke around

[midnight siren]

in this scenario, i can then change the texting plan into -> a ForeverFan (Ultimate Plan)

which makes not too much sense, since the texting plan is supposed to be an add on

thank you!

[spiral token]

ah, sorry my bad, i misunderstood. So the products mentioned in the screenshot, is the product that you can update to. I thought that it was the product you can choose to update.

so the customer portal can't do what you want i.e. only allow updates to a specific product

sorry about that, I'll share feedback for this feature

[midnight siren]

OK understood! Thank you!

I have a quick follow up on this question

The workaround I am currently exploring is as follows -- I create a single product with multiple prices.

This single product is ALL usage + add ons for my company.

within this product, there are multiple (up to 5) prices that can all be active concurrently

What would appear on my customer's invoice?

Would it say --

Usage + Add Ons

5 times?

[spiral token]

i think what you mean is create a Product, but the Price is :

• Price 1 : base subscription A + all usage + add ons,
• Price 2 : base subscription B + all usage + add ons,
• Price 3 : base subscription C + all usage + add ons

is the above what you mean instead?

[midnight siren]

Not quite, I meant,

For each user they can have two subscriptions

Subscription to product 1 (base subscription): Base subscription A/B/C
Subscription to product 2 (usage + addons): contains up to 5 usage based/recurring prices, all of which are active, as seen in the screenshot

But all those prices are active under one single subscription

[spiral token]

i don't believe that'll solve your problem though? The upgrade / downgrade can still be any Price on the Subscription.

oh ooooh, sorry, i think i understand what you mean now

It still won't work because of what I mentioned, the customer portal allows you to view (and update) all subscriptions on a specific Customer