This module makes the pos default to the last used pricelist instead of the default one
auto_awesome What this module does
AI-generated from the code · Odoo 14.0In the Point of Sale, when a new order is started after the previous one is closed, the new order keeps the same pricelist as the order that was just finished instead of falling back to the default pricelist.
This module changes how the Point of Sale screen behaves when a cashier finishes one order and starts the next one.
Normally, each new order in the Point of Sale starts with the default pricelist configured for that point of sale. With this module installed, when an order is removed or closed and a new order is automatically created, the new order inherits the pricelist that was used on the order that was just removed.
- The behaviour is triggered when an order is removed from the order list, for example when it is abandoned or when a temporary order is replaced.
- If no other order remains in the list, a new order is created and it takes over the pricelist of the removed order.
- If other orders are still open, or the removal was not an abandon/temporary case, the pricelist is not copied.
This is useful in shops where the same customer or the same price conditions apply to several consecutive orders, so the cashier does not have to reselect the pricelist every time.
The module only touches the Point of Sale front-end behaviour; it adds no new menus, screens, database models or reports. It works together with the standard point_of_sale module and its order handling logic.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 14.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 14.0
Confirmed on 2026-11-03 in branch 14.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.