Publish Date :
Shifted Holidays and 53-Week Years: Comparing Like With Like
A calendar mismatch can look like demand growth before a single customer has changed behaviour. Compare equivalent trading windows before changing the forecast. Merchmix Core holds the forward MFP/WSSI assumptions, while Atlas supports the period-based analysis used to challenge them.

THE MERCHMIX DECISION / Core + Atlas
The sales are unchanged. The comparison changes.
Align events and week counts before turning a percentage into a buying assumption.
Worked retail planning example. Quantities and financial amounts are independent assumptions; money is shown in US dollars. Proposals remain subject to review.
The sales are unchanged. The comparison changes.
The unchanged two-week totals are 280 and 320, or 14.3% growth. Aligning the comparison does not change recorded sales.
An event week compared with eighty preceding-week units appears 175% higher.
THE KEY IDEA
Align events and week counts before turning a percentage into a buying assumption.
The comparison period is part of the number
A sales percentage has little meaning until the reader knows what sits in each period. A holiday weekend can move between reporting weeks, and a fiscal year can contain an extra trading week. Either change can make date-matched totals describe a different opportunity.
The NRF’s 4-5-4 guidance explains its comparable-weekday approach and the periodic addition of a fifty-third week. It is a guide, not evidence that every retailer follows the same calendar. Establish the business’s own reporting convention before importing a calendar or rebasing a forecast.
Align the event before interpreting its uplift
Use a simple holiday example with no named retailer. Last year’s preceding week sold eighty units and its event week sold 200. This year’s preceding week sells a hundred and its event week 220. Assume the event has moved between the date-based comparison buckets.
Comparing this year’s event week with last year’s preceding week gives 175% growth: 220 divided by eighty, less one. The event-aligned comparison is 220 against 200, or 10%. Both calculations are arithmetically valid; only the second answers whether the event itself sold more.
Keep the surrounding weeks in view
The two-week totals are 280 last year and 320 this year, a 14.3% increase rounded to one decimal place. That wider window helps identify demand moving between weeks. It still does not prove whether the change comes from traffic, price, availability or the product mix.
Keep the comparison window consistent across products and channels before rolling it up. Do not add an event comparison to a calendar comparison as if they represented separate sales. The animation changes the analytical basis while retaining the same underlying event and preceding-week figures.
THE FIGURES BEHIND THE DECISION
| Comparison | Prior basis | Current units | Growth |
|---|---|---|---|
| Date-mismatched event | 80 | 220 | 175% |
| Event-aligned | 200 | 220 | 10% |
| Two-week window | 280 | 320 | 14.3% |
| Separate annual / aligned | 5,200 | 5,460 | 5.0% |
Event growth = 220 ÷ 200 − 1 = 10%. Separate annual example: 5,300 − 100 = 5,200 comparable units; 5,460 ÷ 5,200 − 1 = 5.0%.
Separate the extra week from comparable-year trading
A second, independent example uses prior-year sales of 5,300 units across fifty-three weeks. Its extra week contributed a hundred units. Removing that defined week for this comparison leaves a 5,200-unit fifty-two-week base; current-year fifty-two-week sales are 5,460.
The unadjusted comparison is about 3.0% growth, while the stated comparable base gives 5.0%. This example illustrates a chosen treatment, not a universal restatement rule. Follow the retailer’s approved convention and disclose which week was removed or remapped. Do not smooth it away without explanation.
Use the aligned evidence in Core, not a blind uplift
Core supports weekly sales, stock and intake comparisons with retained versions. The planner can use an agreed comparable basis when considering next year’s event assumption. That does not mean the system automatically remaps every holiday or fifty-three-week year for the business.
Atlas supports analysis by reporting period and merchandise scope. Confirm the configured fiscal calendar and comparison fields, then inspect the results. Keep actual trading unchanged; an analytical restatement changes the comparison basis, not what customers bought or what the financial ledger recorded.
Check whether intake has moved with the event
If a holiday moves earlier, a correct demand total can still be paired with a receipt that arrives too late. After fixing the comparison, review the forward stock path in Core. Event demand belongs in the week customers can use the product, not in a copied column from last year.
Separate the requested date from confirmed receiving availability. An earlier forecast is not permission to move an existing order or evidence that a supplier can comply. The calendar review should produce a dated intake question and an owner, with the actual order workflow handling any authorised change.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| A holiday changes week | Atlas / period analysis | Compare the event and surrounding trading window. |
| A year contains an extra week | Atlas / reporting basis | Disclose the approved comparison treatment. |
| The next event needs earlier stock | Core / MFP/WSSI | Review dated demand and confirmed usable intake. |
Publish the basis beside the performance claim
For the holiday example, state event-aligned growth of 10% and the two-week context of 14.3%. For the annual example, state the fifty-two-week basis and its 5.0% result. Keep the two examples separate so a reader cannot mistake them for one retailer’s trading record.
Merchmix helps connect the scoped evidence and forward plan. The judgement still starts with a precise comparison: same event, comparable weekdays, known week count and explained exclusions. A confident percentage should be the result of that work, not a substitute for it.
BEFORE THE NEXT DECISION
- Reporting owner
Approve the fiscal comparison and exclusions.
- Planner
Retain actuals and document the forward assumption.
- Buyer
Check that intake timing supports the moved event.
Common questions
Does every retailer use 4-5-4?
No. Confirm the actual fiscal calendar and comparison policy used by the business.
Why does 175% become 10%?
The first compares an event week with a preceding week; the second compares equivalent event weeks.
What does the two-week comparison show?
Sales of 320 versus 280, or 14.3% growth, include both the event and surrounding week.
Should every extra week simply be removed?
No. The example uses one disclosed treatment; follow the approved reporting and restatement convention.
Does Core automatically remap holidays?
This article makes no such claim. Confirm calendar configuration and review the aligned planning assumptions.
FROM THE ARTICLE TO YOUR OWN RETAIL PLAN
Review the decision.
See the workflow.
Bring your planning questions to a demo, or explore a proof of concept on your own data.