Spark playbook scenarios · Spark: AI Store Assistant

Detect newly launched products in competitor catalogs

A merchant sees competitors changing their assortments or prices but lacks a consistent record of what changed. In this case, the immediate task is to detect newly launched products in competitor catalogs. The workflow should produce a competitor change log and specific opportunities to investigate, using the merchant's actual records and constraints.

Topic

Competitor Research and Monitoring

Target keyword

track competitor product launches

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 detect newly launched products in competitor catalogs.
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: [provide named competitor URLs, dated public listing snapshots, comparable SKUs and observation period]. Match comparable products, compare snapshots, distinguish launches from edits and summarize price or stock changes without treating public signals as verified sales.
Return a competitor change log and specific opportunities to investigate 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

Scenario & problem

When does this scenario usually come up?

Start with the business context, the trigger, and the expected output before moving into the execution 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.

Step 1

Start with named competitor URLs, dated public listing snapshots, comparable SKUs and observation period.

Step 2

Match comparable products, compare snapshots, distinguish launches from edits and summarize price or stock changes without treating public signals as verified sales.

Step 3

Deliver a competitor change log and specific opportunities to investigate; verify the result against the supplied records and identify unresolved inputs.

FAQ

Common questions when running this scenario

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

Can public competitor listings reveal actual sales?

Usually they do not establish verified sales. Public rankings, reviews and stock messages are signals, not a complete transaction record.

Why compare identical variants?

A size, pack quantity or specification difference can look like a price change when the offers are not equivalent.

What information is needed to investigate this use case?

Start with named competitor URLs, dated public listing snapshots, comparable SKUs and observation period. These inputs establish the relevant scope and help separate an actual issue from missing information or an unsuitable comparison. Without them, the result should remain a proposed approach rather than a confirmed diagnosis.

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.

Competitor Research and Monitoringanalyze competitor product catalogs