How to manage Stripe checkout add-ons and price changes without disrupting existing Memberstack subscribers? Answered

Post author
Andrés Esquivel

Hi, I have some question regarding the Stripe integration:

  1. Is there a way that we can enable Add-Ons in the checkout flow without affecting user access?
  2. If in the future, I want to change the price of the plan I have users subscribed to, will that affect anything in Memberstack? Let’s say I have 500 users already in a plan, and I just want to update the plan moving forward to be 50% more expensive, what are the implications?

Comments

11 comments

  • Comment author
    Shadi null

    #2 is something I myself am quite concerned about too. As it stands, if you archive a price, the plan will still renew on the users next billing cycle so they can technically choose to ignore your new prices. I would love to be able to have an email blasted out or a pop up banner (like Spotify does when they increase prices) where you have 1 month to click “I agree” and pay the extra 1€, or ignore it and have your plan automatically cancelled when the pre-defined date is passed

    0
  • Comment author
    Duncan from Memberstack
    1. No add-ons/upsells yet. We hope to enable this the future, but no ETA.
    2. You will need to create a new price for the plan. Existing members will remain on the old price.

    Shadi null I see what you mean.

    I think we’d need to build a bulk price update feature so you don’t have to upgrade them 1 by 1.

    That said, so long as the plan was created by Memberstack then you use the Stripe API to bulk update customers subscriptions. I have not done it myself, but I don’t see why that wouldn’t work.

    0
  • Comment author
    Shadi null

    Duncan from Memberstack 100% a bulk price update would be FANTASTIC, but there should be an "Opt In" element to it (so users can choose if they want to stay subscribed or cancel because of the increased price).

    Currently the only options we really have as no coders is to find the customers individually on the stripe dashboard, and change their plans 1 by 1 (remember you have to type your password for each user you change the plan pricing for).

    I think a system that automates this headache could be priceless from a developer standpoint, and from a user standpoint as suddenly they actually have a choice (stay or leave depending on the new pricing)

    I also find the whole stripe interface for changing plans quite cumbersome

    0
  • Comment author
    Andrés Esquivel

    Duncan from Memberstack if we create a new plan, can we manually change the plan of the users on the old plan to the new one? Or are they permanently stuck with the old plan?

    0
  • Comment author
    Shadi null

    Andrés Esquivel My screenshot above is where you would go to manually change the users plan to a new one. It will take effect after the current billing cycle, but it is rather cumbersome as the user page reverts to page 1 after every plan change takes effect, and you have to type your entire stripe password in for every user's plan you change.
    All in all, it can take days or weeks if you have lots of users to do this for.

    Under your stripe dashboard go to customers -> (Click on your customer of choice) -> under subscriptions -> Update Subscription -> Products -> Add product -> Delete Product (old subscription) -> Save -> Insert password -> Go back to customers panel (sends you to page 1) and repeat

    0
  • Comment author
    Jamie Debnam

    We have a client who want’s to increase the price of their current users subscription. How can we do this to avoid friction with the users by any other alternative method?

    0
  • Comment author
    A J

    It could be possible to update subscription via Stripe API. I have not tried creating a new price and updating the subscription to use the new price via stripe api yet, but you can explore that approach and see if its possible and fits your use-case.

    Another approach could be that you have an automation, which adds a temporary free plan to users with the old price and setup a plan logic to cancel the recurring paid plans and when users login to the site, they will be redirected to the updated pricing table via which they can purchase the plan with the new price. (assuming the user only has one paid plan), if you have multiple paid plans then to avoid confusion, its safe to take stripe api or the following approach).

    If you don't have many users that would undergo this change, then you could do this directly via Stripe dashboard as explained here.

    In any case, it is best to inform users of the price change so that they are aware and take the purchase decision.

    0
  • Comment author
    Chris Amos

    I have written code to update prices for all customers (members) in their subscription items in Stripe via its API. Works just fine and I can see the future invoice has changed to the new value. (Its charging for annual membership of an organisation)

    Noting Duncans comment up thread re adding a new price to a Memberstack produce i'm hoping to avoid having to set up a new Memberstack product to avoid changing product_IDs on the Webflow front end.

    Of course that will fix it for any *NEW* members but what I need to figure is what that means for existing members who joined under the old price - renewals/payments will be at the correct price from Stripe but what is reflected on the website from Memberstack ??

    0
  • Comment author
    Duncan from Memberstack

    Update Magnaem created a Memberscript + tutorial explaining how to bulk update existing Stripe subscriptions. https://www.memberstack.com/scripts/bulk-update-stripe-member-subscriptions

    Chris Amos Memberstack will always display/respect what is in Stripe. Do you have any prices hard-coded into your website? 

    1
  • Comment author
    Chris Amos

    Thanks Duncan. Very useful tutorial...hadn't used Make before (I coded it in Node Red as very familiar with that - make looks easier in this use case).

    Ah ok. Theres no prices hardcoded in Webflow, it uses the (Memberstack) product ID as the link. I won't be changing product names in either Memberstack or Stripe - i'll just be creating a new product price in Stripe and making that the only/default one for the product on that side, then the code will update the existing (Stripe) Subscription Items with that new price ID.

    If that change is then reflected back into Memberstack that will be a great outcome. Question : when does that happen - is it on an "on-demand" basis when the object is accessed in memberstack or is there a sync process every so often?

    Just trying to understand the end to end process to make it easier next time.

    Thanks!!

    1
  • Comment author
    Duncan from Memberstack

    I think your best bet will be to do a quick prototype to confirm everything is working as expected. If not, let me know what went wrong and I'll see what I can do for you 😁

    0

Please sign in to leave a comment.