Find Products That Customers Buy More Than Once
Return each product with the number of customers who ordered it at least twice.
The challenge runs on the SQLabHub practice database (SQLite) and uses the orders and order_items tables. You can solve it in the browser, with nothing to install.
The task
Find products most frequently reordered by same users.
A correct answer returns 6 rows with 2 columns: product_id, repeat_count.
Tables used in this challenge
orders 200 rows
id INTEGER (PK) · user_id INTEGER · total REAL · discount REAL · item_count INTEGER · status TEXT · order_date TEXT · shipped_date TEXT · shipping_city TEXT · shipping_country TEXT
| id | user_id | total | discount | item_count | status | order_date | shipped_date | shipping_city | shipping_country |
|---|---|---|---|---|---|---|---|---|---|
order_items 496 rows
id INTEGER (PK) · order_id INTEGER · product_id INTEGER · quantity INTEGER · unit_price REAL · subtotal REAL
| id | order_id | product_id | quantity | unit_price | subtotal |
|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| product_id | repeat_count |
|---|---|
The complete result: 6 rows. This is the output of the model solution on the practice database.
What you practise
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Grouping rows with GROUP BY to get one result row per group
- Grouping by more than one column to get a row per combination
- Filtering groups after aggregation with HAVING
- Combining rows from two tables on a matching key with an inner join
- Querying the result of another query with a subquery in FROM
- Sorting the result with ORDER BY
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
GROUP BY product_id, user_id
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Build an inner query first (a derived table):
- Read from the
orderstable. - Join
order_itemsonorders.id=order_items.order_id. - Group the rows by
orders.user_idandorder_items.product_id, so the result has one row for each combination. - For each group, compute
COUNT(*). - Filter the groups in
HAVING: keep those whereCOUNT(*)is greater than 1.
- Read from the
- Group the rows by
product_id, so the result has one row for each value. - For each group, compute
COUNT(*). - Sort the result by
repeat_countdescending.
Model solution
Checking your session…
What to watch for
The inner query finds user and product pairs that occur more than once; the outer query counts those pairs per product. Two lines for the same product within one order also count as a repeat here, since the pairs are built from order lines.
- Derived table. Columns computed in the inner query are only visible outside under their alias, so every calculated column there needs a name.
- INNER JOIN. An inner join drops rows that have no partner on the other side, and it repeats a row once for every match, which inflates SUM and COUNT.
- HAVING. Conditions on single rows belong in WHERE and conditions on aggregates in HAVING. Putting a row filter in HAVING works, but it groups rows that are about to be thrown away.
Related SQL challenges
- Measure Monthly Revenue Volatility per ProductSimilar levelHard
- Find Each Customer's Busiest Day by Order CountSimilar levelHard
- Find Customers with an Above-Average Number of OrdersEasierMedium
- Count Orders in Each Customer's First 7 DaysSimilar levelHard
- Find the Top 2 Products by Revenue in Each CategorySimilar levelHard
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: SQL Subqueries
- Lesson: INNER JOIN
- Lesson: HAVING Clause
- Lesson: GROUP BY Multiple Columns
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database