This guide shows you how Week53 Sales Data is handled in effectmanager POS cubes and Online Reports.
Week 53 comes around every 5-6 years and requires special handling for you to be able to analyze your point of sales data correctly.
In the guide, we will go through how to view your week 53 sales data in:
- POS Cube: Sales Data shared on a daily level
- POS Cube: Sales Data shared on a weekly level
- POS Cube: Benchmark on week 53
- Online POS Reports
Sales Data shared on a daily level
You must identify if the wholesaler shares data on a daily level. Below we will show you how data is displayed in the POS cube and Online POS Reports.
NB! If the Wholesaler shares Sales Data on a daily level, your sales data is always read into the POS cube on the actual dates.
Week 53 in the POS Cube
An example of this is week 53 in 2015 - which is from December 28th, 2015 to January 3rd, 2016.
- Using the YearWeek hierarchy your data will be summarized on week 53.
- Using the YearQuarterMonthDay hierarchy your data will be shown on individual dates in week 53.
Sales Data shared on a weekly level
You must identify if the wholesaler shares data on a weekly level. Below we will show you how data is displayed in the POS cube and Online POS Reports.
NB! If the Wholesaler shares Sales Data on a weekly level, your sales data is always read into the POS cube on Sunday.
Week 53 in the POS cube
An example of this is week 53 in 2015 - which is from December 28th, 2015 to January 03rd, 2016.
POS data shared on a weekly level will be visible on Sunday Week 53 - January 03rd, 2016.
- Using the YearWeek hierarchy your data will be visible on week 53.
- Using the YearQuarterMonthDay hierarchy your data will be Shown on Sunday Week 53, January 3rd, 2016.
Week 53 - Benchmark Key Figures Rules in the cube on a weekly level
The benchmark of Sales data using the YQMD filter is done on a daily level on each date.
The benchmark of Sales data using a YW filter is done on a weekly level and has a different rule.
An example of how the rule for week 53 data is benchmarked, can be seen below
1. Benchmark for a year that has week 53
Week 53 will be benchmarked against week 1 in the same year.
An example of this is 2020 when we had week 53.
- Week 53 2020 is benchmarked against W01 2020
See the green marking in the image
2. Benchmark for the year after a year that has week 53
In the year following a year, that has week 53, we have a special rule to make sure, that all data is included in the benchmark. The following year week 52 will be benchmarked against week 52 + week 53 the previous year.
An example of this is 2021 week 52.
- Week 52 2021 is benchmarked against week 52 + week 53 2020.
See the yellow marking in the image
🔴OBS! This rule is implemented, as we cannot manipulate the YW period filter to include a Fictive Week 53 in the following year, as it is based on an actual calendar.
If we did not Benchmark Week 52 2021 against both Week 52 and Week 53 of 2020, the Week 53 data would not appear in the Benchmarked data, and the client would not see that sales if only Benchmark Key Figures are used. This would provide an incorrect dataset for the client.
Week 53 in Online POS Report
There are 3 different period hierarchies in the online POS reports - Daily, Weekly, and Week-Week. Below we will show you how Week 53 sales data is shown with the 3 different period hierarchies in the online reports. We will use Turnover Reports as an example.
If you want to know more about Online POS Reports, please take a look a the guides in the category POS Reports
Week 53 in Turnover per day
This POS report will provide you with a graph on a daily level based on your filtering selection compared to the same period last year.
In the example, I am viewing data from December 21st, 2015 to January 03rd, 2016. Week 53 is from December 28th to January 3rd, 2016.
For wholesalers who share sales data on a daily level, this will provide you with a graph with sales data on each date benchmarking it to the same dates in the previous period.
For wholesalers who share sales data on a weekly level, this will provide you with a graph where data is on Sundays. Benchmarking with the week last year will displace the Sales data, here it is better to use Turnover per Week or Turnover per Week - Week.
Week 53 in Turnover per Week
This POS report will provide you with a graph on a weekly level, using the day hierarchy, based on your filtering selection compared to the same period last year.
Using the Turnover per Week report with a daily period hierarchy, you will be able to select a period that stretches beyond the defined weeks.
In the example, I am viewing data from December 21st, 2015 to January 03rd, 2016. Week 53 is from December 28th to January 3rd, 2016.
For both wholesalers sharing data on a daily and weekly level, I will view the same graph for week 53, as this report shows data on a weekly level using the day hierarchy in the tables.
In the benchmark, it compares Week 53 dates (28.12 - 03.01) with the same dates in the previous period. But it will be shown as Week 53 in the graph, as this year always determines the week definition.
Week 53 in Turnover per Week - Week
This POS report will provide you with a graph on a weekly level, using the weekly hierarchy, based on your filtering selection compared to the same period last year.
Using the Turnover per Week - Week report with a weekly period hierarchy, your selected period will always be summarized and shown in full weeks.
In the example, I am viewing data from December 21st, 2015 to January 03rd, 2016. Week 53 is from December 28th to January 3rd, 2016.
For both wholesalers sharing data on a daily and weekly level, I will view the same graph for week 53, as this report shows data on a weekly level using the week hierarchy in the tables.
In the benchmark, it compares Week 53 full week with the same week in the previous period. But as there was no week 53 in the previous period, the graph only shows data for week 52 in the previous period.
