Thursday, August 28, 2025
2 changes · 18.0
Enhancements to existing features
Point of Sale now groups rapid local data updates before syncing them to the browser database. This reduces repeated background work and can make synchronization smoother when many records change quickly.
Original PR description
Before this commit, each change to `records` triggered a call to `syncDataWithIndexedDB`, which could result in multiple calls to IndexedDB sync. After this commit, the synchronization function is wrapped with a debouncing mechanism, ensuring that rapid updates are grouped together. opw-5025589 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo now treats ZATCA's duplicate submission response for B2C invoices as confirmation that the invoice was already received. This reduces uncertainty after timeout issues and helps prevent invoices from being incorrectly left as unsent.
Original PR description
ZATCA introduced a new response code (409) to handle duplicate invoice submissions for B2C. This is helpful because when the submission timesout, we are left unsure whether ZATCA successfuly received the invoice or not. The next time Odoo tries to send the same invoice, Zatca will respond with a 409 error if it was received earlier. In which case, we mark the invoice as successfully sent. A similar flow applies for B2B, with a response code of 208 for duplicate invoices. However, for B2B, ZATCA accepts the duplicate with a warning instead of an error, So the invoice gets marked as sent in Odoo, and no changes need to be done there. task-id: 4745275 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#223913 Forward-Port-Of: odoo/odoo#223754