Odoo Changelog — 2026-02-11

Wednesday, February 11, 2026

3 changes · saas-18.4

Improvements(3)

Enhancements to existing features

[IMP] account_edi_ubl_cii: Prevent BIS3 without EndpointID to be send

Coresaas-18.4account_edi_ubl_ciiaccount_peppoll10n_account_edi_ubl_cii_testsl10n_my_ubl_pintl10n_sg_ubl_pintMedium

Odoo now checks that both buyer and seller electronic addresses are configured before sending BIS3 e-invoices. This prevents invalid files from being submitted and immediately rejected, helping users catch setup issues earlier.

Original PR description

If EndpointID is not set, the generated file is invalid due to the 2 following rules:
[PEPPOL-EN16931-R010] Buyer electronic address MUST be provided. [PEPPOL-EN16931-R020] Seller electronic address MUST be provided.

Since this is a configuration issue, there is no point of sending such files to be rejected right away. Instead, let's add those 2 contraints ODOO-side.

task-5890887

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

Forward-Port-Of: odoo/odoo#247857
Forward-Port-Of: odoo/odoo#246961

#e-invoicing#PEPPOL#BIS3#validation

[IMP] html_editor: Blocking browser plugin translation on editable content.

PR #248078

Coresaas-18.4html_editorMedium

Editable content in the HTML editor is now marked so browser translation plugins leave it unchanged. This helps prevent translated text from being accidentally saved over original content during auto-save.

Original PR description

Browser translation plugins were altering editable content by replacing the
original content with translated versions, which caused issues when paired 
with auto-save. To prevent this behavior, the attribute `translate="no"` has 
been added to editable fields.

task-5485078

Forward-Port-Of: odoo/odoo#247827

#html editor#translation#auto-save

[IMP] partner_autocomplete,iap_mail: company info in chatter

PR #246049

Coresaas-18.4iap_mailpartner_autocompleteMedium

Company enrichment data from Dun & Bradstreet is now shown in a dedicated company information card in the chatter instead of being mixed into general partner tags. This makes company context easier to review while keeping partner tags cleaner and more relevant.

Original PR description

Before:
 Industry tags coming from DnB were stored in the Tags section of res.partner.
 and there was no Company info card in chatter.
After:
Industry tags coming from DnB are not stored in the Tags section of res.partner. Company card is created in chatter that is having details from Dnb along with tags.

task-5373200

Forward-Port-Of: odoo/odoo#239464

#company-info#chatter#partner-autocomplete#data-enrichment

If EndpointID is not set, the generated file is invalid due to the 2 following rules: [PEPPOL-EN16931-R010] Buyer electronic address MUST be provided. [PEPPOL-EN16931-R020] Seller electronic address MUST be provided. Since this is a configuration issue, there is no point of sending such files to be rejected right away. Instead, let's add those 2 contraints ODOO-side. task-5890887 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#247857 Forward-Port-Of: odoo/odoo#246961

Browser translation plugins were altering editable content by replacing the original content with translated versions, which caused issues when paired with auto-save. To prevent this behavior, the attribute `translate="no"` has been added to editable fields. task-5485078 Forward-Port-Of: odoo/odoo#247827

Before: Industry tags coming from DnB were stored in the Tags section of res.partner. and there was no Company info card in chatter. After: Industry tags coming from DnB are not stored in the Tags section of res.partner. Company card is created in chatter that is having details from Dnb along with tags. task-5373200 Forward-Port-Of: odoo/odoo#239464