Daily updates from Odoo
Thursday, January 8, 2026
4 changes · 17.0
Enhancements to existing features
This update allows system administrators to customize the main Odoo home menu with a targeted message. Administrators can configure a new setting to display important information, such as planned maintenance, directly on the home screen. This provides a centralized way to communicate critical updates to users.
Original PR description
Display a message on home menu based on an ir.config_parameter that can be added directly in the database by the system administrator.
The ir.config_parameter is sysadmin.message and should be a json loadable. The format shoud be something like this:
{
"type": "warning",
"replace": false,
"warning_type": "user",
"message": "`<span>A maintenance operation is planned on your server on <strong>2026-01-15</strong> between 14h and 15h</span>`"
}
Forward-Port-Of: odoo/enterprise#102239Resolved issues and error corrections
This update fixes an issue where GS1 barcodes weren't accurately reflecting the quantity of products in manufacturing orders. Previously, the system only added one unit regardless of the barcode's quantity. Now, the system correctly uses the barcode's quantity to update the finished product's output, ensuring consistency and accurate tracking of materials.
Original PR description
Description of the issue/feature this PR addresses: The quantity of GS1 barcodes was not taken into account when scanning the final product of a manufacturing order. More details of this issue can be found in https://www.odoo.com/odoo/project.task/4817418 Current behavior before PR: When scanning a GS1 barcode with a quantity defined (e.g. 0120250524135700310210000010LOT887766 ) as the final product of a manufacturing order, the quantity is not taken into account in the call to produceQty(), so the line will have a qty_done of 0 regardless of the quantity specified in the barcode Desired behavior after PR is merged: The qty_done of the final product line should be the one specified in the barcode, in order to make the behaviour consistent with other usages of GS1 barcodes.
This update fixes a recent issue where stock quantities were not displayed correctly. The change removes a restriction introduced in the latest version that limited quantity visibility to sublocations, restoring full product quantity transparency. This ensures users have a clearer view of their stock levels.
Original PR description
In order to fix an issue with stock move line's quants not correctly recomputed, the PR odoo/enterprise#95906 backported a part of 18.2 PR odoo/enterprise#55917. The issue is, this PR also backported unwanted changes, like the restriction of displayed quants. Starting with the 18.2, the displayed quants are restricted to the current operation's sublocations because in this version, clicking on a quant updates the move line's fields. This feature doesn't exist prior to the 18.2 and so, the restriction is not needed. This commit removes this part of the field's compute so users have better visibility of where are their quants. Backport of b366ed214d1eb833016376e57f7bcb8f3b281997 opw-5269614
This update corrects a bug where the simplified invoice limit in VeriFactu POS was consistently set to 400, regardless of user configuration. The fix ensures the system respects the user-defined limit, improving POS order processing and accuracy. This resolves a previous inconsistency and enhances the VeriFactu POS experience.
Original PR description
We had a bug whith simplified invoice limit when verifactu and pos_es were installed. The limit was always 400 no matter how it was set in the settings. Steps to reproduce: ------------------- * Install l10n_es_edi_verifactu_pos (with or without l10n_es_pos) * Enable VeriFactu * Set a simplified invoice limit different from 400 * Create a POS order above the configured limit * Validate without invoicing > Observation: we had the error message saying it's above 400. Why the fix: ------------ To respect configuration, keep behavior consistent when l10n_es_pos is uninstalled. Error message and test are now resilient to limit and not hard-coded. opw-5351516