Odoo Changelog — 2026-04-21

Tuesday, April 21, 2026

2 changes · 19.0

Improvements(2)

Enhancements to existing features

[PERF] sale_purchase_inter_company_rules: batch stock move line unlink/create

Enterprise19.0stockMEDIUM

This change speeds up the validation of large stock transfers by processing many item updates in batches instead of one by one. It reduces database round-trips and prevents slowdowns or timeouts for deliveries with many lines, improving reliability for busy operations.

Original PR description

Before this PR, `button_validate` was using a `write()` call per matched stock move. On every `write()` there is a Command.create and Command.delete which is resulting in N database round-trips for the unlinks and N for the creates, followed by N separate `_apply_putaway_strategy()` calls. This is problematic for pickings with many move_ids.

This PR attempts to accumulates all move lines to delete and to create. Then performs a single `unlink()` and `create()`, followed by a single `_apply_putaway_strategy()` for all pickings.

Unlink is done using `.sudo()` to preserve the superuser context that was previously inherited implicitly through the
`purchase_order.sudo().search` that produced the recordset used to obtain the `receipt_move`(s).

Benchmarks:

| No. move lines in delivery | Before  | After |
| -------------------------- | ------- | ----- |
| 7579                       | Timeout | < 200 s   |

opw-5826905

Forward-Port-Of: odoo/enterprise#110587
Forward-Port-Of: odoo/enterprise#110153

#performance#stock#delivery#batch processing

[IMP] account_accountant: improve invoicing switch threshold explanation

PR #113635

Enterprise19.0account_accountant

The wording for the Invoicing Switch Threshold has been clarified to better explain which records are ignored. This helps users understand that all entries created by Invoicing before the threshold date are excluded, reducing confusion when switching accounting methods.

Original PR description

The previous "Invoicing Switch Threshold" explanation was misleading as it said only invoices prior to the threshold date is not taken into account. The explanation is updated to state that all entries created by Invoicing before the threshold date will be ignored.

task-5940144

#accounting#invoicing#settings#clarification

Before this PR, `button_validate` was using a `write()` call per matched stock move. On every `write()` there is a Command.create and Command.delete which is resulting in N database round-trips for the unlinks and N for the creates, followed by N separate `_apply_putaway_strategy()` calls. This is problematic for pickings with many move_ids. This PR attempts to accumulates all move lines to delete and to create. Then performs a single `unlink()` and `create()`, followed by a single `_apply_putaway_strategy()` for all pickings. Unlink is done using `.sudo()` to preserve the superuser context that was previously inherited implicitly through the `purchase_order.sudo().search` that produced the recordset used to obtain the `receipt_move`(s). Benchmarks: | No. move lines in delivery | Before | After | | -------------------------- | ------- | ----- | | 7579 | Timeout | < 200 s | opw-5826905 Forward-Port-Of: odoo/enterprise#110587 Forward-Port-Of: odoo/enterprise#110153

The previous "Invoicing Switch Threshold" explanation was misleading as it said only invoices prior to the threshold date is not taken into account. The explanation is updated to state that all entries created by Invoicing before the threshold date will be ignored. task-5940144