New SKU Velocity Gate
A new item is missing its launch curve. Flags it for cut or support.
A new SKU tracks below 60% of its launch curve at day 21, measured against the comparable-item benchmark agreed at range review.
Launch-status flag updated in PLM; reorder suppressed or support spend released; POS reporting tag applied.
Every write is gated on an approver role you name. Nothing runs unattended.
- Compare actual sell-through to the launch curve, normalised for distribution and shelf position achieved.
- Separate a demand problem from an execution problem: never shipped, never merchandised, wrong location.
- Where it is execution, route to store ops instead and stop. Where it is demand, size the exit cost now against week 12.
- Open a case to the category merchant with cut, support, or reprice, gated on approval.
- Close when the SKU returns to curve or is exited before the markdown window opens.
Recovered margin against the modelled cost of holding the item to a week-12 clearance. Positive if the decision lands before reorder.
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 New SKU Velocity Gate 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.