Odoo Changelog — 2026-09-02

Wednesday, September 2, 2026

3 changes · 17.0

Bug Fixes(3)

Resolved issues and error corrections

[FIX] delivery_dhl_rest: remove pick-up request

Enterprise17.0delivery_dhl_restMedium

Odoo's DHL REST shipping integration no longer automatically requests a carrier pickup when arranging deliveries. This removes an extra scheduling step, avoids DHL errors from incomplete pickup details, and makes DHL behave more consistently with other shipping carriers.

Original PR description

Before this commit, the DHL REST module had the pick-up request set, which led to an unnatural use flow, needing to set up an scheduled date for pick-up, and several errors from DHL when these were not properly configured.

This feature was unique to this module among the shipping carriers as we don't normally request pick-up for packages and leave it to user to decide how to do it.

This commit removes the request for pick up and the logic that was needed to make it work. This will make the behavior consistent with other carriers in Odoo, and avoids the need to set scheduled pick-up windows and having to deal with unnecessary errors.

opw-6148927

#DHL#shipping#pickup#delivery

[FIX] spreadsheet: replace one-by-one retry with binary split batching

PR #261525

Core17.0spreadsheetMedium

Spreadsheet data loading now handles failed batches more efficiently by retrying smaller groups instead of every request one by one. This reduces delays and lowers the chance of overloading the server when only a few requests in a large batch fail.

Original PR description

## Description of the issue/feature this PR addresses:

Previously, when a batch RPC failed, the system retried each request individually. This resulted in N sequential RPC calls, causing performance issues for large batches and increasing the risk of rate limiting (HTTP 429) or backend overload.

This commit replaces the one-by-one retry strategy with a binary split (divide and conquer) approach. When a batch fails, it is recursively split into two halves and retried independently until either the batch succeeds or only one request remains.

This approach improves performance in common scenarios where only a few requests fail. Instead of retrying all requests individually, only the failing subsets are further split and retried.

Complexity:
- Best case: O(1) when the full batch succeeds
- Worst case: 2N - 1 calls when all requests fail

Although the worst-case number of calls is higher than in the previous approach (N), in practice, it is rare for all requests to fail. This approach performs better in typical scenarios where only a small no of requests fail.

Task: [6113607](https://www.odoo.com/odoo/project/2328/tasks/6113607)

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

[FIX] payment_adyen: retrieve correct values from the payload

PR #284773

Core17.0payment_adyenMedium

This fixes an issue where Adyen payment information could be read from the wrong place in the payment notification payload. It helps ensure payment updates are processed with the correct details, reducing the risk of incorrect transaction handling.

Original PR description

opw-6512723

#payments#adyen#payment notifications

Before this commit, the DHL REST module had the pick-up request set, which led to an unnatural use flow, needing to set up an scheduled date for pick-up, and several errors from DHL when these were not properly configured. This feature was unique to this module among the shipping carriers as we don't normally request pick-up for packages and leave it to user to decide how to do it. This commit removes the request for pick up and the logic that was needed to make it work. This will make the behavior consistent with other carriers in Odoo, and avoids the need to set scheduled pick-up windows and having to deal with unnecessary errors. opw-6148927

## Description of the issue/feature this PR addresses: Previously, when a batch RPC failed, the system retried each request individually. This resulted in N sequential RPC calls, causing performance issues for large batches and increasing the risk of rate limiting (HTTP 429) or backend overload. This commit replaces the one-by-one retry strategy with a binary split (divide and conquer) approach. When a batch fails, it is recursively split into two halves and retried independently until either the batch succeeds or only one request remains. This approach improves performance in common scenarios where only a few requests fail. Instead of retrying all requests individually, only the failing subsets are further split and retried. Complexity: - Best case: O(1) when the full batch succeeds - Worst case: 2N - 1 calls when all requests fail Although the worst-case number of calls is higher than in the previous approach (N), in practice, it is rare for all requests to fail. This approach performs better in typical scenarios where only a small no of requests fail. Task: [6113607](https://www.odoo.com/odoo/project/2328/tasks/6113607) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr