Daily updates from Odoo
Saturday, June 13, 2026
4 changes · saas-19.1
Enhancements to existing features
This update now automatically logs the reasons why orders aren't synchronized with Lazada, eliminating the need for manual investigation. Previously, understanding synchronization issues required examining order details and interpreting code. This change provides clearer insights into order status, improving operational efficiency.
Original PR description
Before this commit, the only way to know why an order was not synchronized was to inspect the order details and infer the reason from the code. This commit now logs those reasons. Forward-Port-Of: odoo/enterprise#120212
Resolved issues and error corrections
This update fixes an issue where LATAM invoices weren't correctly displaying company-specific document layouts in the header. By adjusting how custom headers are handled, the invoice now accurately reflects the chosen layout, ensuring consistent branding for Argentinian and other LATAM businesses. This improves the professional appearance of invoices.
Original PR description
Problem: When printing an invoice for a Latin American (LATAM) company, the company's document layout is not used in the header of the invoice. For example, if an Argentinian company has set up a…
Problem: When printing an invoice for a Latin American (LATAM) company, the company's document layout is not used in the header of the invoice. For example, if an Argentinian company has set up a Bubble layout as its document layout, the header of the invoice will not have the bubble. Steps to reproduce: 1. Install l10n_ar 2. Create an invoice using Electronic Sales Journal 3. Set document layout to Bubble in the company settings 4. Print the invoice 5. Notice that the header of the invoice does not have the bubble Cause: Most LATAM localizations use custom headers for their reports. In report_templates of l10n_latam_invoice_document, it checks if custom_header is set to decide whether to display the custom header. If custom_header is set, the div with class "header" will be hidden, and the custom header will be displayed after the div with class "header". Since the div with class "header" contains the background image that corresponds to the document layout, the background image will not be displayed when div with class "header" is hidden. Solution: Instead of hiding the entire div with class "header" when custom_header is set, only hide the table inside the header. This way, the background image of the document layout will still be displayed even when a custom header is used. opw-6204062
This update resolves an issue where accounting users were incorrectly denied access to Point of Sale closing journal entries. The fix prevents access errors related to POS sessions, ensuring all users can properly view and manage POS reporting data. This improves data visibility and reporting accuracy for accounting teams.
Original PR description
Accounting users can access POS closing journal entries even when they do not have Point of Sale access rights. The PDP POS helper checked POS session/order links directly while computing e-reporting fields on account moves. This could raise an access error on `pos.session` for accounting users without POS rights. <img width="1621" height="728" alt="image" src="https://github.com/user-attachments/assets/fdee75b6-83f0-4d46-b8d1-e06d286447d3" /> Forward-Port-Of: odoo/odoo#269815
Features or functions removed from Odoo
This update removes a redundant requirement for two-factor authentication (2FA) within the l10n_fr_pdp module. Initial assessments indicated 2FA was needed for administration, but further investigation revealed it wasn't. This simplifies the setup process and improves efficiency.
Original PR description
We iniatially though the 2FA was needed by the administration. But in fact, it was not. So we will remove it. Commit of the 2FA: https://github.com/odoo/odoo/pull/239576/changes/7535ce70391348019b4d9b668e49ca928c03052b Commit of the reregister also changed a bit that https://github.com/odoo/odoo/commit/22ba6294d3a2da6cada9dd519bd870c99d0b51b9 no task id --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#269862 Forward-Port-Of: odoo/odoo#269597