assortment-planning

Analyzes category performance, rationalizes underperforming SKUs, and manages new product intake calendars.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill assortment-planning-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assortment-planning
Source: https://github.com/tapway/shogun-os/tree/main/skills/retail/assortment-planning
Command: npx skills add https://github.com/tapway/shogun-os --skill assortment-planning-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Retail merchandising teams struggle to identify which products to keep, delist, or introduce across stores. This Skill automates category performance analysis (sales, margin, inventory turnover), flags underperforming SKUs for rationalization, and tracks the new product introduction pipeline so the right products reach the right stores. ## Core Features & Use Cases - Category Performance Reports: Analyze sales, gross margin, and inventory turnover by category and store, with targets like >40% margin and 6-12x annual turnover. - SKU Rationalization: Flag SKUs below a revenue contribution threshold (default 5th percentile) and generate a proposed discontinuation list with impact analysis. - New Product Intake Calendar: Manage quarterly product introduction timelines, track launch dates, and monitor shelf space conflicts. - Product Lifecycle Tracking: Trace a SKU from introduction to discontinuation with sell-through rate and weeks-of-supply metrics. - Use Case: A retail manager runs a monthly category review, finds 12 SKUs flagged for rationalization in Electronics, and plans the Q1 new product intake calendar in one workflow. ## Quick Start Ask the agent to run an assortment category performance report for the current month and list SKUs below the 5 percent revenue threshold as rationalization candidates.

Frequently Asked Questions about assortment-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify underperforming SKUs to discontinue?

Run the rationalize command with a revenue contribution threshold, such as the bottom 5 percent over a 90-day period. The report flags SKUs below the threshold and generates a proposed discontinuation list with projected impact analysis.

How to analyze category performance for retail stores?

Use the category report command with a period and date to get sales, gross margin, and inventory turnover per category. Results can be filtered by store and compared against category targets like 40 percent margin and 6-12x annual turnover.

What metrics does assortment planning track?

It tracks gross margin percentage, inventory turnover, SKU productivity, sell-through rate, weeks of supply, and category share. Each metric has configurable targets, for example sell-through above 70 percent and 4-8 weeks of supply.

Can I customize margin and turnover targets per category?

Yes, category-specific targets are defined in a categories.yaml file with margin, turnover, and sell-through targets per category. Environment variables like ASSORTMENT_TURNOVER_TARGET and ASSORTMENT_SELL_THROUGH_TARGET set global defaults.

When should I not use SKU rationalization?

Avoid rationalizing seasonal SKUs based on off-season performance; use trailing 12-month data instead. Also check vendor minimum order quantities and potential cannibalization effects before discontinuing products.

How long should new products be evaluated before decisions?

The default evaluation window is 90 days, configurable via ASSORTMENT_NEW_PRODUCT_WINDOW. Categories with longer purchase cycles may need extended windows, so set category-specific evaluation periods based on buying behavior.