Most B2B, wholesale, and trade sellers running Odoo eCommerce eventually hit the same wall: prices are either public to everyone or the entire storefront sits behind a portal login. Odoo core gives you no middle ground. You cannot easily say "show retail prices to guests, show negotiated prices to logged-in trade accounts, and show a Request-a-Quote button to everyone else." The native website_sale templates render list_price and pricelist-adjusted prices unconditionally in the shop grid, the product detail page, and search results — so hiding a price usually means someone hand-overrides QWeb and breaks the add-to-cart flow, structured data, and the pricelist engine in the process.

We build a purpose-made module that adds a first-class price-visibility layer on top of website_sale without forking it. The core is a small set of ORM models and configuration fields: a visibility policy stored against product.template and product.public.category, evaluated per request against the current website, the logged-in res.partner (and their commercial parent), assigned res.groups, geolocation/country, and the resolved pricelist. A compute method decorated with @api.depends on the partner, pricelist, and policy resolves — for each visitor — whether the price is shown, masked, replaced with a call-to-action, or gated behind login. We override the relevant templates through inheritance (xpath on website_sale.products_item, website_sale.product, and the cart/mini-cart) so the price node is conditionally rendered while add-to-cart, wishlist, and comparison behavior stay intact. Where a product is priced-hidden, we optionally swap the buy button for a configurable "Request a Quotation" action that feeds crm.lead or sale.order in draft.

Because visibility touches money and access, we wire it correctly at the data layer: ir.model.access.csv grants for the new configuration models, ir.rule record rules so a website manager only edits policies for their own website in multi-company/multi-website installs, and server-side enforcement so a hidden price is never leaked through the JSON-RPC//shop controllers or the product_template public read — hiding on the template alone is not enough, since a crafted request can otherwise pull the value. Admin-facing configuration lives in clean backend views (form/list) plus a settings panel, and every policy change is captured for auditability. The module ships with an automated action option to flip visibility on schedule (for example, reveal prices only during a trade-show window) and is packaged with a correct __manifest__.py declaring dependencies (website_sale, sale), data files, and version, tested against Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise (Enterprise-only surfaces like advanced pricelist UI are handled gracefully when absent).

Delivery is build-to-order: it starts with a short scoping call to map your exact rules — which visitor segments, which products or categories, what the fallback should be, and how quotation requests should flow — after which we return a fixed quotation and a delivery plan. Typical delivery is one working week from confirmed scope. We build on a staging copy of your database, run UAT with you, and hand over installable source, documentation, and a git repository. Pricing starts from $999 (indicative, single-company base scope); additional websites, multi-company record-rule complexity, deep customer-group/geolocation segmentation, and quotation-workflow integration increase the quoted scope.