Premium Backend Theme (PWA, RTL, Multi-Theme)

No. The Premium Backend Theme is build-to-order. ECOSIRE builds and brands the module specifically for your Odoo version and your visual identity, then installs it for you. It is not an instant apps.odoo.com download — you are commissioning a scoped, delivered engagement, and you receive the full source code you own at the end.

Typical delivery is 2–4 weeks from kickoff, depending on how many of the three styles and how much brand customization you want, and which Odoo versions (17, 18, 19) you need supported. Kickoff begins once we've collected your brand assets (logo, colours, fonts) and confirmed the target Odoo version and hosting. We validate on staging before enabling it on production.

Every build includes a post-launch support window for bug fixes and reasonable adjustments. Because the theme is an overlay (no edited core files), it upgrades cleanly with your database; when you move to a newer supported Odoo version we run a compatibility check and patch anything needed. Ongoing maintenance and feature additions beyond the initial window are available as a support retainer — just ask for a quote.

It's engineered to avoid that. We register assets into the standard web.assets_backend bundle, extend OWL components through the public patch API and inherit QWeb templates rather than editing core. Theme preferences live on res.users with proper ir.model.access.csv entries. This overlay approach means it coexists with Sales, Inventory, Accounting and your custom modules, and survives point-release upgrades far better than a forked or monkey-patched theme.

It works with both Community and Enterprise on Odoo 17, 18 and 19. The theme targets the web client (the OWL backend), which is common to both editions. If you're on Enterprise, we ensure the theme layers cleanly over Enterprise-only UI elements; on Community it provides the modern chrome Community lacks out of the box. Tell us your edition and version at kickoff.

Yes on both counts. Branding is driven by centralized SCSS design tokens — logo, primary/accent colours, fonts, favicon and login screen — so we match your identity precisely and future rebrands are a token change. Full RTL support ships with mirrored layouts and RTL-aware styling, tested against Arabic, Urdu, Hebrew and Farsi, and theme labels are translatable via Odoo's .po files.

You receive the complete installable module (manifest, OWL/QWeb templates, SCSS, static assets, security CSV, translations), the applied brand configuration, PWA assets, installation on your environment, admin and end-user documentation, a recorded training session, and the support window. The source is delivered as a Git repo or ZIP that you own outright — no per-seat licensing lock-in.