Automatic enrollment after purchase
Enrollment turns a completed order into an attendee. This page explains exactly when it happens, what it creates, and the case it does not cover.
When it happens
When the order's thank-you page is rendered.
That is the single most important fact about this integration. Enrollment is triggered by the buyer arriving at the order confirmation page after checkout — not by the payment, and not by the order status changing.
It runs once per order.
What it creates
The buyer is added to the event's attendee list with:
| Field | Value |
|---|---|
| Identity | The order's customer account |
| Comments | The customer's order notes |
| Telephone | The order's billing phone |
| Status | Confirmed, or waiting list if the event is full |
They then appear in the Event assistants panel like any other attendee, and can be moved between statuses and exported in the same way.
Capacity applies
The event's Available space is respected. If the event is already full when the order completes, the buyer is enrolled on the waiting list and told so on the confirmation page.
They have paid. Decide before launch how you handle that — refund, next edition, or hold the place — and say so in your terms. See Refunds, cancellations and attendee status.
Duplicate purchases
If the buyer is already registered for the event, the confirmation page says so. Buying twice does not create two attendee records for the same person.
That is a safeguard, not a refund: the order still exists and still needs handling.
The case that is not covered
A buyer who pays but never reaches the confirmation page is not enrolled automatically.
That happens more often than you would expect:
- the buyer closes the tab when the payment provider confirms;
- the payment provider's redirect back to the site fails;
- payment is completed asynchronously — a bank transfer, an offline method, a delayed provider;
- the order is created manually in the admin.
In every one of those, the order is paid and the attendee list is missing someone.
The routine that catches it
There is no notification, so this has to be a habit:
- Weekly, and again before each event, list the paid orders for the event's product.
- Open the event's attendee list.
- Compare.
- For any missing buyer, either ask them to open their order confirmation page from their account, or add the attendee manually.
For a low-volume event this is a two-minute check. For a high-volume one, export both lists and compare in a spreadsheet.
Adding an attendee manually
There is no "add attendee" button. The supported route is to have the person register through the normal form, if the event still shows one, or to reconcile from the order and manage them as a list entry.
Because of that, the reconciliation routine is best run before the event fills, when there are still places to give.
Offline and manual orders
Orders you create in the admin, and payment methods that confirm later, do not pass through the buyer's confirmation page. Treat those as always needing manual reconciliation.
If most of your sales are offline transfers, the built-in enrollment will do very little of the work for you. Plan the manual step as the norm rather than the exception.
Verify
- Complete a purchase from an event page and stay on the confirmation page.
- Confirm the enrollment message appears.
- Confirm the attendee is in the event's list.
- Complete a second purchase and close the tab before the confirmation page loads.
- Confirm the attendee is not created — so you know what the gap looks like.
- Reconcile it manually.