Rule 1: a product in no catalog is visible to everybody
Putting a product in a catalog restricts it; leaving it out does not. The opposite reading — nothing visible until it is assigned — would turn activating the plugin into an empty shop. Here, nothing changes until you put something in a catalog.
Rule 2: any catalog holding a product is enough
A customer may see a product if they are in any catalog that holds it. Being in two catalogs never shows a customer less than being in one.
A product is "held" by a catalog when the catalog lists it by id, or lists one of its categories or a parent of one of them. A variation is held wherever its product is.
Who is in a catalog's audience:
- a visitor who is not signed in, if the catalog lists
guest, - a signed-in customer, if any of their roles is listed — WordPress users can have several, and every one is read,
- Full edition: a customer whose user id is listed.
Rule 3: a catalog with nobody in it is not open to everybody
A catalog that holds products but names no audience is a catalog you have not finished writing. Its products are exactly the ones you were keeping back, so they stay hidden from every customer rather than being shown to all. Removing the catalog, or unticking In use, is what makes them public again.
A catalog with no products and no categories restricts nothing and is ignored.
Who is never restricted
Anyone who can edit products — administrators and shop managers — sees and can buy everything. That is why you must check the shop from a private window or a customer account.
Rule 4: enforced in four places, not just hidden
Hiding a button stops nobody who has the product's address, a bookmark, or a search engine result. So a restricted product is refused at every step, for anyone outside its audience:
- The shop queries. With Hide restricted products on, the product leaves the shop page, category pages, search results and product archives. Only what your catalogs keep back is excluded — the plugin never walks your whole catalogue. A product the customer's own catalog names (or files under one of its categories) stays listed even when it is also in a category another catalog keeps back, because a customer may see a product held by any of their catalogs.
- Visibility. WooCommerce is told the product is not visible, and the product's own address answers 404 not found.
- Purchasable. WooCommerce is told the product cannot be bought. That one answer covers the classic cart, the Cart and Checkout blocks and the Store API at once.
- Add to cart, and the cart. Adding it is refused with your What a refused shopper reads message. A product already in a cart — from before you changed a catalog, or before the customer signed out — is removed, with a note naming it.
Restricted categories also disappear from category menus, widgets and category lists, so a menu never links to a page that would show nothing.
With Hide restricted products off, steps 1 and 2 are skipped: products stay listed and their pages open, but steps 3 and 4 still apply.
Why a 404 rather than "you can't see this"
A refusal page confirms the product exists. A competitor visiting product addresses and counting refusals would learn the shape of your trade catalogue. "Not found" tells them nothing.
Catalog prices — Full edition
A customer in a catalog that has a Percentage off or Prices of its own pays that catalog's price for its products:
- A price of its own for the product, if the catalog has one.
- Otherwise, Percentage off the product's regular price, rounded to your shop's decimals.
- If the customer is in several catalogs that price the product, the cheapest wins. Being in two audiences is never a reason to pay more.
The price is set on WooCommerce's own price (and sale price), so the shop page, the product page, the cart, the mini-cart, the block cart and the order line all show and charge the same number. The sale price is replaced too — otherwise a lower public sale price would undercut the catalog price — but a sale price is never invented for a product that is not on sale, which would put a struck-through "was" price on it.
WooCommerce caches a variable product's price range. The plugin adds the customer's catalogs to that cache's key, so two customers in different catalogs never share one cached range — and nobody is shown somebody else's prices.
When Say beside a catalog price… is on, a Your price badge follows the price. When Keep catalog prices out of the structured data… is on, the price is removed from the product's structured data for that customer.
Page caches
While any catalog is in force, every storefront page is sent with WordPress' no-cache headers and DONOTCACHEPAGE, which page-cache plugins read as "skip this page". Two customers see two different shops; a cache that cannot tell them apart would eventually serve a guest the page cached for a trade customer. The settings screen says this in as many words.
The free edition and the full edition's catalogs
The free edition has one catalog, catalog, and judges its audience by roles. If the full edition has written other catalogs into the same option, the free edition keeps them and treats their products the safe way round: they stay hidden from everybody (except shop managers), because the free edition does not judge who those catalogs are for. It never charges a catalog price, so a downgrade re-prices nobody — everybody pays your normal prices.
Upgrading reverses that: the full edition reads every catalog, its audience and its prices from the same option, with nothing to migrate.
