I'm not an executive, but certainly interested in data & reporting! I was initially going to suggest a one-off cron job to run each morning, aggregating the pr

I'm not an executive, but certainly interested in data & reporting! I was initially going to suggest a one-off cron job to run each morning, aggregating the previous day's costs/revenues by the core 'dimensions' you use (store, sales region, etc.). This could be done quickly with the 'ROLLUP' modifier in MSSQL/MySQL, and the output placed into a summary table or exported as spreadsheet/CSV data for quick analysis. But reading your post again - I'm not sure where you're worried the time sink will be; is it the interpretation & display of the data you have which you suspect is going to be the tricky part? The temptation might be to look towards more fully-featured OLAP/cube style tools - they do need a good amount of time and focus though!