Wednesday, December 3, 2025
22 changes · 19.0
Enhancements to existing features
This update ensures that invoices for B2G transactions in Germany comply with local regulations. It adds a mandatory 'Leitweg-ID' to the UBL invoice format, correctly directing invoices to the appropriate government entity. This improves compliance and accuracy for German accounting processes.
Original PR description
*= l10n_account_edi_ubl_cii_tests For B2G transactions in Germany, the Leitweg-ID is a mandatory routing identifier to direct the invoice to the correct public entity. Adding this Leitweg-ID for the UBL syntax. task-5194484 Description of the issue/feature this PR addresses: For electronic invoicing in Germany, for B2G transactions, the Leitweg-ID is a mandatory routing identifier to direct the invoice to the correct public entity. We want to add this identifier for the XRechnung format. Current behavior before PR: The Leitweg-ID is not present in the UBL xml format. Desired behavior after PR is merged: The Leitweg-ID is added in the header of the invoice in the cbc:BuyerReference tag. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238255 Forward-Port-Of: odoo/odoo#236333
This update enhances the Odoo call menu by adding mute and deafen controls, improving the user experience for calls. The visual design of the call menu has also been updated for a cleaner and more modern look. This change provides a more intuitive and effective way to manage calls within Odoo.
Original PR description
Currently, there is no way that we can deafen or mute in call menu directly. This commit adds mute and deafen button in call menu for better user experience. Also, adjust the call menu UI for better visual effect. task-5262772 before: <img width="260" height="51" alt="image" src="https://github.com/user-attachments/assets/206b3b3d-cafa-492f-95ed-db8075f16298" /> after:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the user experience by providing clearer placeholders for Peppol identifiers and automatically verifying this information when key partner data changes. A new feature has been added specifically for Belgium, leveraging the VAT number to automatically populate the Peppol identifier through the company registry endpoint, streamlining data entry and validation.
Original PR description
This commit improves the UX by displaying more intuitive placeholders for the peppol identifier. The peppol information is also automatically verified when important data changes. It also adds a special case for Belgium in which we try to use the vat number as the peppol identifier with the company registry endpoint. task: 5172378 Forward-Port-Of: odoo/odoo#238251 Forward-Port-Of: odoo/odoo#233160
Resolved issues and error corrections
This update resolves an issue where duplicate account IDs were causing data overwrites. The changes now correctly segregate accounts for CPF, SHG, and SDL tax calculations according to Singapore's latest tax regulations. The fix also simplifies account code formatting to prevent excessively long account numbers.
Original PR description
Two accounts were using the same XML ID `account_account_864`, causing second definition to overwrite the first. This commit resolves the duplication and updates/segregates accounts for CPF and SHG according to new specifications.
Changes:
- Update `account_account_864` (Employee Expense) to `account_account_866`.
- Update in accounts:
* 862 → CPF Withheld (Employee)
* 863 → CPF Accrued (Employer)
* 864 → SHG Withheld (Employee)
* Add new 865 → SDL Accrued (Employer)
* 859 → CPF Employer Expense
* 860 → SDL Employer Expense
* Removed 861
- Fix `transfer_account_code_prefix` in the template:
* Change from `101100` to `10110` to avoid generating 7-digit account codes.
task-5360160
Forward-Port-Of: odoo/odoo#238264
Forward-Port-Of: odoo/odoo#237506This update enhances the reliability of our point-of-sale (POS) certification process by automatically retrying failed payments due to server unavailability. Specifically, it addresses errors from the FISKAL system (TSS) and ensures tills remain operational even when the system is temporarily unreachable, improving transaction success rates.
Original PR description
In this task: --------------- - Moved the status code handling logic at proper place for all transactions API responses. - Removed the mixed usage of async/await and .then() by async/await totally in all transaction calls to simplify flow and improve readability. - For 5xx errors (e.g., 503), retry once as they occur when the server is unreachable. Print "TSS not reachable" if even after retries followed by exponential backoff logic. - Guarantee tills remain operational and not blocked even if the TSS is unreachable. task:5051693 Forward-Port-Of: odoo/enterprise#100911 Forward-Port-Of: odoo/enterprise#93694
This update fixes an issue where Argentinian invoices weren't correctly displaying taxes in the company's local currency, even when the setting was enabled. The previous code was unintentionally removing the tax section. This change ensures invoices accurately reflect tax amounts in the appropriate currency, improving financial reporting for Argentinian businesses.
Original PR description
**Steps to reproduce:** - Install l10n_ar - Switch to a Argentinian company (e.g. (AR) Responsable Inscripto) - In Accounting settings, enable "Taxes in company currency" option - Activate another currency (e.g. USD) - Create an invoice in USD - Confirm the invoice - Print the invoice **Issue:** The section showing the taxes in the company currency doesn't appear on the invoice despite the enabled option. Cause: An override of "report_invoice_document" from l10n_are is removing the section no matter what the configuration. **Solution:** Do not remove the section. It was done originally in 17.0 where "Taxes in company currency" option didn't exist. opw-5351010 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238204
This update resolves an issue preventing portal users (subcontractors) from accessing picking details within subcontracted manufacturing orders. The fix uses `sudo()` to grant necessary read access to the required models, ensuring a smooth user experience. This improves the functionality for portal users managing subcontracted inventory.
Original PR description
Issue Before This Commit: ======================= When a subcontractor (portal user) tries to open a picking from the Manufacturing orders section in the portal view, the page appears blank with no…
Issue Before This Commit: ======================= When a subcontractor (portal user) tries to open a picking from the Manufacturing orders section in the portal view, the page appears blank with no data loaded on the frontend, while in the the backend logs show read Access Error is raised on the `product.supplierinfo` and on `product.template.attribute.value` models. Steps to Reproduce: ======================= -Install `MRP` and `Purchase` modules, and enable Subcontracting. -Create a product attribute with values and `variant creation` set to `Never`. -Create a product and Assign the created attribute to the product’s attributes. -Create a portal user and grant portal access. -Create a BOM for the product, set it for subcontracting, and assign the portal user as a subcontractor. -Create a Purchase Order for a subcontracted product linked to that vendor. -Log in to the portal view as the portal user and open Manufacturing Orders. -Try to open the related picking and the page fails to load and appears blank. Cause of the issue: ======================= In this [PR](https://github.com/odoo/odoo/pull/177390), The `_compute_description_picking` method was extended to include vendor product code and product name using the `selected_seller_id` field, and the product attribute values using the `product_no_variant_attribute_value_ids` field. Since `selected_seller_id` points to `product.supplierinfo` model and `product_no_variant_attribute_value_ids` points to `product.template.attribute.value` model, `group_portal` do not have read access to these models causing access errors when the picking description is computed, so the page appears blank while opening the picking. After This Commit: ======================= The `_compute_description_picking` method now uses `sudo()` to safely access `selected_seller_id` and `product_no_variant_attribute_value_ids` fields, allowing portal users to compute stock move descriptions without encountering access errors. This prevents the page from appearing blank when opening picking in the portal without granting direct model access. Task-4958070 Forward-Port-Of: odoo/odoo#225519
This update resolves an issue where clicking 'Details' on completed signed documents caused errors. The fix ensures the correct sign request record is retrieved, allowing users to now properly view and access the details of signed documents, improving workflow efficiency.
Original PR description
Version: - saas-18.4 Steps to reproduce: - Open a template that has at least one completed signed request. - Click the Signed Document state button. - See all documents - Click on the detail button Before: - Clicking the Details button on a completed signed document caused a traceback. - This happened because the view was using the record ID from this.props.record.context, which referred to the sign template instead of the sign request, causing incorrect data to be fetched. After: - Use this.props.record.evalContext to retrieve the correct sign request record ID, with this.props.record.context as a fallback. Impact: - Users can now view signed document details without errors, improving workflow continuity and overall usability. task-5253632 Forward-Port-Of: odoo/enterprise#99221
This update resolves a bug preventing the 'Reviewed' button from appearing correctly in certain accounting scenarios. Additionally, a security enhancement has been added to disable secondary buttons during statement reconciliation, improving data accuracy. This ensures the 'Reviewed' button is always visible when appropriate.
Original PR description
Before this commit, we called the wrong variable to know whether the "Reviewed" button is available or not. It leads to have a no show of this button even when it was needed. This commit also adds a small security check to remove the secondary buttons when the statement is reconciled. no task id
This update fixes a bug that caused payment transactions to remain in an 'error' state after processing with Razorpay. The fix prevents the system from skipping necessary updates during error handling, ensuring transactions complete correctly. This improves payment processing reliability.
Original PR description
Steps: - Install razorpay provider. - Set up provider and try to make payment with UPI PM. - Cancel processing payment in Razorpay form while processing keep form open. - Now complete that same tx in same Razorpay form. Issue: - Transaction stays in `error` state. Cause: - _process method skips calling _apply_changes for `error` stage transactions even though it should allowed. Fix: - Improve condition to only skip `_apply_changes` only if `_validate_amount` fails. issued PR: https://github.com/odoo/odoo/pull/224627 Note: This is just temporary fix for the stable in master we will make `_validate_amount` method return boolean value depending on that we will decide whether to apply changes or not.
This update resolves an issue where PayPal payments were failing when required shipping address fields were left blank. The fix adds a default value to these fields, ensuring PayPal transactions can proceed smoothly. This improves the reliability of our payment processing.
Original PR description
Paypal was failing when the address fields were `False` **Solution:** Add a fallback to missing fields in the shipping address Fixes: https://github.com/odoo/odoo/issues/237360 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238340
This update fixes a bug where reverse charge tax amounts were incorrectly recorded as debits on invoices created with down payments from sales orders. The change ensures that reverse charge tax amounts are correctly reflected as credits, aligning with accounting regulations and improving invoice accuracy. This resolves an issue reported in opw-5172402.
Original PR description
When creating an invoice with down payment from a sales order, the reverse charge tax amount goes into the debit side. Make sure the reverse charge tax amount goes into the credit side. opw-5172402 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#237557
This update ensures that the agent's transcription summaries are generated in the user's preferred language, improving the clarity and usability of the AI-powered features. The system now dynamically adjusts the language of the summary based on the selected language of the underlying transcription, providing a more natural and accurate experience.
Original PR description
This commit introduces a change that makes the agent produce a summary in the selected language from the transcription tab. It injects a specific prompt using the `currentLanguage` of the transcription the component. Instructing the LLM to generate in the proper language.
This update restores the automatic copying of followers from parent sales orders to renewal and upsell orders within subscriptions. Previously, this feature was removed for all order types. This change ensures that sales teams can easily maintain consistent customer relationships when managing subscription renewals and upgrades, improving sales efficiency.
Original PR description
[FIX] sale-subscription: Restore automatic follower copying from parent SO In Odoo 18.2 (Task 4655022), automatic follower addition was removed for all users and limited to internal users. However, for subscriptions, it is logical to automatically copy followers from the parent sale order to renewal and upsell orders. This commit restores that behavior for subscription renewals and upsells while keeping the restriction for other record types. task - 5002181 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
This update resolves a crash that occurred when submitting account returns in older Spanish localization databases. The fix ensures the system handles databases without the latest module installation, preventing the application from failing. This improves stability and reliability for users in Spain.
Original PR description
For databases created with spanish localization before the `l10n_es_reports_2025` was backported in stable (see odoo/enterprise#90615), updating the code won't auto install the `l10n_es_reports_2025` module but make every submit of account.return crash with: `AttributeError: 'account.return' object has no attribute '_l10n_es_get_report_modelo_number'` This commit ensure we handle that case without crashing.
This update resolves an issue where Sale Orders with lot-tracked products were incorrectly duplicated when imported into POS. The fix prevents unnecessary line splits during import, ensuring accurate order processing and avoiding data inconsistencies. This improves the reliability of the POS system when handling lot-based inventory.
Original PR description
## Issue: After confirming a Sale Order for a lot-tracked product (in grams for example) and having available quantities, importing the SO in POS duplicates the order lines ## Cause: In the…
## Issue: After confirming a Sale Order for a lot-tracked product (in grams for example) and having available quantities, importing the SO in POS duplicates the order lines ## Cause: In the `settleSO` function, the line is first split because the UoM differs and is not `pos_groupable` Among the default UoMs, only Units, Pack of 6, and Dozen have `is_pos_groupable` = True, meaning most other UoMs will trigger a line split After duplicating the line due to the UoM split, an additional line is then added for each lot to link, causing duplicate entries in the POS order ## Steps to reproduce: - In Settings, enable Lots & Serial Numbers and Units of Measure & Packagings - Create a Product (Tracking: Lot, Sale Unit: g) - Update the Quantity On Hand (Lot: "LOT", Quantity: 5) - Create and confirm a Sale Order for the product (Quantity: 2) - Open POS and import the SO - Before the fix, there is 3 lines (2x no lots, 1x with lot + qty 2 ## Other issues: - The discount was not imported on the lot lines - Some lines were missing when importing lines where part of the quantity had no available lot - (This fix was already made in PR: https://github.com/odoo/odoo/pull/229075/files but was not forward-ported) opw-5018295 Forward-Port-Of: odoo/odoo#238237 Forward-Port-Of: odoo/odoo#234165
This update resolves a bug where a global discount applied during a restaurant order couldn't be correctly split across multiple orders. The fix ensures the discount is consistently applied at each product addition and recalculated accurately after splitting, excluding transfers.
Original PR description
Steps to reproduce: - Order some products in a pos restaurant - Add a global discount - Split the order Issue: The global discount can be chosen to be splitted. Fix: The first fix is to apply the global discount each time we add a product. The second fix is to hide the discount when splitting, and recalculate the discount on each splitted order afterwards execpt when tranferring an order. task-5189067
This update significantly speeds up the 'Products Design' preview feature on the `/shop` page. Previously, editing product variants caused significant lag, but this fix optimizes the process, reducing preview times from 700ms+ to around 120ms. Further improvements are planned to reduce the duration by an additional 30-40ms.
Original PR description
Description ======= This commit aims to reduce performance issues related to the `ProductVariantPreview` interaction. Editing the `/shop` page with the **"Products Design"** option caused severe…
Description ======= This commit aims to reduce performance issues related to the `ProductVariantPreview` interaction. Editing the `/shop` page with the **"Products Design"** option caused severe slowdowns and noticeable lag. 🧩 Problem ======= `ProductVariantPreview` uses `offsetWidth` to calculate the container size for variants and the size of the circles representing them. This is needed to determine how many variants can be displayed based on available space. Every call to `offsetWidth` after a DOM change (for example, adding a class) triggers a layout recalculation, which is expensive (around **6–7 ms** per call). The cost grows quickly since each `ProductVariantPreview` instance performs this for every circle, resulting in dozens or hundreds of layout recalculations. 💡 Solution ======= 1. The variant previewer was changed to target the entirety product grid instead of each single variant previewer, reducing the number of interactions per page to only 1. 2. Batch layout recalculations using `requestAnimationFrame`, given that now all container sizes are computed at the same time. This reduces the total to just **two layout recalculations**. 🔁 How to reproduce ======= 1. Go to `/shop` with several visible products with many variants. 2. Switch to **edit mode**. 3. Preview the **"Products Design"** option (hover over elements). Before this commit: ======= - The UI was extremely slow and laggy. - A single preview took **700 ms+**. - Performance degraded with more products and variants. After this commit: ======= - The interface is **much faster**. - Worst-case preview time is around **120 ms**. - The number of variants no longer impacts performance. Additional PRs related to `html_editor` and `html_builder` are in progress and should further reduce the duration by **30–40 ms**.
This update resolves a problem where global discounts weren't correctly applied when splitting a POS order. The fix ensures discounts are consistently calculated and applied, even after splitting, except during order transfers. This improves the accuracy of pricing and reduces potential errors for restaurant staff.
Original PR description
Steps to reproduce: - Order some products in a pos restaurant - Add a global discount - Split the order Issue: The global discount can be chosen to be splitted. Fix: The first fix is to apply the global discount each time we add a product. The second fix is to hide the discount when splitting, and recalculate the discount on each splitted order afterwards execpt when tranferring an order. task-5189067 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
This update resolves an issue where errors related to Saudi VAT (ZATCA) or network problems during order validation in the Point of Sale system were not being displayed. The change adapts an existing error handling process to the new order validation flow, ensuring that users receive timely notifications about potential problems.
Original PR description
In 18.5 order validation was moved from the payment screen to `OrderPaymentValidation`. The override of the `_finalizeValidation()` in `l10n_sa_edi_pos` was not adapted to the new flow in the forwardport #223759 and as a result the error was not being shown anymore This commit adapts the old override to the new order validation flow. task-5085213 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A recent update caused the margin calculation on sale orders to incorrectly display a 94% margin instead of the expected 66%. This was triggered by confirming the sale order line, which introduced a calculation within a specific override function. The fix addresses this by ensuring the unit of measure (UoM) is considered during margin calculation, restoring the correct 66% margin.
Original PR description
**Problem:** Sale order margin not computed correctly after confirm **Steps to reproduce:** - enable the margins setting - create a new storable product with avco category - set Sale Price to 3 and cost to 1 (remove taxes) - In the Sales Tab, in packagings add pack of 6 - create a sale order for 1 pack of 6 - unhide the margin% column - see how it is rightly computed (66%) - confirm the sale order **Current behavior:** The margin is now 94% **Expected behavior:** It should not have changed when confirming **Cause of the issue:** Because we confirmed the sale order line, it now has valued move, so the pruchase_price will be computed inside the sale_stock_margin override of _compute_purchase_price(). https://github.com/odoo/odoo/blob/38cffd1d1580693c56f0d897b8c8e60b938a8e85/addons/sale_stock_margin/models/sale_order_line.py#L15 There is currently no mechanism to take the UoM into account inside this override. opw-5344915
This update corrects an issue where commas in payment memos for EFT files were causing errors and rejection of the files. The change removes commas from generated files, ensuring correct formatting and preventing payment processing problems. This ensures accurate EFT file submissions to the BNZ bank.
Original PR description
The EFT file format BNZ is exported as a text file. As such, any commas in the field contents will be treated as a new field, resulting in incorrect formatting and a rejected batch file. This…
The EFT file format BNZ is exported as a text file. As such, any commas in the field contents will be treated as a new field, resulting in incorrect formatting and a rejected batch file. This behavior is due to the Odoo community commit [3082d3b](https://github.com/odoo/odoo/commit/3082d3bd0d7a8b45e647c441ba48adcb84a7a070), which partially reversed an improvement to the group payment memo field. - The original behavior was to concatenate the included invoices with spaces (e.g. 'INV/123 INV/124'). - The improvement replaced this with the batch payment reference (e.g. 'BATCH/IN/002'). - The behavior after 3082d3b is to concatenate the included invoices with a space and a comma (e.g. 'INV/123, INV/124' This commit strips the commas from all generated EFT files, instead of further altering the group payment memo field. It also alters existing unit tests to check that commas are removed from payment memo fields. While a fix that changes the memo generation would resolve some issues, this commit ensures that manually added commas will not cause rejected payments. [Ticket link](https://www.odoo.com/odoo/unassigned-tasks/5099220) opw-5099220 Forward-Port-Of: odoo/enterprise#100670 Forward-Port-Of: odoo/enterprise#98613