Odoo Changelog — 2026-02-20

Friday, February 20, 2026

6 changes · saas-18.2

Bug Fixes(5)

Resolved issues and error corrections

[FIX] point_of_sale: correct POS receipt tax label after fiscal position

Coresaas-18.2point_of_sale

POS receipts now show the correct tax label when a fiscal position changes the tax rate, such as replacing 21% with 6%. This helps restaurant staff and customers see receipt details that match the actual taxes applied.

Original PR description

Steps:

- Install l10n_be_pos_restaurant.
- Create a restaurant POS configuration with presets.
- Assign a fiscal position to one preset that replaces 21% tax with 6%.
- Open a POS session and process an order using that preset.

Issue:

- The POS receipt still displays the 21% tax's tax group label, even though the 6% tax is correctly applied.

Cause:

- Fiscal position was not taken into account when computing the tax group label for POS receipt orderlines.

Fix:

- Apply the fiscal position when determining the POS receipt tax group label.

Task-5899938

#pos#receipts#taxes#fiscal-position

[FIX] delivery, website_sale_collect: fix case formatting in pick-up

PR #249575

Coresaas-18.2deliverywebsite_sale_collect

Pickup point names and addresses now keep their original casing, while weekday labels are consistently capitalized across languages. This improves the click-and-collect display for shoppers using localized websites, especially Dutch.

Original PR description

Issue:
---
In pick-up point list, the case formatting should be:
1- Pick-up point's `name`, `street` and `city` should not be auto-capitalized.
2- Weekdays should must be always capitalized regardless of language.

Steps to reproduce:
---
1- Create a second Company named `store`.
2- Create a wh for the created company and add the wh to click-and-collect pick-up points. (There should be more than 1 pick-up points)
3- In the website, add Dutch lang.
4- In website, open a product and, open the `Click and Collect`.

Outcome:
---
Name is capitalized to `Store` and the days are not capitalized if you switch to dutch lang.

Cause:
---
Due to CLDR, luxon doesn't capitalize weekdays in some languages.

opw-5941830

Forward-Port-Of: odoo/odoo#249078

#pickup#click-and-collect#localization#formatting

[FIX] barcodes_gs1_nomenclature: prevent traceback on barcode rule form

PR #249576

Coresaas-18.2barcodes_gs1_nomenclature

Opening an expanded barcode rule form no longer triggers an error when no parent barcode nomenclature context is available. This keeps barcode configuration workflows stable for inventory users managing barcode rules.

Original PR description

Issue before this commit: ========================= When opening a Barcode Rule form view, a traceback was raised due to the following python expression: bool(parent.is_gs1_nomenclature or type ==…

Issue before this commit:
=========================
When opening a Barcode Rule form view, a traceback was raised due to the following
python expression: bool(parent.is_gs1_nomenclature or type == 'alias')

Steps to Reproduce:
=========================
- Install the stock module.
- Go to Configuration → Barcode Nomenclatures in the Stock app.
- Open any Barcode Nomenclature form.
- Go to the Rules tab and open a rule (pop-up form view).
- Click on the Expand button.
- A traceback is raised.

Cause of the issue:
=========================
The form view tries to evaluate `parent.is_gs1_nomenclature`, but the `parent` record
is not defined when the rule form view is opened directly (via expand), leading to a traceback.

This happens because the form view is not defined as a child of any parent view,
so no parent context is available, which leads to a traceback.

With This Commit:
=========================
Removed the usage of `parent.is_gs1_nomenclature` and use `is_gs1_nomenclature`
directly instead. The `is_gs1_nomenclature` field on `barcode.rule` is already a
related field to `barcode.nomenclature`, so it can be safely used without relying on the parent.

opw-5949083

Forward-Port-Of: odoo/odoo#249293

[FIX] l10n_co_reports: enable search and include all entries in Daily Journal

PR #107991

Enterprisesaas-18.2l10n_co_reports

This update fixes a bug preventing users from searching the Colombian Daily Journal (Libro Diario) effectively. The issue was caused by missing data in the journal entries, which blocked the search function. Now, all journal entries are searchable by move, partner, account, and label.

Original PR description

Steps to reproduce:
1. Open the Colombian Daily Journal (Libro Diario).
2. Type a move name or partner in the search bar.
3. Observe that no results are returned.

Cause:
Report lines were generated with an empty 'name' attribute. The accounting 
report framework uses this field for client-side filtering. Empty names 
make the search bar non-functional.

Solution:
Populate the 'name' field with move, partner, account, and label data. 
This enables the frontend search bar to match against these strings.

opw-5495558

Forward-Port-Of: odoo/enterprise#106179

#reporting#Colombia#search

[FIX] stock_barcode: fix for javascript rounding issue in some condition

PR #107933

Enterprisesaas-18.2stock

This update resolves a rounding issue that occasionally occurred when scanning stock barcodes during delivery order processing. Specifically, the system was incorrectly rounding stock quantities, leading to discrepancies in the recorded stock levels. This fix ensures more accurate stock tracking and reduces potential errors in order fulfillment.

Original PR description

To reproduce the issue:
- Create a stock quantity of product1 for example of 275.84 kg in PACK1
- Create a delivery order of 3.6 kg
- Go to the delivery order on stock barcode
- Scan PACK1
- The new line is created as 272.2399999999

Forward-Port-Of: odoo/enterprise#89300

#stock#barcode#rounding#delivery

Other(1)

Miscellaneous changes

[FW][FIX] point_of_sale: prevent double confirmation of dialog

PR #212426

Coresaas-18.2point_of_sale

Original PR description

For the `TextInputPopup` component a feature was introduced in 2f5c5c15644412cfb6493c661b2f1b927c8cc7e2 that allows the user to confirm the popup by simply clicking enter.

The problem is that the dialog itself has a hotkey on "CTRL+Enter" that will also confirm the popup.

This means that if a user uses the "CTRL+Enter" hotkey, the popup will be confirmed twice.

Steps to reproduce:
1. In restaurant, click the button to add a new floor
2. Write a name for the floor
3. Click "CTRL+Enter"
4. Observe that 2 floors with the given name were created instead of one.

The fix:
We stop the propagation of the event

Task: 4698289



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

Forward-Port-Of: odoo/odoo#212134

Steps: - Install l10n_be_pos_restaurant. - Create a restaurant POS configuration with presets. - Assign a fiscal position to one preset that replaces 21% tax with 6%. - Open a POS session and process an order using that preset. Issue: - The POS receipt still displays the 21% tax's tax group label, even though the 6% tax is correctly applied. Cause: - Fiscal position was not taken into account when computing the tax group label for POS receipt orderlines. Fix: - Apply the fiscal position when determining the POS receipt tax group label. Task-5899938

Issue: --- In pick-up point list, the case formatting should be: 1- Pick-up point's `name`, `street` and `city` should not be auto-capitalized. 2- Weekdays should must be always capitalized regardless of language. Steps to reproduce: --- 1- Create a second Company named `store`. 2- Create a wh for the created company and add the wh to click-and-collect pick-up points. (There should be more than 1 pick-up points) 3- In the website, add Dutch lang. 4- In website, open a product and, open the `Click and Collect`. Outcome: --- Name is capitalized to `Store` and the days are not capitalized if you switch to dutch lang. Cause: --- Due to CLDR, luxon doesn't capitalize weekdays in some languages. opw-5941830 Forward-Port-Of: odoo/odoo#249078

Issue before this commit: ========================= When opening a Barcode Rule form view, a traceback was raised due to the following python expression: bool(parent.is_gs1_nomenclature or type == 'alias') Steps to Reproduce: ========================= - Install the stock module. - Go to Configuration → Barcode Nomenclatures in the Stock app. - Open any Barcode Nomenclature form. - Go to the Rules tab and open a rule (pop-up form view). - Click on the Expand button. - A traceback is raised. Cause of the issue: ========================= The form view tries to evaluate `parent.is_gs1_nomenclature`, but the `parent` record is not defined when the rule form view is opened directly (via expand), leading to a traceback. This happens because the form view is not defined as a child of any parent view, so no parent context is available, which leads to a traceback. With This Commit: ========================= Removed the usage of `parent.is_gs1_nomenclature` and use `is_gs1_nomenclature` directly instead. The `is_gs1_nomenclature` field on `barcode.rule` is already a related field to `barcode.nomenclature`, so it can be safely used without relying on the parent. opw-5949083 Forward-Port-Of: odoo/odoo#249293

Steps to reproduce: 1. Open the Colombian Daily Journal (Libro Diario). 2. Type a move name or partner in the search bar. 3. Observe that no results are returned. Cause: Report lines were generated with an empty 'name' attribute. The accounting report framework uses this field for client-side filtering. Empty names make the search bar non-functional. Solution: Populate the 'name' field with move, partner, account, and label data. This enables the frontend search bar to match against these strings. opw-5495558 Forward-Port-Of: odoo/enterprise#106179

To reproduce the issue: - Create a stock quantity of product1 for example of 275.84 kg in PACK1 - Create a delivery order of 3.6 kg - Go to the delivery order on stock barcode - Scan PACK1 - The new line is created as 272.2399999999 Forward-Port-Of: odoo/enterprise#89300

For the `TextInputPopup` component a feature was introduced in 2f5c5c15644412cfb6493c661b2f1b927c8cc7e2 that allows the user to confirm the popup by simply clicking enter. The problem is that the dialog itself has a hotkey on "CTRL+Enter" that will also confirm the popup. This means that if a user uses the "CTRL+Enter" hotkey, the popup will be confirmed twice. Steps to reproduce: 1. In restaurant, click the button to add a new floor 2. Write a name for the floor 3. Click "CTRL+Enter" 4. Observe that 2 floors with the given name were created instead of one. The fix: We stop the propagation of the event Task: 4698289 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#212134