The question that underlies almost every WooCommerce wholesale configuration challenge is the same one: how does the system know who this buyer is? Whether it is showing the correct price, unlocking a restricted product, applying a tax exemption, or enabling the bank deposit payment method — none of these things can work correctly unless the platform knows that the person placing the order is a verified wholesale buyer, and what kind of wholesale buyer they are.
The answer to that question is the WordPress user role system. A buyer who carries a wholesale role — assigned to their account after application and approval — is the account that the system uses to determine pricing, access, payment options, and restrictions. Without that role, the buyer is indistinguishable from any other logged-in WordPress user. With it, every layer of your B2B configuration activates automatically.
Many store owners assume that getting this right requires developer involvement — custom PHP, database manipulation, or at minimum a professional who understands WordPress internals. That assumption is incorrect. The entire wholesale role and registration workflow can be configured through a plugin interface, without writing a single line of code. This guide covers exactly how to do it, using B2B Wholesale Solution for WooCommerce by NEXU WP as the implementation environment.
We cover the role system from first principles, the registration form setup that feeds buyers into your approval queue, the approval and rejection workflow, and what a mature user management process looks like for a wholesale operation handling dozens or hundreds of trade accounts.
How WordPress user roles work — and why they matter for WooCommerce B2B
WordPress has a built-in role system that assigns capabilities to user accounts. By default, these roles are oriented around content management: Administrator, Editor, Author, Contributor, Subscriber. WooCommerce adds its own roles — Customer and Shop Manager — that extend this system for e-commerce. None of these default roles are designed for wholesale buyer differentiation.
What makes roles useful for B2B wholesale is that WooCommerce — and plugins built on top of WooCommerce — can query a user’s role and use it as a condition for behavior. Show this price if the user has this role. Allow purchase if the user has this role. Apply this tax treatment if the user has this role. Enable this payment method if the user has this role. The role is the lookup key that determines everything else.
Custom wholesale roles extend this system with buyer-specific roles that don’t exist in WordPress by default. A “Gold Wholesale” role or a “Distributor” role is a named identifier that your wholesale plugin recognizes and responds to. When that role is assigned to a buyer’s account, the entire B2B configuration — pricing, access, payment methods, restrictions — activates for that account. When the role is removed, the account reverts to standard behavior.
The power of the role system is in its reach. A single role assignment simultaneously activates the correct wholesale price on every product where that role has a configured price, unlocks wholesale-only product categories, enables the bank deposit payment method, applies the appropriate tax treatment, and grants access to wholesale-restricted registration content. You configure each of these behaviors once, keyed to the role, and the role assignment to a new account activates all of them at once.
Creating custom wholesale roles: step by step
In B2B Wholesale Solution for WooCommerce — the no-code wholesale role and registration management plugin, wholesale roles are created and managed from a dedicated Wholesale Roles panel in the WordPress admin. No PHP, no database edits, no developer required.
Before opening the plugin interface, have a clear picture of your wholesale tier structure. How many distinct buyer tiers do you operate? What are they called internally and externally? Do different tiers imply meaningfully different pricing, or is the distinction more about relationship management than commercial terms? Each tier will become a role. Creating roles ad hoc without a clear structure leads to a proliferation of roles that is difficult to manage and produces inconsistent buyer experiences.
Role names appear in your admin interface, in product pricing tabs, in the registration form’s role selection, and in internal reports. Naming conventions that are clear to your team — “Gold Wholesale”, “Silver Reseller”, “Platinum Distributor” — save time and reduce errors when configuring product-level pricing. Avoid ambiguous names like “Tier 1” and “Tier 2” without context, because six months after setup you will not remember which tier has which commercial terms.
In the plugin’s Wholesale Roles interface, add a new role by entering its name and any relevant description. The plugin registers this as a custom WordPress user role that the rest of the wholesale configuration system recognizes. Once created, the role appears in the product pricing tabs — where you configure per-role wholesale prices — and in the registration workflow — where it can be assigned to approved buyers.
A role without pricing configuration is a role that does nothing visible to the buyer. After creating your roles, navigate to each product in your catalog and set the per-role wholesale price in the product’s Wholesale Prices tab. The role you created now appears as a pricing field. This is the connection between the role system and the pricing layer — the role is the key, the product price field is the lock it opens.
Designing a wholesale registration form that works
The registration form is the entry point into your wholesale program. It is the first detailed interaction a potential trade buyer has with your business, and its design communicates something about how you operate. A form that asks for the right information, in a logical order, without unnecessary fields, tells the applicant that you know what you need and you respect their time. A form that is sprawling, unclear, or asks for information irrelevant to a trade account application tells a different story.
The registration form needs to collect what you need to make an approval decision and no more. Consider what that actually requires: the applicant’s business name, their business type (retailer, distributor, reseller), their country of operation, their VAT or business registration number if applicable, and a contact name and email. Some businesses add a field for annual purchasing volume or a description of their business — useful for tiering decisions but optional depending on your approval process.
The approval workflow: from application to active wholesale account
When a trade buyer submits a registration form, their application enters the plugin’s admin queue — a dedicated view that shows you all pending, approved, and rejected applications with the information they submitted. This is the interface from which you manage your entire wholesale onboarding process.
The review process for each application involves reading the submitted business information, verifying the VAT or registration number if applicable, and making a tiering decision: which wholesale role is appropriate for this buyer? For most businesses, this is a simple determination based on the buyer’s business type and the commercial relationship you want to establish. For larger or more complex applicants, it may involve a brief conversation before making the decision.
When you approve an application, you select the wholesale role to assign — choosing from the roles you created — and confirm the approval. The plugin creates the buyer’s WordPress account (or associates the approval with their existing account if they were already logged in during application), assigns the selected wholesale role, and sends an automated approval notification. From this moment, the buyer can log in and access their wholesale pricing, restricted products, and B2B payment options.
When you reject an application, the applicant receives a rejection notification and sees the rejection status page when they attempt to log in or check their application. A professional rejection communicates the outcome clearly without leaving the applicant uncertain about whether their application was received. In some cases — a VAT number that couldn’t be verified, an application that requires additional information — the rejection is a prompt for the applicant to reapply with corrected details rather than a permanent decision.
Using Elementor to build professional wholesale registration pages
The registration form is a functional element, but it is also a brand touchpoint. For stores built with Elementor, the ability to design the registration page using the drag-and-drop editor — placing the form within a branded page layout, adding context about your wholesale program, including testimonials or benefits of the trade account, and controlling the typography and spacing — produces a significantly more professional first impression than embedding a raw form in a default WordPress page.
The Elementor widget integration in the plugin brings the registration form into the page builder as a native component. Drop it onto any Elementor page, surround it with your brand content, and publish. The form submits to the same admin queue as the shortcode version — the frontend presentation changes, the backend functionality stays exactly the same. For Elementor stores, this is the right approach: it maintains the visual consistency of the site while keeping the wholesale logic in the plugin rather than in custom template code.
Managing active wholesale accounts: role changes and ongoing access control
The wholesale user management process does not end at approval. Active wholesale accounts require ongoing management: buyers change their purchasing tier as their volume grows, accounts become inactive and need to be reviewed, and occasionally a wholesale account needs to be suspended or have its role changed.
According to research by Salesforce on B2B commerce trends, retaining an existing wholesale account is typically five to seven times less costly than acquiring a new one, which means the ongoing management of your active trade buyer base is not administrative overhead — it’s a direct driver of wholesale revenue stability. Keeping role assignments current, upgrading high-performing accounts to better tiers, and proactively addressing inactive accounts are all part of a mature wholesale customer management process.
When a buyer’s order volume or relationship justifies moving them to a better tier, change their role in the WordPress user admin — navigate to the user’s profile and update the assigned role to the new tier. From the moment of saving, their pricing on every product updates to reflect the new role’s configured prices. No separate notifications need to be sent, though informing the buyer directly that they’ve been upgraded is good relationship management.
If a wholesale account becomes inactive, disputed, or needs to have its access revoked, change the user’s role back to standard Customer (or a custom non-wholesale role if you prefer). This immediately removes all wholesale pricing, access, and payment method visibility for that account. The account remains in your WordPress user database — with its order history intact — but no longer has wholesale access. Reactivation is as simple as reassigning the wholesale role.
A quarterly or annual review of your wholesale accounts — checking which are active, which have had no orders in six months, and which have grown enough to warrant a tier upgrade — is good practice. WooCommerce’s order reporting by customer makes this straightforward: filter by last order date and wholesale role to identify dormant accounts. Addressing them proactively — re-engagement outreach for dormant accounts, upgrade conversations for high performers — is a direct driver of wholesale revenue growth.
Common mistakes in wholesale user management
Manually assigning wholesale roles to buyers who contact you by email — without a formal registration form and approval process — skips the documentation step that your VAT compliance and commercial records depend on. It also creates inconsistency: some buyers have verified business details on file, others have none. Use the registration form for every new wholesale account, even if you already know the buyer personally.
Every role you create requires maintenance: pricing must be configured on every product for every role, and the list of roles grows in every dropdown across your admin. Five or six roles with meaningful commercial distinctions is manageable. Fifteen roles with minor pricing differences creates an admin burden that compounds over time and increases the risk of pricing inconsistencies.
When you create a new wholesale role and assign it to buyers without first configuring product-level prices for that role, those buyers see no wholesale price — they see the retail price. This is a common source of buyer complaints. Before approving the first buyer into a new role, verify that pricing is configured for that role on every relevant product in your catalog.
Applications that are reviewed but neither approved nor rejected in a reasonable time frame leave buyers in limbo. Set a service standard for your approval response time — 24 or 48 business hours is typical — and apply it consistently. A buyer who applies and hears nothing for two weeks will assume the application was lost and either reapply (creating a duplicate) or simply go to a competitor who responds faster.
Build your entire wholesale role and registration infrastructure without writing a line of code
Custom wholesale buyer roles, a professional registration form, a managed approval queue, and Elementor widget integration — all configured through the plugin interface, no developer required, all working together from day one.
Been using this for our tiered wholesale setup, and honestly, it just works. Mapped out our three buyer levels (bronze, silver, gold) in the plugin settings, assigned pricing rules to each, and boom no code, no dev tickets, no headaches. The guide in the settings header walked me through it step by step. only reason it's not five stars? Took me a hot minute to realize I needed to manually sync the roles after initial setup. Not a dealbreaker, but a tiny stumble in an otherwise smooth process
Finally got the wholesale roles working without having to touch a single line of code what a win. The registration form lets applicants pick their exact buyer type right upfront, so I don't have to go in and manually assign roles later. Pricing tiers, restricted products, even payment methods everything just works once they're approved. Honestly, this saved me from having to hire a dev for something that really should've been simple to set up. Such a relief.
Hey y'all, this saved me so much dev time!