Odoo Changelog — 2025-12-15

Monday, December 15, 2025

6 changes · saas-18.2

Bug Fixes(6)

Resolved issues and error corrections

[FIX] (website_)sale_renting: relativedelta on time-zoned dates

Enterprisesaas-18.2website_sale_rentingsale_rentingMEDIUM

This update fixes an issue where rental price calculations were inconsistent due to how relativedelta handled time-zoned dates. The change ensures accurate price calculations by correctly accounting for time zone differences, preventing discrepancies in rental durations. This improves the reliability of rental pricing displayed to customers.

Original PR description

Relativedelta on UTC dates or time-zoned dates doesn't return the same result. 
In order to calculate consistent prices (price for 1 month in December = price for 1 month in January), we need to work on time-zoned dates.

Example: 
Consider a website in UTC+1 (Brussels timezone DST off).
And a rental from the 01/12/2025 to the 31/12/2025 = by design, from the 01/01/2025 00h00 (start_date) to the 31/12/2025 23h59 (end_date). 
Converted in UTC for the back-end, we have:
from the 30/11/2025 23h00 to the 31/12/2025 22h59.
relativedelta(end_date, start_date) = time between the 2 dates is calculated as follow:
30/11/2025  23h00 + 1 month = 30/12/2025 23h00 +23h59 = 31/12/2025 22h59. 
Time difference = 1 month, 23 hours, 59 minutes. 
Price = 2 months. 

Consider a second rental from the 01/01/2026 to the 31/01/2026. 
31/12/2025 23h00 + 30 days = 30/01/2026 23h + 23h59 = 31/01/2026 22h59. 
Time difference = 30 days, 23 hours, 59 minutes.
Price = 1 month. 

opw-5130762

Forward-Port-Of: odoo/enterprise#98571

#pricing#rental#timezone#calculation

[FIX] pos_l10n_se: allow price control with blackbox

PR #101797

Enterprisesaas-18.2pos_l10n_seMEDIUM

This update resolves an issue where users couldn't adjust prices within the POS system when utilizing the Swedish blackbox integration. Now, price control is enabled, aligning with the requirements for the Swedish blackbox, unlike the Belgian version where it was previously mandatory. This ensures accurate pricing for Swedish POS transactions.

Original PR description

Before this commit, user couldn't control the price in the POS if using the swedish blackbox.

After this commit, user can control the price.

It's not clear why the behavior at integration was set to this but it appears that it's not mandatory for swedish blackbox unlike the belgian one.

opw-5253401

Forward-Port-Of: odoo/enterprise#100984

#POS#Sweden#Blackbox#Pricing

[FIX] sale_subscription(_stock): correct tooltip text and recurring price

PR #101914

Enterprisesaas-18.2salesubscriptionproductMEDIUM

This update corrects an issue where subscription products incorrectly displayed both recurring and list prices on their product cards. Now, subscription products show only the recurring price, ensuring accurate pricing information for our customers. This improves clarity and simplifies product selection.

Original PR description

Version
- 18.0

Steps to Reproduce:
Issue 1: Incorrect tooltip text
  1. Go to Products → Products in subscription app.
  2. Open a product page and select goods product type
  3. observe product_tooltip show incorrect wording:
       * "Based on order" showed end of the period.
       * "Based on delivered" showed beginning of the period.

Issue 2: Product card shows both recurring and sales price
  1. Go to Products → Products in subscription app.
  2. Observe that the product card displays both recurring price and sales price

After this PR:
- Tooltip now correctly states:
   * for "based on order" invoice_policy -> beginning of period
   * for "based on delivery" invoice_policy -> end of period
- Product cards show only the recurring price when applicable.

task-5156390
<img width="1002" height="436" alt="image" src="https://github.com/user-attachments/assets/39f00555-e37a-44a5-8786-d7f8d6882de7" />
<img width="968" height="262" alt="image" src="https://github.com/user-attachments/assets/0d6d5c2d-d5ab-4376-bc03-dba243abce8b" />

Forward-Port-Of: odoo/enterprise#95010

#pricing#subscription#product

[FIX] account_online_synchronization: prevent error when no journal is linked

PR #101177

Enterprisesaas-18.2account

This update resolves an error that occurred when users attempted to duplicate transactions through the account module. The fix ensures the system correctly handles scenarios where a journal isn't linked to the transaction wizard, preventing a data assignment error and improving stability.

Original PR description

Currently, an error occurs when user opens the `account.duplicate.transaction.wizard.form` view and saves it.

**Steps to Reproduce:**

 - Install the `account_accountant` module.
 - Using `Open View`, open the `account.duplicate.transaction.wizard` view > enter the start date, and save..

`ValueError: Compute method failed to assign account.duplicate.transaction.wizard(22,).provider_duplicate_ids`

The error occurs because when the view is opened and saved, the _compute_provider_duplicate_ids method is triggered. Since no journal is linked to the wizard, the method assigns an empty list ([]) to provider_duplicate_ids [1]. Because this is a O2M field, assigning a raw empty list is invalid and causes the error.

This commit ensures that when journal is missing, instead of assigning an empty list ([]), a valid relational command `([Command.set([])])` is used.

Ref: https://github.com/odoo/enterprise/pull/97196/commits/c109e0bcce20f14b6dbd3d28e61b135f1fd048f2

[1] https://github.com/odoo/enterprise/blob/d808ad3f6ff52632e00cf1a68de0e5270e52895d/account_online_synchronization/wizard/account_journal_duplicate_transactions.py#L53

sentry-7080686084

#accountant#transactions#error

[FIX] web_studio: prevent generating invalid field nodes

PR #102150

Enterprisesaas-18.2hr_timesheetMEDIUM

This update resolves an issue where users were encountering errors when creating reports in Web Studio, specifically when adding fields to the report layout. The fix prevents the generation of invalid field nodes, ensuring reports render correctly and avoiding disruptions to the reporting process. This improves the stability and usability of Web Studio for creating custom reports.

Original PR description

cf commit

Forward-Port-Of: odoo/enterprise#101970
Forward-Port-Of: odoo/enterprise#99385

#reporting#web_studio

[FIX] l10n_be_reports: no / in xml when empty comment.

PR #102119

Enterprisesaas-18.2l10n_be_reports

This update fixes an issue where unnecessary slashes were appearing in Odoo's XML reports when there was no comment provided. Removing this slash ensures reports are formatted correctly and consistently, improving data accuracy for financial reporting. This change was implemented as a bug fix.

Original PR description

Since 17.0, we added a / when there was no comment in the comment section of the xml. This is wrong and should be left empty.

opw-5242381

Forward-Port-Of: odoo/enterprise#101339
Forward-Port-Of: odoo/enterprise#100033

#reporting#tax#xml

Relativedelta on UTC dates or time-zoned dates doesn't return the same result. In order to calculate consistent prices (price for 1 month in December = price for 1 month in January), we need to work on time-zoned dates. Example: Consider a website in UTC+1 (Brussels timezone DST off). And a rental from the 01/12/2025 to the 31/12/2025 = by design, from the 01/01/2025 00h00 (start_date) to the 31/12/2025 23h59 (end_date). Converted in UTC for the back-end, we have: from the 30/11/2025 23h00 to the 31/12/2025 22h59. relativedelta(end_date, start_date) = time between the 2 dates is calculated as follow: 30/11/2025 23h00 + 1 month = 30/12/2025 23h00 +23h59 = 31/12/2025 22h59. Time difference = 1 month, 23 hours, 59 minutes. Price = 2 months. Consider a second rental from the 01/01/2026 to the 31/01/2026. 31/12/2025 23h00 + 30 days = 30/01/2026 23h + 23h59 = 31/01/2026 22h59. Time difference = 30 days, 23 hours, 59 minutes. Price = 1 month. opw-5130762 Forward-Port-Of: odoo/enterprise#98571

Before this commit, user couldn't control the price in the POS if using the swedish blackbox. After this commit, user can control the price. It's not clear why the behavior at integration was set to this but it appears that it's not mandatory for swedish blackbox unlike the belgian one. opw-5253401 Forward-Port-Of: odoo/enterprise#100984

Version - 18.0 Steps to Reproduce: Issue 1: Incorrect tooltip text 1. Go to Products → Products in subscription app. 2. Open a product page and select goods product type 3. observe product_tooltip show incorrect wording: * "Based on order" showed end of the period. * "Based on delivered" showed beginning of the period. Issue 2: Product card shows both recurring and sales price 1. Go to Products → Products in subscription app. 2. Observe that the product card displays both recurring price and sales price After this PR: - Tooltip now correctly states: * for "based on order" invoice_policy -> beginning of period * for "based on delivery" invoice_policy -> end of period - Product cards show only the recurring price when applicable. task-5156390 <img width="1002" height="436" alt="image" src="https://github.com/user-attachments/assets/39f00555-e37a-44a5-8786-d7f8d6882de7" /> <img width="968" height="262" alt="image" src="https://github.com/user-attachments/assets/0d6d5c2d-d5ab-4376-bc03-dba243abce8b" /> Forward-Port-Of: odoo/enterprise#95010

Currently, an error occurs when user opens the `account.duplicate.transaction.wizard.form` view and saves it. **Steps to Reproduce:** - Install the `account_accountant` module. - Using `Open View`, open the `account.duplicate.transaction.wizard` view > enter the start date, and save.. `ValueError: Compute method failed to assign account.duplicate.transaction.wizard(22,).provider_duplicate_ids` The error occurs because when the view is opened and saved, the _compute_provider_duplicate_ids method is triggered. Since no journal is linked to the wizard, the method assigns an empty list ([]) to provider_duplicate_ids [1]. Because this is a O2M field, assigning a raw empty list is invalid and causes the error. This commit ensures that when journal is missing, instead of assigning an empty list ([]), a valid relational command `([Command.set([])])` is used. Ref: https://github.com/odoo/enterprise/pull/97196/commits/c109e0bcce20f14b6dbd3d28e61b135f1fd048f2 [1] https://github.com/odoo/enterprise/blob/d808ad3f6ff52632e00cf1a68de0e5270e52895d/account_online_synchronization/wizard/account_journal_duplicate_transactions.py#L53 sentry-7080686084

Since 17.0, we added a / when there was no comment in the comment section of the xml. This is wrong and should be left empty. opw-5242381 Forward-Port-Of: odoo/enterprise#101339 Forward-Port-Of: odoo/enterprise#100033