Daily updates from Odoo
Wednesday, October 15, 2025
4 changes · master
Enhancements to existing features
Austrian POS companies with an email address will now automatically receive an invitation to access their Fiskaly dashboard. If the company email changes, a new invitation is sent, and Fiskaly organization details stay updated even while authentication is pending.
Original PR description
In this commit: ------------------ - If a company email is set in the company information, we send an invitation to that email, allowing the user to access their company data on the Fiskaly dashboard by logging in using the company email. - If the email is later updated, access invitation will automatically be sent to the new email. - If the fiskaly organization exists, we should update the organization data even if the authentication is remaining to keep the data uptodate. Related PR: https://github.com/odoo/iap-apps/pull/1098 Task: 4881786 Forward-Port-Of: odoo/enterprise#88106
Online orders handled through Urban Piper are now protected from manual deletion in the point of sale. This keeps order records aligned with the normal restaurant workflow, where such orders should be cancelled by the aggregator or rejected by the restaurant instead.
Original PR description
Before this commit: =================== - We were able to delete online orders, but generally, online orders are either cancelled by the aggregator or rejected by the restaurant. After this commit: ================== - Online orders can no longer be deleted. Task: 496669 Forward-Port-Of: odoo/enterprise#95074
Peruvian electronic invoices can now include the required withholding reference when selling to customers classified as withholding agents. This helps businesses comply with local invoicing rules by reflecting the total withholding amount correctly in the XML without affecting invoice totals.
Original PR description
Some customers in Peru are considered "agentes de retención", and as such have special considerations that are necessary. We must perform specific actions when working with these customers, when selling to them we must: - recieve a specific document from the customer (A followup task will add this support for companies to generate this document) - Include a retention reference in our XML. This is represented as a specific `AllowanceCharge` node that is the sum of all of the Withholding taxes on the lines with the specific code of 62. We know an invoice is to a withholding customer because all lines must have a tax that is a part of the withholding tax group. This withholding tax is not included in the monetarytotals, tax totals, or invoice line values. And there can be only one AllowanceCharge node per invoice, not one per line. task-4989463 Forward-Port-Of: odoo/enterprise#97071 Forward-Port-Of: odoo/enterprise#94504
Attachments shared during a website helpdesk live chat are now carried into the related lead description in a cleaner, consistent format. This helps sales and support teams keep customer context and supporting files together when following up.
Original PR description
This commit PR attachment conversion logic with `_attachment_to_html` introduced in the related Community PR. Related: https://github.com/odoo/odoo/pull/227563 Task-4777564 Forward-Port-Of: odoo/enterprise#94970