Daily updates from Odoo
Thursday, January 1, 2026
3 changes · saas-18.3
Resolved issues and error corrections
A minor typo in the l10n_ec_edi_pos module caused the system to incorrectly identify the customer during refund processing for specific partners (like 'Deco Addict'). This fix corrects the typo, ensuring accurate customer identification and proper refund functionality. This resolves a potential issue with order processing.
Original PR description
Step to reproduce: - install l10n_ec_edi_pos - start pos and settle order with specific partner(ex. Deco Addict) - process the refund for this order Observation: - on product screen, "Consumidor Final" is selected instead of Deco addict. Cause and Fix: - Fixed a typo: it used `final_consumer_id` instead of `_final_consumer_id` opw-5412346 Forward-Port-Of: odoo/enterprise#102998 Forward-Port-Of: odoo/enterprise#102202
This update resolves an issue where UrbanPiper orders incorrectly displayed a payment difference after completion. The fix ensures that the final payment amount is accurately reflected as $0.00, streamlining the accounting process for these orders. This improves data accuracy and reduces potential discrepancies.
Original PR description
In this commit, The amount difference should be 0.0 after the Urbanpiper order has been paid. task-5441252 Forward-Port-Of: odoo/enterprise#102894 Forward-Port-Of: odoo/enterprise#102872
This update resolves an error that prevented users from opening employee forms within the Point of Sale (POS) frontend. The fix disables the employee form link on the frontend only, allowing it to function correctly in the backend where all necessary assets are available. This ensures a smoother user experience for POS operations.
Original PR description
Opening employee form in the frontend was throwing an error, since not all thre required assets were available on the PoS frontend. So in this commit 57aba149b6e6927f9055124e58bed03f842329d5, we disabled openening the employee form by making the employee_id field unclikcable, both in forntend and backend!! It was enough however to only macking it unclikcable on the frontend, since it was working fine on the backend where all the required assets were loaded anyway. This commit restores the functionality on the backend, but overriding the `Many2OneField` used by the `employee_id`, and making it unclickable only on the frontned. opw-5252486 Forward-Port-Of: odoo/odoo#241100