Find Churned Customers with No Orders in the Last 90 Days
Return the users whose most recent order is more than 90 days old.
The challenge runs on the SQLabHub practice database (SQLite) and uses the orders table. You can solve it in the browser, with nothing to install.
The task
Find users who have not ordered in last 90 days.
A correct answer returns 114 rows with one column: user_id.
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 |
|---|---|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
The result has the columns listed above and 114 rows. This query depends on today's date, so its values change from day to day and no fixed rows are shown here.
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
- Filtering groups after aggregation with HAVING
- Working with dates in SQLite: strftime, julianday and DATE
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
MAX(order_date)
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
orderstable. - Group the rows by
user_id, so the result has one row for each value. - For each group, compute
MAX(order_date). - Filter the groups in
HAVING: keep those whereMAX(order_date)is less than the date 90 days before today.
Model solution
Checking your session…
What to watch for
The cutoff is measured from today with DATE('now', '-90 day'). This dataset ends in December 2024, so every customer who ever ordered now counts as churned. Users who never ordered are absent, because the query reads only the orders table.
- 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.
- GROUP BY. Every selected column must either be in GROUP BY or sit inside an aggregate. SQLite accepts other columns and returns an arbitrary value for them; most databases raise an error.
- Date functions. These date functions are SQLite syntax. MySQL uses DATE_FORMAT and DATEDIFF, PostgreSQL uses TO_CHAR, EXTRACT and date subtraction.
Related SQL challenges
- Find Orders with More Than One Payment RecordSimilar levelHard
- Calculate Customer Lifetime in Days from First to Last OrderSimilar levelHard
- Find Customers with More Than 3 Orders Using HAVINGEasierMedium
- Find Orders with More Than 3 Items Using HAVING SUMEasierMedium
- Count Orders per Month with strftimeEasierMedium
Keep learning
- Lesson: HAVING Clause
- Lesson: GROUP BY
- Lesson: Date Functions
- Lesson: Aggregate Functions
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database