Event organizers often need to provide flexibility for attendees to modify their tickets or add-ons after their initial purchase. In vFairs, you can enable or restrict this functionality based on your event's requirements using specific settings.
This guide will walk you through the available options and their effects, using an example scenario where an attendee initially purchases a $20 Pass.
Step 1: Accessing Ticket Change Settings
- Log in to your vFairs backend.
- Navigate to Registration > Tickets.
- Go to Settings > Ticket Change Rules.
- You’ll find the following toggles:
- Allow Users to Change Their Purchased Tickets
- Hide Purchased Ticket(s)
- Hide Lower-Priced Ticket(s)
- Restrict Changes to Add-ons Only
- Restrict Add-on Quantity Changes
- Disable Coupon Usage
Step 2: Understanding the Toggles
1. Allow Users to Change Their Purchased Tickets
- What it does: Enables attendees to modify their original ticket selection.
- Example: An attendee with a $20 Pass can go back to their registration form and select a different ticket (e.g., a $40 Premium Pass or a $10 Limited Access Pass).
- Use Case: Ideal for events offering multiple ticket tiers where attendees might want to change their ticket or buy additional tickets.
2. Hide Purchased Ticket(s)
- What it does: Prevents attendees from changing their originally purchased ticket but allows them to purchase additional tickets.
- Example: If an attendee already purchased a $20 Pass, they can buy another ticket (e.g., a $40 Premium Pass) but cannot modify the initial $20 Pass.
- Use Case: Useful when organizers want to lock primary purchases but allow supplementary purchases.
3. Hide Lower-Priced Ticket(s)
- What it does: Allows attendees to upgrade to higher or equally priced tickets only.
- Example: An attendee with a $20 Pass will only see tickets priced $20 or above in their options.
- Use Case: Useful for premium events to prevent downgrades.
Important Note: The toggles Hide Purchased Ticket(s) and Hide Lower-Priced Ticket(s) cannot be enabled at the same time.
4. Restrict Changes to Add-ons Only
- What it does: Allows users to modify only their add-ons. The original ticket remains unchanged.
- Example: An attendee with a $20 Pass can add or remove add-ons but cannot change the ticket type or quantity.
- Use Case: Useful for events where ticket selection is final, but add-ons (such as merchandise or meal plans) can be adjusted.
5. Restrict Add-on Quantity Changes
- What it does: Allows users to change the type or distribution of their purchased add-ons without increasing or decreasing the total number of add-ons initially purchased.
- Example: If an attendee originally bought two meal vouchers, they can switch one from a Vegetarian Meal to a Regular Meal, but they cannot add a third voucher.
- Use Case: Ensures attendees maintain their add-on limit while allowing flexibility in selection.
6. Disable Coupon Usage
- What it does: Prevents users from applying discount codes while editing their registration.
- Example: If an attendee initially used a 20% discount code, they will not see the Discount Code field when updating their registration.
- Use Case: Ensures discounts are only applied at the time of initial purchase, preventing misuse when modifying registrations.
Step 3: Attendee Experience
When Allow Users to Change Their Purchased Tickets is enabled, attendees can access their registration form by logging in and navigating to the Upgrade/Downgrade Module.
Here they can:
- Modify their existing ticket selection.
- Remove existing ticket(s).
- Purchase additional tickets.
- Remove existing add-ons.
- Purchase additional add-ons.
When Hide Purchased Ticket(s) is enabled:
- Attendees will not see their previously purchased ticket in the form.
- They can only buy additional tickets or add-ons.
When Hide Lower-Priced Ticket(s) is enabled:
- Attendees will only see tickets priced equal to or higher than their originally purchased ticket.
When Restrict Changes to Add-ons Only is enabled:
- Attendees can only modify add-ons and cannot change their ticket type or quantity.
When Restrict Add-on Quantity Changes is enabled:
- Attendees can modify the type of add-ons but cannot increase or decrease the total number of add-ons they purchased.
When Disable Coupon Usage is enabled:
- The Discount Code field will be hidden when attendees edit their registration.
Step 4: Configuring Settings Based on Event Needs
- Flexible Upgrade/Downgrade: Enable Allow Users to Change Their Purchased Tickets.
- Prevent Downgrades: Enable Allow Users to Change Their Purchased Tickets and Hide Lower-Priced Ticket(s).
- Lock Ticket Selection but Allow Add-on Changes: Enable Restrict Changes to Add-ons Only.
- Maintain Add-on Limits: Enable Restrict Add-on Quantity Changes.
- Prevent Coupon Misuse: Enable Disable Coupon Usage.
Best Practices
Regularly review your ticket configuration before event registration opens.
Communicate clearly with attendees about what changes are allowed.
Test the settings using a sample registration before going live.
By carefully configuring these toggles, event organizers can provide a seamless and flexible registration experience while maintaining control over ticket and add-on purchases.