Odoo Changelog — 2025-11-24

Monday, November 24, 2025

23 changes · saas-18.4

Improvements(4)

Enhancements to existing features

[IMP] pos_no_followup,account_*: restore excluding invoices from follow-ups

Enterprisesaas-18.4account_followupaccount_no_followupMedium

This update brings back the ability to mark specific invoice lines as "No Follow-Up," so they will not trigger payment reminders. It also improves follow-up reports and customer statements so excluded items are handled consistently in views, exports, and reminder emails, while overdue status is not changed when only excluded items remain.

Original PR description

During the rework of the follow-up report, we removed the
"No Follow-Up" field from journal items, making it impossible to exclude
individual journal items from triggering a follow-up.

In this commit we do the following:
- Re-introduce a field for that, since it is a common
requirement to be able to exclude individual items from the follow-up
reports.
The field is stored on the journal item, but can also be toggled from
the journal entry. In case of multiple installments on the invoice,
toggling the field on one installment will toggle it for all
installments.
- Adapt the Follow-Up Report and Customer Statement variants of the
Partner Ledger to add a toggle for the "No Follow-Up" field on each
report line, that toggles the field on the corresponding journal
item(s).
- Prevent the follow-up status on the partner to change when all of the
overdue journal items are marked as "No Follow-Up".
- Make sure users can toggle the "No Follow-Up" setting on the invoice
level when opening the "Overdue Invoices" view from the partner's
"Accounting" tab.
- Make sure all receivable/payable lines without a due date (either
from a manual miscellaneous entry or a PoS entry) are put under the
"Due" section in the Follow-Up Report instead of the "Overdue"
section. Since there is no due date, they can't be overdue.
- Make sure the PDF and XLSX exports of the Follow-Up Report don't
include the "No Follow-Up" lines, and the customer follow up email
only includes the amount of the other lines.

Backport of https://github.com/odoo/enterprise/commit/74b9d2ef17e4f9a217db8432d886de2eca4baef9
and https://github.com/odoo/odoo/commit/2789a0fbfa358c5c164e44380c2a4a10e5679615
Task: 5138378

Upgrade PR → https://github.com/odoo/upgrade/pull/8864

Forward-Port-Of: odoo/enterprise#99743
Forward-Port-Of: odoo/enterprise#96627

#follow-up#invoices#customer statements#payment reminders#reporting

[IMP] sale_subscription: Dynamically fetch billing periods for portal

PR #100187

Enterprisesaas-18.4sale_subscriptionMedium

The customer subscription portal no longer relies on a fixed list of billing periods. It now reads the available billing options directly from the system, so custom periods like daily billing can be displayed without causing errors.

Original PR description

Problem -------- In v18.0, the day billing period was removed from the sale.subscription.plan model. For our use case, we require daily subscriptions, so we added this value back to the…

Problem
--------

In v18.0, the day billing period was removed from the sale.subscription.plan model.

For our use case, we require daily subscriptions, so we added this value back to the billing_period_unit selection field via inheritance.

However, this customization causes an error (a KeyError) when accessing the customer portal at /my/subscriptions/<int:order_id>. This is because the controller logic relies on a hardcoded list of periods and does not account for the new custom "day" value.

- Screenshot Order with plan Daily: 
<img width="1246" height="483" alt="image" src="https://github.com/user-attachments/assets/5dc5ca0d-a2f2-434d-8183-15a0424d9f34" />

- Screenshot when trying to get in order on the website: 
<img width="1250" height="776" alt="image" src="https://github.com/user-attachments/assets/5b10504e-71e2-4c13-8611-39e8a41e05d1" />


Proposed Solution
--------

This PR improves the subscription portal by dynamically retrieving billing periods instead of using a hardcoded list.

The portal now reads the available options directly from the billing_period_unit field's selection (i.e., self.env['sale.subscription.plan']._fields['billing_period_unit'].selection).

This improves maintainability, as future changes to the field's selection will be automatically reflected without requiring code modifications. This makes the portal robust and automatically compatible with any custom periods added via inheritance.

- 
<img width="1331" height="752" alt="image" src="https://github.com/user-attachments/assets/4f7be6c3-d96b-4525-8e23-6e1323adabde" />

Forward-Port-Of: odoo/enterprise#100084
Forward-Port-Of: odoo/enterprise#99207

[IMP] point_of_sale, pos_*: add LNA support to PoS and Self-ordering

PR #237033

Coresaas-18.4point_of_salepos_epson_printerpos_self_orderMedium

This update lets Point of Sale and self-ordering connect to local devices like Epson printers and the black box over regular HTTP in modern Chrome browsers. As a result, businesses no longer need to install certificates just to keep these local connections working.

Original PR description

*: pos_self_order, pos_epson_printer

Feature: https://chromestatus.com/feature/5152728072060928

Since Chrome 142, a new feature called “Local Network Access” has been added, allowing local IPs to be contacted via HTTP without mixed content errors.

This means that certificates are no longer required to contact Epson printers or the black box.

Forward-Port-Of: odoo/odoo#236916
Forward-Port-Of: odoo/odoo#235702

#pos#self-order#printer#chrome#local-network-access

[IMP] l10n_in_reports_gstr: enhance GSTR-2B error handling and cron filtering

PR #100267

Enterprisesaas-18.4l10n_in_reportsMedium

This update improves how GSTR-2B processing handles certain errors and avoids retrying records that are already in an invalid state. As a result, background jobs run more reliably and waste less time on records that cannot be processed successfully.

Original PR description

Before this commit:

- `RET2B1017` error code was not handled.
- Cron methods `_cron_get_gstr2b_data` and `_cron_gstr2b_match_data` processed all records with status:
  - `"waiting_reception"`
  - `"being_processed"`
- Records with blocking level `"error"` were still being processed by cron.

After this commit:

- Added handling for `RET2B1017` and mapped it to `"warning"` level.
- Updated cron domain filters to exclude records where `gstr2b_blocking_level = "error"`.
- Cron jobs now skip invalid/error-state return periods, preventing unnecessary processing.

Forward-Port-Of: odoo/enterprise#100150
Forward-Port-Of: odoo/enterprise#99378

#gstr-2b#cron#error-handling#performance

Bug Fixes(19)

Resolved issues and error corrections

[FIX] sale_subscription_stock: update delivered qty on return

PR #100094

Enterprisesaas-18.4sale_subscription_stockstockMedium

This fix ensures subscription deliveries are properly counted even when a product is returned. As a result, the delivered quantity on the sales order stays accurate, which improves billing and subscription tracking.

Original PR description

**Steps to reproduce**
- Create a new subscription using a subscription product. Confirm it.
- Run the "Sale Subscription: generate recurring invoices and payments" scheduled action to generate the delivery. Validate the delivery.
- Return the delivery and validate the return.
- Issue: the delivered quantity of the sale order line is not updated.

**Cause**
Currently, we consider a move as related to a subscription period based on the `date_deadline` field (see _get_outgoing_incoming_moves). Since `_prepare_procurement_values` is not called when creating a return, the `date_deadline` is not set on the return moves.

**Change**
The returns linked to a move in a subcription period will be conisdered
for the computation of the delivered quantities.

opw-5136406

Forward-Port-Of: odoo/enterprise#99734
Forward-Port-Of: odoo/enterprise#98690

During the rework of the follow-up report, we removed the "No Follow-Up" field from journal items, making it impossible to exclude individual journal items from triggering a follow-up. In this commit we do the following: - Re-introduce a field for that, since it is a common requirement to be able to exclude individual items from the follow-up reports. The field is stored on the journal item, but can also be toggled from the journal entry. In case of multiple installments on the invoice, toggling the field on one installment will toggle it for all installments. - Adapt the Follow-Up Report and Customer Statement variants of the Partner Ledger to add a toggle for the "No Follow-Up" field on each report line, that toggles the field on the corresponding journal item(s). - Prevent the follow-up status on the partner to change when all of the overdue journal items are marked as "No Follow-Up". - Make sure users can toggle the "No Follow-Up" setting on the invoice level when opening the "Overdue Invoices" view from the partner's "Accounting" tab. - Make sure all receivable/payable lines without a due date (either from a manual miscellaneous entry or a PoS entry) are put under the "Due" section in the Follow-Up Report instead of the "Overdue" section. Since there is no due date, they can't be overdue. - Make sure the PDF and XLSX exports of the Follow-Up Report don't include the "No Follow-Up" lines, and the customer follow up email only includes the amount of the other lines. Backport of https://github.com/odoo/enterprise/commit/74b9d2ef17e4f9a217db8432d886de2eca4baef9 and https://github.com/odoo/odoo/commit/2789a0fbfa358c5c164e44380c2a4a10e5679615 Task: 5138378 Upgrade PR → https://github.com/odoo/upgrade/pull/8864 Forward-Port-Of: odoo/enterprise#99743 Forward-Port-Of: odoo/enterprise#96627

Problem -------- In v18.0, the day billing period was removed from the sale.subscription.plan model. For our use case, we require daily subscriptions, so we added this value back to the billing_period_unit selection field via inheritance. However, this customization causes an error (a KeyError) when accessing the customer portal at /my/subscriptions/<int:order_id>. This is because the controller logic relies on a hardcoded list of periods and does not account for the new custom "day" value. - Screenshot Order with plan Daily: <img width="1246" height="483" alt="image" src="https://github.com/user-attachments/assets/5dc5ca0d-a2f2-434d-8183-15a0424d9f34" /> - Screenshot when trying to get in order on the website: <img width="1250" height="776" alt="image" src="https://github.com/user-attachments/assets/5b10504e-71e2-4c13-8611-39e8a41e05d1" /> Proposed Solution -------- This PR improves the subscription portal by dynamically retrieving billing periods instead of using a hardcoded list. The portal now reads the available options directly from the billing_period_unit field's selection (i.e., self.env['sale.subscription.plan']._fields['billing_period_unit'].selection). This improves maintainability, as future changes to the field's selection will be automatically reflected without requiring code modifications. This makes the portal robust and automatically compatible with any custom periods added via inheritance. - <img width="1331" height="752" alt="image" src="https://github.com/user-attachments/assets/4f7be6c3-d96b-4525-8e23-6e1323adabde" /> Forward-Port-Of: odoo/enterprise#100084 Forward-Port-Of: odoo/enterprise#99207

*: pos_self_order, pos_epson_printer Feature: https://chromestatus.com/feature/5152728072060928 Since Chrome 142, a new feature called “Local Network Access” has been added, allowing local IPs to be contacted via HTTP without mixed content errors. This means that certificates are no longer required to contact Epson printers or the black box. Forward-Port-Of: odoo/odoo#236916 Forward-Port-Of: odoo/odoo#235702

Before this commit: - `RET2B1017` error code was not handled. - Cron methods `_cron_get_gstr2b_data` and `_cron_gstr2b_match_data` processed all records with status: - `"waiting_reception"` - `"being_processed"` - Records with blocking level `"error"` were still being processed by cron. After this commit: - Added handling for `RET2B1017` and mapped it to `"warning"` level. - Updated cron domain filters to exclude records where `gstr2b_blocking_level = "error"`. - Cron jobs now skip invalid/error-state return periods, preventing unnecessary processing. Forward-Port-Of: odoo/enterprise#100150 Forward-Port-Of: odoo/enterprise#99378

**Steps to reproduce** - Create a new subscription using a subscription product. Confirm it. - Run the "Sale Subscription: generate recurring invoices and payments" scheduled action to generate the delivery. Validate the delivery. - Return the delivery and validate the return. - Issue: the delivered quantity of the sale order line is not updated. **Cause** Currently, we consider a move as related to a subscription period based on the `date_deadline` field (see _get_outgoing_incoming_moves). Since `_prepare_procurement_values` is not called when creating a return, the `date_deadline` is not set on the return moves. **Change** The returns linked to a move in a subcription period will be conisdered for the computation of the delivered quantities. opw-5136406 Forward-Port-Of: odoo/enterprise#99734 Forward-Port-Of: odoo/enterprise#98690

Issue ----- Gantt view's drag & drop allows the user to change the value of readonly fields if they are stored. E.G. in the Planning view of MRP, grouped by Work Center > Product, dragging & dropping can change the product of the WO if the user is not careful and drops the WO on top of another product's WO. Steps to reproduce ----- - Have 2 products - Create a MO for product 1 with a WO at work center 1, plan it - Create a MO for product 2 with a WO at work center 2, plan it - Got to Manufacturing, Planning, Planning by Work Center - Add a custom group (by product) - Drag the WO of WC2 and drop it on top of the other WO > Both the WC and the product of the second WO change Cause ----- The example problem is only for versions 17.0 & 18.0 where the `product_id` field of `mrp.workorder` is both readonly and stored. https://github.com/odoo/odoo/blob/31e46a841b38de0f99beb1844f985bc670621486/addons/mrp/models/mrp_workorder.py#L34 While the user cannot change the field value manually, automatic actions such as a gantt view drag & drop can change its' value by passing it to `write` since the field is stored. This does not pose any problem for related fields that are not stored. More broadly, gantt views should not ignore the `readonly` attribute of fields. Solution ----- Add a new `o_gantt_readonly` class to all cells of rows grouped by a readonly field - and their "child" rows. For example, if the grouping is done by "Work Center > Product > Quality Check" and "Product" is readonly, rows grouped by either "Product" or "Quality Check" will be marked as readonly. When the user drags a pill, dynamically remove the class from cells of the same "child group". The class will then be added back upon pill drop. ----- Ticket: opw-4875366 Forward-Port-Of: odoo/enterprise#100088 Forward-Port-Of: odoo/enterprise#94166

### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/4f8366721 [REL] 18.4.18 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/83c393f62 [FIX] Spreadsheet: fix scroll on ios [Task: 5270869](https://www.odoo.com/odoo/2328/tasks/5270869) https://github.com/odoo/o-spreadsheet/commit/948c51e86 [FIX] headers_overlay: disable interaction in read-only mode [Task: 5182854](https://www.odoo.com/odoo/2328/tasks/5182854) https://github.com/odoo/o-spreadsheet/commit/3ce3152f7 [FIX] spreadsheet: fix button height [Task: 5253888](https://www.odoo.com/odoo/2328/tasks/5253888) https://github.com/odoo/o-spreadsheet/commit/16b2e4115 [FIX] composer: change mode to editing when composer cursor selection changes [Task: 5226615](https://www.odoo.com/odoo/2328/tasks/5226615) https://github.com/odoo/o-spreadsheet/commit/e4b3ebef8 [FIX] SidePanel: reset initial props on Model change [Task: 5059484](https://www.odoo.com/odoo/2328/tasks/5059484) https://github.com/odoo/o-spreadsheet/commit/62dfe8a88 [FIX] composer: Enter/Tab confirm when assistant is force-closed [Task: 5153666](https://www.odoo.com/odoo/2328/tasks/5153666) https://github.com/odoo/o-spreadsheet/commit/2a23dddf4 [FIX] reference_type: add single quotes for sheet names with spaces [Task: 5244798](https://www.odoo.com/odoo/2328/tasks/5244798) Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Ronak Mukeshbhai Bharadiya (rmbh) <rmbh@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com> Co-authored-by: Marceline Thomas (matho) <matho@odoo.com>

### [FIX] mail: clean the "beforeunload" listener in tests Some tests trigger a call to the function `Rtc.joinCall` which adds a listener on `beforeunload` event that cancels the event. Some of these tests do not trigger a later call to `Rpc.clear`, thus the listener stays registered. This could mess with other unrelated tests that check their own handlers of `beforeunload` are correct. This commit adds a cleanup on the helper used by the problematic tests. task-5138313 ### [FIX] website, html_builder: run after-save handlers if aborted Usually, running the after save handlers is not needed after the save because we are about to close or reload the builder. Thus they are not run as an optimization. But there are a few cases where they are needed: - The saving of the page failed. This case was correctly handled only when clicking on the save button or adding a module - When adding a language, but cancelling the dialog to choose the language This commit changes the save function of the save plugin, to take a async callback to determine whether the after-save handlers should run. The callback is async to be able to wait for the language choice dialog. If the callback returns `true`, then the after-save handlers are run. Steps to reproduce: - Open website builder - Open "Theme" tab - Click "Add Language" - Confirm the first dialog (about save) - Cancel the second dialog (language choice) - Bug: the save button stays disabled with the spinning wheel next to it task-5138313

Improvements(4)

[IMP] pos_no_followup,account_*: restore excluding invoices from follow-ups

[IMP] sale_subscription: Dynamically fetch billing periods for portal

[IMP] point_of_sale, pos_*: add LNA support to PoS and Self-ordering

[IMP] l10n_in_reports_gstr: enhance GSTR-2B error handling and cron filtering

Bug Fixes(19)

[FIX] sale_subscription_stock: update delivered qty on return

Improvements(4)

[IMP] pos_no_followup,account_*: restore excluding invoices from follow-ups

[IMP] sale_subscription: Dynamically fetch billing periods for portal

[IMP] point_of_sale, pos_*: add LNA support to PoS and Self-ordering

[IMP] l10n_in_reports_gstr: enhance GSTR-2B error handling and cron filtering

Bug Fixes(19)

[FIX] sale_subscription_stock: update delivered qty on return

[FIX] web_gantt: disable drop for rows grouped by readonly field

[FIX] currency_rate_live: wrong dates for Swiss FTA rates

[FIX] account_iso20022: restore NURG SvcLvl for non-SEPA payments

[FIX] account_edi_ubl_cii*: update 'invoice_edi_format' when uninstalling

[FIX] l10n_es_reports: fix accounts coverage report

[FIX] spreadsheet: update o_spreadsheet to latest version

[FIX] {account,l10n_it}_reports: journal report pdf template

[FIX] website: fix search header alignment views

[FIX] sign: show date placeholder only for the current signer

[FIX] stock_account: compute avg price using only move with same product

[PERF] account: Avoid OOM error when processing batch payments

[FIX] l10n_ph: missing tax_negate on custom tax tags.

[FIX] account_accountant: edit partner

[FIX] account_reports: include expense_other in P&L

[FIX] l10n_fr_reports: missing accounts in BS

web: Hoot - fix blob handling

[FIX] website, html_builder: run after-save handlers if aborted

[PERF] stock: Speedup _find_delivery_ids_by_lot