Cluster Reassortment
Cluster mismatched to demand. Re-maps to its real velocity.
A store consistently sells a category more like a different cluster than its assigned one, for two consecutive seasons and more than 15% apart.
Cluster assignment updated in Blue Yonder; assortment plan and replenishment parameters re-pointed in SAP.
Every write is gated on an approver role you name. Nothing runs unattended.
- Re-cluster stores on realised category velocity, basket composition, and demographic drift rather than the original banner rules.
- Identify stores whose assigned cluster costs them: over-assorted on slow lines, under-assorted on fast ones.
- Model the reassortment: what changes on the shelf and what it releases in working capital.
- Open a case to the assortment planner with the proposed cluster moves, gated on approval.
- Close when the reassorted stores hold sell-through above their new cluster benchmark for a full season.
Sell-through in reassorted stores over one season vs. their prior-cluster benchmark. Positive at 3 points.
The case closes on this number, not on the action being taken. A playbook without a close condition is a dashboard.
The rest of Merchandising
Run Cluster Reassortment on your data.
Pick three playbooks from the catalog. We wire them against your system of record for the pilot.
Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly
Find out what your data has been hiding.
Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.