Tuesday, September 15, 2026
1 change · saas-18.3
Resolved issues and error corrections
The POS Average Preparation Time report now calculates averages correctly when users apply search filters. This gives managers more reliable preparation time insights across custom date ranges or other filtered views.
Original PR description
Prior to this fix, the Average Preparation Time report in POS cannot handle user-defined domains through the search bar. This is due to the calculation being SUM(AVG(line.prep_time)/COUNT(\*)). However, any search domain is applied after AVG(line.prep_time)/COUNT(\*). This rework uses the 'avg' aggregator on the field 'avg_preparation_time' to perform the proper aggregation, as well as simplifying the select query overall. Steps to Reproduce on Runbot: 1. Create 2 POS Orders w/ 1 product each 2. Modify preparation_time on each line to be unique values 3. Change create_date for one of the pos.order.line to be > a month before the first line 4. View Average Preparation Time report, values should be off opw-6420735