Saturday, January 24, 2026
5 changes · saas-18.4
Enhancements to existing features
The CRM enrichment email template now reuses existing information fields instead of adding duplicate ones. This helps show richer company data in the activity chatter without requiring an upgrade and reduces repeated entries for users.
Original PR description
- Remove newly added fields that can be replaced by existing keys present in `iap_mail.enrich_company` template to ensure we get more data in chatter without upgrade and avoid duplicate entries IAP PR: https://github.com/odoo/iap-apps/pull/1390 Forward-Port-Of: odoo/odoo#245068
Resolved issues and error corrections
This fix prevents the self-ordering kiosk from sending empty tickets to preparation printers when no product categories are configured for that printer. Restaurants avoid unnecessary blank printouts and reduce confusion for kitchen staff during checkout.
Original PR description
Before this commit: To reproduce (version 17 and >): 1. Install Restaurant 2. In PoS restaurant config allow "Self ordering" in Kiosk mode and enable "Preparation printers" 3. Create a preparation printer with NO categories and set it as a restaurant preparation printer 4. Open the Kiosk 5. Make an order with any product and checkout -> Printer will print a ticket with no product <img width="512" height="415" alt="image" src="https://github.com/user-attachments/assets/31bd08f9-2470-4f72-9e3d-822564b43f70" /> After this commit: No kitchen printer is printed (expected as no category set on the kitchen printer) Forward-Port-Of: odoo/odoo#245353 Forward-Port-Of: odoo/odoo#245193
This fix lets customized Studio fields be used in stock quantity views without being blocked by internal validation. Businesses can safely tailor inventory screens to their needs while avoiding errors when creating or editing stock quantity records.
Original PR description
In versions prior to 18.3, the “stock.quant” view did not have an “xml_id”, which prevented it from being modified through Studio. However, starting from version 18.3 and specifically since this commit: https://github.com/odoo/enterprise/commit/f4a4d54d45392c2ba46a123d4951f8b4468c5cba it is now possible to modify views through Studio even if they don't have an xml_id. But in the 'stock.quant' view, we perform a check at creation time to ensure that the field is among the allowed fields. Fields coming from Studio or from a customized view should, however, be ignored by this check and allowed. opw-5107591 Forward-Port-Of: odoo/odoo#230126
The sample company name used across demo and test data has been changed from “Deco Addict” to “Acme Corporation” after a real company reported user confusion. Sample invoice options are also limited to demo databases, reducing the chance that users add irrelevant demo data to their own live environments.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/odoo#245650 Forward-Port-Of: odoo/odoo#245205
This pull request resolves a customer complaint regarding demo data. The name "Deco Addict" was replaced with "Acme Corporation" to prevent users from mistakenly believing they had a business relationship with this company. This ensures a cleaner and more accurate demo experience.
Original PR description
A company that happens to be named "Deco Addict" has complained some of our users thought they had business with them due to test and demo data containing that name. It will now be named Acme Corporation. task-5865502 Forward-Port-Of: odoo/enterprise#105440 Forward-Port-Of: odoo/enterprise#105151