Daily updates from Odoo
Wednesday, February 4, 2026
11 changes
3 changes
Enhancements to existing features
This update ensures that the top bar with embedded actions is visible by default when a new audit working file is created and opened for the first time. While user preferences can still control this visibility later, this change provides a better initial experience for users. This improves usability and efficiency within the audit process.
Original PR description
Currently, the top bar (embedded actions) in Working Files in audit is not visible by default when the user creates and opens it for the first time. This commit makes it visible when the Audit is created and opened for the first time, later on the visibility is decided as per the user preferences set in the `res.users.settings.embedded.action` model. task-5388717 Forward-Port-Of: odoo/enterprise#101924
This update significantly improves the speed of database synchronization for our SaaS customers. By intelligently grouping and processing database requests in parallel, we've reduced synchronization times from 50 seconds to just 15 seconds. This translates to a more responsive and efficient system for our users.
Original PR description
With this commit, the requests sent to retrieve the information from the databases are grouped by IP, and each group is treated in parallel using a ThreadPoolExecutor, which uses a pool of 5 times the number of CPUs. On a set of SaaS databases, we reduced the time needed to synchronize 30 databases from 50s to 15s. Forward-Port-Of: odoo/enterprise#105673
This update ensures Odoo complies with Mexican tax regulations (SAT) regarding the descriptions of refunded products. Specifically, for global invoices, refund descriptions now include the return amount, discounts, or bonuses, as required by the SAT. This change simplifies reporting and reduces the risk of compliance issues.
Original PR description
The SAT specifies how the description of refunded product should be set and specifically for refunds of global invoices it should contain the amount of the return, discount or bonus and why. Currently, Odoo when a credit note of a global invoice is issued, it sets an specific label for the description. To keep with what SAT asks for, we will keep that label only for credit notes of pos global invoices, and for the others, we keep from what the user put as an input on the line task-5170675 target: 19.0 -> master Forward-Port-Of: odoo/enterprise#97681
1 change
Enhancements to existing features
This update enables IoT devices connected to our Point of Sale system to function correctly without requiring a secure HTTPS certificate. A new setting allows requests to use HTTP instead, simplifying the connection process for IoT boxes. This improves reliability and reduces setup complexity.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/246781 This is a backport of odoo/enterprise#100331. Since odoo/odoo#235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate. This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate. task-5353672 Forward-Port-Of: odoo/enterprise#106183
4 changes
Enhancements to existing features
This update ensures that sales exceeding USD 50 for 'Consumidor Final' customers in Odoo's Ecuador POS comply with local regulations. It prevents users from finalizing transactions above the legal limit, forcing them to select the correct customer and avoid potential issues with tax reporting (SRI).
Original PR description
PURPOSE - Enforce SRI rules for unidentified consumer invoicing in Ecuador - POS users in Ecuador cannot finalize a sale above the legally allowed limit (currently USD 50) using the default “Consumidor Final” customer with 'RUC' identification type and '9999999999999' VAT - When the sale exceeds the threshold, the PoS must force the user to select the real customer. TECHNICAL DETAILS - A new monetary field 'Final Consumer Max Amount' has been added in pos.config, which can be set from the POS Settings. - In POS, on the order payment validation page, added one more validation. In which if the total price is greater than the amount set in the 'Final- Consumer Max Amount' field in the res settings, and if the order is for a 'Consumidor Final' and if the to_invoice is True, then block the user from validating the payment by showing a relevant alert. Related Com PR: https://github.com/odoo/odoo/pull/237498 Task-5266304
This update enhances product BOM tracking by including the BOM version within the 'Used In' list, mirroring changes made in the community version. This provides better visibility and simplifies tracking of product components across different BOM versions.
Original PR description
To support the updated "Used In" list of BoMs for a product in community, we now also include the BoM version for easier tracking. Task: 4788617 Related: https://github.com/odoo/odoo/pull/212727
This update makes the top bar with embedded actions visible by default when a new audit file is created and opened for the first time. While user preferences can still control visibility later, this change provides a more intuitive starting experience for users working with audit files. This improves usability and efficiency.
Original PR description
Currently, the top bar (embedded actions) in Working Files in audit is not visible by default when the user creates and opens it for the first time. This commit makes it visible when the Audit is created and opened for the first time, later on the visibility is decided as per the user preferences set in the `res.users.settings.embedded.action` model. task-5388717 Forward-Port-Of: odoo/enterprise#101924
This update improves sales forecasting by displaying Monthly Recurring Revenue (MRR) within sales quotations. Previously, only recurring and non-recurring amounts were shown, making it difficult to accurately predict revenue targets. The MRR is now prominently displayed below the quotation totals, streamlining the sales process.
Original PR description
As a salesperson, I need to easily see the Monthly Recurring Revenue (MRR) of a subscription in the quotation so that I can forecast targets in the commission module. Currently, only the recurring and non-recurring amounts are shown, but the MRR is not displayed. The MRR is now shown below the totals in the quotation form. If the MRR is equal to the recurring amount, the recurring amount is hidden to avoid duplication. task-5436781
2 changes
Enhancements to existing features
This update ensures Odoo complies with Mexican tax regulations (SAT) regarding the description of refunded products. Specifically, for global invoices, the refund description now includes the return amount, discounts, or bonuses, as required by the SAT. The change adjusts how Odoo handles credit notes to align with these requirements.
Original PR description
The SAT specifies how the description of refunded product should be set and specifically for refunds of global invoices it should contain the amount of the return, discount or bonus and why. Currently, Odoo when a credit note of a global invoice is issued, it sets an specific label for the description. To keep with what SAT asks for, we will keep that label only for credit notes of pos global invoices, and for the others, we keep from what the user put as an input on the line task-5170675 target: 19.0 -> master
This update simplifies the one-time payment form by removing a redundant version field. The form now automatically displays payments for the correct employee based on the context, ensuring accuracy and streamlining the process. This change improves usability and avoids potential errors.
Original PR description
… payment form The one time payment view is accessed only via the smart button on the employee form for a specific version. This view displays only that employee's one time payments for the selected version. Since the version is provided by the context and creating a payment for a different employee or version would not make sense, the version field is made invisible. Task: 5384437
1 change
Enhancements to existing features
This update adjusts a test case within the l10n_pe_edi module to reflect a recent change in how debit notes are processed through Peppol. This ensures the test case accurately validates the system's functionality after the Peppol update. The change was necessary to accommodate the addition of a new node during debit note creation.
Original PR description
A Node was added when creating debit notes in peppol, so the change was also applied to the debit note template to adjust a test case task-5875689