Out-of-stock badges appear and disappear, and the merchant cannot tell a short absence from a delisting. In this case, the immediate task is to track observable competitor stock changes. The output should compare availability across dated snapshots and separate temporary gaps from permanent removal.
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 track observable competitor stock changes.
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: [availability messages, affected variants, pre-order or restock badges and observation dates captured from the same listing URL under one fixed shipping destination on every pass].
Compare each pass against the one before it and treat availability as a visible signal rather than a quantity, holding an item for several consecutive later snapshots before calling it removed and recording cases where nothing was displayed as not-shown rather than as available.
Return a competitor change log and specific opportunities to investigate recording which stock signals were visible 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.
Capture the availability message, the variants affected, any pre-order or restock badge and the observation date from the same listing URL on every pass under one fixed shipping destination so regional differences are not read as changes, including passes where no stock message is displayed at all.
Compare each pass against the one before it and treat availability as a visible signal rather than a quantity, holding an item for several consecutive later snapshots before calling it removed and recording cases where nothing was displayed as not-shown rather than as available.
Deliver a stock change log separating temporary absences from likely removals with the pass dates behind each judgement, verify that every tracked listing was reachable on every pass, and list observations where the page itself failed to load.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Only observed. A badge or message is what the seller chose to display, not an inventory level, so every row records the visible wording and its date and never a quantity the page never displayed. That keeps later readers from treating a signal as a count.
Not until consecutive later snapshots still show the item missing from its position, since a temporary shortage returns. A single absent pass is recorded as an interval gap rather than as a judgement, which is why the monitoring cadence has to stay regular.
Variant by variant, because one size being unavailable while the others still ship is a different signal from the whole listing going dark. Collapsing them into a single row hides exactly the case worth watching from one pass to the next.
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.