N058-E3 Tier 5 · Expert · easy ecommerce · Brightlane

Return each product's `id`, name, and total revenue earned from its line items in `order_items`

Part of Multi-CTE Query Architecture in SQL

The problem

Scenario: Brightlane's buying team is evaluating which products have generated the most revenue across all order activity.

Task: Write a query to return each product's id, name, and total revenue earned from its line items in order_items.

Assumptions:

  • A line item's revenue is quantity multiplied by unit_price.
  • The result covers only products that appear on at least one order line.

Output:

  • One row per product with at least one line item on record.
  • Columns in this order: product_id, product_name, total_revenue.
  • Sorted by total_revenue descending.
Schema · ecommerce 5 tables
categories
id integer
name text
parent_id? integer
products
id integer
name text
category_id integer
price numeric
stock_qty integer
attributes? jsonb
order_items
id integer
order_id integer
product_id integer
quantity integer
unit_price numeric
customers
id integer
name text
email text
city? text
country text
created_at timestamptz
is_active boolean
orders
id integer
customer_id integer
ordered_at timestamptz
status text
total_amount numeric

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first
Solution query
WITH
  item_revenue AS (
    SELECT
      oi.product_id,
      p.name AS product_name,
      oi.quantity * oi.unit_price AS line_revenue
    FROM
      order_items oi
      JOIN products p ON oi.product_id = p.id
  ),
  product_totals AS (
    SELECT
      product_id,
      product_name,
      SUM(line_revenue) AS total_revenue
    FROM
      item_revenue
    GROUP BY
      product_id,
      product_name
  )
SELECT
  product_id,
  product_name,
  total_revenue
FROM
  product_totals
ORDER BY
  total_revenue DESC

The shape

Two CTEs, with the per-line revenue derived once in the first and rolled up once in the second. Computing quantity * unit_price inside the join layer means every downstream reference to line revenue points at the same expression in the same place. The aggregation in the second layer just sums what is already there.

Clause by clause

WITH item_revenue AS (
    SELECT oi.product_id, p.name AS product_name, oi.quantity * oi.unit_price AS line_revenue
    FROM order_items oi
    JOIN products p ON oi.product_id = p.id
)

The join attaches each line item to its product name, and quantity * unit_price AS line_revenue derives the row-level revenue right here. This is the only place the multiplication is written, which is the architectural point.

product_totals AS (
    SELECT product_id, product_name, SUM(line_revenue) AS total_revenue
    FROM item_revenue
    GROUP BY product_id, product_name
)

GROUP BY product_id, product_name collapses the line items per product, and SUM(line_revenue) adds the already-computed line revenues. Crest Pro 14" tops the list at 11,994, Sofa 3-Seater follows at 7,990.

  • SELECT product_id, product_name, total_revenue FROM product_totals ORDER BY total_revenue DESC returns the per-product totals sorted from largest to smallest.

You practiced staging the per-line revenue derivation in one CTE before per-product totals in another, so the line-revenue computation lives in a single named layer.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.