Product Hide Cost
Product Hide Cost helps organizations protect sensitive product valuation information by restricting access to product cost data in Odoo. The module introduces a dedicated security group that allows administrators to grant product cost visibility only to authorized users, ensuring that confidential cost information remains hidden from standard users.
Main Features
Dedicated Cost Visibility Permission
Adds a dedicated security group called See Product Cost. Only users assigned to this group can view product cost information within the system.
Hide Product Cost Information
Restricts visibility of the Cost field on product records, helping organizations protect sensitive pricing, valuation, and margin-related information from unauthorized access.
Supports Product Templates and Variants
Applies cost visibility restrictions across product templates and product variants, ensuring consistent access control throughout the product catalog.
Easy Administration
Administrators can manage access through standard Odoo security settings without requiring additional configuration or customization.
Multi-Language Support
Available in English (US) and Spanish (GT), allowing users to operate the module in their preferred language.
Business Benefits
- Protect sensitive product cost information.
- Limit access to authorized personnel only.
- Improve internal data security and confidentiality.
- Reduce the risk of exposing product margins and valuation data.
- Integrate seamlessly with Odoo's standard security framework.
Configuration
- Navigate to Settings - Users and Companies - Users.
- Open the desired user record.
- Assign the See Product Cost security group.
- Save the changes.
Compatibility
Odoo Community Edition and Odoo Enterprise Edition.
Supported Platforms
Compatible only with Odoo.sh and On-Premise installations.
Supported Versions
Compatible with supported Odoo versions for which this module is released.
Screenshots
See how the module controls product cost visibility for different users and product screens.
1. Configure Cost Visibility Permission
A dedicated user permission named Product Cost Visibility lets administrators decide who can see product costs. Users without the permission will have cost-related values hidden from product screens.
2. Product Form Without Cost Exposure
The product form keeps commercial information such as sales price, taxes, category, reference and barcode visible, while restricting sensitive cost information according to the assigned permission.
3. Product Selection in Sales
Sales users can continue selecting products normally from quotations and sales orders without exposing internal product cost information.
4. Product List View
The product list shows commercial and stock-related information such as Sales Price, On Hand and Forecasted quantities, while cost visibility remains controlled by the security group.
5. Purchase Product Search
Purchase users can search and select products during RFQ creation. Cost visibility should be reviewed according to the groups assigned to the user and the views loaded by the module.
6. Inventory Reporting Review
Inventory reporting may contain valuation-related columns. Access to these reports should be validated with the correct user profile after installation.
7. Forecasted Report Review
Some Odoo standard reports may display value fields depending on installed applications, access rights and reporting views. Validate this screen with a restricted user after installation.
Support
For support, bug reports, or customization requests, please contact the publisher team and provide:
- Odoo version and edition
- Module version
- Installed apps that expose product cost or valuation reports
- Screenshots or a short video showing the visibility issue
Sales: sales@ariesbt.com
Support: odoo@ariesbt.com
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) |
| Lines of code | 136 |
| Technical Name |
ariesbt_hide_cost_products |
| License | LGPL-3 |
| Website | https://www.ariesbt.com |
Please log in to comment on this module