WooCommerce User Management Guide

• Model type: role-based
• Description: WooCommerce extends the WordPress core role-based capability system. Each user is assigned one role; roles map to a set of capabilities (e.g., 'manage_woocommerce', 'edit_shop_orders'). Capabilities are checked at runtime to gate access to features. WooCommerce adds its own capabilities on top of WordPress defaults.
• Custom roles: Yes
• Custom roles plan: Custom roles require a third-party plugin (e.g., User Role Editor, Members) or custom code; not available natively in WooCommerce core. No specific paid WooCommerce plan required-depends on chosen plugin.
• Granularity: Capability-level granularity is available via code or third-party role-editor plugins. Out of the box, WooCommerce ships with two store-specific roles (Shop Manager, Customer) plus inherits WordPress roles (Administrator, Editor, Author, Contributor, Subscriber).

1. Log in to WordPress Admin Dashboard.
2. Navigate to Users → Add New.
3. Enter the required fields: username, email address.
4. Set a password (auto-generated or manual entry).
5. Select the appropriate role from the Role dropdown (e.g., Customer, Shop Manager, Administrator).
6. Click 'Add New User' to save.
7. Optionally check 'Send the new user an email about their account' to notify them.

Required fields: Username, Email address

Watch out for:

• Username cannot be changed after account creation in WordPress core.
• If 'Allow customers to create an account on the My Account page' is enabled in WooCommerce → Settings → Accounts & Privacy, customers can self-register; this creates a Customer-role account automatically.
• Bulk user creation natively is not supported; requires a third-party plugin or the paid Customer/Order CSV Import Suite extension.
• Email notifications to new users depend on WordPress email delivery being correctly configured (SMTP plugin often required on self-hosted installs).

• Can delete users: Yes
• Delete/deactivate behavior: WordPress (and WooCommerce) supports permanent user deletion via Users → All Users → Delete. There is no native 'deactivate' or 'suspend' state in WordPress core or WooCommerce core. Deletion is permanent. When deleting a user, WordPress prompts the administrator to either delete all content attributed to that user or reassign it to another user.

1. WooCommerce core does not provide a native deactivate/suspend function.
2. To effectively block access without deleting: navigate to Users → All Users, click the user, change their role to a role with no meaningful permissions, or use a third-party plugin (e.g., 'Disable Users' or similar) to block login.
3. Some security plugins (e.g., Wordfence) provide user blocking functionality as an alternative to deletion.

Watch out for:

• There is no recycle bin or undo for user deletion in WordPress core; deletion is immediate and permanent.
• Customer order history is stored against the order record (with billing email), not solely against the user account, so order data may persist in the database even after user deletion depending on reassignment choice.
• Administrators cannot delete their own account from the Users screen; another Administrator must perform the deletion.
• On WordPress Multisite, user deletion from a single site only removes the user from that site; the network-level account remains unless deleted by a Super Admin.

• Where to check usage: WordPress Admin → Users → All Users. Filter by role using the role links at the top of the Users table (e.g., 'Administrator', 'Shop Manager', 'Customer'). Total user count per role is displayed.
• How to identify unused seats: No native 'last login' tracking in WordPress core or WooCommerce core. Identifying inactive users requires a third-party plugin (e.g., 'WP Last Login', 'Inactive Logout') that logs last login timestamps.
• Billing notes: WooCommerce core has no seat-based billing. Extension licenses are per-site annual subscriptions purchased from WooCommerce.com. Hosting costs are separate and determined by the hosting provider. There is no WooCommerce-managed billing console for user seats.

WooCommerce core carries no per-seat cost, so adding or removing users does not affect billing. Extension licenses are per-site annual subscriptions-for example, WooCommerce Subscriptions runs $279/year per site and Memberships $199/year per site. Hosting costs are separate and set entirely by the hosting provider;

there is no WooCommerce-managed billing console for user seats.

Community evidence is not specific enough to quote or summarize yet for this app.

WooCommerce is the right fit when you need a self-hosted store with full database ownership and are comfortable assembling a plugin stack for gaps in core. It is a poor fit if your team needs enterprise identity features-SSO, IdP provisioning, or automated deprovisioning-without significant plugin investment.

Every app in your stack that requires clean offboarding will expose the same gap: no native suspend, no SCIM, and no last-login signal in core. Teams managing more than a handful of admin or Shop Manager accounts should establish a documented offboarding checklist early, since deletion is immediate and permanent with no undo.

Bottom line

WooCommerce gives you granular role-based access control and zero per-seat cost, but every app lifecycle task beyond basic add/remove requires you to close gaps with plugins or custom code.

The absence of native user deactivation, last-login tracking, and bulk import means that operational overhead scales with your user base in ways that are not obvious at initial setup.

Teams that treat user lifecycle management as a first-class concern should audit their plugin stack before go-live rather than after.