N062-E1 Tier 5 · Expert · easy ecommerce · Brightlane

Return the combined value of `quantity` multiplied by `unit_price` across every line item belonging to shipped `orders`

Part of Choosing Between Subqueries, CTEs, and Joins in SQL

The problem

Scenario: Brightlane's finance team needs the combined value of every line item belonging to a shipped order, computed from line-item data rather than any pre-stored total.

Task: Write a query to return the combined value of quantity multiplied by unit_price across every line item belonging to shipped orders.

Assumptions:

  • A shipped order has status equal to 'shipped'.
  • A line item's value is quantity multiplied by unit_price.
  • The result is a single combined value across every line item belonging to a shipped order.

Output:

  • One row, holding the combined shipped line-item value.
  • Columns in this order: total_shipped_item_value.
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
  shipped_items AS (
    SELECT
      oi.quantity * oi.unit_price AS item_value
    FROM
      order_items oi
      JOIN orders o ON oi.order_id = o.id
    WHERE
      o.status = 'shipped'
  )
SELECT
  SUM(item_value) AS total_shipped_item_value
FROM
  shipped_items

The shape

A CTE narrows the rows to shipped-order line items first, then a single SUM over that named result returns the combined value. Splitting the row-narrowing from the totaling is what makes the query read as two clean steps instead of one dense expression.

Clause by clause

  • WITH shipped_items AS (...) names the intermediate result. Inside the CTE, SELECT oi.quantity * oi.unit_price AS item_value computes each line's value, JOIN orders o ON oi.order_id = o.id brings the order's status into reach, and WHERE o.status = 'shipped' keeps only line items that belong to a shipped order. The CTE returns one row per qualifying line item, each carrying its value.
  • SELECT SUM(item_value) AS total_shipped_item_value FROM shipped_items collapses those rows into the single combined figure of 4374.98.

Why this and not a single query

The same total comes out of SELECT SUM(oi.quantity * oi.unit_price) FROM order_items oi JOIN orders o ON oi.order_id = o.id WHERE o.status = 'shipped'. That form is shorter and, for a single-stage aggregation, the leaner choice. The CTE earns its keep when the row-narrowing step is reused or when naming it makes the intent legible. Here the CTE is a stylistic choice; both shapes are correct.

You practiced narrowing the relevant line items in a CTE before producing the single combined total — separating the row-narrowing step from the final calculation.

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.