Friday, August 14, 2026
2 changes · saas-18.4
Enhancements to existing features
Settling large sales orders in Point of Sale is now faster because the system avoids repeated background requests and repeated screen refreshes for each order line. Loyalty updates are also handled once after the order is settled, reducing delays for staff using POS with sales orders and loyalty features.
Original PR description
In `settleSO`, two per-line bottlenecks were addressed: 1. `has_valued_move_ids` was called once per order line via a separate RPC, causing N sequential HTTP round-trips. It is now computed server-side inside `read_converted`, which is already called once for all lines. 2. `addLineToCurrentOrder` was awaited per line, yielding to the event loop each iteration and triggering a full Owl re-render for every line. Lines are now created directly, batching all mutations into a single render. `recomputeOrderData()` is called once after the loop. `updatePrograms` is moved to a `pos_sale_loyalty` patch on `settleSO` so the loyalty concern belongs to the bridge module. opw-6319922 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#281035 Forward-Port-Of: odoo/odoo#271742
Only the person who created a signature request can now change a signer’s email address. This helps prevent unintended or unauthorized recipient changes, improving control and trust in the signing process.
Original PR description
Forward-Port-Of: odoo/enterprise#127582 Forward-Port-Of: odoo/enterprise#126675