The short answer
Retailer catalogue access determines which products a connected buyer can browse. In CeramicPortal, a product can be hidden from a selected retailer while remaining in the master catalogue. Review this separately from the retailer’s rate list and from stock availability.
Keep these in mind
- Define the intended assortment before changing access.
- Check a known visible SKU and a known hidden SKU.
- Visibility does not establish an available-to-promise quantity.
Start with an assortment decision
A supplier may stock more ranges than every connected showroom sells. A showroom’s display selection, a commercial agreement or a discontinued range can change what is useful for that buyer to browse. Write down the assortment you intend to offer before changing settings.
The goal is a deliberate product view. If an administrator cannot explain why a product is hidden, the next administrator may reverse that decision while trying to solve a different issue. Keep the reason and responsible person in your normal business handover.
Prepare product records that are easy to distinguish
Use consistent category, size and product or variant information. Finish and suitable-for attributes help distinguish products that would otherwise appear alike. If the same trade name is used for multiple sizes, include enough detail for the retailer to identify the exact item.
Avoid changing the master product name solely to explain one customer’s access. The master record should describe the tile; the retailer’s access setting should describe whether they may browse it.
Test both a visible and a hidden product
- Select one familiar SKU that the retailer should see.
- Select a second SKU that should be hidden for that retailer.
- Check the retailer’s assignment in Admin, including the rate list independently.
- Open the connected retailer view and search for both SKUs.
- Confirm the allowed tile opens and the hidden tile is absent. Repeat with another retailer who should have different access.
Use an access matrix for a small rollout
| Illustrative range | Retailer A | Retailer B |
|---|---|---|
| Everyday floor tiles | Visible | Visible |
| Premium wall collection | Visible | Hidden |
| Retired display range | Hidden | Hidden |
This table is a planning example, not a screenshot or a claim that the app includes this exact matrix. A short list like this helps your team agree the result before testing settings. Add an owner and review date in your own operating checklist.
Use actual product identifiers during the check. A generic range name is not enough when a range contains exceptions or several similar variants.
Keep access, rate and availability separate
Visibility answers Can the retailer find this product? A rate list answers Which agreed rate is shown? Stock review answers a different operational question. A visible product is not, by itself, a promise that the full requested quantity is available.
After adding a new range or changing a relationship, repeat the retailer-view check. If a retailer cannot find a product, first check the intended supplier context and assignment rather than recreating the product.
Make the demo answer your real access question
Bring two customer examples with different assortments. Ask to inspect the same product under both relationships, then check a hidden product by search. This shows whether the experience matches your policy without relying on a generic catalogue tour.
Common questions
Does hiding a product delete it from the master catalogue?
No. The retailer visibility control changes the buyer’s catalogue view; the Admin product record remains.
Does a hidden product appear as a disabled item?
The intended retailer experience is absence from that catalogue. Test the retailer view after changing access.
Explore the relevant workflow
Put the explanation in context.
Product education from CeramicPortal. Examples are illustrative unless identified as recorded product evidence. The available actions depend on your account and assigned access.