Monday, July 6, 2026
9 changes · saas-18.2
Enhancements to existing features
The salary configurator now better supports language changes by ensuring previously untranslated terms can be translated automatically. This improves clarity for employees and HR teams using the tool in languages other than English.
Original PR description
Originally, some terms remain untranslated when chaging the language from English. Thus, those terms have been adjusted to adhere to automatic translation
The Sendcloud delivery option formerly called "Use Batch Shipping" is now called "Use Multicollo". This aligns the wording with Sendcloud terminology, reducing confusion for users configuring shipments.
Original PR description
In order to avoid confusion for the customer, "Use Batch Shipping" was renamed to "Use Multicollo".This way it is consistent with the terminology used by Sendcloud. task-6048477 Forward-Port-Of: odoo/enterprise#122133
Budget reporting now uses the same analytic profitability criteria as profitability analysis. This helps business users see more consistent figures between budget reports and analytic profitability views, reducing confusion when comparing performance.
Original PR description
Use the new field analytic_profitability in the conditions of the query to get the account analytic lines of the budget report task-4959636 Forward-Port-Of: odoo/enterprise#121760
Resolved issues and error corrections
This update fixes automated test checks for Web Studio's report editor. It helps keep internal quality controls reliable so future changes can be validated with less risk of hidden regressions.
Original PR description
https://github.com/odoo/odoo/pull/210144
Miscellaneous changes
Add in missing modules to tx/config where their pots were auto-added by the pot export sync. Note that new pot files that were only for model names (i.e. not user facing) are usually bridge modules with nothing to translate => they weren't added to the config file
Original PR description
Add in missing modules to tx/config where their pots were auto-added by the pot export sync. Note that new pot files that were only for model names (i.e. not user facing) are usually bridge modules with nothing to translate => they weren't added to the config file
Chilean export invoice PDFs now keep the customs information table columns aligned even when origin or destination ports are not provided. This prevents package quantities from appearing under the wrong headings, improving document accuracy for exports.
Original PR description
### Issue: On Chilean export invoices, the customs information table may display data in the wrong columns When `Origin Port` or `Destination Port` is not set, the corresponding `td` is omitted by…
### Issue: On Chilean export invoices, the customs information table may display data in the wrong columns When `Origin Port` or `Destination Port` is not set, the corresponding `td` is omitted by QWeb, causing the remaining columns to shift left This results in `Qty of Packages` appearing under `Origin Port` or `Destination Port` in the printed document ### Cause: `l10n_cl_port_origin_id` and `l10n_cl_port_destination_id` have no default value and are optional fields `t-out` on a falsy value omits the `td` entirely in QWeb, breaking the column alignment Adding `or ''` ensures an empty `td` is always rendered, preserving the table structure regardless of whether the fields are set ### Steps to reproduce: - Install `l10n_cl_edi_exports` and switch to CL Company - Create an Invoice (any customer, any line) - In the gear menu, select Print > Invoice PDF copy (Chile) Before the fix, `Qty of Packages` appears under `Origin Port` when neither port field is set opw-6304670 Forward-Port-Of: odoo/enterprise#121923
This fix changes how accounting-related demo data is prepared so it can work more reliably across multiple companies. It also gives better control over which accounts and journals receive demo records, avoiding unwanted setup requirements before the system is ready.
Original PR description
It gives more flexibility in various aspects: * we can install the demo on multiple companies, like already done for invoices etc * we have a finer choice on which accounts and journals we want to select (i.e. no asset on the Tax Adjustment journal) * we don't force installing a chart of accounts for the main company before the registry is loaded
The EU IoT scale certification module is no longer available for installation in this version. This avoids customers enabling a certification feature that will only be supported in major releases.
Original PR description
This PR makes the module non installable as the scale certification will only be available in major versions Upgrade PR: https://github.com/odoo/upgrade/pull/8537
Fixed an issue where the option to request signatures could disappear on some forms depending on how users opened them. The change ensures the option is shown whenever the form has the activity and message area needed to track signature requests.
Original PR description
### Issue: In #61250, the `SignRequestCogMenuItem` allowing for signature requests was removed from forms that did not have a chatter to track the actual requests. In 18.1, the method used to do this no longer works, so the button is now hidden on certain Views depending on how you access them. ### Solution: The conditions to meet haven't changed, so we can instead use the `chatter` itself. On form views with a chatter, the `Chatter` component will set the `fetchThreadData` to false, which we can check for. opw-4817423