This module extends Odoo Point Of Sale features.
By default, products are sorted by sequence in the Point of Sale Front End :
This behavior is correct for a point of sale with a few products, but does not correspond to the needs of the cashiers, when there are thousands of products.
Once installed, the products are sorted by name :
auto_awesome What this module does
AI-generated from the code · Odoo 14.0In the Point of Sale screen, products are now listed alphabetically by name instead of by their internal sequence order, making it easier for cashiers to find items when the catalogue is large.
This module changes how the product list is ordered inside the Point of Sale interface. By default, Odoo loads products in the order defined by their sequence field, which is fine for small catalogues but impractical when there are thousands of items.
Once installed, the Point of Sale front-end loads the product.product records sorted by their name. Cashiers therefore see the product buttons and search results in alphabetical order, which speeds up finding an item.
- No new menus, screens or buttons are added.
- No new database models or fields are created.
- No business rules, checks, emails or scheduled jobs are added.
- The change applies only to the Point of Sale interface; other Odoo areas keep their normal ordering.
The module works by extending the Point of Sale front-end model and overriding the loading order of the product list. It depends on the standard Point of Sale module and only affects the order in which products appear, not their data, prices or availability.
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: 3 confirmed, 6 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.