Step 1
Collect product identifiers, complaint and review text, the merchant's stated classification rules and each item's sales exposure, and record which rules apply mechanically and which require reviewer judgement.
Listings carry claims and material restrictions a small team cannot recheck by hand as the catalog grows. In this case, the immediate task is to organize product compliance signals for further review. The workflow should produce a prioritized review queue with alert thresholds, built from the complaint text, classification rules and exposure data supplied.
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 organize product compliance signals for further review.
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: [product identifiers, complaint and review text, the stated classification rules, sales exposure, and units shipped per item]. Sort signals into the stated categories, weighing recurring reports against units shipped rather than raw counts, and route each product onto the queue as a signal pending confirmation rather than a confirmed violation.
Return a prioritized review queue with alert thresholds, confirmed against the supplied records 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 product identifiers, complaint and review text, the merchant's stated classification rules and each item's sales exposure, and record which rules apply mechanically and which require reviewer judgement.
Sort signals into the stated categories, weighing recurring reports against units shipped rather than raw counts, and route each product onto the queue as a signal pending confirmation rather than a confirmed violation.
Deliver a prioritized review queue with alert thresholds per category, the classification rule used for each entry and the judgement-based entries marked, then confirm the queue against the supplied records before it is assigned to an owner.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
No. A complaint is a signal to review, and the stated rules confirm or dismiss it before any product is classified. Acting on raw complaints without that step pulls items unnecessarily and erodes trust in the queue.
A named owner with an agreed review cadence, otherwise entries accumulate without decisions recorded. Named ownership also keeps the judgement-based entries consistent, because the same reviewer applies the same rules.
It lets another reviewer reproduce the outcome later and shows which entries rest on judgement rather than evidence. When a rule changes, the recorded provenance tells you which past decisions need revisiting.
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.