inventory-reorder-planner — Claude Code skill: install and use
The inventory-reorder-planner Claude Code skill turns sales history and stock counts into reorder points and purchase recommendations. It runs on requests for a buying plan, an urgent stock list, or a dead-stock report.
MIT 103 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill inventory-reorder-planner -a claude-codeWhat inventory-reorder-planner does
The skill reviews sales and current stock for each SKU, then factors in supplier lead times, demand variation, and seasonality when the sales history supports it. It writes a weekly buying plan to reorder-plan.csv, grouped by supplier, and marks items URGENT when stock is projected to run out before a delivery arrives.
A separate dead-stock report lists units on hand, tied-up cost, time since the last sale, and an exit option such as bundling, discounting, donating, or returning the item. SKUs with no sales history are labelled NEW and kept apart from calculated recommendations. The workflow needs a sales export, stock counts, and supplier lead times; supplier minimums and case-pack sizes are used when known.
What it helps with
- calculate a reorder point for each SKU
- prepare this week’s purchase list
- spot items likely to run out before delivery
- identify dead stock and its tied-up cost
Example prompts for the agent
- Build a purchase plan from
sales.csvandstock.csv. - What should I order this week?
- Show items at risk of stocking out and dead stock.
How to install inventory-reorder-planner
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill inventory-reorder-planner -a claude-code2Manually: put the files in place
~/.claude/skills/inventory-reorder-planner/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/inventory-reorder-planner/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill inventory-reorder-planner -a codex2Manually: put the files in place
.agents/skills/inventory-reorder-planner/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill inventory-reorder-planner -a cursor2Manually: put the files in place
.cursor/skills/inventory-reorder-planner/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills inventory-reorder-planner2Manually: put the files in place
.github/skills/inventory-reorder-planner/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill inventory-reorder-planner -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path inventory-reorder-plannerManually: put the files in place
.devin/skills/inventory-reorder-planner/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill inventory-reorder-planner -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about inventory-reorder-planner
How do I install inventory-reorder-planner in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill inventory-reorder-planner -a claude-code. The skill file is at ~/.claude/skills/inventory-reorder-planner/SKILL.md.
What does inventory-reorder-planner do?
It calculates reorder points and suggested order quantities from sales, stock levels, and supplier lead times. It also creates a weekly buying list and a dead-stock report.
What does inventory-reorder-planner need to work?
It needs a sales history export, current stock counts, and supplier lead times. Supplier minimums and case-pack sizes are incorporated when known.
Source text
SKILL.md · MIT
---
name: inventory-reorder-planner
description: Turn sales history and current stock counts into reorder points, order quantities, and a this-week purchase list -- so a product business stops stocking out of winners and stops burying cash in losers. Handles seasonality, supplier lead times, and the dead-stock cleanup.
tools: Read, Glob, Grep, Write, Bash
model: inherit
---
# Inventory Reorder Planner
Stockouts burn revenue on the products that sell; overstock buries cash in the ones that do not. Both come from ordering by gut. Input: sales history export (POS, Shopify, marketplace, or spreadsheet), current stock counts, and supplier lead times (asked per supplier if not provided). Output: reorder points per SKU and the purchase list for this week.
## Workflow
1. **Profile every SKU.** From sales history: average daily/weekly velocity, variability, trend (growing/flat/dying), and seasonality where the history is long enough to show it (holiday spikes, summer lulls) -- flagged per SKU, never assumed.
2. **Classify.** ABC by revenue contribution (A: the ~20% of SKUs driving ~80%), crossed with velocity: `WINNERS` (high velocity, healthy margin -- never stock out), `STEADY`, `SLOW`, `DEAD` (no sales in 90+ days with stock on hand).
3. **Compute reorder points.** Per SKU: lead-time demand (velocity x supplier lead time) plus safety stock scaled to demand variability and the SKU's class -- A items get generous buffers, C items get lean ones. Show the formula inputs per SKU so the owner can sanity-check against what they know ("velocity 4/wk, lead time 3 wks, safety 1.5 wks = reorder at 18").
4. **The purchase list.** `reorder-plan.csv`: every SKU at or below reorder point, recommended order quantity (covering the review cycle plus lead time, respecting supplier minimums and case packs when known), cost, and supplier -- grouped by supplier to build actual POs. Flag `URGENT` where projected stockout lands before the order can arrive.
5. **Free the cash.** The dead-stock report: units, cost tied up, days since last sale, and the exit per item -- bundle with a winner, discount, donate for the writeoff, or return to supplier. Cash sitting in dead stock is the cheapest funding most product businesses never tap.
## Rules
- Velocity from real sales only; no history means `NEW -- judgment order`, clearly separated from computed recommendations.
- Stockout periods bias velocity down -- when the data shows zero-stock stretches, compute velocity from in-stock days only and note it.
- Seasonality is applied only where the data shows it, and the applied multiplier is stated per SKU.
- Supplier constraints (minimums, case packs, price breaks) are asked for, and rounding to meet them is shown, not silent.
- A items err toward buffer, C items err toward lean -- one safety-stock policy for everything is the amateur tell.
- Re-run on a cadence (weekly or per supplier order cycle); each run compares last cycle's recommendation to what actually sold and tightens.
## Quick Commands
- "Plan from [sales export] and [stock counts]" -- full workflow
- "What do I order this week?" -- the purchase list only
- "What's about to stock out?" -- URGENT list
- "Where's my cash buried?" -- dead-stock report
© OneWave-AI · MIT · OneWave-AI/claude-skills