> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# What is ticket exchange and rescheduling?

> Learn how ticket exchanges differ from transfers, cancellations and refunds.

**A ticket exchange changes an existing booking into a different eligible ticket or performance; rescheduling is usually a change of date or timeslot.** The system must preserve a coherent order and admission history while accounting for availability, price differences and business rules.

## What is exchanged?

An exchange can move a buyer between performances, seats, ticket categories or dates. A reschedule is often a narrower move to another occurrence of the same product. Some operations cancel and rebook instead of modifying a ticket in place; either approach needs to avoid producing duplicate valid credentials.

| Decision             | Example                                               |
| -------------------- | ----------------------------------------------------- |
| **Eligibility**      | Exchanges allowed up to 24 hours before a performance |
| **Capacity**         | Replacement seat or slot must actually be available   |
| **Price difference** | Collect an upgrade payment or determine refund policy |
| **Fees**             | Decide whether original booking fees are retained     |
| **Entitlements**     | Revoke or update the original admission credential    |
| **Communication**    | Confirm the new event, time, seat and terms           |

The table illustrates policy questions, not mandatory industry rules.

## Why do exchanges become complicated?

A single order may contain a group booking, add-ons or a ticket already transferred to someone else. A seat can be held temporarily during checkout but sold before the change completes. Tax, fee, insurance and payment-plan treatment may differ between original and replacement items. An organiser therefore needs a defined sequence of inventory, payment and credential changes.

Consider a customer moving two tickets from Friday to Saturday when only one seat remains. The experience should explain the constraint before voiding anything. A failed payment for an upgrade should not strand the customer without a valid original ticket.

## What makes the customer experience good?

Show the original and replacement details together, the all-in amount due or refundable, deadlines and whether the change is final. Confirm the result through the same channels used for initial ticket delivery. Staff need an audit trail showing what changed and when, not just the new order snapshot.

## Which metrics matter?

Measure completed exchanges, failed attempts caused by unavailable inventory, support interventions, payment errors and erroneous double admissions. If exchanges are permitted only through support, distinguish policy restrictions from poor software self-service.

## Related explanations

#### [How do customers manage tickets after purchase?](/distribution-access/how-do-customers-manage-tickets-after-purchase)

Distribution & Access · Delivery and after purchase

#### [How should venues handle ticket delivery failures?](/distribution-access/how-should-venues-handle-ticket-delivery-failures)

Distribution & Access · Delivery and after purchase

#### [How do mobile wallet tickets work?](/distribution-access/how-do-mobile-wallet-tickets-work)

Distribution & Access · Delivery and after purchase

[More in Distribution & Access →](/distribution-access)