There are three common ways to sell membership to a company or group on WordPress. A company buys seats and assigns people to them. A parent account sits over child accounts, such as divisions or chapters. Or the customer's own login system proves who people are, and there are no seats at all. Pick by who pays, who uses the site, and whether the buyer already runs single sign-on. Then check what each plugin does when the parent stops paying, because the documentation on that is thin and uneven.
We handle seat and sub-account changes regularly, and the plugin facts below come from the vendors' own documentation, named as we go. Where something is our opinion, we say so. When no plugin covers your seat rules, that is custom membership plugin development.
Which of the three models do you have?
Two questions pick the model before you compare a single plugin: who pays, and who logs in.
| Model | Who pays | Who logs in | How access is granted | Main risk |
|---|---|---|---|---|
| 1. Seats sold to a company | The company, on one billing record | Individual employees, invited by the buyer | A seat count on the parent's purchase | Seat changes and the parent's payment status do not reach the members correctly |
| 2. Company hierarchy | A parent organization | Members in child groups, with leaders at each level | Parent-child relationships, sometimes with pooled seats | Who can see and manage what at each level |
| 3. Institution authenticates | The institution, by contract | Students, staff or employees using the login they already have | The institution's identity system vouches for them | Setup with the identity provider, not seat counting |
A university that wants access for its whole campus through the login it already has is model 3, and selling that as “500 seats” means keeping a list of names nobody needs. A named cohort for one course is model 1 instead. A 40-person company buying training for its team is model 1, and forcing it through a single sign-on project is more work than the sale needs.
Model 1: a company buys seats and assigns people to them
In the seat model, one buyer owns the billing record and assigns the seats. MemberPress Corporate Accounts, Paid Memberships Pro Group Accounts, WooCommerce Memberships for Teams and LearnDash Group Registration all work this way. They differ in four decisions that change what you can sell.
How a seat is priced
As of October 2026, WooCommerce's Teams product page lists two pricing options: per-member pricing, with the example “$15 per member,” or per-team blocks, with the example “$1000 for 500 seats.” PMPro offers fixed seats or variable seats, and a per-seat price you can apply to the initial payment, the recurring payment or both. MemberPress works differently. Its documentation says you set the number of sub-accounts on the membership, and a parent can add that many “without additional charge.” An admin can change the cap for one parent later. So the seat count is a cap, not a price. Our reading: different company sizes mean different membership products or hand edits.
Whether the owner takes a seat
The question is whether the owner counts against the seat total. Two of these plugins make it a setting. In WooCommerce Teams it is “Owners must be members.” LearnDash Group Registration has an option that requires the Group Leader to “consume a seat (and pay for access).” Decide it before your first sale, because it changes how many seats a team of a given size has to buy.
How people get added
A MemberPress parent can add sub-accounts by existing username, a new-user form, a signup URL or a CSV. The docs say adding an existing user “does not move an existing user if they are currently associated with another Corporate Account.” Members of a PMPro group join with a group code, an invite link or an invite by email. In WooCommerce Teams they use a join link or an email invite, and the docs call the link “less secure.”
Adding people in bulk
A parent's CSV upload in MemberPress is capped at “a maximum of 200 sub-account entries.” The admin importer has no limit, though MemberPress recommends 100 to 200 users per file.
Model 2: a company hierarchy with leaders and pooled seats
In a hierarchy, the parent is an organization with parts of its own, and each part has a leader.
Uncanny Groups for LearnDash supports parent and child groups and can pool seats. Its documentation gives the example of a parent group with 100 seats and a child group with 50: with pooling on, the pool is 150, and if 30 users enroll through the child group, 120 seats remain across the whole hierarchy. Only administrators can create the hierarchy, unless you turn on the front-end edit option.
PMPro Group Accounts can run three tiers: grandparent, parent and child. Its documentation states the limit: “Grandparent does not directly manage or see the Child accounts.” The documented structure also assumes the grandparent pays for everything below it, because a group code sets the price of the sponsored level to zero.
MemberPress Corporate Accounts describes a parent and its sub-accounts. The documented way to hand the account to someone else is “Make Parent”: an administrator first adds the future parent as a sub-account, then swaps the roles. When a PMPro leader departs, the new leader checks out for the parent level with the right number of seats, and an administrator transfers the members to the new group code. PMPro then recommends updating or removing the old leader's membership level and canceling their subscription.
If buyers need to see progress, check reporting before you check pricing. MemberPress Courses 1.1.6 and later let corporate owners view the course progress and quiz scores of their sub-accounts. LearnDash's core Groups feature lets a Group Leader track the progress and performance of any user in their group. Confirm that the view you need, for example one that rolls up across divisions, exists before you buy.
Model 3: the institution logs people in, and there are no seats
For institution-wide access, the institution's identity system confirms who each person is, and your site decides what that person can open. This suits buyers who will not hand you a list of names, such as universities, libraries, hospital systems and large employers, who want their people to sign in with the login they already have.
OpenAthens, whose federation page says it has over 3,000 members, states that it “supports SAML, a highly secure, privacy-preserving authentication method.” With SAML, the institution's own system handles the sign-in. How your site turns that sign-in into a WordPress account and an access level is part of the build. In this model you sell an institutional contract rather than a seat count. That framing is ours, not a feature of the standard.
Free Movement's university single sign-on through OpenAthens went live in under two months. The case study reports that OpenAthens said such projects typically take under a year. Details are in the OpenAthens integration case study.
Plugin by feature, as of October 2026
Compare the stack you need, the seat model, bulk enrollment and hierarchy support. Prices are vendor-listed in October 2026 and can change, so confirm on the vendor's page before you budget.
| Plugin | What you need | Seat model | Bulk add | Hierarchy |
|---|---|---|---|---|
| MemberPress Corporate Accounts | MemberPress Scale 1.3+ and the MemberPress Importer add-on. Scale first-year price as of October 2026: $499.50, listed as normally $999, with renewals at full price | A parent membership with a set number of sub-accounts, no added charge | Parent CSV up to 200 rows. Admin importer has no limit | Parent and sub-accounts only, in the docs we read. Admin can promote a sub-account to parent |
| PMPro Group Accounts | A Premium add-on. The Standard license is listed at $499 a year for one site with all Premium Add Ons | Fixed or variable seats, with optional per-seat pricing | CSV import: parents first, then children by group ID | Three tiers are the documented practical structure, and more are possible. The top tier cannot see or manage the bottom |
| WooCommerce Memberships for Teams | WooCommerce Memberships (bought separately, price not checked) plus Teams, listed at $129 for a 1-year plan. The recurring-billing workflow below also requires WooCommerce Subscriptions | Per-member or per-team block pricing, with optional minimum and maximum | Join link or email invite. Team data exports, but there is no import | Owner, manager and member roles |
| LearnDash Group Registration | LearnDash, WooCommerce, the LearnDash WooCommerce Integration add-on and Group Registration, plus WooCommerce Subscriptions or an equivalent for subscription products. Nexcess lists group seats on every LearnDash plan (as of November 2026) | A WooCommerce product sells seats. The buyer becomes Group Leader | CSV with first name, last name and email | LearnDash's Group Hierarchies setting. Sub-groups take seats from the parent, and sub-groups cannot create further sub-groups |
| Uncanny Groups | LearnDash and WooCommerce, plus WooCommerce Subscriptions for the subscription workflow below. Single license first-year price as of October 2026: $179, listed as normally $249, with renewals at full price | Group licenses sold once or on subscription. Buyers can pick courses and seats | Leaders add users singly, in bulk, by CSV or by enrollment key | Parent-child groups with pooled seats, which need Uncanny Groups v5.0 or later and LearnDash Group Hierarchies |
MemberPress sells Launch, Growth and Scale plans, and Corporate Accounts sits on Scale only. Its docs say: “This add-on is available to MemberPress Scale plan members.” One Google AI Overview we pulled in October 2026 said Pro. On LearnDash, the older Pro and Elite plans are closed to new buyers. It now comes only inside the Nexcess plugin stack, from $350 a year for one site, and Nexcess's package page lists group seats and multiple instructors as part of the LearnDash product on every plan (our LearnDash pricing guide has the dates for existing subscribers). Confirm on Liquid Web's LearnDash page before you buy.
Our default: if you already run MemberPress on the Scale plan, start with Corporate Accounts, because it adds no second billing system. If your product is courses on LearnDash and you sell to organizations, Group Registration or Uncanny Groups fit better. If the seat rules you need are in neither column, that is when custom code earns its cost.
What happens when the parent stops paying
Vendors document a parent who stops paying unevenly: some spell it out, and for MemberPress the docs we read do not. Roundups and setup guides mostly skip it, so lapse behavior takes digging. The table shows what each vendor documents, and only that.
| Plugin | Parent cancels, lapses or is refunded | Adding seats mid-cycle | Removing seats | Watch for |
|---|---|---|---|---|
| MemberPress Corporate Accounts | The docs do not spell it out. They do say an admin who unchecks the Corporate Account box revokes access for all sub-accounts | An admin raises “Max Sub Accounts.” The docs describe no billing change | A parent can remove sub-accounts. The docs do not say what happens if the cap is set below the number in use | Test lapse, failed renewal and refund on staging before launch |
| PMPro Group Accounts | When the parent loses membership or changes level, children “lose access immediately.” Removal runs in the background through Action Scheduler, so check timing on staging. They do not rejoin when the parent comes back, so the parent must send a new invite link. The pages we read do not separately cover a refund | An admin can change the seat count, and the docs note this “does not update the subscription price” | A parent can bulk remove members | Per-seat totals do not display at checkout. Promo codes apply to the parent level, not to seats |
| WooCommerce Teams with Subscriptions | A canceled subscription cancels all team memberships. A paused one pauses them. A full refund cancels them all. After a partial refund you adjust seats and members by hand | The owner pays a prorated charge now and a new recurring total | Per-member: the lower recurring total applies at the next renewal, with no refund for unused time. Per-team blocks: seats cannot be removed | Subscription switching cancels the team and creates a new one, so everyone must be re-added |
| LearnDash Group Registration | With a subscription product, if the subscription ends and is not renewed, the group may move to Draft until renewed, depending on configuration | Buy more seats on the same product, or an admin edits the seat count | Depends on settings. Leaders remove directly or send a request to an admin | A CSV with more users than seats fails entirely |
| Uncanny Groups | Canceling a group cancels all of its subscriptions together. If fully expired, the buyer starts one new subscription sized to current needs. The page does not say what happens to enrolled members | Each added seat block on a subscription group creates its own new subscription | Seats are reserved from the moment an enrollment key is issued. Removing a pending user frees the reserved seat but does not invalidate their enrollment key, so they can still register later if seats are available | Courses cannot be added to subscription groups. Downgrading a WooCommerce group is not reversible through the plugin interface |
Sources, all read in October 2026: MemberPress's Corporate Accounts documentation, PMPro's Group Accounts documentation (member experience and admin guides), WooCommerce's Teams documentation, LearnDash's Group Registration documentation and Uncanny Owl's knowledge base.
Do not carry one plugin's behavior over to another, and treat MemberPress's undocumented lapse behavior as unknown until you have tested it on staging.
The pages we read describe cancellation, refund, pause and expiry. None of them walks through a card that fails and is retried over several days. Run this list on staging before you sell the first seat:
- Let the parent's renewal payment fail, and watch what the members see on day one, day three and after the last retry.
- Cancel the parent's subscription at the end of the period, then immediately, and compare.
- Refund the parent in full, then in part.
- Restore the parent after a lapse and check whether members return on their own.
- Remove a member, then add the same person again, and check the seat count each time.
- Try to reduce seats below the number in use.
- Add seats mid-cycle and check the charge today and the recurring total.
- Check who gets the renewal and expiry emails. In WooCommerce Teams, members get none and only the owner does.
LearnDash Groups, Group Registration and Uncanny Groups
LearnDash's core Groups feature can enroll a group's users in courses automatically, but it does not sell seats by itself. LearnDash's documentation says selling to organizations needs an add-on, and Group Registration is that add-on. A WooCommerce purchase creates a LearnDash Group, and the buyer becomes its Group Leader. It supports buying more seats on the same product, and a setting called “Fix Group Limit” controls whether seats reopen when users are removed.
Uncanny Groups for LearnDash adds a front-end dashboard for leaders, CSV upload, enrollment keys and pooled seats, and sells group licenses through WooCommerce one time or on subscription. To pick the LearnDash plan underneath, our LearnDash pricing breakdown covers what each plan includes and the November 16 renewal change. If you are still choosing the LMS itself, our comparison of WordPress LMS plugins puts LearnDash next to MemberPress Courses, Tutor LMS and LifterLMS and scores each on seats for organizations.
What we see on real sites
Recently an owner asked us about a MemberPress site that sold individual plans and two kinds of group plans, one with fixed seats and one with variable seats. They wanted to simplify it or move to PMPro without breaking renewals.
Five design rules for any seat system
These are general design advice, and they hold whichever plugin you choose.
- Treat seats as their own record, not a number tucked into user data. With a large member count, a purpose-built table holds up better than user meta.
- Protect occupied seats before reducing. Block a reduction that would leave fewer seats than people using them, or make the buyer choose who goes.
- Decide whether leaders count as seats before the first sale, because pricing depends on it.
- Keep both directions in sync. Removing a user from the group should end the sub-membership and update the seat count, and the reverse.
- Log every change and retry failures, so a failed sync shows up in the log and a retry replays it.
Keep the history of people who lost a seat, too. A person who left a team should stay in the group's reports, marked as unseated, so the leader keeps the record.
Seat code also breaks in ordinary updates. The MemberPress Corporate Accounts changelog for version 1.6.1, dated 10/16/2026, says: “Fixed adding and removing sub-accounts and importing them from CSV, which broke in 1.6.0.” PMPro Group Accounts 1.6.1 fixed a bug where “new group members could be created on the Manage Group page after all seats in the group were filled.” After every update, test add, remove, CSV import and the full-seats case.
Moving a seat setup without breaking renewals
Treat billing records and seat records as two jobs. Move the seat records first and leave billing alone until the seats match.
- Export each parent with its seat count, and each member with the parent they belong to.
- Check how the target plugin imports. PMPro's guide says to import parents first, with a
pmprogroupacct_group_total_seatscolumn, then import children with apmprogroupacct_group_idcolumn. WooCommerce Teams has no import: its docs say you cannot update team information via an import, so teams are created by hand and linked to the subscription. - Compare counts. For every parent, reconcile occupied seats against the plugin's rules, including whether the owner or Group Leader takes a seat.
- Run the lapse tests above on a copy of the site.
- Switch parents over in batches, not all at once.
We rebuilt TechServe Alliance's platform over 20 months, and not one member had to re-subscribe or re-enter payment details. See the TechServe Alliance case study. For PMPro sites, see our Paid Memberships Pro development work.
Frequently asked questions
Which MemberPress plan includes Corporate Accounts?
Scale. MemberPress's documentation says “This add-on is available to MemberPress Scale plan members.” It requires MemberPress Scale 1.3 or later and the MemberPress Importer add-on.
What happens to employees if the company cancels or loses its membership?
PMPro's documentation says child accounts lose access immediately when the parent loses membership (removal runs in the background through Action Scheduler, so verify the timing on staging) and do not rejoin automatically if the parent returns. In WooCommerce Teams with Subscriptions, a canceled subscription cancels every team membership. MemberPress's documentation does not describe parent lapse, so test it on staging.
Can a company add seats in the middle of a billing cycle?
Yes in WooCommerce Teams, where the owner pays a prorated charge now and a new recurring total after. In Uncanny Groups, each added seat block on a subscription group becomes its own subscription. In PMPro, an admin can change the seat count, but that does not update the subscription price.
Do I need seats if my customers are universities?
Not necessarily. If the institution runs an identity provider, it can authenticate its own people through SAML, for example through OpenAthens, and you grant access based on that sign-in.
Can I move from MemberPress to PMPro without breaking renewals?
Plan it as two jobs, seat records and billing records. Import parents before children where the target plugin imports at all, and test lapse behavior on a copy of the site before you switch real accounts.
If your seat rules do not fit these plugins, or you are moving seat data and cannot afford to disturb renewals, Book a chat and tell us the plan. For the build itself, see our custom membership plugin development.