Saturday, April 25, 2026
2 changes · saas-18.4
Resolved issues and error corrections
Point of Sale loyalty history now records points earned and points spent separately when both happen in the same order. This prevents misleading net-only entries and gives businesses a clearer view of customer loyalty activity.
Original PR description
When a loyalty card both earned and spent points in the same POS order, the history entry only reflected the net difference instead of the gross amounts. The root cause was that the JS payload sent only a single `points` field representing the net change. Fix by tracking `points_earned` and `points_spent` separately in `couponData` and sending them to the server. opw-6041420 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#261236 Forward-Port-Of: odoo/odoo#256022
This fix ensures upgrade scripts are loaded under the correct Odoo upgrade area. It improves internal logging and warning handling during upgrades, helping technical teams diagnose upgrade issues more reliably without changing normal user workflows.
Original PR description
The resulting modules should be bound to the `odoo.upgrade` package. Side effects: - the loggers created inside the upgrade scripts are now in the `odoo.upgrade` namespace. - warnings raised by bad usages in upgrade scripts are now correctly filtered. Forward-Port-Of: odoo/odoo#261050 Forward-Port-Of: odoo/odoo#258025