01
Step 1
Gather per SKU the sellable stock, committed and inbound quantities, the recent sales rate with the period it covers, and each supplier's recorded lead time.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Trigger reorder reminders from projected stock coverage
Low stock is noticed only after a SKU has run out, too late to reorder in time. In this case, the immediate task is to trigger reorder reminders from projected stock coverage. The workflow should produce a replenishment plan with timing and quantity rationale from the merchant's stock, committed and inbound quantities and per-SKU sales rate.
Topic
Replenishment and Inventory Planning
Target keyword
shopify reorder alerts
Copyable AI prompt
A prompt you can drop directly into Spark
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
ai-prompt.txt
Act as a Shopify operations specialist.
Help me trigger reorder reminders from projected stock coverage.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [per-SKU sellable stock, committed and inbound quantities, the recent sales rate with its coverage period, and each supplier's recorded lead time]. Project each SKU's remaining coverage as available quantity divided by that rate, set the alert to fire while coverage still exceeds the supplier lead time plus the merchant's stated buffer, and mark SKUs whose rate covers an unusual or distorted period as unreliable.
Return a replenishment plan with timing and quantity rationale for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.How to solve
A recommended resolution workflow
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
02
Step 2
Project each SKU's remaining coverage as available quantity divided by that rate, set the alert to fire while coverage still exceeds the supplier lead time plus the merchant's stated buffer, and mark SKUs whose rate covers an unusual or distorted period as unreliable.
03
Step 3
Deliver the replenishment plan with the coverage math and trigger point per SKU, then re-verify the triggered SKUs against the stock and inbound records so no alert rests on a stale count.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
How is remaining coverage computed?
Available quantity, meaning sellable stock plus confirmed inbound minus committed, is divided by the recent sales rate recorded for that SKU, and the period the rate covers is noted beside it. A rate drawn from an unusual week misstates coverage, so such SKUs are marked. The alert point is expressed in the same unit as the lead time so the two compare cleanly.
Why does the buffer sit on top of lead time?
The alert must fire while coverage still exceeds the supplier lead time, or the replacement cannot arrive before stock runs out. The merchant's stated buffer adds room for rate swings and delivery slippage on top of that floor. Without the buffer, any rate increase during the lead time turns into a stockout.
What happens to SKUs with an unreliable sales rate?
They are reported on a watch list instead of the trigger list, with the reason their rate was rejected, such as a period distorted by a promotion or a stockout. They do not fire alerts, because a trigger from a bad rate either panics the buyer or sleeps through a real gap. They move to the trigger list once a clean rate exists.
Related scenarios
Continue with adjacent or same-topic scenarios
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Next step
Want these AI scenarios embedded directly into daily operations?
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.