Single Date Event

About this experience

Three things need testing before relying on this:

• Quantity: there is no quantity column or unique attendee/ticket ID. We need a booking for three tickets to establish whether it exports three rows or one.

• Money: Total Order Price is ambiguous. We shouldn’t sum it until we know whether it represents the whole order, ticket line or individual ticket, and whether discounts/refunds are reflected.

• Joining exports: this file has excellent IDs, but we must check whether your actual Shopify exports expose matching IDs at the necessary level. Matching only by order won’t safely allocate revenue where an order contains several events.

I’d pause building the Apps Script sync and test the export route first. Create one test order containing multiple tickets and two different event dates, apply a membership discount, then partially refund or reschedule a ticket and export again.

If those tests pass, you could run your reporting from periodically refreshed exports with no monthly exporter fee. Apps Script would then be useful mainly for removing manual work—not becaus