Daily updates from Odoo
Saturday, September 6, 2025
10 changes · master
Enhancements to existing features
Odoo Enterprise now lets backend users keep their preferred light, dark, or device-based appearance across sessions and devices. This improves comfort and consistency, especially for users who rely on system-wide dark mode settings.
Original PR description
*: test_discuss_full_enterprise This commit implements the support for the browser/device/system prefered color scheme in addition to arbitrary light/dark schemes. Also, it persists accross sessions…
*: test_discuss_full_enterprise This commit implements the support for the browser/device/system prefered color scheme in addition to arbitrary light/dark schemes. Also, it persists accross sessions (and devices) the color scheme choosen by the user in a `res.user.settings`. Note that, as for the existing "dark mode", it only applies to the backend. About the browser/device/system scheme support, please note that as the only current way to actually detect the color scheme (light/dark) to apply is via the `prefers-color-scheme` media query, hence run in the browser ; the server as no way to know it by itself [1]. To work around this limitation, the (existing) cookie is used as the link between the client and server. The drawback is that a reload has to be performed when the user has its browser/device/system set to "dark" and connects for the first time. [1]: Chrome implements the HTTP header `Sec-CH-Prefers-Color-Scheme` but no other browser does at this time and the corresponding spec is very much a "work in progress/draft" at the moment... References: - https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme - https://chromestatus.com/feature/5642300464037888 - https://wicg.github.io/user-preference-media-features-headers/#sec-ch-prefers-color-scheme task-4282066 task-4286033 task-4812669
When a helpdesk ticket is converted into a sales lead, the system now assigns the lead to the sales team leader if the ticket's responsible person is not part of that sales team. This reduces the chance of new sales opportunities being left unassigned and overlooked.
Original PR description
The wizard that converts tickets to leads already has a heuristic to assign the new leads to a user if the ticket's responsible user is also a salesperson in the target team, but if they are not, then the lead remains without responsible and could be missed if no automatic assignment rules exist. This commit extends that heuristic: the wizard now automatically assigns the newly created lead to the sales team's leader if it failed to find the ticket's responsible in the team's members. task-4684660
This update reorganizes accounting-related menu entries across several Odoo Enterprise apps and localizations. Users should find reports, configuration items, and accounting tools in more consistent places, reducing time spent searching through menus.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/225344 task-5060337
Indian localization reports now let each bank template decide whether payment CSV exports include a header row, instead of relying on fixed bank-specific rules. The HDFC export format was also aligned with bank requirements, while an unused template model was removed to simplify maintenance.
Original PR description
- Added a boolean field `include_header` to `enet.bank.template` to control whether CSV exports include a header row for batch payments. - Updated the batch payment CSV generation logic to use this new flag instead of hardcoded checks for specific bank templates. - Removed the `enet.template` model along with related fields and access rules to simplify the codebase. This change improves flexibility in CSV export formatting and reduces code complexity. Upgrade PR: https://github.com/odoo/upgrade/pull/8311
Users are now prompted to complete identity verification as soon as they add a bank account in Odoo, rather than waiting until their first payment. Odoo supports this with an email, notification, and scheduled activity so the process is less likely to be missed.
Original PR description
Users currently initiate the KYC flow automatically when making a first payment. This improves the KYC flow by prompting users to complete it as soon as they add a bank account in Odoo. We send them an email, create a notification and schedule an activity to ensure they complete the KYC process. Task ID: 4487895
Odoo now sends message reactions made by users through WhatsApp, so customers can see those reactions in their WhatsApp conversations. This keeps chat interactions more consistent between Odoo and WhatsApp and avoids confusion when reactions previously stayed only inside Odoo.
Original PR description
Add support for sending reaction type messages via the WhatsApp API by introducing the `reaction` message type in the WhatsAppApi. This resolves the issue where reactions made by Odoo users are not reflected in the customer's WhatsApp conversation. API Documentation: https://developers.facebook.com/docs/whatsapp/cloud-api/messages/reaction-messages Task-4828394 Forward-Port-Of: odoo/enterprise#93932 Forward-Port-Of: odoo/enterprise#88520
Indian reporting now uses the updated PAN entity identifier instead of the older PAN field. This helps keep tax reports and payroll demo data aligned with the latest partner identification model, improving consistency for GST reconciliation and related reporting.
Original PR description
Community PR - https://github.com/odoo/odoo/pull/214189 Upgrade PR - https://github.com/odoo/upgrade/pull/7865 Task [link](https://www.odoo.com/odoo/project/967/tasks/4137199) task-4137199
The purchase product catalog now better connects suggested purchase quantities with the kanban product cards. Suggested items are easier to spot, can be filtered interactively, and adding a product uses the recommended quantity when available.
Original PR description
Description of the issue/feature this PR addresses: The new Suggest UX of the purchase product catalog is more visible (part 1) but not linked directly to the kanban view of the catalog. This PR syncs the new UX with the kanban view. Current behavior before PR: No Link between the product catalog Kanban (of the purchase module) and new Suggest UX. Desired behavior after PR is merged: Show the kanban cards with suggested quantities first, with active style and with the suggested quantities. Change the Add button of the Kanban card from adding 1 unit to suggested quantity if any Make the Suggest UX and Kanban card interactive with the filtering. Part 1 - PR: https://github.com/odoo/odoo/pull/215363 Task: [4783508](https://www.odoo.com/odoo/project/966/tasks/4783508) I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr)
The Master Production Schedule now separates direct and indirect actual demand, making it easier to understand where needs are coming from. It also improves replenishment suggestions by accounting for early replenishment and highlights products where real demand is higher than forecast, helping planners spot risks sooner.
Original PR description
This commit will apply the following improvements on the information display of MPS: - Add an `Actual Indirect Demand` field instead of adding all the actual demand to the same field. It is direct if it's from SO, and indirect if it's from MO/ transfer to subcontracting location. - Handle the early actual replenishment by taking it into calculation when suggesting forecasted replenishment in the future. - Add a filter `Forecast Too Low`to filter out MPS where actual demand is greater than the forecasted demand. - Indicate if the actual demand is greater than the forecasted by coloring it red. Task-4936437
Barcode users handling subcontracting can now open the correct manufacturing order details directly from move lines. This streamlines subcontracting checks and removes an older intermediate record display that no longer fits the updated process.
Original PR description
We remove record components and instead make sure the subcontract details button on the move lines links directly to the correct backend MO form view. task-4321311