Odoo Changelog — 2026-04-13

Monday, April 13, 2026

2 changes · 19.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] sale_renting,sale_stock_renting: correct pickup/return quantity and timezone offset

Enterprise19.0salestockrentalMedium

This update corrects a reporting issue in the Rental app where pickup/return quantities were incorrectly duplicated and the report displayed the wrong start date. The fix addresses a problem with how the database handles timezones and ensures accurate reporting of rental activity. This improves the reliability of rental data analysis.

Original PR description

Steps to reproduce: 1- Install Rental app and create a rental product. 2- Create a Rental Order for that product from Feb 27, 12:00 AM to Feb 28, 11:30 PM. 3- Confirm the order and deliver the…

Steps to reproduce:
1- Install Rental app and create a rental product.
2- Create a Rental Order for that product from Feb 27, 12:00 AM to Feb 28, 11:30 PM.
3- Confirm the order and deliver the quantity.
4- Open the [Rental -> Reporting -> Rental Analysis] Pivot view.
5- Set the measures to "Picked up Quantity" and group by "Date: Day".

Description of issue:
Two issues occur:
1- The "Picked up Quantity" is duplicated and shown on every single day of the rental period. The same happens for the "Returned Quantity" which is shown on every row.

2- The report shows the start date on the previous day (Feb 26).

Expected behavior:
1- The Picked up/Returned Quantity should only appear on the day the pickup/return actually occurred.

2- The start date should be on the same day (Feb 27).

Why this happens?
1- The SQL view uses generate_series to expand the rental duration into individual days. The original query was pulling the qty_delivered/qty_returned into every resulting row without a conditional check.

2- Datetime fields are stored in UTC format in the database, and the SQL view was performing a date cast directly on the UTC field without converting to the local timezone.

opw-5501263

#reporting#rental#timezone#quantity

[IMP] sale_subscription: allow to process SO invoice without country

PR #100166

Enterprise19.0sale_subscriptionMedium

This update removes an outdated requirement for country information on payment tokens used for subscription invoices. Previously, this restriction caused processing errors, particularly with certain payment providers. This change ensures invoices can be processed correctly, improving subscription billing reliability.

Original PR description

Before this commit, a country was mantadory on the payment token when it
was used to pay invoices of subscriptions. This behavior was fetched
back from internal code in 15.3. This issue was not visible until
recently. Some token are fine without country, the provider allows it
but the cron fails to process the sale order when the contract is
processed. THis commit remove that old constraint.

opw-5268156
task-5349998

#billing#subscriptions#payments

Steps to reproduce: 1- Install Rental app and create a rental product. 2- Create a Rental Order for that product from Feb 27, 12:00 AM to Feb 28, 11:30 PM. 3- Confirm the order and deliver the quantity. 4- Open the [Rental -> Reporting -> Rental Analysis] Pivot view. 5- Set the measures to "Picked up Quantity" and group by "Date: Day". Description of issue: Two issues occur: 1- The "Picked up Quantity" is duplicated and shown on every single day of the rental period. The same happens for the "Returned Quantity" which is shown on every row. 2- The report shows the start date on the previous day (Feb 26). Expected behavior: 1- The Picked up/Returned Quantity should only appear on the day the pickup/return actually occurred. 2- The start date should be on the same day (Feb 27). Why this happens? 1- The SQL view uses generate_series to expand the rental duration into individual days. The original query was pulling the qty_delivered/qty_returned into every resulting row without a conditional check. 2- Datetime fields are stored in UTC format in the database, and the SQL view was performing a date cast directly on the UTC field without converting to the local timezone. opw-5501263

Before this commit, a country was mantadory on the payment token when it was used to pay invoices of subscriptions. This behavior was fetched back from internal code in 15.3. This issue was not visible until recently. Some token are fine without country, the provider allows it but the cron fails to process the sale order when the contract is processed. THis commit remove that old constraint. opw-5268156 task-5349998