LAUNCH30 at checkout, until 30 November. See the pluginsSee plugins
Restrict WooCommerce product visibility by specific customers or user roles. Simple per-customer restrictions without complex membership plugins.
Features
Products can be made exclusive to certain users without complex membership plugins.
Make products visible only to specific customers
Restrict products by WordPress user role
Only selected users/roles can see the product
Hide products from specific users/roles (everyone else can see)
Restricted products are hidden from shop, search, and direct URL access
Prevents adding restricted products to cart
No bloat, just focused functionality
Show wholesale products only to approved business customers (whitelist)
Create exclusive items for your best customers (whitelist)
Hide products from known competitor accounts (blacklist)
Different product catalogs for different customer tiers
Let select customers preview new products (whitelist)
Hide products from certain user groups (blacklist)
Guides
Step-by-step guides from the team that builds it. All guides
WooCommerce
How to run trade-only ranges, client-specific products and members-only collections in one WooCommerce store, with visibility rules by role, category and individual customer.
An interrupted save can no longer make a product visible to a customer you blocked, and a failed save is reported instead of shown as saved. ## What's fixed in 1.0.9 - **A failed save can no longer make a product visible to someone you blocked.** The customer list was deleted before the new one was written, with no check on either step, so a database error part-way through could leave a blocked customer able to see the product while the screen still said "saved". The save now applies its changes in the order that tightens access first, so an interrupted save never leaves the product more visible than it was. Where the database supports transactions the save is reverted on failure; where it does not, each write that landed is undone individually and confirmed. If even that cannot be completed, the notice tells you what is actually stored instead of claiming your previous rules survived. - **The AJAX save checks permission for the specific product.** It previously only required the general "edit products" capability; it now also requires that you can edit the product whose rules are being changed. - **Activation only records the database version once the table really exists.** Previously the version was stored regardless, so a table that failed to create was never retried. The table is now confirmed first, and a missing table (including one dropped later) is recreated on a later admin page load, checked at most once every five minutes. - **The table definition can now be upgraded in place.** It is written in the form WordPress's dbDelta() can compare against the existing table, so future schema changes will apply on update rather than being skipped. No change is made to the table itself in this release. - **Category/tag rules report save failures.** On the Visibility Rules screen, adding or deleting a rule whose save did not land was still shown as a success. Both now show an error and leave your existing rules unchanged. - **A failed read can no longer save as a success.** If the list of a product's existing customer rules could not be read, the save treated it as "no rules" and committed, leaving the stored rules untouched while reporting success. The read is now checked and the save is refused instead. No settings or data changes otherwise.
