– Prevent same email in the owner info
you’ve noticed buyers putting their own email address on every attendee row when buying multiple tickets in a single order — instead of filling in the actual attendee’s email. That’s a problem when each ticket really does need to reach a different person (group bookings, gifts, corporate purchases). This small add-on prevents the lazy shortcut at the form level.
Two flavours — one per mode
We maintain two versions of the add-on, one for each operating mode of Tickera. Use whichever matches your setup:
- Tickera standalone → tickera-same-email-2.zip
- Tickera + Bridge for WooCommerce → bridge_for_woocommerce_disallow_same_attendee_email.zip
Install & activate
- Download the version matching your mode.
- WordPress admin → Plugins → Add New → Upload Plugin, upload the ZIP, install, activate.
- Done. No settings page — the rule is enforced automatically.
What the buyer sees
If a buyer tries to enter the same email address for more than one attendee in the same order, the checkout submit is blocked and they get a validation message asking them to use a unique email per attendee. Same-buyer / different-tickets is fine — the rule only checks within a single submission.
When NOT to install this
This rule makes sense for events where the email genuinely needs to differ per attendee (each attendee gets their own ticket emailed to them, or they need to log in separately to a virtual event platform). For events where:
- One buyer naturally buys multiple tickets for their own family or group (and they collect the tickets to distribute manually),
- You don’t email attendees individually, only the buyer,
- The buyer’s email is genuinely fine as a contact point for the whole order,
… this add-on causes friction at checkout for no benefit. Skip it.
Working differently in Bridge mode
The Bridge version hooks into WooCommerce’s cart validation, so the check runs before the order is created. Tickera-standalone version hooks the Tickera checkout submit handler. Same outcome, different implementation reflecting how each mode runs the checkout.
Related
Was this article helpful?
Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.