Step 1
Start with orders, refund events and amounts, reason codes, product IDs and matched time windows.
Refunds are increasing or concentrating in certain products, but the source of the change is unclear. In this case, the immediate task is to identify products with concentrated refund activity. The workflow should produce a refund breakdown and evidence-based action list, using the merchant's actual records and constraints.
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 identify products with concentrated refund activity.
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 orders, refund events and amounts, reason codes, product IDs and matched time windows]. Separate counts from amounts, account for refund timing and identify recurring product or reason patterns before proposing alerts or fixes.
Return a refund breakdown and evidence-based action 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.Start with the business context, the trigger, and the expected output before moving into the execution steps.
Refunds are increasing or concentrating in certain products, but the source of the change is unclear. In this case, the immediate task is to identify products with concentrated refund activity. The workflow should produce a refund breakdown and evidence-based action list, using the merchant's actual records and constraints.
Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Start with orders, refund events and amounts, reason codes, product IDs and matched time windows.
Separate counts from amounts, account for refund timing and identify recurring product or reason patterns before proposing alerts or fixes.
Deliver a refund breakdown and evidence-based action list; verify the result against the supplied records and identify unresolved inputs.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Either measure can be useful, but they answer different questions. Label the chosen denominator explicitly.
A refund recorded today may relate to an older order. Timing can distort a simple same-day comparison.
Start with orders, refund events and amounts, reason codes, product IDs and matched time windows. 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.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Refunds are increasing or concentrating in certain products, but the source of the change is unclear. In this case, the immediate task is to…
Refunds are increasing or concentrating in certain products, but the source of the change is unclear. In this case, the immediate task is to…
Refunds are increasing or concentrating in certain products, but the source of the change is unclear. In this case, the immediate task is to…
Refunds are increasing or concentrating in certain products, but the source of the change is unclear. In this case, the immediate task is to…
A merchant cannot identify which products are driving revenue or underperforming after accounting for exposure. In this case, the immediate …
A merchant cannot identify which products are driving revenue or underperforming after accounting for exposure. In this case, the immediate …
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.