Olsen Planning Suite

Planning Suite · Canada

Integrated Retail
Planning Platform

A connected toolset for curve-based forecasting, budget setting, seasonal collection management and in-season performance steering — from pre-season to final FC.

M 1 — Curve Studio

M 2 — Setting Plan

M 3.1 — Seasonal Planning

M 3.2 — In-Season Planning

M 4 — Management Information

M 5 — Admin & Access

M 1

Curve Studio

Historical analysis and scenario-based forecasting. Entry point — defines annual targets and seasonality curves per store.

Sales Dashboard

Budget vs Act 2024; growth factor slider; KPI bar

Weekly Sales Curves

% share per week; multi-store overview

Simulation FC

Low / Medium / High per store; Target / Financial / Buy cases

Curve & FC Library

Built-in + imported curves; publish Medium FC to M 2

Input

Excel Act 2023/24

Output → M 2

FY target + curve per store

Roles

Planner: editViewer: read

M 2

Setting Plan

Full store universe. Combines LfL curve-based targets with Non-LfL manual entries. Weekly revenue distribution per store.

Store Registry

All stores; channel; activation/closing; curve assignment

Planning

FY targets; 52-week modifier grid; import from M1

Summary

Aggregated weekly chart; LfL vs Non-LfL split

Budget (Freeze)

Snapshot management; archived versions; active baseline

Input

M1 publishNon-LfL manual

Output → M 3.x

weeklyRevenue[52] per store

Planned input

Revised FC from M 3.2

Roles

Admin: freezePlanner: edit

M 3.1

Seasonal Planning

Collection calendar, markdown schedule and marketing actions. Defines the commercial rhythm of the season.

Shop Drops

23 collections; start WK; RTW per channel; season tag

Markdown Plan

Step-down schedule per collection; promo stacking

Marketing Calendar

Weekly events; Email / Paid / Promo; budget vs invest

Weekly Summary

Active collections per week by markdown phase

Input

M2 freeze (display)

Planned → M 3.2

Collections + MD% per week

Roles

Planner: editViewer: read

M 3.2

In-Season Planning

Weekly actuals entry and rolling forecast. Compares actuals against M2 plan curve, generates revised FY forecast.

Sales Dashboard

Act 26 vs Plan 26 (M2) vs Bud 26 (Orig) + Act 24

Simulation

Actuals entry per store/week; plan vs actual chart

Weekly Planning

52-week table; manual curve edits; FC trend

Curve Library

Act 2024 + Plan 26 (M2) + Bud 26 (Original)

Units / Transactions

Planned — no data source connected yet

Traffic + Conversion

Planned — leading indicators

Input

M2 freeze (auto-load, LfL)

Output → M 2

Revised FC → new freeze

Roles

Planner: enter actualsViewer: read

M 4 — Planned

Management Information

Executive dashboard. Single view across all modules — original budget vs revised FC with channel, store and week breakdowns. Read-only for most users.

FY Overview

Budget vs revised FC vs YTD actual; deviation by channel

Coverage Tracker

YTD % of budget covered; store ranking

Event Context

M3.1 events overlaid on revenue chart; markdown impact

Rolling FC

Actuals + remaining plan by week; scenario range

KPI Summary

Traffic, conversion, ATV (once connected)

Export

Excel / PDF snapshot for management reporting

Reads from

M2 freezeM3.2 revised FCM3.1 events

Roles

All users: readNo editing

M 5 — Planned

Admin & Access Management

User management, role assignment and audit trail. Controls who can view, edit or freeze data in each module.

User Management

Create / deactivate users; assign roles per module

Role Configuration

Admin / Planner / Viewer; custom per-module overrides

Audit Log

Who changed what and when; freeze history

Data Snapshots

Version history; restore previous freeze states

Roles

Admin only

Note

Requires server deployment

Planning Suite

PLANNER

AB

Active modules — click card for details, Open to launch

M 1
Curve Studio

              
              Live
              
            
Tabs & functions
Sales DashboardBudget vs Act 2024 per store; growth factor slider; KPI bar
Weekly Sales Curves% share per week; multi-store overview; budget background
Simulation FCLow / Med / High scenarios; Target / Store / Financial / Buy cases
Curve & FC LibraryBuilt-in + imported curves; publish Medium FC to M 2
Sends to M 2
FY target + cluster curve per store
Receives
Standalone input layer
M 2
Setting Plan

              
              Budget 2026 V1
              
            
Tabs & functions
Store RegistryAll stores; channel; activation/closing weeks; curve per store
PlanningFY targets; 52-week modifier grid; import from M1 + Non-LfL
SummaryAggregated weekly chart; LfL vs Non-LfL split; KPIs
Budget (Freeze)Snapshot management; archived + active versions
Receives from M 1
FY targets + cluster curves
Sends to M 3.x
weeklyRevenue[52] per store
M 3.1
Seasonal Planning

              
              23 collections
              
            
Tabs & functions
Shop Drops23 collections (SD + DC); start WK; RTW per channel
Markdown PlanStep-down schedule per collection; promo stacking
Marketing CalendarWeekly events; Email / Paid / Promo; budget vs invest
Weekly SummaryActive collections per week by markdown phase
Receives from M 2
M2 freeze (display only)
Planned → M 3.2
Collections + MD% per week
M 3.2
In-Season Planning

              
              WK 13 · M2 loaded
              
            
Tabs & functions
Sales DashboardAct 26 vs Plan 26 (M2) vs Bud 26 (Original) vs Act 24
SimulationActuals entry per store / week; plan vs actual chart
Weekly Planning52-week table; manual curve edits; FC trend bar
Units / TransactionsPlanned — no data source yet
Receives from M 2
M2 freeze (auto-load, LfL)
Sends to M 2
Revised FC → new freeze
M 4
Management Info

              
              Planned
              
            
Planned tabs
FY OverviewBudget vs revised FC vs YTD; deviation by channel
Coverage TrackerYTD % of budget covered; store ranking
Rolling FCActuals + remaining plan; scenario range
Reads from
M2 freezeM3.2 revised FCM3.1 events
M 5
Admin & Access

              
              Needs server
              
            
Planned tabs
User ManagementCreate / deactivate users; assign roles per module
Role ConfigAdmin / Planner / Viewer; module-level overrides
Audit LogWho changed what and when; freeze history
Requires
Server deployment

User roles & permissions

Requires server deployment (M 5). Locally: all users have full access.

⚙ Administrator

✓View all modules

✓Edit all modules

✓Freeze budgets (M 2)

✓Save revised FC (M 3.2)

✓Manage users (M 5)

✓Delete / restore snapshots

✓Publish M1 curves to M2

✓Access audit log

✏ Planner

✓View all modules

✓Edit M 1, M 3.1, M 3.2

●M 2: edit targets (no freeze)

✓Enter weekly actuals (M 3.2)

●Save revised FC (approval req.)

–Freeze budgets

–Manage users

–Delete snapshots

👁 Viewer / Other

✓View all modules

✓M 4: Management Info

✓Export / download data

–Edit any module

–Enter actuals

–Freeze / save FC

–Publish curves

–Access audit log

Legend: ✓ Full access · ● Restricted / approval required · – No access · All permissions require server deployment (M 5) — locally all users see everything.

Development roadmap

Phase 1
Done ✓

M 1 — Curve Studio

Historical analysis, cluster curves, Low/Med/High FC, publish

M 2 — Setting Plan

LfL + Non-LfL stores, curve distribution, budget freeze

M 3.1 — Seasonal Planning

Shop drops, markdown, marketing calendar

Phase 2
In progress

M 3.2 — In-Season Planning

Actuals, plan vs actual, rolling FC, revised freeze → M2

M2 ↔ M3.2 data loop

Revised FC → new freeze; M3.2 auto-loads LfL baseline

Launcher (local)

Single hub; shared localStorage via python http.server

Phase 3
Next

M3.1 → M3.2 context feed

Collections + markdown % per week as in-season context

Units + Transactions

Weekly actuals layer in M 3.2

M 4 — Management Info

FY FC, coverage%, deviation — reads M2 + M3.2 + M3.1

Phase 4
Future

Traffic + Conversion

Store visits → ATV, conversion as leading indicators

Server deployment

Team access, persistent data, version history

M 5 — Admin & Access

User roles, audit log, snapshots — requires server

Planning workflow

From historical data to In-Season FC

10 steps

1

Load historical data

M 1: Import Excel Act 2023/24 to curve analysis + cluster

Done ✓

2

Generate FC scenarios

M 1: Low / Med / High, Publish Medium Case to M 2

Done ✓

3

Set store targets

M 2: Import M1 targets; Non-LfL; assign curves; weekly distribution

Done ✓

4

Freeze budget

M 2: Lock plan to olsen_sp_freeze_v1 baseline for all M 3.x

Done ✓

5

Define 4 planning cases

M 3.2 (new): Company=Median, Financial, Buy, Store via %

Planned

6

Plan seasonal calendar

M 3.1: Shop drops, markdown schedule, marketing calendar

In progress

7

Enter weekly actuals

M 3.3: Revenue actuals per store per week; auto-detect WK

In progress

8

Compare plan vs actual

M 3.3: Act 26 vs Plan 26 (M2) vs Company and Financial target

In progress

9

Generate revised FC

M 3.3 Save as FC to M 2 new freeze. M 3.4 Rolling FC module

Planned

10

Review in M 4 Dashboard

Budget vs revised FC; channel deviation; coverage%; event context

Planned

Planning Suite — Infrastructure Architecture

v1.0 · April 2026

System architecture

Current state (local) and target state (server deployment) — data flow between modules, storage and devices

Phase 1–2

Today

Local server

shared
storage

Phase 3+

Server

Team access

Devices

All users

M 0 Launcher + Active modules — localhost:8080 — HTML files in one folder

M 0Launcher

›

M 1Curve Studio

M 2Setting Plan

M 3.1Seasonal Planning

M 3.2In-Season Planning

M 4Mgmt Info

Browser localStorage — shared across all modules on same origin

olsen_sp_freeze_v1

olsen_curve_library_published

olsen_m3_v1

olsen_m32_m2_import

olsen_planned

olsen_act26

Read/write · per browser · resets on clear

Web server — required for team access, user auth and persistent data

Application server

e.g. planning.olsen.ca — serves all HTML modules from one domain

M 5 — Admin & Access

User authentication

Role management

Audit log

Snapshot storage

Multi-user sync

AdministratorFull access · freeze · manage users

PlannerEdit modules · enter actuals

ViewerRead-only · M 4 dashboard

Desktop / Laptop

Full access

M 0M 1M 2M 3.1M 3.2M 4M 5

Planning · Admin · All modules

Tablet

Planner / Viewer

M 1M 2M 3.1M 3.2M 4M 5

Actuals entry · Dashboard · Review

Mobile

Viewer

M 1M 2M 3.1M 3.2M 4M 5

M 4 Dashboard · read-only