Overview
WaveRez offers two ways to change ticket prices: default pricing (set under Resources > Trips > Tickets) and Ticket Control (a Calendar Control that overrides pricing for specific date ranges, days of the week, and time slots). Default pricing is the simplest method and is best for partners who change prices on the fly or only need one price year-round. Saving a default change updates the price immediately on the booking portal. Ticket Control is used to set up pricing variations for specific date ranges, such as seasons, holidays, or weekends, without altering the year-round default. Both methods can be used together: defaults handle most pricing, and Ticket Control handles specific dates or times that need different pricing.
The most important rule to understand before changing any price: Ticket Control always overrides default pricing. Once a Ticket Control is set for a specific date and time, the default price will no longer apply to that date and time. Changing the default afterward will not affect any date and time already controlled by a Ticket Control. To change a price that was set with Ticket Control, the only option is to edit it again with Ticket Control. There is no way to revert a controlled date back to using the default.
Which Pricing Method to Use
The right method depends on how often prices change and how the partner wants to manage them.
Use default pricing when:
Prices rarely change, or change permanently when they do
The partner wants the simplest possible setup
Pricing is the same year-round
The partner changes prices on the fly and wants the change to take effect immediately
The partner is not familiar with Calendar Controls and is likely to be confused by the override behavior
Use Ticket Control when:
Pricing varies by season, holiday, day of the week, or time of day
The partner wants to set up pricing variations in advance across a large date range, such as a season, a year, or longer
Pricing differences are stable and do not change frequently
The partner is comfortable using Calendar Controls and understands the override behavior
Use both together when:
The default handles most pricing year-round, and Ticket Control handles exceptions. For example, discounted 9:00 AM and 10:00 AM departures every Saturday, while every other time slot uses the default price.
When both methods are in use, remember the override rule: any date and time covered by a Ticket Control will always use the controlled price. The default only applies to dates and times that do not have an active Ticket Control.
⚠️ Critical Warning: Ticket Control Cannot Be Reverted to Default Once a date and time is set with Ticket Control, the default price will never apply to it again. Changing the default does not affect any date and time controlled by a Ticket Control. To change a controlled price, the only option is to edit it again using Ticket Control. There is no way to "release" a date and time back to using the default price.
Change Default Ticket Prices
Default ticket pricing is set per ticket under Resources > Trips > Tickets. A default price change applies immediately on save and affects every date and time that does not have an active Ticket Control overriding it.
Step 1 — Navigate to Resources > Trips in the WaveRez Admin. The Trips list opens showing all trips on the account.
Step 2 — Click the trip whose ticket price needs to change. The trip's configuration screen opens with several tabs across the top.
Step 3 — Click the Tickets tab. A list of every ticket type configured for this trip appears, each with its current default price.
Step 4 — Locate the ticket to update and edit its price field. Enter the new default price.
Step 5 — Save the changes. WaveRez updates the default price immediately. The new price now appears on the booking portal for every date and time that does not have an active Ticket Control overriding it.
💡 Tip: Check for Active Ticket Controls Before Changing Defaults If a default price change does not appear on the booking portal for a specific date, an active Ticket Control is overriding the default for that date. Default price changes only appear on dates and times that are not currently controlled by Ticket Control. To change those dates, the price must be updated with Ticket Control directly.
Change Prices for a Date Range Using Ticket Control
Ticket Control is found under Calendar Controls > Ticket Control and is used to set pricing variations for specific date ranges, days of the week, and time slots. Only one ticket type can be edited at a time, but multiple time slots, multiple date ranges, and multiple days of the week can all be configured together in a single Ticket Control session. Once a date and time is set with Ticket Control, that price will always apply on that date and time, and the default price will no longer have any effect on it.
Step 1 — Navigate to Calendar Controls > Ticket Control in the WaveRez Admin. The Ticket Control screen opens with selection fields for Activity, Ticket, Schedules, Date Range, and Days of the Week. The Ticket Control screen displays an Activity panel at the top with dropdowns for Activity, Ticket, and Schedules, a Date Range panel in the middle with Date from and Date to fields and an Add new range option, and a Days panel at the bottom with checkboxes for each day of the week.
Step 2 — Select the trip from the Activity dropdown. The list of tickets configured for that trip becomes available.
Step 3 — Select the ticket to control from the Ticket dropdown. Only one ticket type can be selected per Ticket Control session. To change pricing on multiple ticket types, each must be done as a separate Ticket Control session.
Step 4 — Click the Schedules dropdown and select the time slots that should receive the price change. A scrollable list of every active time slot for the selected trip appears with checkboxes for each time. The Schedules dropdown shows each available time slot (9:00am, 9:30am, 10:00am, and so on) with a checkbox to the left, and a Select All option at the top.
Select Select All to apply the price change to every time slot, or check individual times to apply it only to specific times.
Step 5 — Set the date range in the Date from and Date to fields. Both dates are inclusive. To apply the same pricing across multiple non-consecutive date ranges in one session, click Add new range and enter additional ranges.
Step 6 — In the Days panel, confirm or adjust which days of the week the price change should apply to. By default, all seven days are checked. Uncheck any day that should keep its current pricing. For example, uncheck Monday through Friday to apply pricing changes to weekends only. Use Unselect all to clear all days and select only the specific days needed.
Step 7 — Click Edit in the bottom right of the screen. WaveRez opens the price entry screen, which displays each selected time slot as its own block with editable fields for Sell (the price shown on the booking portal), Sell (TripShock) (the price sent to the TripShock OTA channel if integrated), Min, Total, and Total (TripShock). A Bulk Update (All Schedules) row appears at the top to apply the same values across every selected time slot at once.
Step 8 — Enter the new Sell price for each time slot, or use the Bulk Update (All Schedules) row at the top to set the same price across every time slot at once by clicking the down arrow next to the field after entry.
Step 9 — Click Save Changes in the top right of the screen. WaveRez applies the new pricing to every selected date and time. The new prices now appear on the booking portal for the controlled dates and times. To set up additional pricing with the same selections, click Save & Edit New Range instead. This saves the current changes and returns to the date range setup for another round.
⚠️ Batch Update Behavior on Large Selections If the Ticket Control session includes a very large number of line items (each combination of ticket, date, and time counts as one line item), WaveRez switches the edit screen into Batch Update mode. In Batch Update mode, individual date-by-date editing is not available. Only the Bulk Update row appears, and changes are applied to every selected combination at once. There is no exact threshold for when Batch mode triggers; it depends on the total number of line items in the session.
Expected Outcome
After saving a default price change, the new price appears on the booking portal immediately for every date and time not covered by a Ticket Control. After saving a Ticket Control price change, the new price appears on the booking portal for every selected date, day of the week, and time slot within the chosen date range. The controlled price will continue to apply on those dates and times until edited again with Ticket Control. Changing the default afterward will not change them.
Troubleshooting
Symptom: A default price change is not appearing on the booking portal for certain dates. Cause: An active Ticket Control is overriding the default for those dates. Ticket Control always wins over default pricing, regardless of when the default was changed.
Resolution: Navigate to Calendar Controls > Ticket Control and edit the price for the affected dates and times directly using Ticket Control. There is no way to revert a controlled date back to the default. The only way to change a controlled price is to edit it with Ticket Control.
Symptom: A Ticket Control was set up for a date range but the new price is only showing on some of the selected dates or times. Cause: The Ticket Control session likely entered Batch Update mode due to a large number of line items, and Bulk Update was used without confirming it applied to every block, or the selection inadvertently excluded some times or days. Batch mode is triggered by the total number of ticket-date-time line items in a session.
Resolution: Return to Calendar Controls > Ticket Control, reselect the same activity, ticket, schedules, date range, and days, and verify the current prices on the edit screen. Re-apply pricing where needed. To avoid Batch mode on the next attempt, narrow the date range, reduce the number of selected time slots, or split the work into multiple smaller Ticket Control sessions.
Symptom: The partner wants to remove a Ticket Control and have a date go back to using the default price. Cause: There is no method in WaveRez to revert a controlled date and time back to using the default price. Once Ticket Control has been applied to a date and time, that date and time will always use a controlled price.
Resolution: Edit the Ticket Control for the affected dates and times and manually set the price to match the current default. The control will still technically exist, but the price displayed will match the default. If the default later changes, the previously controlled dates will not change with it and will need to be edited again with Ticket Control.
Symptom: Only one ticket type's price was updated in a Ticket Control session even though multiple were selected. Cause: Ticket Control only allows one ticket type per session. The Ticket dropdown is a single-select field.
Resolution: Run a separate Ticket Control session for each ticket type that needs a price change. The same Activity, Schedules, Date Range, and Days selections can be reused for each session.