Organizer-level discount codes and affiliate links

[VKronmar]

Right now, discounts and affiliate tracking need to be set up per event. This creates repetitive work and makes it hard to run consistent promotions across multiple events or a full season.

Proposed solution
Add the ability to create and manage discount codes and affiliate links at the organizer level, so they can be applied to multiple events (or all events) under the same organizer.

Key capabilities

1. Create an organizer-level discount code once, then choose:

• Apply to all current and future events, or
• Apply to selected events only

2. Support limited-use discounts across multiple events:

• Global usage cap (example: 100 total redemptions across all selected events)
• Optional per-event cap (example: max 10 per event)

3. Control discount rules:

• Percentage or fixed amount
• Start and end dates
• Ticket type restrictions (optional)
• Minimum order value (optional)

4. Create organizer-level affiliate links:

• Track attribution per affiliate across events
• Reporting by event and aggregated across the organizer

5. Success metrics

• Reduced setup time for recurring promotions
• Fewer misconfigured discounts across events
• Increased affiliate-driven sales due to consistent links and tracking

Acceptance criteria (examples)

• I can create a discount code at organizer level and apply it to multiple events.
• A limited-use discount stops working once the global redemption limit is reached, even if spread across events.
• Affiliate reports can be viewed per event and combined across all organizer events.

[SCodeGit]

Thanks for the detailed proposal!
This is a really valuable suggestion — setting up discounts and affiliate links per event does create a lot of repetitive work, and having organizer‑level controls would definitely streamline things.

I especially like the idea of:

Global vs per‑event usage caps

Flexible discount rules (percentage, fixed, start/end dates, restrictions)

Aggregated affiliate reporting

Next steps:

We’ll review how this fits into the current event/organizer data model.

Identify any dependencies (e.g., ticketing system, reporting layer).

Consider whether this should be rolled out incrementally (discounts first, affiliates later).

If anyone has use cases or examples of how they’d apply organizer‑level discounts, please share — that will help us prioritize and design the feature @SCodeGit