Theme & Storefront Customizer Pack for Odoo Website

The Theme & Storefront Customizer Pack is a build-to-order Odoo theme module that ECOSIRE designs, builds, installs, and supports for your specific catalog and brand. Technically it is a proper theme/website module with a __manifest__.py declaring the theme, its asset bundles, and dependencies on website, website_sale, and (where relevant) website_sale_wishlist. The storefront chrome is delivered as QWeb templates that inherit and extend Odoo's core views with <template ... inherit_id="website_sale.products">-style XPath overrides — we never fork core, so upgrades stay clean. Interactive pieces (mega-menu, quick-view modal, wishlist toggles, filter facets) are implemented as OWL components and website widgets registered into the web.assets_frontend bundle, talking back to the server through Odoo's JSON-RPC controllers (http.Controller routes) so add-to-wishlist and quick-view fetches happen without a full page reload.

Discovery is the core of the pack. We build layered/faceted product filters on top of product.template and product.attribute / product.attribute.value, with an option to add stored compute fields (via @api.depends) for derived facets like price bands, availability, or brand, and matching database indexes so filtering a large catalog stays fast. The mega-menu is data-driven from your website.menu / eCommerce category tree (product.public.category) rather than hand-built, so merchandisers maintain it in the normal Odoo backend. Homepage building blocks ship as reusable website snippets (drag-and-drop snippet templates with editable options) — hero, category showcase, featured/bestseller carousels, promo banners, trust bars — so your team keeps editing pages in the standard Odoo Website editor after handover. Every custom model and controller is secured properly with ir.model.access.csv rules and, where multi-website or B2B visibility matters, record rules. Performance work is explicit: scoped SCSS in a dedicated asset bundle, responsive srcset images, deferred non-critical JS, and a Core Web Vitals pass (LCP, CLS, INP) validated on staging.

Because this is build-to-order, there is no instant download. You start with a short scoping call; we confirm your Odoo version (17.0, 18.0, or 19.0), Community vs Enterprise, brand direction, catalog size, and the exact navigation and filter facets you need. We then build on a staging copy of your database, run UAT with you, and only deploy to production once you sign off — typical delivery is 2 to 4 weeks from confirmed scope. You receive the full installable source, documentation, a training session, and a post-go-live support window. Everything is your code, handed over in a git repository you own.