In the admin panel
How staff see and handle the orders an app places.
An order is one attendee, tagged with the key's name. It works like a HomeTown ticket: the buyer holds these exact tickets in the seller's app, so staff can rename it, change one ticket's type, void or scan its tickets, but not re-issue or remove it.
It isn't emailed from here unless the order asked for that with sendEmail; one that did shows as sent, queued or unsent like any other attendee, and Send Unsent and Resend Email work on it. It can also show as Unconfirmed: the API was sending it when our email provider stopped answering, so it may or may not have gone. Send Unsent passes those by; staff check with the buyer, then send it with Resend Email if it didn't arrive.
An attendee import with the same email doesn't replace it. Archiving the event moves its orders along with every other attendee, and the API finds them there.
Refunds
Refunds aren't part of the API yet. Until they are, staff void a refunded ticket in the admin panel, and the order then shows it as voided.