Odoo Changelog — 2026-08-20

Thursday, August 20, 2026

3 changes · saas-18.4

Bug Fixes(3)

Resolved issues and error corrections

[FIX] sale_shopee: fix shop re-authorization error

Enterprisesaas-18.4sale_shopeeMEDIUM

Fixed an issue where reconnecting a Shopee shop with a different API account did not update the linked account in Odoo. This ensures shops stay connected to the correct Shopee credentials after re-authorization, reducing setup errors and manual corrections.

Original PR description

Context: when a user re-authenticate a shop, they might use different shopee.account (API key). Currently Odoo will not change the shopee.account when they re-auth with another shopee.account.

Enable a shopee.shop switches to another shopee.account when we run `create_or_update_shop` function.

Forward-Port-Of: odoo/enterprise#92446

#shopee#authorization#account

[FIX] account_sepa_direct_debit: SchmeNm missing

PR #128276

Enterprisesaas-18.4account_sepa_direct_debit

SEPA direct debit payment files now include a required scheme name in the initiating party section. This improves compatibility with banks such as Nordea in Sweden and helps prevent payment file rejection.

Original PR description

We are missing a SchmeNm node in the InitgPty node.

This is mandatory for Nordea in Sweden at least. Such as:

```xml
<SchmeNm>
  <Cd>CUST</Cd>
</SchmeNm>
```

task-6385960

Forward-Port-Of: odoo/enterprise#124693

#SEPA#direct debit#bank compatibility#Nordea

[FIX] whatsapp: order template parameters by placeholder

PR #128466

Enterprisesaas-18.4whatsappMEDIUM

This fixes an issue where WhatsApp message templates with 10 or more mixed variables could send values in the wrong positions. Businesses can rely on larger templates to show the correct customer, user, and text details when messages are sent.

Original PR description

**Issue**:
Sending a WhatsApp template with 10 or more variables can assign values to the wrong placeholders when the body contains mixed variable types, such as free text, field, or user name variables.
Templates containing only free-text variables are not affected.

**Reason**:
Meta consumes template parameters positionally, but for mixed variable types, Odoo built the parameter list using the template variable recordset order.
That order can differ from the numeric placeholder order, notably placing {{10}}, {{11}}, {{12}}... before {{1}}
when sending the message, as the payload parameters are not ordered by their numeric placeholder index.

**Fix:**
Sort body variables by their numeric placeholder index before preparing the Meta payload.

Task-6401501

Forward-Port-Of: odoo/enterprise#125671

#whatsapp#templates#messaging

Context: when a user re-authenticate a shop, they might use different shopee.account (API key). Currently Odoo will not change the shopee.account when they re-auth with another shopee.account. Enable a shopee.shop switches to another shopee.account when we run `create_or_update_shop` function. Forward-Port-Of: odoo/enterprise#92446

We are missing a SchmeNm node in the InitgPty node. This is mandatory for Nordea in Sweden at least. Such as: ```xml <SchmeNm> <Cd>CUST</Cd> </SchmeNm> ``` task-6385960 Forward-Port-Of: odoo/enterprise#124693

**Issue**: Sending a WhatsApp template with 10 or more variables can assign values to the wrong placeholders when the body contains mixed variable types, such as free text, field, or user name variables. Templates containing only free-text variables are not affected. **Reason**: Meta consumes template parameters positionally, but for mixed variable types, Odoo built the parameter list using the template variable recordset order. That order can differ from the numeric placeholder order, notably placing {{10}}, {{11}}, {{12}}... before {{1}} when sending the message, as the payload parameters are not ordered by their numeric placeholder index. **Fix:** Sort body variables by their numeric placeholder index before preparing the Meta payload. Task-6401501 Forward-Port-Of: odoo/enterprise#125671