Inventory Risk Brief - E-commerce
Use this skill when
The user wants an inventory-aware growth or promo review from exports.
Common requests:
- "Review this inventory export."
- "Which products are at risk of stockout?"
- "Which products need promo support?"
- "What should we avoid pushing in ads?"
Required input
Minimum useful input:
- Inventory export with SKU, product name, current stock, and variant.
- Sales export for the last 30, 60, or 90 days.
- Date range and sales velocity.
- Promo calendar or planned campaign notes if available.
Recommended columns:
- SKU
- product name
- variant
- current inventory
- units sold
- revenue
- margin or priority flag if available
- incoming stock quantity and ETA if available
- supplier lead time if available
Before analysis
- Confirm the purpose: prevent stockout, reduce overstock, plan promo, or protect paid traffic.
- Ask for exports if the user only describes inventory from memory.
- Mark missing lead time, incoming stock, and margin data as caveats.
- Do not pretend to run demand forecasting.
Analysis workflow
- Normalize SKU and product names.
- Calculate simple signals where data allows:
- recent sales velocity
- days of inventory remaining
- sell-through risk
- slow mover status
- promo conflict risk
- Classify products:
- stockout risk
- overstock risk
- safe to promote
- do not scale traffic
- needs more data
- Tie risks to marketing action.
- Name what cannot be decided yet. Reorder quantity needs lead time and incoming stock; a promo decision needs margin. Where those are absent, hand the owner the question rather than a recommendation built on a guess.
Decision and evidence standard
Every finding should include:
- Evidence tag:
export, screenshot, url, review_cluster, support_ticket, return_reason, policy, feed_diagnostics, margin_csv, inventory_export, hypothesis, or needs_data.
- Severity: low, medium, high, or critical.
- Confidence: low, medium, or high.
- Business impact: revenue, margin, cashflow, retention, conversion, support_load, or risk.
- Effort: XS, S, M, or L.
- Owner decision: do_now, test, investigate, monitor, ignore, or approval_needed.
If the evidence is weak, mark the finding as hypothesis or needs_data and lower confidence.
Output format
Inventory verdict
Short owner-level summary.
Risk table
| Product/SKU |
Status |
Evidence |
Marketing implication |
Recommended action |
Promo notes
Products suitable for promotion, products to protect, and products to avoid scaling.
Missing data
Fields needed for better confidence.
Example input and output
Input:
- inventory export
- 60-day sales export
- incoming stock ETA
- promo calendar
Good output excerpt:
| Finding |
Evidence |
Severity |
Confidence |
Business impact |
Effort |
Owner decision |
| Bestseller SKU may stock out during planned campaign |
inventory_export, export |
high |
medium |
revenue/risk |
S |
approval_needed |
| Slow-moving variant has high stock and low recent sales velocity |
inventory_export, export |
medium |
medium |
cashflow |
S |
test |
What not to do yet: infer stock risk without inventory or sales exports, or recommend purchase orders without lead time and approval.
Guardrails
- Requires an inventory or sales export. Do not infer stock risk from product names alone.
- Do not replace ERP, inventory planning, or demand forecasting systems.
- Do not recommend purchase orders without lead time, margin, and business approval.
- Do not recommend pushing products that may stock out during the campaign.
- Do not ignore variant-level constraints.
1---2name: inventory-risk-brief-ecommerce3description: Turns e-commerce inventory and sales exports into a practical risk brief for stockouts, overstock, promo conflicts, and traffic allocation. Use when the user provides inventory CSVs, stock reports, sell-through data, or asks which products are risky to promote.4---56# Inventory Risk Brief - E-commerce78## Use this skill when910The user wants an inventory-aware growth or promo review from exports.1112Common requests:1314- "Review this inventory export."15- "Which products are at risk of stockout?"16- "Which products need promo support?"17- "What should we avoid pushing in ads?"1819## Required input2021Minimum useful input:2223- Inventory export with SKU, product name, current stock, and variant.24- Sales export for the last 30, 60, or 90 days.25- Date range and sales velocity.26- Promo calendar or planned campaign notes if available.2728Recommended columns:2930- SKU31- product name32- variant33- current inventory34- units sold35- revenue36- margin or priority flag if available37- incoming stock quantity and ETA if available38- supplier lead time if available3940## Before analysis41421. Confirm the purpose: prevent stockout, reduce overstock, plan promo, or protect paid traffic.432. Ask for exports if the user only describes inventory from memory.443. Mark missing lead time, incoming stock, and margin data as caveats.454. Do not pretend to run demand forecasting.4647## Analysis workflow48491. Normalize SKU and product names.502. Calculate simple signals where data allows:51 - recent sales velocity52 - days of inventory remaining53 - sell-through risk54 - slow mover status55 - promo conflict risk563. Classify products:57 - stockout risk58 - overstock risk59 - safe to promote60 - do not scale traffic61 - needs more data624. Tie risks to marketing action.635. Name what cannot be decided yet. Reorder quantity needs lead time and incoming stock; a promo decision needs margin. Where those are absent, hand the owner the question rather than a recommendation built on a guess.6465## Decision and evidence standard6667Every finding should include:6869- Evidence tag: `export`, `screenshot`, `url`, `review_cluster`, `support_ticket`, `return_reason`, `policy`, `feed_diagnostics`, `margin_csv`, `inventory_export`, `hypothesis`, or `needs_data`.70- Severity: low, medium, high, or critical.71- Confidence: low, medium, or high.72- Business impact: revenue, margin, cashflow, retention, conversion, support_load, or risk.73- Effort: XS, S, M, or L.74- Owner decision: do_now, test, investigate, monitor, ignore, or approval_needed.7576If the evidence is weak, mark the finding as `hypothesis` or `needs_data` and lower confidence.7778## Output format7980### Inventory verdict8182Short owner-level summary.8384### Risk table8586| Product/SKU | Status | Evidence | Marketing implication | Recommended action |87|---|---|---|---|---|8889### Promo notes9091Products suitable for promotion, products to protect, and products to avoid scaling.9293### Missing data9495Fields needed for better confidence.9697## Example input and output9899Input:100101- inventory export102- 60-day sales export103- incoming stock ETA104- promo calendar105106Good output excerpt:107108| Finding | Evidence | Severity | Confidence | Business impact | Effort | Owner decision |109|---|---|---|---|---|---|---|110| Bestseller SKU may stock out during planned campaign | `inventory_export`, `export` | high | medium | revenue/risk | S | approval_needed |111| Slow-moving variant has high stock and low recent sales velocity | `inventory_export`, `export` | medium | medium | cashflow | S | test |112113What not to do yet: infer stock risk without inventory or sales exports, or recommend purchase orders without lead time and approval.114115## Guardrails116117- Requires an inventory or sales export. Do not infer stock risk from product names alone.118- Do not replace ERP, inventory planning, or demand forecasting systems.119- Do not recommend purchase orders without lead time, margin, and business approval.120- Do not recommend pushing products that may stock out during the campaign.121- Do not ignore variant-level constraints.