Cost price is one of the most sensitive numbers in your Odoo database, yet by default it is visible to anyone who can open a product form. Salespeople, POS cashiers, warehouse operators, and external consultants all land on the product.template / product.product standard_price field with nothing standing between them and your margins. Odoo's native controls only get you part of the way there: you can gate the field behind the groups="..." attribute in a view or hide it with the Product Costs access group, but that leaves the value fully readable through list exports, invoice and inventory valuation reports, the Developer Tools inspector, and any read() call over XML-RPC/JSON-RPC. The moment a user has export rights or a bit of technical curiosity, "hidden in the view" stops being hidden.

We build a Hide Cost Price module that treats cost visibility as a first-class access-control concern rather than a UI convenience. At the presentation layer we apply groups and computed-visibility on standard_price (and related cost fields such as product.supplierinfo price, purchase price on stock moves/layers, and margin columns) across every form, tree, kanban, and search view where it surfaces. But the enforcement does not stop at the view: we add an ORM guard so that users outside the authorized security group receive a masked or zeroed cost when they read the field — including through list-view exports, read_group aggregations, and direct RPC calls — while authorized users see the real figure. This is driven by a dedicated security group defined in the manifest, wired through ir.model.access.csv and record rules, so "who can see cost" becomes an assignable role, not a scattered set of view tweaks.

Technically, the module is a clean, versioned addon: a __manifest__.py declaring the new group_view_cost_price security group and its data files, a small models/ layer that overrides the relevant read/compute paths using @api.depends and environment-context checks (self.env.user.has_group(...)), XML view inheritance to bind the groups attribute onto every cost-bearing field, and adjustments to QWeb report templates so cost columns render blank or "—" for unauthorized users on valuation, margin, and sale/purchase reports. We keep the logic idempotent and upgrade-safe so it survives future Odoo updates, and we test the escape hatches specifically — export, RPC, studio-added views, and superuser bypass expectations are all covered. It works on Community and Enterprise, and we target Odoo 17.0, 18.0, and 19.0 with a build matched to your exact edition and version.

Delivery is build-to-order. After a short scoping call we confirm precisely which cost fields, reports, and RPC surfaces must be locked, which security group(s) map to your org's roles, and how masking should behave (blank, zero, or "restricted"). We build against a copy of your configuration, validate on a staging database with a rollback plan, and hand over installable source plus a git repository. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company cost isolation, custom report templates, additional cost-bearing models, and stricter RPC/export hardening increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise on the invoice.