Weekly report from weekly_sales.csv

R2 weekly report - week over week from one CSV export · read-date 2026-11-10 · generated 2026-11-10T14:00:00Z

recipe	R2 weekly report - week over week from one CSV export (read-date 2026-11-10)
input	samples/weekly_sales.csv (16 data row(s) read)
generated	2026-11-10T14:00:00Z
date column	date (date shapes read: 13 ISO (2026-11-02), 1 named month (Nov 2, 2026), 1 slash month first (11/02/2026))
this week	2026-45 Mon 2026-11-02 to Sun 2026-11-08 (8 data row(s) dated in it)
last week	2026-44 Mon 2026-10-26 to Sun 2026-11-01 (6 data row(s) dated in it)
weeks in file	2026-43 (1), 2026-44 (6), 2026-45 (8)
metrics totalled	units, revenue, refunds
columns not totalled	region (0 of 16 filled value(s) read as a number); notes (0 of 7 filled value(s) read as a number); export_email (0 of 16 filled value(s) read as a number)

metric	this week	last week	delta	change	values used (this/last)	not read as a number
units	48	39	+9	+23.1%	7/6	0
revenue	3,546	2,691	+855	+31.8%	6/6	2
refunds	2	3	-1	-33.3%	8/6	0

What was left out, and why

units: 1 cell(s) in this file were blank. A blank is treated as no figure, not as 0, so it is in no total.
revenue: 2 value(s) in this file could not be read as a number, so they are in no total - row 10 held 'n/a', row 14 held '49,95'.
1 row(s) had a date this recipe could not read, so they are in no week and no total - row 17 held '31/11/2026'. Nothing was dated by guess.
1 dated row(s) fall in neither reported week. They are counted in the weeks-in-file line and in no total.
A value written with a comma as its decimal mark (49,95) is deliberately not read: read as 4995 it would be a wrong number rather than a missing one. Ask the export for a dot, fix the cells, and they will be counted.
This recipe reads local files and writes local files. It has no way to send, upload or post anything: no mail, no network, no login.