Daily updates from Odoo
Thursday, March 5, 2026
9 changes · master
Resolved issues and error corrections
This update corrects inaccuracies in the XML files used for Swedish payments (SEPA). Specifically, it ensures the correct BIC number is used, removes a misleading placeholder value, and allows users to select the appropriate payment version for 'iso_se' payments, regardless of SEPA method selection. This improves the accuracy and reliability of payment processing for Swedish customers.
Original PR description
We currently have customizations for the iso20022 xml file for payments in Sweden. But those customizations aren't correct. This commit fix multiples issues: 1) In DbtrAgt, we sometimes have bankgiro information. But this node should always contain the BIC number for Swedish payments. 2) The _get_cleaned_bic_code method was replacing the real bic code with a fake value like 'SE:Bankgiro', but this seems to be wrong. None of the SE banks ask for this BIC, so we remove it. 3) The sepa_pain_version field is supposed to tell Odoo which pain version to use. But the problem is this field is computed, and only editable once the user set the SEPA payment method, but for iso_se, we want to let the user choose as well, even if he didn't add SEPA as payment method. This commit change the invisible on the field, so it can be edited as soon as iso_se is in the journal payment methods. task-5427570 Forward-Port-Of: odoo/enterprise#105536
This update resolves an issue where custom reports, built using specialized models, were causing Studio to crash. The change ensures Studio can handle these tailored reports without errors, improving stability and usability for users creating and running reports.
Original PR description
…eport Some report build their data via a report model. Those are often tailor made to their business use cases and may crash when entering studio. This commit prevents this Forward-Port-Of: odoo/enterprise#107229
This update resolves an issue preventing the export of Eco-Voucher data to Excel after a recent system update. The change reflects a necessary adjustment to how Eco-Voucher status is tracked due to a shift in the system's versioning process. This ensures accurate reporting for Belgian payroll compliance.
Original PR description
Since the switch from contracts to versions, exporting Eco-Vouchers to excel has not been functional, this commit fixes this. **Steps to reproduce:** - Open Payroll App as a Belgian company - Under Reporting Menu, select Eco-Vouchers - Try exporting with XLSX **Issue:** Since introduction of versions, version module does not contain state field anymore which was present in contracts **Fix:** Removed the state field and replaced it with the corresponding field in version. task:5163668 Forward-Port-Of: odoo/enterprise#109500 Forward-Port-Of: odoo/enterprise#97375
This update resolves an issue where users could inadvertently add partners from different companies when managing multiple companies within Odoo. This change ensures that partners are correctly associated with the intended company, improving data accuracy and streamlining accounting processes. It’s a crucial fix for reliable multi-company reporting.
Original PR description
Before this commit, it was possible to add a partner that was from another company when multiple companies were selected. task-5941113 Forward-Port-Of: odoo/enterprise#108048 Forward-Port-Of: odoo/enterprise#107546
This update resolves a problem where CFDI-compliant invoices generated in Mexico were producing PDF reports with a section line that was too short, failing to include the subsequent invoice details. The fix ensures that the section line in the PDF accurately reflects the full invoice content, improving compliance and report accuracy. This impacts users generating invoices for Mexican companies.
Original PR description
**STEP TO REPRODUCE** 1. Select a MX company. 2. Create an invoice for a MX company with a section. 3. Send the invoice via CFDI. 4. Notice the section line in the section pdf is no long enough and does not cover the lines below. opw-5501379 Forward-Port-Of: odoo/enterprise#106123
This update addresses a change in Amazon's SP-API, which is used to automatically update inventory levels between Odoo and Amazon. The system has been upgraded to use a new feed type (`JSON_LISTINGS_FEED`) to maintain compatibility with Amazon's updated API. This ensures continued accurate stock synchronization.
Original PR description
Amazon SP-API is dropping support for the `POST_INVENTORY_AVAILABILITY_DATA` feed type. This was previously used in Odoo to synchronize the stock level with Amazon. This commit upgrades the feed api to use the new `JSON_LISTINGS_FEED` as a replacement. task-3820591
This update now accurately tracks shipments with multiple delivery orders for Amazon, providing the correct tracking number for each sale order line. Previously, only the first delivery's tracking number was shared with Amazon, leading to inaccurate customer visibility. This enhancement ensures customers receive correct and complete shipment information.
Original PR description
Previously, shipments via multiple delivery orders could not be tracked accurately. Only the tracking number of the first delivery was provided to Amazon, and displayed to the customer. With this commit, deliveries are now split per sale order line, and all tracking numbers are synchronized correctly. task-3062424
This update fixes an issue where refund calculations in the MX e-receipt module were incorrectly assuming all refund amounts were positive. The change ensures accurate calculations for refunds, particularly those with negative price subtotals, leading to more reliable financial reporting. This improves the accuracy of financial data related to MX e-receipt transactions.
Original PR description
From this version, the price_subtotal of a refund line is by default always positive so we have to inverse the check of this constraint.
This update fixes a bug preventing custom URLs for appointment types from being correctly reflected in the website's SEO settings. Now, users can set a custom URL for their appointment types, improving their visibility in search results. This change ensures better SEO performance for appointment pages.
Original PR description
Previously, appointment types URLs were not replaced by the value entered in the Cutsom Url field of the Optimize SEO form, this is not longer the case. This PR replaces the appointment type's id by…
Previously, appointment types URLs were not replaced by the value entered in the Cutsom Url field of the Optimize SEO form, this is not longer the case. This PR replaces the appointment type's id by the slug of this one in the appointment URLs. This allows users to change the slug of the appointment types and to get a better SEO for the appointment pages. This change has not been done for URLs that users are not supposed to access in order to prevent them from competing with URLs that need to be indexed. The model is not used in the backend URLs' patterns since URLs can be shared with users that may not have access to the appointment model triggering an AccessError. For this reason, the routes expect the slug to be a string, which is unslugged in the controller method to get the appointment's id and then fetch the appointment's record with it. Reproduce: On the page of an appointment type, submit a custom URL in the "Search Engine Optimization" form which is displayed when clicking on "Optimize SEO", in the "Site" menu shown when the website editor is enabled. The user should be redirected to the new URL which is not the case. After the fix: The slug of the appointment type must be replaced by the value submitted in the "Search Engine Optimization". Community PR: https://github.com/odoo/odoo/pull/249487 Task-5114394