Settings

Site-wide settings live under Event Tickets → Settings. They apply to every event on the site; per-event options like ticket types, capacity, and sales cutoff are set on the event itself.

Administrators only

The Settings screen requires the manage_options capability. Event authors can reach Check-in and All Tickets but not Settings.

Ticket Code Settings

Every ticket gets a unique code in the format PREFIX-XXXXXX.

Setting	Description	Notes
Ticket Prefix	The prefix before the code — for example TKT, EVT, TICK.	Alphanumeric only, 10 characters max
Code Length	Number of characters after the prefix.	4–12. Longer codes are more unique but harder to type at the door

The screen shows a live example of the resulting code as you change these.

Cart Reservation

Reservations prevent overselling by holding tickets for a customer while they complete checkout.

Setting	Options
Reservation Duration	Disabled, 5, 10, 15 (recommended), or 20 minutes

Customers see a countdown timer while their tickets are held. With reservation Disabled, tickets are only committed when the order completes — which means two people can check out the last ticket at the same time.

Pick a duration that matches your checkout

Longer holds reduce overselling but keep inventory off the market. 15 minutes suits most checkouts; raise it if you use offline payment, where buyers take longer to finish.

Service Fees

Setting	Description
Enable Service Fees	Allows event creators to add a fee to their ticket sales
Default Type	Fixed Amount or Percentage
Default Amount	The pre-filled value
Default Label	What buyers see on the breakdown, e.g. "Service Fee"

The defaults are pre-filled when an event creator enables the fee on a ticket — they can still change them per event. Fees are shown separately to buyers and included in the order total.

See Adding Service Fees for the event-side workflow.

Email Settings

Controls how attendee emails are sent. Batching prevents timeouts and rate limiting on large recipient lists.

Setting	Description	Range
Batch Size	Emails sent per batch. Lower is safer on shared hosting.	10–200
Delay Between Batches	Pause between batches, in seconds. 0 for no delay.	—
Hourly Limit	Maximum emails per hour. 0 for unlimited.	—

Check your host's sending limits

Most shared hosts cap outbound mail per hour. Setting Hourly Limit above your host's cap causes silent failures rather than an error you can see.

These settings govern the Message Attendees widget.

Create Event Form

Controls which optional ticket sub-sections event creators see in the create-event form. Hiding a section only removes the editor UI — previously saved data is preserved.

Setting	What it shows	Default
Time Slots Section	The "Time Slots (Optional Overrides)" section — lets creators override times, price, and capacity for specific dates, and mark individual sessions as sold out	Off
Attendee Information Section	The "Attendee Information" section — lets creators define custom fields collected for each ticket	Off

Both default to off

These sections were hidden in 1.1.0 to streamline the create-event form. Version 1.1.2 added these toggles so you can bring them back without editing templates. Re-enabling Time Slots also restores the per-date Mark as sold out toggle.

Developers can override both in code. The filters run after the settings, so they take precedence:

add_filter( 'voxel_events_create_form_show_time_slots', '__return_true' );
add_filter( 'voxel_events_create_form_show_attendee_fields', '__return_true' );

Each filter receives the current boolean and should return one.

Apple Wallet

Lets attendees add tickets to Apple Wallet. Requires an Apple Developer Program membership ($99/year) and a Pass Type ID certificate.

Setting	Description
Apple Wallet Mode	Disabled, or Enabled (Upload Certificate)
Certificate	The .p12 certificate and its password
Pass Type Identifier	From your Apple Developer account
Team Identifier	From your Apple Developer account
Organization Name	The name shown on the pass, and where it's sourced from
Pass Appearance	Background, foreground, and label colours

The certificate and appearance fields only appear once a mode is selected. See Creating a .p12 Apple Certificate for the full walkthrough.

Google Wallet

Lets attendees add tickets to Google Wallet. Requires a Google Cloud project with the Google Wallet API enabled.

Setting	Description
Enable Google Wallet	Turns the integration on
Issuer ID	From your Google Wallet issuer account
Class ID	The pass class your tickets belong to
Service Account JSON	Credentials for the Google Wallet API

See Configuring Google Wallet for the setup steps.