Level 3 · The channel summary with SUMIFS

A channel summary is the table every manager asks for first: how much came through the website, the app and the marketplace. The export here is already rolled up one step: Aaron’s query returns one row per week and channel for the whole of November 2025, 15 rows in A2:D16. That is small enough to paste in full, so the numbers in this level are the real month, not a sample.

SUMIFS, one criterion

SUMIFS adds the cells of one range where every criterion is true:

=SUMIFS(sum_range, criteria_range1, criterion1, [criteria_range2, criterion2], …)

Unlike SUMIF, the range to add comes first. Many analysts use SUMIFS even for one criterion, so adding a second one later doesn’t mean reordering the arguments.

G4   =SUMIFS($D$2:$D$16,$B$2:$B$16,F4)

F4 holds app, so G4 adds the app’s five weekly rows: 118,601.68. Fill down to G6 and each row reads its own channel name: marketplace 57,032.56, web 116,730.16. The ranges are locked; only F4 moves.

Orders work the same way on column C: app 294, marketplace 113, web 244. Adding weekly order counts is safe here because each order falls in exactly one week, so no order is counted twice.

A date criterion built with &

Black Friday week starts on Monday, November 24, and that date sits in G1. To keep only the weeks on or after it, the criterion has to read “greater than or equal to the date in G1”:

I4   =SUMIFS($D$2:$D$16,$B$2:$B$16,F4,$A$2:$A$16,">="&$G$1)

">="&$G$1 glues the text >= to the date’s serial number, and SUMIFS reads it as a comparison. Both pairs of criteria must hold, so I4 is the app’s revenue in that one week: 33,463.80. Change G1 to another Monday and the whole column follows.

criterion	means
F4 or "app"	equal to app (not case sensitive)
">="&$G$1	on or after the date in G1
"<"&$G$1	strictly before it
"<>app"	anything except app

The last week is short: November 24 to 30. The export stops at the end of the month, so Cyber Monday, December 1, belongs to December’s report. Say so when you present the number.

The total row is your check

G7 =SUM(G4:G6), filled right to I7. G7 must equal SUM(D2:D16): 292,364.40. H7 must be 651. If the channels don’t add up to the data, a channel is misspelled in column F or missing from it. These are the same November totals the SQL holiday case returns, by channel, to the cent.

What Kevin can take to his meeting: in Black Friday week the app brought 33,463.80, ahead of web at 25,991.76 and the marketplace at 19,457.89, while for the whole month web and app were almost level.

Common mistakes

• ">=G1" in quotes. That criterion is the text “G1”, nothing matches and the cells show 0.
• Using SUMIF argument order with SUMIFS. SUMIF puts the sum range last, SUMIFS first. Swapping them adds the wrong column or returns 0.
• ">" instead of ">=". A week starting exactly on November 24 is not greater than November 24, so ">" drops the very week you asked for.
• Counting rows instead of adding orders. =COUNTIFS($B$2:$B$16,F4) counts the app’s weekly rows, 5, not its 294 orders. On an export that is already summarised, the counts live in a column: add them with SUMIFS.