Leadership wants revenue grouped by region, not a spreadsheet of every order

Every time leadership asks how one region compares to the others, I end up exporting a spreadsheet with thousands of order rows for them to sift through by hand.

Beginner to intermediateRead 5 minDoing: 20 to 30 minutes once you know the schema, a bit longer the first time7 steps

▶ Start

What you'll have at the end

A one-row-per-region revenue table, checked so the regional totals add up to the grand total

Before you start

You need

Read access to an orders table with an amount and a status column, plus a customers table carrying a region column, joined by a shared customer id.

Not covered

Ranking or comparing individual customers within each region once the region totals exist.

Leans on

Decide what actually counts as revenue

Nail down what counts as revenue
Pull the grand total first

Attach and label the region on every order

Attach each order's region with a join
Turn a blank region into a labeled bucket

Roll the orders up and prove the total holds

Group by region and sum the revenue
Check the total against the anchor

Hand leadership something they read in seconds

Turn the three rows into one chart

Where to go next

One global top-spenders list hides the winners in each region

for ranking each region's own top customers once these region totals exist

Checked 26 Aug 2026

Part of the SQL cookbook