Point of Sale - Prevent Double Closing Sessions
This module extends Odoo Point Of Sale features, to prevent user to double close sessions.
This can happen if the user clicks twice on the "close session" button in two different windows.
In this case, Odoo will generate two sales entries, one of which will have a zero amount. Deleting it will create a hole in the sales entries numbering.
This module prevent such cases.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Prevents closing a Point of Sale session twice, avoiding duplicate accounting entries and gaps in the sales journal numbering.
This module adds a safety check to the Point of Sale session closing process. When a user clicks the "Close Session" button, Odoo normally creates accounting entries. If the user clicks twice (for example, in two different browser windows), two entries can be created, one with a zero amount, which later causes a gap in the sales entry numbering when deleted.
With this module, if a session is already closed, any attempt to close it again is blocked with an error message: "You can not close a closed session." This check only applies when the closing action is triggered from the Point of Sale interface, so it does not interfere with other ways of changing the session state.
The module extends the pos.session model and overrides the action_pos_session_close and write methods. It does not add new menus, fields, or reports. The change is automatic and invisible to users except for the error message when they try to close an already closed session.
Depends on
Models and fields (1)
- pos.session · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 12.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/pos.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.