Plan a category assortment with a clear good-better-best range
Keep, add, drop, or online-only decisions for every SKU, a price ladder, and store clustering, based on sales, margin, and space.
The prompt
Help me plan the assortment for a product category.
Category and channels: [e.g. "cookware, 40 stores plus online"]
Current SKU performance: [PASTE: SKU, price, units and $ sales, gross margin %, sell-through, store count, return rate, in-stock %]
Customers and competitors: [WHO BUYS, what competitors carry, price points they hit]
Space and SKU limits: [linear feet or fixtures per store, maximum SKU count, whether online-only items are allowed]
Role of the category: [traffic driver / profit driver / destination / convenience]
Vendor factors: [minimums, exclusives, private label options]
Do this:
1. Rank SKUs by sales, margin dollars, and productivity per unit of space; identify the long tail.
2. Find duplicates (SKUs meeting the same need at the same price) and gaps (customer needs or price points not covered).
3. Propose a good-better-best ladder with real step-ups in features or quality, not just price, and a target price for each tier.
4. Recommend keep, add, drop, or move online-only for each SKU, with the reason. Flag drops that could cost loyal shoppers, such as items that are the main reason for a trip or that appear in large baskets.
5. Suggest store clusters (by size, climate, or customer profile) that get different depth or breadth.
6. Estimate the effect on sales and margin, stating your assumption about how much demand transfers from dropped SKUs to the ones that remain.
Return:
- A short summary.
- The SKU decision table.
- The price ladder.
- Data to validate before the line review.
Use only my numbers; do not invent competitor prices or sales figures.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Data & Analysis prompts
What to fill in
- e.g. "cookware, 40 stores plus online"
- WHO BUYS, what competitors carry, price points they hit
- traffic driver / profit driver / destination / convenience
- minimums, exclusives, private label options
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Test that a migrated report or pipeline matches the old oneA parity-testing plan for migrations that compares old and new outputs at the right level, with tolerances and sign-off criteria.
- Find what drove my store's weekly sales resultBreaks a store's sales variance into traffic, conversion, ATV, and UPT, then gives specific actions for next week.
- Turn my monthly or quarterly numbers into an executive business reviewTurns your numbers into an executive business review: headline, performance vs. plan, drivers, risks, and decisions needed, as a report or slides.
- Build a logic model and performance measures for a public programA logic model linking resources to outcomes, with output, outcome, efficiency, and equity measures you can report to councils, legislators, or funders.