Uses inventory signals for operating decisions
The source works with stock, demand, or reorder information to identify what should be replenished, monitored, or investigated.
Inventory Forecasting Prompt is a copyable AI prompt for Shopify, Amazon, WooCommerce sellers. Use it to estimate stock needs from sales history and draft reorder suggestions. Copy the full instruction, add your inputs and check the result before use.
Turn cleaned sales and supply inputs into a reviewable reorder proposal rather than an automatic purchase order. Using the prompt is simple; judging seasonality, lead times, stockout cost, promotion effects, and working-capital risk requires an experienced operator.
This prompt asks the model to estimate stock needs from sales history and draft reorder suggestions; the points below reflect instructions present in the source text.
The source works with stock, demand, or reorder information to identify what should be replenished, monitored, or investigated.
The source asks for analysis, classification, ranking, or scoring before it reaches a conclusion or next action.
The complete source is shown below. Copy it from the top right to use it.
Act as an inventory planning analyst for an ecommerce business. Given sales history data, generate:
1. DEMAND FORECAST:
- 30-day projection by SKU
- 90-day projection for top sellers
- Seasonality adjustments (month-over-month patterns)
- Confidence intervals (high/low estimates)
2. REORDER RECOMMENDATIONS:
- Which SKUs to reorder this week (stockout risk < 30 days)
- Optimal order quantities (EOQ calculation)
- Lead time buffer recommendations
- Minimum order quantity considerations
3. RISK ASSESSMENT:
- Products at risk of stockout (ranked by revenue impact)
- Overstock items (> 90 days supply)
- Dead stock identification (> 180 days)
4. PROMOTION IMPACT:
- Expected demand spike for planned promotions
- Safety stock adjustment for promo periods
- Post-promotion demand dip estimate
5. CASH FLOW IMPACT:
- Estimated inventory investment needed this month
- Working capital tied up in slow-moving stock
- Liquidation recommendations for dead stock
Focus on actionable reorder dates and quantities. Flag anything that requires immediate attention with ⚠️.Copy a starter instruction, add the required inputs, then run one example and review the output.
Use consistent SKU, date, unit, and currency fields. Separate returns, stockouts, bundles, and one-off promotions. Use this when missing periods and abnormal events are visible rather than silently treated as normal demand.
Use the Prompt above to help me with this task: Clean and label the data.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Use consistent SKU, date, unit, and currency fields. Separate returns, stockouts, bundles, and one-off promotions.
Return a practical result and clearly flag anything that needs human review.[TASK_DETAILS][CONSTRAINTS]Provide lead time, order cadence, MOQ, safety-stock policy, promotion calendar, and known supply constraints. Use this when the recommendation can be traced to explicit assumptions.
Use the Prompt above to help me with this task: State the operating assumptions.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Provide lead time, order cadence, MOQ, safety-stock policy, promotion calendar, and known supply constraints.
Return a practical result and clearly flag anything that needs human review.[TASK_DETAILS][CONSTRAINTS]Ask for base, low, and high demand cases with the formula or reasoning behind reorder dates and quantities. Use this when the output shows uncertainty instead of one false-precision number.
Use the Prompt above to help me with this task: Request a range.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Ask for base, low, and high demand cases with the formula or reasoning behind reorder dates and quantities.
Return a practical result and clearly flag anything that needs human review.[TASK_DETAILS][CONSTRAINTS]Run the same method on an earlier period and compare the forecast with what actually sold. Use this when forecast error is understood by SKU group.
Use the Prompt above to help me with this task: Backtest before buying.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Run the same method on an earlier period and compare the forecast with what actually sold.
Return a practical result and clearly flag anything that needs human review.[TASK_DETAILS][CONSTRAINTS]The generated result is a draft; check claims, numbers and operating conditions against source data before publishing, importing or acting on it.
If the instruction mentions inventory, treat that as an operational step to verify. A pasted Skill cannot change stock records unless a separately configured and approved integration performs that action.
This section identifies the prompt’s creator and source, and marks details that could not be verified.
Public sources do not currently identify the original author. If you created this resource, use the claim entry below to submit evidence.
I am the author — submit a claimNo original publication page or author information was found.
New prompts added weekly. Create an account to get weekly recommendations.
Content checked:
No reviews yet.