01
Step 1
Collect the sales basis the merchant states for the numerator, the treatment rules for taxes, shipping and discounts, the order statuses that count as valid, and the refund and cancellation records for every period reported.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Report average order value with a defined sales basis
Two teams report different average order values because each handles tax, shipping, discounts and excluded orders its own way. In this case, the immediate task is to report average order value with a defined sales basis. The workflow should produce an AOV analysis and improvement hypotheses verified against the supplied sales records.
Topic
Average Order Value Analysis
Target keyword
shopify average order value report
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 report average order value with a defined sales basis.
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: [the merchant's stated sales basis for the numerator, treatment rules for taxes, shipping and discounts, the order statuses counted as valid, and refund and cancellation records for every period reported]. Apply one stated numerator and denominator across every period, dividing the chosen sales basis by the count of valid orders in the same period, and listing excluded orders with their reason and value beside the result so a reader can rebuild the figure.
Return an AOV analysis and improvement hypotheses verified against the supplied sales 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.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.
02
Step 2
Apply one stated numerator and denominator across every period, dividing the chosen sales basis by the count of valid orders in the same period, and listing excluded orders with their reason and value beside the result so a reader can rebuild the figure.
03
Step 3
Deliver the AOV analysis and improvement hypotheses verified against the supplied sales records, then confirm that the recomputed sales total and order count match the source export, that every excluded order is listed and that the measure is presented beside order count and margin rather than on its own.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
What belongs in the sales figure?
Exactly what the stated basis allows, with taxes, shipping and discounts each declared as included or excluded. Two teams reach different averages from the same orders when one basis is applied and another is described, so the basis is printed beside the number.
Are refunded or cancelled orders excluded?
One stated rule applies to every period, and the treatment of refunds is printed beside the result. Refunds landing after a period closes are noted there too, so an earlier period is never restated without a visible mark.
Can AOV rise while the business weakens?
Yes, because fewer orders lift an average even when total sales fall, so the measure is never read alone. It is shown beside order count and margin, and a rise alongside a falling count is called out as a mix effect.
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.
Next step
Want these AI scenarios embedded directly into daily operations?
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.