- stores pos_order_count field to use it in filters and pivot view
- adds pos_order_ids field to use it in pivot view
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Stores the number of Point of Sale orders per customer directly on the contact record, so you can filter, group and analyse POS orders in list and pivot views.
This module changes how the customer's Point of Sale order count is handled. Normally that count is calculated on the fly and cannot be used for filtering or grouping. Here it is stored on the contact (res.partner) as pos_order_count, and a related list of the customer's POS orders (pos_order_ids) is added.
Because the count is stored, you can: - Filter contacts by how many POS orders they have. - Group and analyse POS orders by customer in pivot views. - See the stored count on the contact form.
The count is kept up to date automatically whenever the customer's POS orders change, through the standard recomputation of _compute_pos_order.
When the module is installed, a one-time setup step fills in the count for all existing customers by counting their POS orders, so historical data is immediately available for reporting.
The module only touches the contact model (res.partner) and the Point of Sale order model (pos.order). It adds no new menus or screens of its own; the new fields appear wherever contacts and POS orders are shown or analysed.
Depends on
Models and fields (1)
- res.partner · extends an existing modelpos_order_ids, pos_order_count
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.