Advanced Coupon Rules
- View as Markdown Open this page as plain Markdown (opens in a new tab)
- Open in ChatGPT Ask questions about this page (opens in a new tab)
- Open in Claude Ask questions about this page (opens in a new tab)
- Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)
Eventixa Pro extends the standard coupon system with more advanced controls for deciding when and where a coupon can be used.
Advanced Coupon Rules are useful when a basic percentage or fixed discount is not enough and you need tighter control over promotion eligibility.
Available in: Eventixa Pro
Location: Eventixa → Coupons → Add New / Edit Coupon
Related features: Coupons, Tickets, Checkout, Payments, Recurring Events
What Are Advanced Coupon Rules?
Basic coupons normally define:
- Coupon code
- Discount type
- Discount amount
- Event eligibility
- Validity dates
- Usage limits
Advanced Coupon Rules add more detailed conditions around when a coupon can be accepted.
This makes it possible to create more controlled event promotions.
When to Use Advanced Rules
Advanced Coupon Rules are useful for promotions such as:
- Ticket-specific discounts
- Limited campaigns
- Conditional offers
- Private partner promotions
- High-value VIP coupons
- Date-sensitive campaigns
- Restricted registration offers
Use advanced rules when you need more control than a simple event-wide discount.
Open Advanced Coupon Settings
Go to: Eventixa → Coupons
Create a new coupon or edit an existing one.
Configure the basic coupon settings first.
Then review the available advanced rule options provided by Eventixa Pro.
Start with the Basic Coupon
Before adding advanced conditions, configure:
- Coupon code
- Discount type
- Discount amount
- Status
- Validity
- Event eligibility
Advanced rules build on this basic coupon configuration.
Coupon Eligibility
Advanced coupon rules determine whether the current checkout satisfies the coupon’s conditions.
When a customer clicks: Apply
Eventixa validates the coupon before reducing the booking total.
If any required condition fails, the coupon should not be applied.
Event Restriction
A coupon can be limited to specific events.
For example: Coupon: CONF20
Eligible event: Annual Conference
The same code should not be valid for unrelated events.
Ticket-Level Targeting
Where supported, advanced coupon rules can restrict a coupon to specific ticket types.
For example:
Eligible: Standard Event Pass
Not eligible: VIP Pass
This lets organizers discount one ticket tier without affecting every ticket on the event.
Example: Student Ticket Promotion
Suppose an event offers:
- Student Admission
- General Admission
- VIP Pass
You want a discount only for Student Admission.
Configure the coupon to apply only to the eligible ticket.
This prevents the same code from reducing VIP ticket prices.
Multiple Eligible Tickets
A coupon can potentially be configured for more than one eligible ticket depending on the active rule set.
For example:
Eligible:
- General Admission
- Premium Pass
Excluded:
- Staff Pass
Test every ticket combination before publishing the promotion.
Start Date
Advanced promotions can use a defined start date.
For example: Starts: October 1
Before October 1, the coupon should not be accepted.
Expiration Date
Set an expiration date when the campaign should end.
For example: Expires: October 15
After the configured period, Eventixa should reject the coupon.
Time-Limited Campaigns
Date rules are especially useful for:
- Early-bird offers
- Flash sales
- Launch campaigns
- Holiday promotions
- Last-minute registration offers
Usage Limits
Coupons can be restricted by usage count.
For example: Usage limit: 50
After the allowed number of successful uses, the coupon should no longer apply.
Limited Partner Campaign
For example:
Coupon: PARTNER20
Discount: 20%
Usage limit: 25
This allows a partner to distribute a discount to a limited number of registrants.
Usage Limit vs Ticket Quantity
Usage count and ticket quantity are not necessarily the same concept.
One coupon redemption may belong to a booking containing multiple tickets.
Always test your intended multi-ticket scenario before launching a limited campaign.
Minimum Booking Value
Where supported, an advanced rule can require a minimum eligible booking value before the coupon applies.
For example: Minimum subtotal: $100
A booking with a subtotal of $80 would not qualify.
A booking with a subtotal of $120 would qualify.
Why Use Minimum Spend?
Minimum-value rules are useful when you want to encourage larger bookings.
For example: Save $20 when spending $100 or more
This prevents the discount from being used on very small orders.
Maximum Discount Control
For percentage coupons, an advanced configuration can be useful when you want to control the total value of a promotion.
Where supported, a maximum discount prevents an unexpectedly large percentage discount on high-value bookings.
For example:
Discount: 20%
Maximum discount: $50
A large booking would never receive more than the configured maximum.
Customer Eligibility
Where available, advanced coupon rules can restrict who may use the coupon.
Possible eligibility concepts can include:
- Logged-in customer
- Guest customer
- Specific customer context
- Other configured registration conditions
Use customer restrictions only when they are genuinely needed.
Guest Checkout
When Guest Checkout is enabled, advanced coupon rules should still be evaluated during checkout.
If a rule requires an authenticated customer, a guest should not qualify.
If no login-specific rule exists, eligible guests can use the coupon normally.
Logged-In Purchasers
Authenticated customers can use advanced coupons when all configured conditions are satisfied.
Do not assume login alone makes a customer eligible.
All active coupon rules still apply.
Coupon Usage per Customer
Where supported, advanced rules can limit how often the same customer may use a code.
For example: Limit: 1 use per customer
This can help prevent repeated use of a one-time promotion.
Why Use Per-Customer Limits?
This is useful for:
- Welcome offers
- Partner benefits
- Member offers
- One-time campaign codes
It prevents one purchaser from repeatedly claiming the same discount.
Ticket Quantity Conditions
Where supported, advanced coupon rules can depend on the number of tickets selected.
For example: Minimum quantity: 2
The coupon would only apply when at least two eligible tickets are selected.
Group Booking Promotion
A quantity rule can support an offer such as:
Book 4 or more tickets and receive 15% off
This is useful for:
- Group registrations
- Corporate teams
- Family events
- Training sessions
Quantity Rules vs Ticket Quantity Limits
Do not confuse coupon quantity conditions with ticket quantity limits.
Ticket Quantity Limit
Controls how many tickets the customer may select.
Coupon Quantity Rule
Controls when the discount becomes eligible.
These are different settings.
Combination with Ticket Capacity
Coupon rules do not override ticket capacity.
For example:
A coupon may require:
Minimum quantity: 4, but if only two tickets remain, the customer cannot select four merely to satisfy the coupon.
Availability still takes priority.
Coupon Rules and Free Tickets
Advanced coupon conditions do not make a free ticket less free.
If an eligible ticket already costs: $0
there is normally no financial discount to apply.
Coupon Rules and RSVP
RSVP registration does not require a paid ticket transaction.
Advanced coupon rules are therefore generally intended for standard paid-ticket checkout rather than RSVP Going or Not Going.
Recurring Events
Advanced coupons can be used with eligible recurring-event bookings.
The booking still remains associated with the selected occurrence.
Coupon rules do not change recurrence behavior.
Occurrence-Specific Promotions
If your Eventixa configuration supports occurrence-aware coupon restrictions, use them carefully.
For recurring events, test every occurrence that should or should not qualify.
Do not assume a rule applied to one date automatically behaves the same for every occurrence.
Virtual and Hybrid Events
Advanced coupon rules can also apply to paid Virtual and Hybrid event tickets.
The discount affects pricing only.
It does not alter:
- Meeting access
- Reveal timing
- Virtual provider
- Registration eligibility after booking
Coupon and Checkout Session
Applying a coupon does not reset or extend the checkout session.
The standard Eventixa checkout timer continues to apply.
Customers should complete payment before the active checkout reservation expires.
Coupon and Payment Gateway
After Eventixa validates the advanced rules and applies the discount, the final amount is passed into the applicable payment workflow.
For example:
Subtotal: $200
Advanced coupon discount: $40
Final total: $160
The payment gateway should process: $160
PayPal
For PayPal bookings, verify that the final discounted amount matches what PayPal receives.
Stripe
Requires Eventixa Pro
For Stripe bookings, verify that the final charged amount matches the coupon-adjusted total.
Offline Payment
For Offline / Local payments, the organizer should collect the discounted amount displayed by Eventixa.
WooCommerce
When using WooCommerce checkout, test advanced coupon behavior together with the WooCommerce order total.
Make sure the final payable amount remains consistent.
Multiple Coupons
If Eventixa allows only one active coupon per booking in your current workflow, customers should not expect coupons to stack.
If stacking is supported in a future or customized workflow, test rule interactions carefully.
Do not advertise coupon combinations unless you have verified them.
Coupon Priority
When several rules exist on one coupon, the customer must satisfy all applicable required conditions.
For example:
- Correct event
- Eligible ticket
- Within validity period
- Usage limit not reached
- Minimum quantity satisfied
Failure of one required rule should prevent the coupon from applying.
Example: Early-Bird Standard Ticket
Coupon: EARLY25
Rules:
- Event: Annual Conference
- Ticket: Standard Admission
- Discount: 25%
- Starts: September 1
- Expires: September 15
- Usage limit: 100
Only eligible Standard Admission bookings during that period receive the discount.
Example: Group Discount
Coupon: GROUP15
Rules:
- Event: Business Workshop
- Eligible ticket: General Admission
- Minimum quantity: 4
- Discount: 15%
A customer selecting only three tickets does not qualify.
Example: VIP Partner Code
Coupon: VIPPARTNER
Rules:
- Event: Annual Summit
- Ticket: VIP Pass
- Fixed discount: $50
- Usage limit: 20
This creates a controlled partner-only VIP campaign.
Example: Minimum Spend Offer
Coupon: SAVE30
Rules:
- Eligible event: Expo
- Minimum subtotal: $150
- Fixed discount: $30
A $120 booking does not qualify.
A $200 booking qualifies.
Example: One-Time Customer Offer
Coupon: WELCOME20
Rules:
- Discount: 20%
- Per-customer usage limit: 1
- Eligible event: Workshop Series
The same eligible customer cannot repeatedly redeem the offer if the rule is supported and enabled.
Advanced Rules and 100% Discounts
Be especially careful when advanced rules are combined with a 100% discount.
Test:
- Eligibility
- Usage restrictions
- Zero-total checkout
- Booking creation
- Capacity
- Confirmation email
- Payment bypass behavior
A misconfigured full-discount code can create unintended free registrations.
Editing Advanced Rules
You can edit the coupon from: Eventixa → Coupons
Changes affect future coupon validations.
Existing completed bookings should continue to preserve the discount that was applied when they were created.
Changing Rules During a Live Campaign
Avoid changing important rules after distributing a coupon publicly.
For example, changing:
- Eligible ticket
- Minimum quantity
- Discount amount
- Expiration
can lead to customer confusion.
If the promotion must change, communicate the new terms clearly.
Disable Instead of Delete
If an advanced coupon should stop working, disable it where possible.
This is usually preferable to deleting it because historical bookings may still reference the promotion.
Testing Advanced Coupons
Always test the exact rule combinations you configure.
For example, if a coupon requires:
- Specific event
- Specific ticket
- Minimum quantity 3
- Valid date range
test both qualifying and non-qualifying scenarios.
Positive Test
Create a booking that satisfies every rule.
Confirm that:
- Coupon is accepted
- Correct discount is applied
- Final total is correct
Negative Test
Change one rule at a time and confirm the coupon is rejected.
For example:
- Wrong event
- Wrong ticket
- Quantity too low
- Expired date
- Usage limit reached
This helps verify each condition individually.
Multi-Ticket Test
If an event offers several ticket types, test mixed selections.
For example:
- 2 Standard
- 1 VIP
Verify the coupon only discounts the ticket scope it is intended to affect.
Multi-Quantity Test
Test quantities above and below the rule threshold.
For example: Minimum quantity: 4
Test:
- Quantity 3 → Should not qualify
- Quantity 4 → Should qualify
- Quantity 5 → Should qualify
Refunds and Advanced Coupons
When refunding a booking that used an advanced coupon, base the refund on the amount actually paid.
For example:
Subtotal: $200
Coupon discount: $50
Paid: $150
The original transaction amount is $150.
Historical Records
Do not expect edited coupon rules to recalculate past bookings.
Completed bookings should remain historical records of what happened at checkout.
Troubleshooting
Coupon Is Valid but Still Rejected
Review every advanced condition.
One failed rule can make the whole coupon ineligible.
Coupon Works on the Wrong Ticket
Check the ticket targeting configuration.
Minimum Quantity Rule Does Not Work
Verify:
- Eligible ticket
- Selected quantity
- Current availability
- Saved coupon configuration
Usage Limit Appears Reached Too Early
Review how coupon usage is counted in the current workflow, especially for multi-ticket bookings.
Guest Cannot Use Coupon
Check whether an authentication-related rule is active.
Coupon Applies Outside Intended Dates
Review the configured start and expiration dates and the site’s Eventixa timezone settings.
Coupon Discount Is Larger Than Expected
Verify:
- Discount type
- Discount value
- Maximum discount if configured
- Eligible subtotal
Coupon Reduces Wrong Ticket
Review ticket targeting and mixed-ticket checkout behavior.
Gateway Amount Does Not Match
Confirm the coupon was applied successfully before the payment step.
Then compare:
- Checkout total
- Booking total
- Gateway transaction amount
Recommended Advanced Coupon Workflow
- Go to Eventixa → Coupons.
- Create or edit a coupon.
- Configure the basic discount.
- Open Advanced Coupon Rules.
- Select the eligible event.
- Configure ticket restrictions where needed.
- Configure validity dates.
- Add usage restrictions.
- Add quantity or value conditions where applicable.
- Save the coupon.
- Test a valid scenario.
- Test an invalid event.
- Test an invalid ticket.
- Test quantity thresholds.
- Test date restrictions.
- Test usage limits.
- Verify checkout total.
- Complete a test payment.
- Confirm the booking amount.
Recommended Rule Design
Keep the rule set as simple as possible.
A promotion with too many conditions becomes difficult for:
- Customers to understand
- Administrators to support
- Organizers to test
Use only the restrictions that serve a real business requirement.
Important Notes
- Advanced Coupon Rules require Eventixa Pro.
- Advanced rules extend the normal Eventixa coupon system.
- Coupons can be restricted by event and other supported eligibility conditions.
- Advanced rules never override ticket capacity.
- Coupon quantity conditions and ticket quantity limits are different settings.
- Coupon discounts affect price, not attendee quantity.
- Always test both qualifying and failing scenarios.
- Verify final payment amounts with your gateway.
- Full-discount coupons require careful testing.
- Editing rules does not retroactively change completed bookings.
- Disable old campaigns instead of deleting useful historical coupon records.
