Repeat Purchase Plans
Repeat SKU Orchestration Plan
Pairs core SKUs with adjacent basket builders so repeat trips feel natural, not coupon-stuffed.
- Timeline
- 5–7 weeks
- Format
- Remote-first with two on-site days
- Indicative fee
- KRW 15,200,000
Scope narrative
We isolate hero SKUs, model adjacency from loyalty logs (anonymized), and propose cadence windows that respect promo fatigue caps. Output is a quarter-by-quarter mechanic calendar with retailer annotations.
Inside the box
- • SKU clustering with elasticity notes
- • Retailer cadence calendar
- • Creative guardrails for in-store voice
- • Elasticity assumptions documented for finance
- • Shelf strip copy options
- • Post-mortem template after each burst
What you leave with
- ↳ Quarterly mechanic calendar with owner per retailer
- ↳ Finance-ready assumptions appendix
- ↳ Creative starter kit for trade agencies
Questions teams actually ask
Do you need raw loyalty data?
Aggregated exports are enough if they include category mix. We sign a data handling addendum before transfer.
Can this cover more than three SKUs?
Yes, but each additional cluster adds modeling time. We quote that explicitly before kickoff.
What is excluded?
We do not run paid media or social listening — only in-store and owned-retailer surfaces tied to repeat.
Field notes
“Finance asked fewer “where did this number come from?” emails after the assumptions appendix. That alone saved weeks.”