WooCommerce Memberships 1.11.0 is here! The new version is packed with important features both above and under the hood. This release of Memberships represents an important milestone in the evolution of this extension, and we’re very excited to see what it brings next.

We have a really cool new integration, tools developers will love, and better guidance for new users. Let’s dive in! ????

PHP 5.3 is now required

Starting from this version, Memberships will require PHP 5.3. According to WordPress statistics, only a tiny fraction of installations still run PHP 5.2, which has been unsupported since January 2011 (which means this version of PHP is older than WooCommerce!). We can build more performant software with better security by building on new technologies, so most of our extensions are beginning to require PHP 5.3 or PHP 5.6. You can read more about upgrading PHP here.

We still maintain compatibility with WooCommerce 2.6, although we will phase out support for this version within a few months as well. Just like PHP, you’re better off running updated software on your server — keep the engine for your online store well-oiled. 🙂

Of user onboarding and wizards

Memberships is a large plugin, and a powerful one. To build a member system on top of WooCommerce, it adds new settings and emails, introduces unique concepts like plans and members, and adds data to products and other content. Many users feel just comfortable with this, but it can be intimidating for others who are new to WooCommerce or WordPress.

While much of our customer feedback indicates that Memberships is easy-to-use, we can always improve the experience for new users and make it even simpler. A first step in this direction is the addition to Memberships of what we call a Setup Wizard ????: an onboarding tool resembles the WooCommerce wizard that users see the first time they activate WooCommerce.

WooCommerce Memberships: onboarding step 1

Very familiar, isn’t it?

In the first screen, we introduce the concept of restriction and explain how each mode affects non-members. We’ll save the answers here to the Memberships settings, breaking up the “getting started” process for new users, while taking the time to explain more complex concepts.

We then ask questions that are directed at creating a membership plan right away. The wizard helps users get acquainted with Memberships concepts they’ll find in the plans creation pages later on.

WooCommerce Memberships: onboarding step 2

Rules determine what is restricted or offered to members only, so it’s important to introduce this concept early with explanation. For teaching purposes, we limit the screen to set one rule per group (content restriction, products restriction, and purchasing discount). But, as the new plan will be saved (as a draft), more rules can be added later with this foundational knowledge in hand.

WooCommerce Memberships: onboarding step 3

Finally, users can enable Member Emails and define their sending schedule. You’ll notice from the screenshot below that there’s also a new group of emails! We’ll show you more in a moment.

WooCommerce Memberships: onboarding step 4

We wrap up by letting users know they can edit their new plan, and point them to helpful resources to get started.

WooCommerce Memberships: onboarding step 5

A RESTful API for Memberships

So those new email types we just mentioned? They’re made possible because Memberships now supports the WordPress and WooCommerce REST APIs!

This means that external systems can now interact with Memberships via the common WordPress API — this is also used by WooCommerce and other extensions. This is very handy if you plan to build apps or tools that need to read your membership data, from command line tools to system tools, mobile apps and so on.

For this first step we will provide support for v2 of the API and list read (GET) endpoints for Membership Plans and User Memberships. In future versions, we will add full CRUD support.

The two main endpoints that have been added under the WooCommerce namespace are: api/wc/v2/memberships/members for User Memberships and api/wc/v2/memberships/plans for Membership Plans.

There is a limitation to be aware of: rules are not listed in the plan endpoints or as an independent object yet. We are still debating how rules should fit into the Memberships API, and will collect feedback on the best way to implement API support. Your voice matters as well, so please don’t hesitate to reach out if you plan to build something with the Memberships REST API: we’d love to see what you’re working on!

We have published documentation for the Memberships REST API where you can learn more about the responses delivered by these endpoints and how to query the API. We will keep updating this document as we add more features and endpoints. We plan to add more code examples as well.

If you’re interested in contributing to this project, you can also log an issue or submit a pull request.

WooCommerce webhooks support

With the REST API support, of course, we could also easily introduce support for WooCommerce webhooks.

You can now configure new WooCommerce webhooks to be triggered every time a membership event is fired: when a membership is created, when it is updated, when it expires, when it is transferred to another user or when it is deleted. CRUD events for plans are supported too.

With the added webhook support you can now connect WooCommerce Memberships to third party apps and services that are informed when a membership event takes place at your site! The payload delivered is equivalent to that of the REST API responses, for consistency.

Jilt-powered membership emails

So a REST API on its own isn’t necessarily too exciting, right? It’s most valuable when an app or integration uses that API to connect to your store. As part of making a great start on read-only endpoints, we wanted to be the first consumer of this API. I’m happy to say that Jilt has already integrated with WooCommerce Memberships. (You can learn about Jilt here).

Developers on our Jilt and WooCommerce extension teams have been working in tandem for several weeks to accomplish a couple of things:

  • help Jilt evolve from sending automated order emails, to being able to send other kinds of automated emails, too.
  • ensure that Memberships has a robust starting point for its API by building an end-to-end integration with Jilt.

This means that advanced member emails are here.

WooCommerce Memberships: Jilt membership campaigns

Jilt membership campaigns

One of our most common requests from merchants was to be able to send more emails to members. However, we were hesitant to add more scheduled emails than the basic ones that are already built into Memberships — WordPress isn’t great at a few things: managing thousands of scheduled events, and sending emails are two of them.

However, Jilt is great at these things, so offloading your automated emails to a system that can schedule them, send as many as you need (with excellent deliverability), and segment your members as much as you choose (by status, plan name, or other membership properties) was a clear path forward for our team.

WooCommerce Memberships: Jilt welcome campaign rules

If you connect your WooCommerce store to Jilt, you can enable the WooCommerce Memberships integration. Then, you’ll have several membership templates available for your campaigns:

  • New member welcome — Every new member should feel valued, and know exactly what they’re going to get out of your membership. You can send a single welcome email or a series to thank your new members, get feedback, and outline what to expect from your membership.
  • Paused membership reminder — Keep in touch with members who have paused memberships to help them re-activate. This is useful if your site uses WooCommerce Subscriptions, as a subscription-tied membership can be paused by your member. Help reengage these paused members with a reminder. Or, if you pause memberships on request manually, this reminds your members to get back in touch when they’re ready to reactivate.
  • Membership ending soon — Send one or more emails before a membership ends to encourage your customers to renew a membership. This can help you ensure that the membership end date is no surprise, and that your customers can purchase again to extend memberships before they lose access.
  • Cancelled membership win-back — Did you member request cancellation, or cancel via their subscription? You can send a win-back email or series to get feedback to understand why they left, or to see if you can save the sale.
  • Expired membership win-back — Should your members repurchase when their membership ends? Send a series of 3 emails to win-back members after their membership expires. Jilt will even automatically stop sending emails if your member does renew.

WooCommerce Memberships: Jilt email content

You can completely customize the content of these member emails, and can segment your audience using Jilt’s built in rules for memberships and customers. Target specific plans with different content, change the timing of your emails based on plan time, and more!

We’re not done with this integration yet, and we’re very excited to unite two of our most popular products here at SkyVerge.

Published by

Beka Rice

Beka leads product direction for SkyVerge and technical documentation. She spends a lot of time on research and interviews, but likes to write so she has an excuse to spend more time jamming out to anything from The Clash to Lady Gaga.

Fulvio Notarstefano

Fulvio is a WordPress engineer, and spends most of his time on new plugin development and updating existing plugins. You'll find him on the SkyVerge blog keeping you in the loop on what's new with our plugins, along with helping in your support threads.


  1. […] enabled when Jilt detects that your store has the Subscriptions (v2.1+) or Memberships (v1.11+) plugin active, so there’s nothing you need to install or […]

  2. Can’t wait to dig into the api

  3. […] emails, educational series after a purchase, feedback requests to encourage product reviews, emails for WooCommerce Memberships, and […]

  4. Is it on the timeline or in the plans to include the ability to update memberships via the API? Seems the current endpoints are GET only.

    • Hey Steve! PUT / POST / DELETE support is indeed on our radar — currently we’re looking at full CRUD support for user membership endpoints in v1.13.

  5. +1 to Steve Palm’s comment. Very excited for this release and finally tying into the REST API, but we have a specific use case that requires updating memberships via POST / DELETE.

    Looking forward to CRUD support in v1.13 soon… hopefully! 🙂

    • Us, too! We’re beta testing v1.13 now with CRUD support for user memberships (and will be looking at write endpoints for plans in the following release).

  6. //However, we were hesitant to add more scheduled emails than the basic ones that are already built into Memberships//

    Can’t understand why a new member welcome email is not considered a ‘basic one’.

    Seems like it’s crippling a functionality to sell a different product.

    • Hey Srikanth, the next part of that sentence is just as important as the part you cited: “WordPress isn’t great at a few things: managing thousands of scheduled events, and sending emails are two of them.” If we loaded your site with tens of thousands of scheduled events for future emails, we could risk degrading its performance. We also don’t recommend sending emails from the shared IP address your website uses since it’s not good for deliverability, but we also recognized it might be a “good enough” starting point until the site grows enough to invest in proper email infrastructure. We want to balance performance and features as much as possible, so we’ve added the emails that 90%+ of users need (even it’s not the way you should do email if you can avoid it), and more advanced needs, such as drip series, can be covered by other tools.

      Can’t understand why a new member welcome email is not considered a ‘basic one’.

      We see most folks do this via their order receipts — unlike dedicated member systems where you signup in a form, using WooCommerce means you’ve completed a checkout flow. Since new members have to purchase to get access, they’ll get your receipt email, and you can add purchase notes for the member product for details for specific information.

      Seems like it’s crippling a functionality to sell a different product.

      Not in the slightest — in fact, it’s main reason we included the Memberships integration on the Jilt free plan, not its paid plan (and continue to offer a free plan for Jilt even though it costs us a lot of money), and have built integrations with other email systems. We also built a public REST API in Memberships so other email services could get your member information, too. To be clear, the Jilt integration with Memberships is great, and opens up some cool, advanced usage. 🙂 If it’s not right for you though, of course we don’t want you to use it — without Jilt, we still wouldn’t add things to Memberships we don’t think are best for users, we would simply continue to recommend using a dedicated email solution to go further. As the site grows enough to need more from email, it’s important to offload those scheduled events and use proper email sending infrastructure, regardless of where it is.

      • Beka, Thanks for the detailed reply. I understand and appreciate the motivation behind the decision.

        I apologize for the tone of my comment.



        • Hey Srikanth, no worries, it’s pretty hard to find the right toolset for your site! I hope this clarifies how we approach these problems, and we appreciate the feedback 🙂

Hmm, looks like this article is quite old! Its content may be outdated, so comments are now closed.