Order confirm rules
By default, every order is confirmed by hand. Order confirm rules let you automate that. Each rule is an order rule with an outcome, and the first rule that matches decides what happens to the order. For the fields a rule can match on, see that page; this page covers what confirm rules do with a match.
When they run
Section titled “When they run”Confirm rules are evaluated automatically after an order is fully placed, usually within a few minutes (and never less than a minute). During busy periods, such as a large ticket launch, it can take longer. The order stays as placed until then.
Outcomes
Section titled “Outcomes”Each rule has an outcome:
- Approve. Confirm the order automatically, taking payment just as confirming it by hand would.
- Review. Hold the order for a person to check. Registration staff are notified.
- Cancel. Reject the order. Any pending payment authorisation or hold is released, so the customer is never charged. No money has been taken at this point, so there is nothing to refund. Reserved stock (tickets, add-ons) is released for others to buy.
If no rule matches, the order is left for manual approval, which is the default.
The outcome is recorded
Section titled “The outcome is recorded”Whatever happens, a note is added to the order’s history saying which rule matched and, in plain words, why (for example, “order total is at least 4000”). Personal details are never written to the note. When no rule matches, the history records that the order was left for manual approval.
The blocklist is checked first
Section titled “The blocklist is checked first”Before any confirm rule runs, the order’s attendees are checked against the attendee blocklist. If any attendee matches, the order is held for review straight away and the confirm rules are not evaluated. See that page for how matching works.
A confirm rule can belong to a single event, or apply across every event as a tenant-wide default. An event’s own rules and the tenant-wide defaults are combined into one list and evaluated together in priority order; they are not kept separate. So a default rule with a lower priority number runs before an event rule with a higher one. When an event rule and a default rule share the same priority, the event rule is considered first.
Active dates
Section titled “Active dates”A rule can have a start and end date, so it only applies during a set window.
Priority
Section titled “Priority”Rules run in priority order (lower numbers first, and negative numbers are allowed so you can put a rule before the defaults). The first rule that matches decides the outcome, so put more specific rules above more general ones.