Zuddl’s ticketing engine is built for every revenue model—from a free community webinar to a multi-session, paid conference with regional taxes and offline invoices.

​
Creating a ticket

Every ticket starts with a name, a short description, and a type—In-Person, Virtual, or Hybrid—so the platform can determine which venues, badge rules, and analytics slices apply later. Defining the type up front prevents mix-ups, such as a livestream guest appearing on an on-site badge list. It keeps financial reporting clear across access modes and allows you to vary prices or capacities without creating duplicate events. For example, a hybrid two-day tech summit sells a $799 “On-Site All-Access” pass and a $99 “Virtual Keynote” pass; the system automatically issues QR badges for the first group, grants stream access to the second, and reconciles both in one revenue report.

​
Sales window and quantity

Each ticket carries its own inventory count and a start and end-time for sales, ensuring scarcity drives early action while protecting you from overselling seats or bandwidth. Because the timer and quantity gate are automated, you can set a 200-seat early-bird ticket that disappears exactly 30 days before showtime, see it sell out overnight without manual monitoring, and have the standard ticket take over at 12:01 a.m. without lifting a finger.

​
Visibility, hidden, and locked states

A simple “Active” toggle publishes or unpublishes a ticket, “Hidden” removes it from view unless the buyer enters a matching coupon, and “Locked” keeps the tier visible but grayed-out until a code is applied. Hidden tickets power partner bundles and staff passes, while locked tiers can be used for premium upgrades without risking unauthorized use.

A Platinum sponsor can unlock an “Exhibitor Staff” pass with a private code, whereas general attendees just see an unavailable option, planting the idea of an upgrade without exposing the code itself.

​
Bulk purchase limits

Turning on bulk buying and setting minimum and maximum quantities controls inventory hoarding and streamlines corporate procurement. Suppose a consulting firm needs exactly 30 seats; you can let one finance contact pay for all 30 in one transaction, then prevent a different buyer from scooping all remaining stock by capping orders at 50 percent of inventory.

​
Invite list and domain restriction

Tickets can be restricted to specific email addresses in CSV or domains such as “@company.com,” blocking consumer accounts and uninvited guests. This is crucial for confidential kickoffs or customer-only roadshows, where the system refuses a Gmail address and nudges users to enter their corporate email instead, eliminating manual vetting and last-minute cancelations.

​
Field-based conditions

A ticket can hide or reveal itself according to answers collected earlier in the registration flow—job role equals “Developer,” or a session picker includes “Workshop A.” Conditional visibility means attendees never scroll through irrelevant options, while event owners channel each cohort toward the product or session built for them, improving conversion and simplifying choices.

​
Coupons and discounts

Flat or percentage codes, each with its own usage cap and validity window, allow price experimentation without touching the underlying ticket. Marketers can measure channel ROI precisely—“NEWS20” converts newsletter readers at 8 percent—then retire or extend the promotion in real time.

​
Skip-ticketing URL

Appending parameters like ticket_id=abc123&coupon=VIP&skip_ticketing=true to a registration page pre-selects a tier, applies a coupon, and bypasses the ticket step altogether. Targeted emails land users directly on payment page, reducing abandonment, protecting coupon confidentiality, and shortening funnels for high-value prospects such as board members or enterprise leads.

​
Unassigned tickets

When “Assign later” is enabled, a purchaser can pay immediately, lock inventory, and distribute magic links for individual attendees to complete their details later. This feature secures revenue early, accommodates teams that finalize rosters close to the event, and pushes data entry to the people who actually attend, reducing organizer edits and typos.

​
Auto-fill across bulk orders

Admins can mark specific fields—Company, Country, or Job Title—to copy from the first attendee to the rest in a bulk purchase, shaving minutes off checkout and keeping data consistent. For instance, a team lead entering ten colleagues’ registrations fills in company data once, focuses only on names and emails, and submits the form in half the time it would take to complete a blank slate form.

​
Merchant accounts

Native integrations with Stripe and PayPal, and Cybersource accept global cards, wallets, and local methods while handling PCI compliance, multi-currency pricing, and refunds from within the dashboard. A Singapore-based registrant sees SGD, an American sees USD, both clear the same report, and refunds trigger confirmation emails automatically.

​
Offline invoices

Enabling “Pay by Invoice” produces a PDF sent to the purchaser and places the order in a pending state until finance marks it as Cash, Check, or Bank Transfer. Once flagged as paid, the system issues receipts, letting procurement departments that can’t use cards participate without breaking your audit trail.

​
Tax handling

Per-ticket tax rates can be embedded or itemized, and Stripe’s tax module syncs automatically, or you can enter custom rates. An attendee in Germany sees 19 percent VAT calculated precisely, while a U.S. attendee sees no tax, satisfying regional regulations and simplifying reconciliation.

​
Refunds and cancelations

Full or partial refunds issue directly from the Transactions view, re-open inventory if desired, and generate confirmation emails to buyers. If a Pro ticket holder downgrades to a Keynote Only pass, you click “Partial Refund,” inventory adjusts, and both accounting and the attendee receive instantaneous records.