Ciwi
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Identify supplier disruptions affecting relevant products

A supplier notice arrives, but nobody knows which SKUs depend on that supplier or how much stock cover remains. In this case, the immediate task is to identify supplier disruptions affecting relevant products. The workflow should produce a disruption log that rates exposure by available cover and alternatives, checked against the stock records.

Topic
Market and Supply Chain Alerts
Target keyword
ecommerce supply chain disruption 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 identify supplier disruptions affecting relevant products.
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: [dated supplier notices, the SKU list each supplier covers, current stock cover for those SKUs, and the alternative sources already on record]. Rate exposure by the cover remaining on each affected SKU and by whether an alternative source exists, not by the wording of the notice, and mark as high exposure any SKU whose cover is shorter than the lead time recorded for its replacement.
Return the disruption log and impact review list 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.
Use in Spark
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.

01

Step 1

Gather the dated supplier notices, the SKUs each supplier covers, the current stock cover for those SKUs and the alternative sources already on record.

02

Step 2

Rate exposure by the cover remaining on each affected SKU and by whether an alternative source exists, not by the wording of the notice, and mark as high exposure any SKU whose cover is shorter than the lead time recorded for its replacement.

03

Step 3

Deliver a disruption log listing the affected SKUs, their exposure rating and the reason for each rating, then check the SKU list and stock figures against the merchant's records and flag any SKU whose supplier could not be identified.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

Does a supplier delay always threaten stock?

No, compare the cover remaining against the replacement lead time first. A delay on a well-covered SKU often needs no action, while a short delay on a thin-cover SKU can consume the whole selling window.

How should an unconfirmed disruption report be treated?

Log it with its source and the date received, then confirm with the supplier before changing any purchase plan. Acting on a rumor early can trigger duplicate orders that fill the very cover you were protecting.

When should customers be told?

Only after the effect on specific orders is known, and then in wording the merchant has approved. A message sent before the impact is clear makes commitments about dates nobody has yet confirmed.

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.

Open Spark product pageBack to Spark scenario library