Odoo Changelog — 2025-09-18

Thursday, September 18, 2025

2 changes · 17.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] l10n_in_reports: show proper values for purchase entries GSTR-3B

Enterprise17.0l10n_in_reportsl10n_in_reports_gstr_posMEDIUM

The GSTR-3B report now includes purchase credit notes, receipts, and other purchase records so reported values are accurate. Purchase-related report data was also removed from the POS reporting area because POS does not handle purchase records, reducing the risk of misleading tax figures.

Original PR description

Currently, purchase entries are not displaying the correct data because the credit notes and receipts were not included.

This PR removes purchase-related data from `l10n_in_reports_gstr_pos` (as POS has no relation to purchase records) and ensures that credit note data and other purchase records are properly displayed in the GSTR-3B report.

**opw**-5079401

Forward-Port-Of: odoo/enterprise#94582

#GSTR-3B#India#tax reporting#purchase entries

[FIX] sale_loyalty: handle multiple orders in `_recompute_prices`

PR #227278

Core17.0sale_loyaltyMEDIUM

This fixes a crash that could occur when a customer had open carts on multiple eCommerce sites and changed their address. Loyalty rewards are now recalculated separately for each cart, keeping checkout flows stable when tax or fiscal rules change.

Original PR description

Versions
--------
- 16.0+

Steps
-----
1. Have 2 eCommerce sites;
2. have a user with an open cart in both sites;
3. have a reward applied in one or both of carts;
4. have a fiscal position applicable to the user's address;
5. change the user's country to one with a different fiscal position.

Issue
-----
> ValueError: Expected singleton: sale.order(1, 2)

Cause
-----
As of commit ede8846987a98, fiscal positions get recomputed on address changes. When a fiscal position changes, the `_recompute_prices` method gets called on all open carts.

This method does not include an `ensure_one` check, so it should be able to handle multiple sales orders.

However, the `sale_loyalty` override will call `_update_programs_and_rewards` on `self` if any reward line is encountered. This method does have an `ensure_one` check, leading to the error.

Solution
--------
Rewrite the override as a loop, so it can handle multiple records in `self`.

opw-5017669

Forward-Port-Of: odoo/odoo#224225

#eCommerce#loyalty#cart#checkout

Currently, purchase entries are not displaying the correct data because the credit notes and receipts were not included. This PR removes purchase-related data from `l10n_in_reports_gstr_pos` (as POS has no relation to purchase records) and ensures that credit note data and other purchase records are properly displayed in the GSTR-3B report. **opw**-5079401 Forward-Port-Of: odoo/enterprise#94582

Versions -------- - 16.0+ Steps ----- 1. Have 2 eCommerce sites; 2. have a user with an open cart in both sites; 3. have a reward applied in one or both of carts; 4. have a fiscal position applicable to the user's address; 5. change the user's country to one with a different fiscal position. Issue ----- > ValueError: Expected singleton: sale.order(1, 2) Cause ----- As of commit ede8846987a98, fiscal positions get recomputed on address changes. When a fiscal position changes, the `_recompute_prices` method gets called on all open carts. This method does not include an `ensure_one` check, so it should be able to handle multiple sales orders. However, the `sale_loyalty` override will call `_update_programs_and_rewards` on `self` if any reward line is encountered. This method does have an `ensure_one` check, leading to the error. Solution -------- Rewrite the override as a loop, so it can handle multiple records in `self`. opw-5017669 Forward-Port-Of: odoo/odoo#224225