I wanted to ask the community: what are the key improvements in Odoo 19 compared to Odoo 18? We’re considering an upgrade and want to understand whether the new version brings significant performance, UI, or module enhancements.

Has anyone tested or implemented Odoo 19 already? How does it perform in real business use cases? Also, I saw that companies like Webkul are already supporting Odoo 19—does anyone have feedback on working with their apps or migration services for this version?

Would love to hear your experiences, pros/cons, and upgrade recommendations.

Thanks!

I’m currently planning an Odoo Implementation for a retail business that needs not only robust ERP functionalities but also a highly customized frontend for both web and backend users. While I’ve explored the core Odoo modules, I’m particularly interested in how developers are handling Odoo Theme Development and Odoo Template Development in Odoo 16 and 17.

Some specific points I’d love community input on:

• How do you structure theme inheritance for scalability across multiple modules?

• Are there best practices for minimizing latency introduced by overly customized templates?

• When integrating a new theme during Odoo Implementation, do you version it separately for staging vs production environments?

• Has anyone integrated third-party UI frameworks (like Tailwind or Bootstrap 5) cleanly into Odoo without breaking ORM-driven views?

• Also, if you’ve worked with custom templates for the Odoo eCommerce or POS frontend, how do you ensure compatibility during future upgrades?

Looking forward to any real-world experience, code snippets, or tips. Trying to avoid pitfalls early on and make sure theming aligns smoothly with the broader Odoo implementation strategy.

Thanks in advance!

I’m currently working on customizing the backend interface in Odoo 18 and wanted to share some insights for those diving into Odoo Theme Development and Odoo Template Development.
To create a custom backend theme, start by creating a new module with assets_backend declarations. You’ll mainly work with SCSS, XML (for QWeb templates), and JavaScript to style views or override default layouts. For backend modifications:

• Extend existing templates from web.base_layout

• Use the t-inherit directive for template overrides

• Leverage custom SCSS via Webpack or Odoo’s asset bundling system

• Structure your theme cleanly to support modular updates

Anyone here working on backend themes for version 18? Let’s share best practices or issues you’ve encountered with template inheritance and asset optimization.

If you're building or modifying Odoo payment apps, it’s better to extend existing payment models rather than creating from scratch—this allows smoother backend configuration and compatibility with payment workflows.
For developers working with custom flows, here are a few helpful tips:

Use the payment register wizard for transaction processing.
Ensure the external API communication is handled with proper error catching and logging.
Make sure your Odoo payment methods follow the expected state transitions (draft → pending → done/failed).

Anyone else working with Odoo payment gateway integrations in 18?
Would love to hear how you've structured your flows or dealt with challenges like tokenization or partial payments.