Catalog Visibility Options for WooCommerce
Original price was: $59.00.$4.99Current price is: $4.99.
Advanced visibility control for products and prices in WooCommerce, allowing catalog segmentation and cart access by configurable roles and rules, maintaining a single store and stable flows.
This WooCommerce extension allows you to control which products are displayed, to whom they are displayed, and how the shopping cart behaves, making it ideal for B2B stores, restricted catalogs, or hidden prices, with the main technical benefit of segmenting visibility without touching code, preserving existing business flows and data.
Introduction to Catalog Visibility Options for WooCommerce
This WordPress plugin focuses on managing product and price visibility within the WooCommerce ecosystem, allowing you to adapt your catalog to different types of users and business contexts without restructuring the entire store or breaking existing internal navigation, filtering, or search flows.
The tool operates on the listing, product detail, and cart access layers, integrating with WooCommerce's native rules (roles, user states, theme templates) to reduce operational friction. The technical goal is to have a flexible catalog without duplicating products or creating separate stores for each segment.
Micro-scenario: A B2B store technician reviews with the sales team which products should only be seen by registered customers, configures rules from the panel, validates in a private browser session, and documents the flow so that support can replicate or adjust the visibility without touching the theme code.
Product overview
This extension primarily operates on the functional area of catalog and cart access, affecting how products, prices, and purchase buttons are displayed in WooCommerce, with a direct impact on user experience, frontend operational stability, and data consistency in navigation flows.
Previously, a small store would hide custom products with snippets scattered throughout functions.php, while a medium-sized store would maintain duplicate stores for wholesalers and retailers, and a large business would manage manual rules by role. With this module enabled, everyone centralizes restrictions in one dashboard. As a result, maintenance becomes more predictable, visibility errors decrease, and changes to business policies translate into configurable settings rather than code changes.
- Step 1: Initial situation without the add-on: visibility rules spread across code, theme widgets or various plugins, difficult to audit and maintain.
- Step 2: Key action using a specific function: Define which products are visible to guests, registered users, or specific roles, and adjust whether the add to cart button is displayed or only information.
- Step 3: observable result in operation: less friction when applying changes, consistent UX flows for each type of user, lower risk of displaying unauthorized prices or products.
Requirements and dependencies (without versions)
This module requires a working WordPress installation with WooCommerce active and a basic store flow already set up, including products, shop pages and a compatible template. It is recommended to review previous visibility customizations to avoid logical conflicts and unexpected behavior.
- Main dependency: You need WooCommerce up and running, with products defined and the shop, cart, and account pages set up so that the visibility rules have an effect on the actual purchase flow.
- General compatibility: It integrates with standard checkout, WordPress user roles, tax systems, and shipping already configured, respecting the native logic of prices and methods, while conditioning who sees what in the catalog.
- Typical limitations: It is advisable to test in a test environment if using page builders, highly customized themes, or extensions that alter the product loop, to check that filters are not duplicated or critical content is not hidden by mistake.
Key benefits for your project
- Precise catalog segmentation without duplicate stores: allows different types of users to see different products, prices, or buttons on the same database. This reduces maintenance, eliminates parallel catalogs, and improves change traceability within a single configuration layer.
- Centralized operational control for technical teams: the development team configures global rules, and then support or marketing can adjust visibility by product or category from the dashboard. This improves governance, documents decisions, and avoids reliance on one-off code edits that are difficult to audit.
- Improved UX in B2B scenarios and private catalogs: the tool eliminates confusing steps for guests, showing only what's strictly necessary. Meanwhile, approved users gain full access to the catalog and cart, with a consistent experience that respects WooCommerce's native logic.
- Reduced human error in price or policy changes: By using structured rules and options, the typical errors of manually hiding products or modifying templates are reduced. The impact is greater operational stability when commercial conditions, promotions, or role-based access changes.
- Scalability for growing projects: As the store expands its channels and customer profiles, visibility rules become a critical component. This plugin makes it easy to add new segments without redesigning the entire architecture, maintaining consistent data flows and operations.
- Ease of controlled testing and change validation: teams can apply rules to specific groups and verify how the store, cart, and account behave before a full rollout, reducing risks when introducing new catalog access policies.
Highlighted Features of Catalog Visibility Options for WooCommerce
- Visibility control by user role: This allows you to define which products or prices are seen by guests, registered customers, or custom roles. This is key in B2B workflows, where differentiated catalogs are required with a single WooCommerce installation.
- Options to hide prices or the "add to cart" button: the product can be displayed as an information sheet, without direct access to purchase. This is useful for creating reference catalogs, corporate catalogs, or processes where orders are managed through manual quotes outside of the standard checkout.
- Rules applicable at a global, category, or product level: general policies can be established, followed by specific exceptions. This granularity improves governance, preventing conflicting rules and allowing the technical team to model complex workflows without rewriting templates.
- WooCommerce store template compatibility: The plugin leverages common hooks and filters, reducing the need to modify the theme. This ensures visual consistency in the catalog while managing who sees what is handled through the settings.
- Ability to redirect users based on their status: instead of displaying generic messages, guests can be guided to the registration or login form when they try to access restricted products, improving the experience and facilitating conversion to authorized users.
- Integration with the standard cart and checkout flow: the rules not only affect listings, but also the ability to add products to the cart, preventing someone from completing an order for items they shouldn't be able to buy from their profile.
Who is this product ideal for?
This add-on is especially useful for projects that need to separate the catalog between different user groups, such as wholesale stores, corporate portals, or hybrid B2B/B2C websites, where it is key to control access to products and prices without complicating the technical architecture.
- Administrators who need order and traceability: profiles responsible for maintaining clear standards on what is displayed, requiring a single point of configuration to document rules and be able to audit visibility changes over time.
- Teams with multiple projects and operational consistency: agencies or internal departments that manage several stores and want to apply similar catalog policies, reducing the dispersion of customized snippets and maintaining consistent flows.
- Implementers, designers, and marketing managers: professionals who need to adjust the catalog without breaking layouts, who seek to control access to special prices or products, and who want to coordinate campaigns with specific customer segments.
Practical use cases
- Context: B2B store for industrial supplies. Problem: Guests see prices that should be reserved for negotiated customers. Extension use: Prices are hidden from unregistered users, and an access request form is displayed. Observable result: Informative public catalog and restricted purchasing area with agreed-upon prices.
- Context: A business serving both wholesalers and retailers from the same location. Problem: Specific prices and product codes should not be displayed to end users. Solution: Rules are configured by user role to show certain categories only to wholesalers. Observable result: A single backend, but two distinct catalog experiences.
- Context: A brand launches private collections for select distributors. Problem: They don't want to create an additional store for each campaign. Module use: Access to products is restricted through roles and private links. Observable result: Distributors have access to exclusive catalogs, and the general public doesn't even see those items.
- Context: A website using WooCommerce solely as a catalog, without direct online sales. Problem: The shopping cart confuses users who should actually order by phone or through a form. Plugin implementation: The "add to cart" function is disabled, and the price is hidden, displaying only technical data. Observable result: A pure catalog experience, with no purchase friction.
Frequently Asked Questions about Catalog Visibility Options for WooCommerce
Is it necessary to have a fully configured store to take advantage of this type of visibility control?
For visibility rules to have practical meaning, it's advisable to have WooCommerce configured with products, shop pages, and a defined basic flow, even if not all checkout steps are used, so that the catalog has a structure on which to apply restrictions.
In environments where WooCommerce is used solely as a catalog, it's still important to define categories, attributes, and user roles before applying rules. This allows visibility logic to be based on the same taxonomy and organization that the team already uses to manage inventory, pricing, and business segmentation.
How does visibility control affect the user experience at checkout?
Visibility rules primarily impact what is seen before reaching the checkout, filtering products or prices according to the user type, thus preventing the customer from trying to buy items for which they do not have permission or that are not intended for their specific segment.
In practice, if a user doesn't have access to a certain product, they won't be able to add it to their cart, reducing errors such as rejected orders or manual reviews. It's important to validate with thorough testing that the expected user roles can indeed complete the purchase flow, from listing to confirmation, without unexpected blocks due to overly restrictive rules.
Can automatic visibility rules be defined based on user roles or states?
This type of extension typically allows you to create automatic rules based on user roles, registration status, or product groupings, reducing the need to manage visibility element by element and facilitating more scalable operations that are less prone to individual errors.
For example, it's possible to configure guest users to see only specific categories, while users with the approved client role have access to the full catalog. This logic can be combined with account statements, manual onboarding reviews, and approval workflows, creating an automated system for opening and closing the catalog based on operational criteria.
What happens to order renewals or failed payments if some products become invisible?
If visibility rules change, a customer might have orders in their history with products that are no longer visible in the catalog, which doesn't necessarily prevent that order from existing, but it can affect direct reorders or access from the account.
In scenarios involving renewals or reorders, it's advisable to define a clear policy: keep previously purchased products visible to the customer, or block reorders when a product is marked as restricted or discontinued. It's recommended to test previous order flows and failed payments with different user roles to verify that the final behavior aligns with the defined business operations.
Does visibility control affect existing taxes, shipments, or coupons?
Visibility control affects what the user sees and what they can add to the cart, but it does not modify the already configured tax, shipping, or coupon rules; these will continue to apply to the products that actually go into the order.
However, hiding certain items from specific user segments indirectly reduces the possible product combinations in a shopping cart, which can simplify complex tax or shipping scenarios. It's good practice to review test orders by user role, verifying that tax conditions, shipping costs, and coupons continue to apply correctly with the subset of products visible to each segment.
Can this type of catalog control affect site performance or stability?
Any additional layer of logic on top of the catalog introduces new filters and checks, so it's important that the extension uses standard hooks and optimized queries to avoid degrading the overall performance of listings and product pages in WooCommerce.
In large stores with extensive catalogs and numerous custom user roles, it's advisable to monitor response times before and after activating intensive rules, avoiding unnecessary combinations of conditions. A prudent approach is to start with a small set of rules, measure behavior using profiling tools, and adjust until the balance between control and performance is found.
Is it compatible with multisite environments or projects with multiple associated stores?
In a multisite environment, the extension is usually managed site by site, allowing different visibility rules to be applied depending on the channel, country or line of business, while maintaining a similar technical management base and unified governance criteria.
For multi-store projects, it's important to define whether each site will have its own access policies, or if the goal is to replicate configurations across instances. Documenting the settings on a reference site and then reproducing them helps maintain consistency. In any case, it's advisable to thoroughly test interactions with themes and plugins specific to each installation before extending the same strategy to the entire ecosystem.
How can I practically verify that the visibility rules are working correctly?
A basic validation involves reviewing the catalog from different profiles: session as a guest, as a standard customer and with any special role, observing visible products, prices and access to the cart to detect inconsistencies between what is expected and what each user actually sees.
A helpful checklist includes: clearing caches, testing in private browsing mode, confirming that restricted categories don't appear in menus or widgets when they shouldn't, verifying restricted access messages, and simulating shopping carts with multiple products under each role. Recording screenshots and results helps document the status and repeat tests after future configuration changes or updates.
Written and reviewed by the PrimeGPL Team
At PrimeGPL, we ensure that every piece of published content is verified and reviewed by our team. We analyze features, compatibility, and performance to provide you with clear, up-to-date, and truly useful information for each product listed in our store.
Get your questions answered here
We answer your questions so you can buy in an informed and confident manner.
Does my purchase include updates?
Yes. Every product purchase includes lifetime updates, so you won't have to pay extra under any circumstances.
Is there a daily download limit?
No, not at all. After your purchase, you can download it as many times as you need, without any problem.
On how many websites can I use the products?
You can use your purchases on as many domains (websites) as you want, without any problems.
Does it include technical support?
Yes. We offer technical support Monday through Friday, during business hours UTC -3. This support includes assistance with issues related to download problems, installation problems, or errors with the purchased product.
Furthermore, support does not include configurations, customizations, tutorials, or services associated with the author.
Does my purchase have a warranty?
Yes, of course. If you have any problem that we can't solve, or if there's an external issue that doesn't have a general solution related to our service, you'll receive support and, if necessary, a full refund.
How do I access support?
After your purchase, from your user account, you can access the support section, where you can open a ticket and our team will assist you with whatever you need.
Download Previous Versions
If you have purchased this product, or have an active membership, you can download previous versions without any limits or restrictions.
| Product Name | Version | Size | Date | Download |
|---|---|---|---|---|
| Catalog Visibility Options for WooCommerce | 3.3.7 | 0.08 MB | 16/06/2025 | Join Now |
Related Products
Below we show you different products that share the same category.
