Step 1
Gather the reporting day's orders and refunds with their timestamps, the store timezone, the currency and conversion basis, and the sales definition to apply.
Yesterday's sales are reported before the day has fully closed in the store's own timezone. In this case, the immediate task is to produce a reconciled daily sales report. The workflow should produce a sales report with definitions and reconciliation notes, using the merchant's orders, refunds and the reporting day.
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 produce a reconciled daily sales report.
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 reporting day's orders and refunds with their timestamps, the store timezone, the currency and conversion basis, and the sales definition to apply]. Close the day on the store's own timezone boundary rather than the reader's, normalise every order to that definition and that day, and keep the still-open day in a separate partial line that is never compared with completed days.
Return a sales report with definitions and reconciliation notes 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.
Gather the reporting day's orders and refunds with their timestamps, the store timezone, the currency and conversion basis, and the sales definition to apply.
Close the day on the store's own timezone boundary rather than the reader's, normalise every order to that definition and that day, and keep the still-open day in a separate partial line that is never compared with completed days.
Deliver the daily report with a reconciliation note listing each adjustment between the source orders and the reported figure, restate and mark as revised any earlier day changed by a late refund or a captured payment, and confirm the day is complete before it enters any trend.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Yes, but only as a partial line kept apart from completed days, because comparing it with finished days understates the latest period. The report states the timezone boundary and the timestamp it was produced at, so the reader knows what is still missing.
Every adjustment between the source orders and the reported total, with why it was made: refunds, currency conversion, excluded test orders and late captures. Written that way, the same note makes tomorrow's report comparable instead of a fresh negotiation over the number.
Restate it and mark the revision, with the reason and the previous value. Silent changes stop readers trusting earlier versions, whereas a visible revision history lets a trend be read without wondering whether the past moved underneath 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.