Reservation

canonical term: reservation | reference format: RSV_{YYMMDD}_NNNN This document explains what a Reservation is, what data it captures about a guest’s booking, and how it relates to events, payments, and offers.

What Is a Reservation?

A Reservation is a guest’s booking for a specific event. It captures:

Who is coming — name, email, phone
When — which event (show + date)
How many — guest count
What they bought — booking path, offers selected
How much — all pricing computed by backend
Payment status — paid, pending, refunded
Check-in status — arrived, seated, not yet arrived

A reservation is created when a guest completes the booking flow. It lives on after the show — it is the record of what happened.

Reservation vs. Booking Draft

There are two states before a reservation is confirmed:

Term	Meaning
`bookingDraft`	The in-progress reservation while the guest is still in the booking flow. Not yet submitted.
`reservation`	A confirmed booking — guest has submitted and (usually) paid.

The bookingDraft is an ephemeral object in the booking flow. The reservation is a persisted database record that survives after the show.

The Two Booking Paths

Every reservation is on one of two paths:

Path	Meaning	Offers available in Choose Experience
`DINNER_SHOW`	Show + dinner included	Dinner Show Packs
`TICKETS_ONLY`	Show only, no dinner	Ticket Only Bundles

The path determines:

What appears in Choose Experience (offers)
What is included in the base ticket price
What the guest sees on the confirmation

What Happens in the Booking Flow

The guest moves through the conditional booking flow:

Section	What happens	Doc
1	Select event — choose show + date	Select Date
2	Guest count — total attending guests	Guest Count
3	Experience — select offers (bundles, packs, add-ons)	Choose Experience
4	Menu review — confirm the active menu PDF	Menu Review
5	Conditional add-ons — Tickets Only + No Extra Bundle	Add-ons
6	Guest details and personal requests	Guest Details
7	Medical and dietary notes	Guest Details
8	Payment — redirect to OnePay	Payment
9	Confirmation — reservation confirmed, payment recorded	Confirmation

By confirmation, the bookingDraft becomes a reservation.

What a Reservation Records

Guest Information

The primary guest’s contact details — used for confirmation email, WhatsApp updates, and operational contact.

guestName: "Nguyen Van Minh"
guestEmail: "minh.nguyen@example.com"
guestPhone: "+84 912 345 678"
specialRequests: "Vegetarian options for 2 guests. It's our anniversary."

Booking Details

showEventId: "01ARZ3NDEKTSV4RRFFQ69G5FAV"
guestCount: 4
bookingPath: DINNER_SHOW

Offer Selections

What the guest added in Choose Experience. These are stored as offerSelections on the reservation:

offerSelections:
  - offerId: "01ARZ3NDEKTSV4RRFFQ69G5FAV"
    offerName: "The Celebration Pack"
    quantity: 1

Pricing Summary

All pricing is computed by the backend. The frontend displays it but never recalculates.

priceSummary:
  baseTickets: 4 × 1,390,000 = 5,560,000
  dinnerPack: The Celebration Pack = 960,000
  promoDiscount: -0
  total: 6,520,000

Payment Status

paymentStatus: PAID
paidAt: 2026-06-01T14:32:00Z

Check-in Status

checkInStatus: NOT_CHECKED_IN
# Transitions: NOT_CHECKED_IN → CHECKED_IN → SEATED

The Three Identifiers of a Reservation

Identifier	Example	Purpose
`id` (ULID)	`01ARZ3NDEKTSV4RRFFQ69G5FAV`	Machine identity — joins, API
`reference`	`RSV_260603_0001`	Internal ops identifier
`guestReference`	`HOL_260603_0001`	Guest-facing identifier — shown on confirmation, used for support

The guestReference (e.g. HOL_260603_0001) is what the guest uses to identify their booking — it is shorter and more memorable than the internal reference.

Reservation Status Lifecycle

DRAFT → CONFIRMED → CANCELLED
         ↓
       PAID ← (after payment)
         ↓
    REFUNDED ← (if refunded)

A DRAFT reservation is abandoned if the guest leaves mid-flow. A CONFIRMED reservation has been submitted. Once payment is recorded, it becomes PAID.

Key Fields

Field	Type	Notes
`id`	ULID	Machine identity
`reference`	string	e.g. `RSV_260603_0001`
`guestReference`	string	Guest-facing, e.g. `HOL_260603_0001`
`showEventId`	ULID	FK to the event
`guestName`	string	Primary guest
`guestEmail`	string	Contact
`guestPhone`	string	Contact
`guestCount`	number	Seats reserved
`bookingPath`	enum	DINNER_SHOW or TICKETS_ONLY — see Pricing Model for the full decision matrix
`status`	enum	DRAFT, CONFIRMED, CANCELLED
`paymentStatus`	enum	PENDING, PAID, REFUNDED
`checkInStatus`	enum	NOT_CHECKED_IN, CHECKED_IN, SEATED
`specialRequests`	string	Dietary, accessibility, occasion
`offerSelections`	array	Offers chosen in Choose Experience
`priceSummary`	JSON	Backend-computed pricing breakdown

​Reservation

​What Is a Reservation?

​Reservation vs. Booking Draft

​The Two Booking Paths

​What Happens in the Booking Flow

​What a Reservation Records

​Guest Information

​Booking Details

​Offer Selections

​Pricing Summary

​Payment Status

​Check-in Status

​The Three Identifiers of a Reservation

​Reservation Status Lifecycle

​Key Fields

​See Also