Monday, April 20, 2026
8 changes · saas-18.3
Resolved issues and error corrections
This update adds the product unit of measure to the information sent to ECPay, making invoice lines easier to understand. As a result, printed documents now show the unit description alongside each item, reducing confusion for customers and accounting teams.
Original PR description
Issue: -- The documents returned by the ECpay API can be confusing as it does not include the measurement (UOM). The make it clearer a description is provided to ECpay through the json with the Key "ItemRemark" Current behavior: -- displayed data in PDF 品名 數量 單價 金額 備註 test 1 5 5 Expected behavior: -- displayed data in PDF 品名 數量 單價 金額 備註 test 1 5 5 商品單位: Units opw-6070269 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#259536
There were some translation overrides for `fr_BE` and `fr_CA` that were incorrect or unnecessary. We are deleting these files so they use the correct translations in `fr` instead. In the `nl_BE` translation, we are fixing a menu item so it is shorter, but still correct. task-5921458 Forward-Port-Of: odoo/enterprise#114069 Forward-Port-Of: odoo/enterprise#106998
Original PR description
There were some translation overrides for `fr_BE` and `fr_CA` that were incorrect or unnecessary. We are deleting these files so they use the correct translations in `fr` instead. In the `nl_BE` translation, we are fixing a menu item so it is shorter, but still correct. task-5921458 Forward-Port-Of: odoo/enterprise#114069 Forward-Port-Of: odoo/enterprise#106998
The Reference field in Inventory move history is now read-only, so users no longer see a field they can edit when changes would not actually be saved. This removes confusion and makes the screen behave consistently with the system's behavior.
Original PR description
### Issue before this commit: Before this commit, the Reference field displayed on stock.move.line was editable in the user interface, even if the modification made by the user was not persisted.…
### Issue before this commit: Before this commit, the Reference field displayed on stock.move.line was editable in the user interface, even if the modification made by the user was not persisted. After saving and reloading the Move History view, the original value was restored. ### Steps to reproduce the issue: 1. Go to Move history in Inventory app 2. Try to change the name of a line and save 3. If you go back to the Move history you can see that the name is not changed ### Cause of the issue: The issue was caused by a mismatch between the stock.move.line.reference field and its target field stock.move.reference. The field on stock.move.line is a related field that appears editable (readonly=False), but the underlying stock.move.reference field was not writable. As a result, user could edit the field but the modifications were ignored, preventing changes from being effectively saved. ### Reason to introduce the fix: The fix ensures that the reference field in stock.move and in stock.move.line are readonly. opw-6055708 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#256434
This change corrects a test barcode format used by the point of sale barcode scanning checks. It ensures the scanned product is recognized properly during the test, preventing false failures in the POS test suite.
Original PR description
The test_GS1_pos_barcodes_scan was failing because the "GS1 Variant Product" barcode was defined as a 13-digit string, while the tour scans it using the GS1 AI 01 (GTIN), which expects a 14-digit GTIN-14. By adding a leading zero to the barcode in the test setup, we align it with the GTIN-14 format parsed by the POS barcode parser during the scan, ensuring the product is correctly added to the order. runbot-error: 242323 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#258089
The self-ordering system now sends only the fields the frontend actually needs. This reduces unnecessary data transfer and helps keep the client-side payload simpler and more efficient.
Original PR description
Fix _generate_return_values to remove some fields that are not needed on the frontend Forward-Port-Of: odoo/odoo#259915
This update fixes an automated POS loyalty test that was failing because a customer list in a popup could scroll indefinitely. It helps keep the loyalty feature’s checks reliable so future updates can be validated more safely.
Original PR description
fw-port fails because of infinite scroll in pop modal .modal .partner-list Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#218604
When an invoice is sent through Indian E-Invoicing, the IRN number is now saved directly on the invoice record as soon as the response is received. This means users can see the same information in both the PDF and the invoice form, improving consistency and making invoice tracking easier.
Original PR description
**Steps to reproduce:** * Install module *Indian E-Invoicing (l10n_in_edi)*. * Configure *Indian integration* with required credentials (E-Invoicing, E-Way bill, etc.). * Save the settings. * Create a *customer invoice*. * Post the invoice. * Send the invoice through *E-Invoicing (EDI)*. * Open the generated *Invoice PDF* and the *form view*. **Observed behavior:** * The *IRN number* is correctly present in the *Invoice PDF*. * However, it is *not saved/displayed* in the invoice form view. **Cause:** * No specific condition existed in the invoice flow to store the *IRN number* in the corresponding field, even though the value was available in the EDI response. **Fix:** * Update *_get_l10n_in_edi_response_json* to store the IRN number directly on the invoice when the response is received. * This ensures the value is saved without impacting the existing EDI flow. opw-6097923
This change updates the classification of the 12% tax entry used in the Philippine localization from “Capital 12%” to “VAT 12%”. It helps ensure the sales report uses the correct tax grouping, reducing confusion and improving reporting accuracy.
Original PR description
In this commit: - We change the group of tax '12% I', from 'Capital 12%' to 'VAT 12%' task-6092566 Forward-Port-Of: odoo/odoo#259145