This module extends the functionality of Point of Sale to prevent to delete order lines, if there are related to done or invoiced orders.
This module is a fix of Odoo Core.
You should install it if you have certification module installed. Otherwise, unlinking order lines will break the certification.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Prevents deleting Point of Sale order lines that belong to confirmed or invoiced orders, so sales history and certification data stay intact.
This module adds a safety rule to Point of Sale order lines. When someone tries to delete an order line, Odoo first checks the status of the order it belongs to.
- If the order is still in a new (draft) or cancelled state, the line can be deleted as usual.
- If the order has been confirmed, paid or invoiced, the deletion is blocked and the user sees an error message explaining that only lines linked to new or cancelled orders can be removed.
The rule is applied on the pos.order.line model, which is the record behind every product line shown in a Point of Sale order. There are no new menus, screens, buttons or reports; the change is purely a restriction on the existing delete action.
This matters because removing lines from completed or invoiced orders can break the Point of Sale certification and corrupt the link between the order and its accounting entries. Installing the module keeps that data consistent without changing how normal Point of Sale orders are created or validated.
Depends on
Models and fields (1)
- pos.order.line · 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.