If you run more than one storefront on a single Odoo database, product visibility quickly becomes a manual chore. Odoo's native is_published flag plus the per-product website_id field let you tie a product to one website or leave it global, but the moment a regional catalog, a wholesale portal, and a retail brand share the same product master, you hit the wall: there is no bulk "assign these 400 products to these 3 websites" action, no single screen showing which SKU is live where, and no guardrails stopping a merchandiser from exposing a draft or region-restricted item on the wrong domain. Teams end up editing products one at a time, forgetting exclusions, and reconciling spreadsheets against the live sites.

This is a build-to-order module that ECOSIRE designs for your specific website topology — it is not an existing download. Technically, we extend product.template (and product.product where you need variant-level control) with an explicit many-to-many visibility relation to website instead of relying on the single website_id Odoo ships with. A compute method with @api.depends derives an effective per-website published state, so the /shop controller and website search only surface products a given website is actually allowed to show. Visibility is enforced end to end: we override the eCommerce product domain so restricted SKUs never appear in listings, related-product blocks, or direct URL access on a website that lacks visibility.

The operational core is a mass-assignment wizard built as a TransientModel, launched from a server action on the product.template list view. Select any number of products, choose target websites, and add, replace, or remove visibility in one transaction — with a QWeb-rendered change summary you can archive for audit. Access is governed by ir.model.access.csv entries plus record rules so a brand's catalog manager can only touch products and websites they own, and every bulk run is written to the chatter and an optional log model for traceability. Where you sync from a PIM or external channel, we expose the visibility fields cleanly over the XML-RPC/JSON-RPC API so create/write calls set website assignment without post-processing. The module targets Odoo 17.0, 18.0, and 19.0 on Community or Enterprise; note that multi-website itself is an Enterprise-tier website capability, so we confirm your edition during scoping and adapt the approach accordingly.

Delivery is build-to-order. After a short scoping call we confirm your website count, catalog size, variant-vs-template granularity, and any PIM/API sync, then send a fixed quote. Typical delivery is one working week from confirmed scope, including UAT on a staging copy of your database and a rollback plan before we touch production. Pricing starts from $999 (indicative, single-company base scope); additional websites, variant-level control, multi-company record rules, PIM/API integration, and data migration of existing visibility state increase the quoted scope.