01
Step 1
Compile, for each product at zero sellable quantity, the inventory record per variant with its location, the published state per channel, the last movement date and the first date the product was observed at zero.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Report products with no sellable stock
A merchant needs one periodic view of every item sitting at zero, grouped in a way that shows where the gap is concentrated. In this case, the immediate task is to report products with no sellable stock. The workflow should produce a report grouping zero-stock items by category and channel, with the affected variants and the last movement date.
Topic
Stock Availability and Alerts
Target keyword
shopify out of stock product 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 report products with no sellable stock.
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: [inventory records per variant with location, published state per channel, last movement dates, and the first date each product was observed at zero]. Group the zero-stock products by category and by channel so the merchant can see where the gap concentrates, count the affected variants per product and mark products where only some variants are affected, and keep a product on the report until stock arrives or it is unpublished rather than dropping it after one cycle.
Return an out-of-stock report with affected variants 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
Group the zero-stock products by category and by channel so the merchant can see where the gap concentrates, count the affected variants per product and mark products where only some variants are affected, and keep a product on the report until stock arrives or it is unpublished rather than dropping it after one cycle.
03
Step 3
Deliver an out-of-stock report with the variant count, the last movement date and the days at zero per product, report inventory state and storefront state as separate columns because a product can be at zero and still visible to customers, and reconcile the product count against the inventory extract used.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Should variants be listed one by one?
Yes wherever variants are tracked separately, because a product-level view hides that only one size or colour is unavailable and leaves the rest looking sold out. Where a product has a single variant, the product row and the variant row are the same.
When does a product leave the report?
When stock arrives or the product is unpublished, not simply when a new cycle runs. The first observed date stays on the row throughout, so the duration at zero remains visible and repeated gaps can be recognised.
Does being on the report mean customers cannot see it?
No, visibility follows the published setting, which can leave a zero-stock product visible and purchasable or hidden. The report therefore carries inventory state and storefront state in separate columns so the two are never confused.
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.