Give every partner, team, and user their own catalog — enforced everywhere
Restrict which product categories each partner tier, sales team, or individual user can see — enforced at the server level so the same rule protects Sales, Purchase, Inventory, exports, and the API.
Odoo's product catalog is all-or-nothing by default: once a user can see products, they can see nearly all of them, on every screen the product appears on. Businesses juggling wholesale tiers, dedicated sales teams, or compliance-restricted catalogs are left hand-crafting record rules, building fragile custom portals, or simply trusting everyone to only look at what they should.
Product Category Visibility gives admins one place to grant category access by partner tier, sales team, or individual user — enforced by a single server-level record rule that protects every screen at once, with a permission-matrix grid to audit who can see what in seconds.
This app speaks your language.
Tell us the language your team works in and we translate this module for you, free of charge — so everyone works in the language they know best.
Request my free translation →No hidden fees. No subscription.
Everything you need to control the catalog
Every capability below is implemented in the module.
Unified Targets
One place to manage visibility for partner tiers, sales teams, and individual users, instead of stitching together three separate apps.
Category-Level Control
Show or hide entire product categories per target, with child categories included automatically.
Partner-Tier Inheritance
Higher partner tiers automatically inherit every category granted to a lower tier, with no manual re-entry needed.
Sales-Team Mapping
Assign categories to a sales team so every member quotes only from their own catalog.
Server-Level Enforcement
A single ORM record rule enforces visibility across Sales, Purchase, Inventory, exports, API calls, and reports at once.
Exceptions & Denials
Grant a specific product outside a category, or deny one within an allowed category — denials always win.
Variant Inheritance
Product variants automatically follow their parent product's category restrictions, so admins never configure variants separately.
Permission-Matrix Grid
An at-a-glance pivot showing exactly which categories every partner tier, team, or user can see.
Bulk Tools & Templates
Bulk-assign categories to many targets at once, or apply a reusable visibility template, with a full chatter audit trail.
How it works
Enable Restriction
Add the users who need a limited catalog to the Restricted Catalog User group; everyone else keeps full access automatically.
Assign Categories
Grant categories to a partner tier, sales team, or individual user, or apply a reusable template.
Fine-Tune
Add exceptions to grant a specific product, or denials to hide one, then set an optional scheduling window.
Verify
Open the permission matrix, or a user's Catalog Visibility page, to confirm exactly what they can see.
See it in action
Real screens from a running install — assignments, the permission matrix, templates, and enforcement proof.
The assignment list shows every partner-tier, team, and user grant in one place, with category counts and active status at a glance.
Assignments grouped by target type in kanban, color-coded for a quick visual overview of who has been granted access.
An assignment form for a sales team: categories, an applied template, and inherited vs. directly assigned categories shown side by side.
The permission-matrix pivot — the module's headline view — answers "who can see what" at a glance across every target and category.
The same matrix data as a flat list, for exporting or scanning row by row.
Reusable visibility templates bundle a set of categories so onboarding a new team or tier takes one click.
A template form showing its category bundle, ready to be applied to any partner tier, team, or user.
A restricted user's Catalog Visibility page proves server-level enforcement: effective categories, exceptions, and denials computed live.
The bulk-assign wizard grants or replaces categories across many targets in a single action.
The apply-template wizard stamps a reusable template's categories onto any selection of targets.
Frequently asked
Does this replace Odoo's native access rights?
No. It works alongside your existing groups and adds category-level record rules scoped to a dedicated Restricted Catalog User group, so nothing else in your access setup changes.
What happens if a user has no assigned categories?
They see a friendly empty catalog instead of an error — a defined, documented zero-access state rather than an undefined edge case.
Which wins if a category is allowed but a specific product is denied?
The denial always wins, even when the product's category is otherwise granted to that target.
Is enforcement limited to the backend UI?
No. Because it is implemented as a server-level ORM record rule, the same restriction applies to Sales, Purchase, Inventory, data exports, API calls, and reports.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Product Category Visibility — server-level catalog visibility by partner tier, sales team, or user, with a permission matrix, templates, and bulk tools, for Odoo 19.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Purchase (purchase) • Sales (sale_management) • Invoicing (account) |
| Lines of code | 879 |
| Technical Name |
cerevantix_product_category_visibility |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module