01
Step 1
Pull the current sellable quantity per SKU, the threshold in force for that SKU, the sales channels each SKU is published on with its recent demand, and the replenishment status including any open purchase order and its expected date.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
List products below relevant stock thresholds
A merchant has a threshold policy in place, but the stock list comes out alphabetically, so urgent lines sit next to harmless ones. In this case, the immediate task is to list products below relevant stock thresholds. The workflow should produce a list ordered by channel exposure and replenishment risk, giving the quantity and restock status for each item.
Topic
Stock Availability and Alerts
Target keyword
shopify low stock report
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 list products below relevant stock thresholds.
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: [current sellable quantities per SKU, the threshold in force per SKU, the sales channels each SKU is published on with recent demand, and replenishment status including open purchase orders and expected dates]. Include a SKU when its sellable quantity sits below its own threshold, compute the shortfall against that threshold, rank the rows by channel exposure and replenishment risk rather than by name or SKU code, and separate SKUs at zero quantity into their own section because the response differs from topping up.
Return a low-stock list with quantities and restock status 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
Include a SKU when its sellable quantity sits below its own threshold, compute the shortfall against that threshold, rank the rows by channel exposure and replenishment risk rather than by name or SKU code, and separate SKUs at zero quantity into their own section because the response differs from topping up.
03
Step 3
Deliver a low-stock list with quantity, threshold, shortfall, replenishment status and expected receipt date per row, stamp the extract time on the report with the last inventory movement included, and reconcile the row count against the count of SKUs below threshold in the supplied inventory extract.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Which threshold applies to a SKU?
The one in force for that SKU in the merchant's records, and where none is set the SKU is listed in a separate group rather than judged against a borrowed number. A global value misrepresents SKUs whose demand differs sharply.
Why are zero-stock SKUs held apart?
A SKU at zero needs a different response, meaning a hold, an unpublish or an urgent receipt, from one that merely needs topping up, and mixing them lets urgent lines sit beside harmless ones. Zero rows keep their own ordering and their first observed date.
How current must the underlying data be?
The report carries the extract time and the last movement included, and is refreshed at the cadence the merchant sets against how fast stock moves. A report older than the last movement can show stock that has already sold through.
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.