Tuesday, February 24, 2026
3 changes · 19.0
Enhancements to existing features
This update refreshes parts of Odoo's spreadsheet interface and related styling. It should provide a more polished and consistent experience for users working with spreadsheets in Odoo.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change improves mail generation performance by making the plain-text alternative email body optional. Businesses sending large campaigns can disable this extra generation step to reduce delays when preparing thousands of emails.
Original PR description
Description of the issue/feature this PR addresses: The implementation of html2plaintext is very slow. On large number of emails, e.g. when using the mass mailing module, each email takes 10 to 30 seconds (on odoo.sh) to generate depending on the email size. This makes it impossible to send several thousands of emails. Current behavior before PR: The 'body_alternative' is always generated. With this PR, this value is optional. Of cause it would be good to have an "body_alternative", but therefore the html2plaintext performance need to be increaced significant. Desired behavior after PR is merged: The 'body_alternative' is optional and can be disabled by config paramter 'mail.bypass_body_alternative_generation' --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Imported XML invoices and vendor bills now use the tax information contained in the XML file when suggesting taxes. This prevents extra taxes from being added based on past customer history, improving billing accuracy and reducing manual corrections.
Original PR description
Context: When importing an XML invoice or vendor bill, the tax prediction was based on the customer’s invoice history. Example: if the imported invoice contains an item found in the history with two taxes (6% and 21%), the prediction would return both taxes (6% and 21%), even though only one tax is present in the XML file. The actual tax data present in the imported XML was not taken into account. After this commit, the prediction is more rigorous and correctly relies on the tax information provided in the XML (restricted search domain) task-5503126 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#249307 Forward-Port-Of: odoo/odoo#246308