Odoo Changelog — 2025-04-11

Friday, April 11, 2025

3 changes · saas-18.1

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_it_stock_ddt: compute price for product with packaging

PR #204586

Coresaas-18.1l10n_it_stock_ddtMedium

Delivery slips in the Italian transport document module now calculate prices correctly when products are sold in packages. This prevents overstated prices on printed delivery documents, helping customers and staff see accurate totals.

Original PR description

### Steps to reproduce:

- Install  l10n_it_stock_ddt and enable product packaging.
- Create a storable product with a sale price of 1 and that can be packed by pack of 6.
- Create and confirm an SO for 1 pack of 6.
- Validate the delivery for 6 units.
- Print the DO.
#### > The price correspond to the price of 6 pack of 6.

### Cause of the issue:

The `packaging` and product `uom` have been merged in 18.1. As such, the quantity used in the report template needs to be recomputed based on the uom conversion:
https://github.com/odoo/odoo/blob/195e3fb3fbba355e40f55f4ef88ea9ae52545908/addons/l10n_it_stock_ddt/report/l10n_it_ddt_report.xml#L130-L131

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

#delivery slips#packaging#pricing#Italy

[FIX] barcodes_gs1_nomenclature,product: skip GS1 preprocessing when not needed

PR #196438

Coresaas-18.1barcodes_gs1_nomenclatureproductMedium

Users can now save product records after removing a barcode when GS1 barcode rules are enabled. This prevents an error that interrupted normal product updates in Inventory.

Original PR description

Currently, an exception is generated when a user tries to save a product record without a barcode, whether it is a newly created record or an existing one. Steps to reproduce: 1. Install the…

Currently, an exception is generated when a user tries to save a product record without a barcode, whether it is a newly created record or an existing one.

Steps to reproduce:

1. Install the Inventory module.
2. Go to Inventory settings.
3. Set Barcode Nomenclature to Default GS1 Nomenclature.
4.  Go to Inventory -> Products, create a product with a barcode, and save it.
5. Edit the same product, remove the barcode, and save it again.
6. An error occurs.

Error: `StopIteration`

This issue [1] occurs because when a user tries to save the record without a barcode, the value is false, and an false value is not iterable.

[1] - https://github.com/odoo/odoo/blob/9eb6c16cd7d4fe9364d043e2af96876bf82a44d4/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L163

This fix resolves an issue where GS1 preprocessing was always applied when checking for duplicate product barcodes. By introducing the skip_preprocess_gs1 context flag, the GS1 preprocessing step is now bypassed when verifying barcode uniqueness.

Related Enterprise PR:- https://github.com/odoo/enterprise/pull/80544

sentry-6267124218

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

[FIX] stock_barcode: add test for GS1 barcode addition & removal

PR #80544

Enterprisesaas-18.1stock_barcodeMedium

Products can now be saved after their barcode is removed when GS1 barcode rules are enabled. This prevents an unexpected error in Inventory and helps users manage product records without interruption.

Original PR description

Currently, an exception is generated when a user tries to save a product record without a barcode, whether it is a newly created record or an existing one. Steps to reproduce: 1. Install the…

Currently, an exception is generated when a user tries to save a product record without a barcode, whether it is a newly created record or an existing one.

Steps to reproduce:

1. Install the Inventory module.
2. Go to Inventory settings.
3. Set Barcode Nomenclature to Default GS1 Nomenclature.
4.  Go to Inventory -> Products, create a product with a barcode, and save it.
5. Edit the same product, remove the barcode, and save it again.
6. An error occurs.

Error: `StopIteration`

This issue [1] occurs because when a user tries to save the record without a barcode, the value is false, and an false value is not iterable.

[1] - https://github.com/odoo/odoo/blob/9eb6c16cd7d4fe9364d043e2af96876bf82a44d4/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L163

This fix resolves an issue where GS1 preprocessing was always applied when checking for duplicate product barcodes. By introducing the skip_preprocess_gs1 context flag, the GS1 preprocessing step is now bypassed when verifying barcode uniqueness.

Related Community PR:- https://github.com/odoo/odoo/pull/196438

sentry-6267124218

### Steps to reproduce: - Install l10n_it_stock_ddt and enable product packaging. - Create a storable product with a sale price of 1 and that can be packed by pack of 6. - Create and confirm an SO for 1 pack of 6. - Validate the delivery for 6 units. - Print the DO. #### > The price correspond to the price of 6 pack of 6. ### Cause of the issue: The `packaging` and product `uom` have been merged in 18.1. As such, the quantity used in the report template needs to be recomputed based on the uom conversion: https://github.com/odoo/odoo/blob/195e3fb3fbba355e40f55f4ef88ea9ae52545908/addons/l10n_it_stock_ddt/report/l10n_it_ddt_report.xml#L130-L131 opw-4683247 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Currently, an exception is generated when a user tries to save a product record without a barcode, whether it is a newly created record or an existing one. Steps to reproduce: 1. Install the Inventory module. 2. Go to Inventory settings. 3. Set Barcode Nomenclature to Default GS1 Nomenclature. 4. Go to Inventory -> Products, create a product with a barcode, and save it. 5. Edit the same product, remove the barcode, and save it again. 6. An error occurs. Error: `StopIteration` This issue [1] occurs because when a user tries to save the record without a barcode, the value is false, and an false value is not iterable. [1] - https://github.com/odoo/odoo/blob/9eb6c16cd7d4fe9364d043e2af96876bf82a44d4/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L163 This fix resolves an issue where GS1 preprocessing was always applied when checking for duplicate product barcodes. By introducing the skip_preprocess_gs1 context flag, the GS1 preprocessing step is now bypassed when verifying barcode uniqueness. Related Enterprise PR:- https://github.com/odoo/enterprise/pull/80544 sentry-6267124218 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Currently, an exception is generated when a user tries to save a product record without a barcode, whether it is a newly created record or an existing one. Steps to reproduce: 1. Install the Inventory module. 2. Go to Inventory settings. 3. Set Barcode Nomenclature to Default GS1 Nomenclature. 4. Go to Inventory -> Products, create a product with a barcode, and save it. 5. Edit the same product, remove the barcode, and save it again. 6. An error occurs. Error: `StopIteration` This issue [1] occurs because when a user tries to save the record without a barcode, the value is false, and an false value is not iterable. [1] - https://github.com/odoo/odoo/blob/9eb6c16cd7d4fe9364d043e2af96876bf82a44d4/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L163 This fix resolves an issue where GS1 preprocessing was always applied when checking for duplicate product barcodes. By introducing the skip_preprocess_gs1 context flag, the GS1 preprocessing step is now bypassed when verifying barcode uniqueness. Related Community PR:- https://github.com/odoo/odoo/pull/196438 sentry-6267124218