Orders Above the Average

Fraud review at Whetcode Supply cannot look at every order, so it samples: anything worth more than a typical order gets a human glance, on the reasoning that a stolen card is used for something expensive rather than for a notebook set.

The cut-off is not a number anyone can type. It is the average order value, computed from the same orders being filtered, and it moves with every sale. Writing today's figure into the query gives a rule that is wrong next week and never says so.

orders — one row per order. customer_id is the id of the customer who placed it, product_id the id of the item bought, quantity how many units of that item, and order_date the day it was placed. An order row covers one item only.

products — the catalogue, one row per item on sale. price is what a single unit costs, in dollars.

The tables already exist in the database — there is nothing to create or load.

Task: Write a query returning two columns, id (the order's own id) and order_value (that order's item price times its number of units, rounded to two decimal places), one row per order worth strictly more than the average order value across all orders — equal to the average does not qualify. Rows come back by order_value, largest first; two orders here are worth exactly the same, so break that tie on id, smallest first. The review queue must read the same way every time it is built.

Example output