Use AI to produce a sales report with verifiable numbers
Define the period, order statuses and currency, then distinguish sales, usage, refunds and payouts.
Try: “Produce a sales report for our event. Explain the data coverage and do not change anything.”
Define the scope
Provide the page, event or period. Resolve start and end with year and timezone, included order statuses and whether amounts are before or after refunds and fees. A current month is not a closed month.
Workflow for the AI assistant
- Verify the page, event and current time. Look up orders list, orders export, refunds list and relevant analytics reads with hap_help.
- Read through hap_read. Use --output - for order export when supported by current help. A server filename is not a delivered report.
- Follow pagination. State filters, coverage and generation time. Do not describe a sample as the full sale.
- Keep currencies separate. Check units; convert øre to kroner by dividing by 100.
- Distinguish orders, order lines, tickets and unique buyers. More lines do not necessarily mean more orders or people.
Explain the outcome
Sales describe purchases, check-ins describe usage and payouts describe settlement. These figures need not match on the same date.
Show completed sales and relevant refunds separately. Do not subtract refunds again if the chosen net figure already includes them. Do not add overlapping groups’ unique-person counts together.
Finish with totals, period, currency, definitions and unresolved differences. Explain missing history or access; a failed lookup does not mean zero sales.
This is a read task. Do not change bank accounts, fees or payouts through the connection to force the figures to balance. Omit buyer contact data when totals are enough.