114
Multiple membership plans
under review
Duncan Hamra
1) My customers can only have one plan (role, membership, product, etc) at a time.
2) I can't use Memberstack with my pricing model. My pricing model is key to my business model, branding, positioning, marketing, etc. Pricing is core to any business.
3) Change my pricing. Use another tool. Build a direct Stripe integration.
4) Please let me add multiple subscriptions to a particular member or multiple quantities on a single subscription.
Activity
Newest
Oldest
L
Lauren Pope
Any update on this? I really want to be able to sell multiple memberships., and will have to swap to another solution if this will not arrive soon.
Naitik Mehta
Lauren Pope: Hi Lauren! If you or a team member is technical, Memberstack 2.0 has multiple memberships and can currently be implemented via code. We're sending out invites to the waitlist - sign up here if you're interested. :)
L
Lauren Pope
Naitik Mehta: I'm not technical unfortunately. any update on when it will be part of the core product please?
Naitik Mehta
Lauren Pope: Gotcha! We'll drop an update when we have an ETA for a public release of multiple memberships. It's currently being tested by developers in our beta. 🙏
L
Lauren Pope
Naitik Mehta: Any update on this?
Tanner
This would be FANTASTIC for us...currently going to try to do a workaround by having several dozen memberships that represent different bundles of products. Please put me at the top of your beta developers list!
Naitik Mehta
Tanner: Be sure to sign up here for 2.0 so we can loop you in as soon as we're ready 💯
M
Martijn Hoppenbrouwer
Is there some insight in when this will become available?
We're planning to have new subscription items every week, so we cannot use a combined package - we need pure separate subscriptions and let people choose (on different websites) which they all want to subscribe to.
K
Kyle B
How is this STILL not done?
Duncan Hamra
Kyle B: Hey Kyle! 👋 Hope you're doing well.
We're having to rebuild everything to make this happen. It's quite hard to rebuild from scratch, so it's taking some time. That said, we're doing our very best and it will be ready ASAP. If you need something right now, let me know. I'm happy to help you find another solution that's a better fit 👍 We don't want to rush this suuuuper important next step, but we also don't want to slow you down.
A
Anthony Templin
Having the ability to treat memberships as plans and let users join and pay for multiple exactly what I need right now! Thank you for working hard on this! Any estimates on when we get the new version?
Duncan Hamra
Anthony Templin: Hi Anthony 😊 Thank you so much for the kind message! We're making steady progress. I'm afraid there's still now ETA, but I can confirm this feature is in alpha for developers. That said, we still need to finish the no-code layer, which will take some time.
C
Colin Simmons
I cannot WAIT for this. I actually was unable to use Memberstack for a recent project because of this limitation — customers needed to add new memberships at will (buying courses). Had to use Memberspace as they do offer that functionality, but I'm really not as excited by Memberspace — they have a lot more limitations as far as API and styling goes.
Duncan Hamra
Colin Simmons: Thank you for letting us know 🙏
I'm happy to share that multiple memberships are officially built into Memberstack 2.0. I wish it was/is ready for you, but not quite. We're getting there!
J
Jérôme
Duncan Hamra: When are you planing to release it ? I need this exact feature for a project that is starting now. Thanks !
Duncan Hamra
Jérôme: I wish I could say right now, but it will likely be a few more months. We're making steady progress though! I'll follow up directly with an alternative solution for you.
J
Jacob Binnie
Duncan Hamra: I CAN'T WAIT! What's the expected timeframe for a beta release of Memberstack 2.0? Multiple memberships are going to be an absolute game changer.
Duncan Hamra
Jacob Binnie: ASAP is the best I can say right now! I wish I could be more specific, but this is our first time building something like this. Makes estimating quite hard 😅 How soon do you
need
it? I'm happy to help you find a solution when you need itWe can't wait either 😁 Ahhh this is going to be soooo darn great!
J
Jacob Binnie
Duncan Hamra: Hey Duncan. Ideally, I'd love to be implementing this ASAP. What kind of time frame do you realistically think we're looking at? Can appreciate you guys are working hard on it. Also would love the ability to assign specific users EDIT rights to certain memberships.
Duncan Hamra
Jacob Binnie: Definitely not in the next month, but we are making steady progress.
Can you tell me more about that last note? If you have time, can you make a new wishlist post about it? I'm really curious to learn what problem that will solve for you.
J
Jacob Binnie
Duncan Hamra: Hey Duncan. Ideally, the multiple memberships functionality will solve everything. As long as I can trigger a Zap to edit specific memberships and/or create new memberships I’m sorted. Will you know if I’d be able to trigger new membership creations / edits of current memberships with zapier automations?
m
make give live
Hey Duncan
My scenario could be to have a Free Tier that everyone can sign up to and then a premium tier that's charged on a monthly fee.
I don't want people to have to choose one or the other but to first become a Free member and then be offered the Premium membership once they are logged in. They can sign up and pay for this with their existing credentials.
Is this possible right now or would it be possible in Memberstack 2.0?
Thanks
Jonathan
Duncan Hamra
make give live: Hello hello! This is a great question. This is currently possible with Memberstack 1.0, but would require a member to transition from the free plan to the paid plan. This works great 90% of the time, but has some not-ideal side effects. For example: If they cancel their plan, instead of falling back to the free tier, they end up "stuck" on the cancelled paid tier.
Duncan Hamra
Update time 🎉🎉🎉 This feature is entering suuuuper early alpha as part of Memberstack 2.0 this week.
We want to share the good news, but also make it perfectly clear we're still some months away from having this be readily available to all users. Thanks for your patience!
Gowtham Sundaresan
This would be amazing!
For those of you who want to do this immediately, until the feature comes out, I managed to get this functionality for my course-selling platform.
I essentially have made each course a different membership on MS. I've also set up MS fields for each course (Course 1, Course 2, etc). The user pays for a course by signing up for a membership and then I pass a hidden field to make the MS field "Course 1 = Purchased". When they purchase another one, we make them change their membership to say Course 2 and make "Course 2 = Purchased".
Now, on Webflow, we gate content based on what the values of Course 1/2/3 are (Purchased, Completed, Not Purchased), and not what the user's membership is. This gives us flexibility to bundle courses or sell multiple courses to the same person.
D
Dominic Coutts
Gowtham Sundaresan: Hi Gowtham, I don't quite follow, can you elaborate on how you implemented this workaround as really need to find a way to allow people to sign up to different courses without losing access to the gated content. Your help will be hugely appreciated!!
D
Dominic Coutts
Duncan Hamra Are you able to give me a bit more detail on how to implement Gowtham's workaround - I'm using Webflow and very familiar with that, but new to Memberstack so can't quite follow the process he's suggesting but it may make total sense to you.
D
Dominic Coutts
Duncan Hamra Gowtham Sundaresan - I would really like to implement this but need your help!
I have created the hidden fields and am guessing you used Zapier to update the value to 'Purchased' etc
However, I can't figure out how to gate/hide the content based on this value?
Duncan Hamra
Dominic Coutts: I'm afraid I don't fully understand how Gowtham has his site setup 🤔 If I had to guess, I assume he's using the backend API to update the membership which is granting/revoking access to content. But I'm really not sure 😞 We're super excited to get this feature released!!!!
D
Dominic Coutts
Duncan Hamra: Thanks for coming back to me. At least I wasn't being dim!
In the meantime, I'm back to the drawing board with finding a solution that offers this functionality - outseta.com is nearly there, but not quite and also has the required features on their roadmap.
Would be interested to know how soon you'll be able to release these features... Q1 perchance?
Duncan Hamra
Dominic Coutts: Hey Dominic! We're releasing this feature into a suuuuuuper early alpha as part of the roll out for Memberstack 2.0. We're making progress but there's still ALOT of work before this feature is available to everyone. At this point, it would be irresponsible for me to ask you to wait for us to release it. That said, we'll keep working and get it out ASAP!
Gowtham Sundaresan
Duncan Hamra: Dominic Coutts
Hey, just saw this thread - didn't realize that there was discussion going on here. Anyway, Dominic got in touch and I ran him through how I did it, but for anyone else who wants to implement the same, here's how I went about it.
Step 1:
Create fields for every course on Memberstack. Course 1, Course 2, Course 3 for this example. These fields will always be one of “Not Purchased”, “In Progress”, “Completed"
Step 2:
Create a membership for each of these courses. Course 1, Course 2, Course 3 for this example. Since we are dependent on MS for billing, if someone buys a course after already buying a course previously (and hence associated with some membership), we can bill them for the second course only if we “change their membership”. And hence having just one general membership wouldn’t suffice, since we wouldn’t be able to bill them again.
Step 3:
On Webflow, create a sales page for each course. For this example we will delve into the sales page of Course 1.
3.1 On this page, create a form with a button that has the attribute of the Course 1 membership and input fields. You would need to decide what input fields you would like. Usually it’s “email", “password", “name". (I restricted it to just “email" as an experiment to see if a lower barrier of entry leads to higher conversion rate.)
3.2 Create input field in the same form with the element IDs #course-1, #course-2, #course-3 and set the display property of these fields to “none”. Make sure that these fields have the attributes set corresponding to the fields on Memberstack. In this example: "data-ms-member = course-1”. Of course, the submit button needs to have a data-ms-membership attribute set to the corresponding to the Course 1 membership ID on Memberstack.
Step 4 (where the fun stuff happens):
In the page <head> tag, add this code
var Webflow = Webflow || [];
Webflow.push(function () {
$(‘#course-1').val("In Progress");
});
So when the user clicks the button to purchase the course, their profile on MS will automatically get updates with these 3 fields as well, on top of what they filled out for name, email and password. Make sure to change the code to reflect which course is to be set to In Progress depending on which course’s sales page this code is placed.
Now we have the workflow built for new members who don’t have an account and are making their first purchase, or create a new account without purchase.
Step 5:
Existing members who already have signed up and purchased Course 1, would need to be able to buy Course 2. We would need to either re-direct them from the sales page created in Step 3 to a “Sales page for members”, or play around with showing and hiding elements on the page created on Step 3. I went with the latter for different reasons, but for the sake of this example let’s go with the former.
5.1 Setup a re-direct to go from course sales page -> course sales page for members if the user is logged in.
MemberStack.onReady.then(function(member) {
if (member.loggedIn) {
}
});
5.2 Create with a “Buy Now” button with the data-ms-membership = membership ID. Clicking this will allow the user to switch memberships by paying the corresponding amount associated with Course 2 membership.
Step 6:
6.1 On Zapier, create a Zap with Trigger for “Membership Changed in Memberstack"
6.2 Make the action to “Update Member in Memberstack” depending new Membership. If “New Membership Subscribed to exactly matches <course 2 membership ID>”, then update the member's Course 2 field to “In Progress”.
Please note that Zapier “Paths” is used to create an if/else structure but they’re currently limited to 3. So if you plan to have more than 3 courses, use Integromat instead of Zapier. Or possibly duplicate the Zap for every 3 sets of courses (haven’t tested this, but it would not be the most optimal way to do things)
Now we’re able to keep track of who buys what courses for any number of courses :)
Step 7:
Now it’s all upto showing/hiding the content we want to show on our site. So if we have a dashboard page for logged-in users, and someone clicks Course 2 without purchasing it, we want to send them to the “Course 2 sales page for members” instead of being able to view the videos. So what we would do is:
MemberStack.onReady.then(function(member) {
let course2 = member[“course-2"];
if (!(course2 == “In Progress”) && !(course2 == “Completed”)) {
}
});
Similarly you can get creative with showing/hiding elements to craft a better UX.
Gowtham Sundaresan
If you’re using Collection Lists, skip the embeds, just pull in the values directly into the relevant Text Blocks or Image Fields, etc via CMS. In order to manipulate a specific Collection Item from data taken from the API, do this:
Example: We want to set a Text Block to indicate the Course Status (“In Progress”, “Not Purchased”, “Completed”) for any given course for a logged-in user.
var collectionItems = document.getElementsByClassName(“course-collection-item”); //“course-collection-item” is the Class Name of the Collection Item (immediately under Collection List)
var courseTitles = document.getElementsByClassName(“course-titles”); //“course-titles” is the Class Name of the Text Block that displays the Course Name in a Collection Item. Taken from CMS.
var courseStatusText = document.getElementsByClassName(“course-status”); //“course-status” is the Class Name of the Text Block that displays the Course Status. We want to set this value.
//From MS API
let course1Status = member[“course-1”]; //Will return one of “In Progress”, “Not Purchased” or “Completed”.
let course2Status = member[“course-2”];
for (var i = 0; i < collectionItems.length; i++) {
if (courseTitles[i].innerHTML == “Course 1") {
//Now we know that we are in the Collection Item of Course 1. We can do whatever we want here.
courseStatusText[i].value = course1Status;
}
else if (courseTitles[i].innerHTML == “Course 2”)
//Now we know that we are in the Collection Item of Course 2. We can do whatever we want here.
courseStatusText[i].value = course2Status;
}
}
C
Chris Allen
Hi Duncan Hamra I am currently in the process of building out my first course based service for a customer and my stack is Webflow and Memberstack. Then I realised multiple memberships couldn't be applied to the same user. Do you have any times frames for when this will be completed?
Duncan Hamra
Chris Allen: Hi Chris! I'm going to follow up via email. I'm afraid we won't have an Webflow version of this feature until we're able to migrate to Memberstack 2.0
Load More
→