Daily updates from Odoo
Thursday, May 8, 2025
10 changes
5 changes
Enhancements to existing features
The website setup flow has been refined to make onboarding clearer and more polished for users creating a new website. This should help new users move through the configurator with less friction and a better first impression.
Original PR description
task-4505899
The Sign sharing flow was updated to make the share wizard clearer while preserving the existing ability to manually stop sharing documents. This improves the user experience around shared signature documents, though expiration dates for shares are still not available.
Original PR description
Before this commit, when sharing a document, you could only stop sharing manually using the Stop Sharing option. Unlike other documents, there was no option to set an expiration date for shared documents. With this commit, the ability to manually stop sharing documents using the Stop Sharing option remains. However, the option to set a validity period like with other document types, is still not available. task-4163986
Users now receive a warning when changing a contact’s email address if that contact has pending signature requests. This helps prevent important signing documents from being silently sent to a new email address without confirmation.
Original PR description
Before this commit, when the email address of a res.partner was changed, any pending sign requests were automatically sent to the new email without notifying the user. With this commit, a warning is displayed when the email address is updated: "There are pending sign requests for this contact. Would you like to send them to the new email address?" Task-4570835
Brazilian localization now supports external tax calculation and electronic document submission for vendor bills and vendor bill refunds. This helps businesses handle cases where the customer must pay taxes on supplier bills that are not charged directly by the vendor.
Original PR description
This does both tax calculation and EDI for vendor bills and vendor bill refunds. It's needed because in certain cases the customer will pay a specific tax on bills that is not directly charged by the…
This does both tax calculation and EDI for vendor bills and vendor bill refunds. It's needed because in certain cases the customer will pay a specific tax on bills that is not directly charged by the vendor. Luckily, not many changes are needed to adapt the tax calculation and EDI code for invoices to work on bills as well. The most important ones are changing the operation type and allowing to use the account.move.send wizard to work with bills. Because this needs to change what `move_type`s an external tax calculator acts on, we take the opportunity to absorb those conditions into the `is_tax_computed_externally` field. It simplifies the logic a bit, and makes it easier to change based on the needs of the tax calculator. It means that every tax calculator is now responsible for marking the types of records they act on in a `_compute_is_tax_computed_externally` override. It's necessary because the move_type domain used to be part of the view in *external_tax*, it's not possible to add that check in the default `_compute_is_tax_computed_externally` because then every sale document would be considered eligible for external taxes. task-4608570
The Indian tax reports module now checks that GST numbers follow the required format before sending requests to GST, e-Invoice, and E-Waybill services. This reduces unnecessary external API calls and helps users receive clearer validation feedback when a GST number is invalid.
Original PR description
Currently, we only check if a GST number is present before making API calls for GST, e-Invoice, and E-Waybill services. This allows invalid GST numbers (such as single-character inputs), leading to unnecessary API calls and ambiguous error responses. This **PR** aims to ensure that only valid GST numbers, formatted according to GST specifications, are sent for API requests. **task**-4668014 **Community PR** - https://github.com/odoo/odoo/pull/207888
5 changes
Enhancements to existing features
Partner lists now include the invoice sending method as a hidden field, allowing teams to use mass editing when they need to update how invoices are sent. This reduces manual work when maintaining customer billing preferences.
Original PR description
Add the Invoice Sending Method field to the partner's list view to enable mass edit. task-no (feedback from WTA)
The Guatemala localization now supports local CUI and NIT identification types and includes Guatemala-specific fuel taxes. This helps companies operating in Guatemala keep partner records and tax calculations aligned with local requirements, with updated demo data to reflect the new setup.
Original PR description
Added support for CUI and NIT identification types, added GT-specific fuel taxes (requiring a dependancy on account_tax_python), updated demo data. CUI for demo_partner set to an obviously fake 1111111100000 for the moment as the originally provided one doesn't pass the validation. To work alongside l10n_co, requires the fix in https://github.com/odoo/enterprise/pull/81216 (temporary branch for 18.0 to work with the runbot is added here https://github.com/odoo/enterprise/pull/80671) task-4318265 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The purchase product category search view now places the “In the order” filter in its own section and in a clearer position. This makes it easier for purchasing users to compare products and prices when reviewing order-related items.
Original PR description
Description of the issue/feature this PR addresses: When purchasing a product in a unit different than the product unit, it is not easy to compare price for purchaser (alternative, ...) Current behavior before PR: Desired behavior after PR is merged: - One line change for purchase category search view, to add the "In the order" filter in its own section and change its order within the search view, the rest of the changes are on-save auto format. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Deleting expenses is now much faster when accounting records are large. This reduces waiting time for users and improves day-to-day performance without changing how expenses work.
Original PR description
Description ----------- Deleting an expense is slow when the `account_move_line` table is large, as the `Many2one`/`fkey` `expense_id` needs to be set to `NULL` where necessary. If there is no index on the `fkey`, it's `Seq. Scan` on the table `account_move_line`. Benchmark: ---------- On odoo.com, unlinking an expense took: | Before | After | |--------|-------| | 10s | 58ms | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Financial report settings now show the integer rounding option directly in the report options. This makes the setting easier to discover and use without needing technical knowledge or code inspection.
Original PR description
This is a useful option that is hard to know about unless you read the code or are told it exists. It should be visible in the report options. In the context of: task-4734528