Step 1
Take a dated catalog snapshot to audit against, the checklist of checks to run, the findings recorded in the previous run, and the product scope and exclusions stated for this run.
The merchant wants one product audit that can be rerun after each catalog change instead of ad hoc spot checks. In this case, the immediate task is to run a repeatable product data audit. The workflow should produce a prioritized product issue report in which every finding carries the evidence recorded during the pass and this run's scope is stated.
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 run a repeatable product data audit.
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: [a dated catalog snapshot, the checklist of checks to run, the findings recorded in the previous run, and the product scope and exclusions stated for this run]. Run the same checklist over every product in scope without reinterpreting it mid-pass, capture the evidence behind each finding as it is found, and tag every prior finding as closed, still open or recurring since the last run.
Return a prioritized product issue report with evidence and suggested fixes 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.
Take a dated catalog snapshot to audit against, the checklist of checks to run, the findings recorded in the previous run, and the product scope and exclusions stated for this run.
Run the same checklist over every product in scope without reinterpreting it mid-pass, capture the evidence behind each finding as it is found, and tag every prior finding as closed, still open or recurring since the last run.
Deliver a prioritized product issue report stating the snapshot date, the scope covered and the number of products checked, then reconcile that count against the snapshot and list any checklist item that could not be judged from the snapshot alone.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
A snapshot freezes what was actually checked, so any finding can be reproduced later. Auditing live data means products can change between the check and the report, leaving findings that nobody can confirm.
Re-test each one and mark it closed, still open or recurring. A finding that reappears points at the import or the workflow that keeps producing it, not at the product itself, and needs a different fix.
Mark it as not assessable instead of passing it by default. An unverifiable item recorded as clean makes the run look more complete than it is, and the gap stays invisible until someone re-checks it.
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.