01
Step 1
Collect for each customer the purchase date, ordered quantity of each consumable SKU, the stated usage cycle per SKU, contact permission status, and any later orders placed for the same SKU.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Draft reorder reminders at a relevant point in the cycle
Consumable products run out on their own schedule, but reminders land too early or after the customer has reordered. In this case, the immediate task is to draft reorder reminders at a relevant point in the cycle. The workflow should produce a replenishment reminder rule and email draft from the merchant's purchase dates, quantities and contact permissions.
Topic
Reorder Reminders and Replenishment Emails
Target keyword
shopify reorder reminder emails
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 draft reorder reminders at a relevant point in the cycle.
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-customer purchase dates, ordered quantities of each consumable SKU, the stated usage cycle per SKU, contact permission status, and later orders for the same SKU]. Compute each line's projected run-out point as the purchase date plus the ordered quantity spread over the stated cycle, set the send date before that point by the merchant's chosen lead, and exclude customers with a later order for the same SKU or without email permission.
Return a replenishment reminder rule and email draft 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
Compute each line's projected run-out point as the purchase date plus the ordered quantity spread over the stated cycle, set the send date before that point by the merchant's chosen lead, and exclude customers with a later order for the same SKU or without email permission.
03
Step 3
Deliver the per-customer reminder rule plus an email draft naming only the SKU and quantity actually ordered, then reconcile the audience against the purchase and later-order records and confirm every excluded customer carries a stated reason.
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 the send date derived for each customer?
The send date is the projected run-out point, calculated as the purchase date plus the ordered quantity spread over the stated usage cycle, moved earlier by the merchant's chosen lead. This keeps the message inside the cycle instead of after it. Where a customer's own repeat history shows a different pace, the recorded pace overrides the generic cycle.
What happens when a customer reorders before the reminder date?
Any later order for the same SKU removes that customer from the audience, because the run-out clock restarts from the new purchase. The rule checks later orders at send time, not only when the rule is built. A reorder on a different SKU does not suppress the reminder unless the merchant's rule says so.
Can one usage cycle serve every product?
No. The cycle is stated per SKU, so customers who bought several products in one order receive reminders timed to each product's own run-out. A single store-wide cycle sends messages too early for slow-use products and too late for fast ones. Where no cycle is stated, the line is flagged rather than timed by assumption.
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.