Step 1
Collect stock receipt records, current stock levels, the demand range the merchant records as usual for each SKU, supplier lead times, existing alert rules, and the named owner who is authorised to change purchasing or pricing.
Stock keeps arriving against weak demand, and no threshold warns anyone before the surplus becomes costly to hold. In this case, the immediate task is to detect accumulating excess stock. The workflow should produce an inventory health analysis and prioritized actions, setting thresholds from usual demand ranges and routing each alert to a named owner.
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.
Act as a Shopify operations specialist.
Help me detect accumulating excess 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: [stock receipt records, current stock levels, the usual demand range recorded per SKU, supplier lead times, existing alert rules and the named owner for each alert]. Trigger an alert when a SKU's stock covers more than the demand expected over its recorded lead time plus the merchant's stated review period, suppress alerts inside the merchant's stated tolerance and for receipts already recorded as planned seasonal builds, and mark as undetermined any SKU whose demand range is missing.
Return an inventory health analysis and prioritized actions 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.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Collect stock receipt records, current stock levels, the demand range the merchant records as usual for each SKU, supplier lead times, existing alert rules, and the named owner who is authorised to change purchasing or pricing.
Trigger an alert when a SKU's stock covers more than the demand expected over its recorded lead time plus the merchant's stated review period, suppress alerts inside the merchant's stated tolerance and for receipts already recorded as planned seasonal builds, and mark as undetermined any SKU whose demand range is missing.
Deliver an inventory health analysis with one row per triggered alert carrying the SKU, the coverage, the threshold breached, the receipt that caused it and the named owner, add prioritized actions, and reconcile the alert count with the receipt records and confirm that every alert reached its owner before the cycle closes.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
From each SKU's own demand range and its recorded lead time, so coverage is judged against replenishment reality rather than one fixed number for the catalogue; a SKU with a long lead time is allowed more cover. Where no demand range is recorded no threshold is derived and the SKU is listed as needing one.
A seasonal build or a consolidated shipment raises stock without any change in demand, so receipts already recorded as planned are matched before an alert is raised. Anything arriving without a matching plan stays an alert, because an unexplained receipt is exactly what the rule exists to surface.
It is routed to the person authorised to change purchasing or pricing, with the SKU, the coverage and the causing receipt attached. An alert with no named owner is treated as undelivered rather than closed, since a signal nobody can act on leaves the surplus sitting in the warehouse.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
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.