Change Booking Activity
Step-by-step guide to switching a booking's activity, including equipment migration, repricing, and pricing controls.
Change a booking's activity when a customer wants to swap to a different experience — for example, moving from a 1-hour jet ski rental to a 2-hour pontoon cruise. Resytech walks you through a 4-step wizard that previews equipment, addon, facilitator, and price impact before you commit.
For the conceptual overview, see Change Activity.
Before you begin
- The booking must not be in a Canceled status.
- The new activity must be at the same location as the current booking.
- The new activity must be published (or you'll need to use Force override).
Step 1: Open the Change Activity wizard
- Go to Bookings and open the booking you want to modify.
- Click the actions menu (three-dot icon) in the booking overview.
- Choose Change Activity.
- Pick the new activity from the list of activities at the location. The current activity is excluded.
The wizard advances to the Preview step as soon as you pick an activity.
Step 2: Review the Preview
The Preview is where Resytech tells you exactly what will happen. Take a moment with each section:
| Section | What it tells you |
|---|---|
| New Activity | The activity you're switching to |
| Availability | Whether the new activity runs at the booking's current time slot |
| Price Difference | How the customer's grand total will move |
| Equipment Changes | Which equipment will be preserved, removed, or modified |
| Addon Changes | Which add-ons will survive and which will be dropped (follows equipment) |
| Facilitator Assignments | Whether assigned facilitators will be remapped or dropped |
| Operator-added line items preserved | Count of custom charges / pricing adjustments / trip protection that survive |
| Warnings | Soft warnings (minimum-notice, blackout overlap, coupon revalidation) |
Adjust the customer's total
If the price moves and you want to control it, use the controls in the Price Difference section:
| Control | Effect |
|---|---|
| Match old booking price | When the new activity prices higher, caps the customer at the original total via a pricing adjustment. No-op when prices are equal or lower. |
| Comp amount | Additional dollar discount applied as a pricing adjustment. Composable with Match. |
| Adjust balance automatically (in Advanced) | Recompute the customer's balance owed against captured payments at commit. On by default — turn off only when reconciling outside Resytech (cash refund, external platform). |
The "Operator adjustment" and "Effective change" rows update live as you tick the boxes — verify the final customer total before committing.
Step 3: Select equipment (if needed)
If the Preview flagged Requires equipment selection, click Select Equipment to move into the Equipment step.
- Automatic migration — if you don't change anything, Resytech keeps compatible equipment from the original booking and drops incompatible items.
- Manual selection — tick equipment, set quantities, and pick add-ons explicitly. The cart prices add-ons at the same quantity the booking will store (one per equipment unit by default, capped at the addon's per-equipment limit).
Click Next to advance — to Reschedule if needed, otherwise to Confirm.
Step 4: Select a new time (if needed)
If the new activity isn't available at the booking's current time, the Reschedule step opens with suggested slots grouped by:
- Today — same day as the booking
- This week — within 7 days
- Later — beyond 7 days
Resytech searches 7 days first and expands to 30 if fewer than 3 slots are found, so you don't dead-end on weekly or seasonal activities. You can also pick custom dates with the date-range picker above the grid.
Pick a slot, then click Confirm Change.
Step 5: Force override conflicts (advanced)
If Resytech would normally block the change but you need to push it through anyway, expand the Advanced section in the Preview and tick Force override conflicts.
Force unlocks:
- Activity isn't yet published
- Activity isn't available at the proposed time (skips the Reschedule step entirely)
- Equipment overcommit and other cart-validation failures
Force does not unlock canceled bookings, cross-location moves, or negative comp amounts — those would corrupt booking data. Every overridden conflict is recorded in the audit log.
When Force is on, the Confirm Change button appears immediately in the Preview footer regardless of whether reschedule or equipment selection would otherwise be required.
What happens on commit
- Equipment is migrated based on Preview/Equipment step decisions.
- Facilitator assignments are remapped where the same person staffs the new activity; otherwise dropped.
- Pricing is recomputed using the new activity's rates, fees, and any OTA markup from the original booking.
- Coupons and gift cards are revalidated against the new activity — kept and reapplied if still valid, silently dropped if not.
- Operator-added line items (custom charges, pricing adjustments, trip protection, tips) are preserved.
- Any Match old booking price or Comp amount adjustments are written as a pricing adjustment line item.
- The booking row is updated (activity, time, totals, optionally balance).
- A
Booking Activity Changedworkflow event fires to subscribers. - Connected calendar integrations are re-synced in the background.
- An
activity.changedevent lands in the booking's event log with the full diff.
Tips
- Use Preview religiously. It surfaces addon loss, facilitator drops, and balance drift that operators most often miss. The whole point of the wizard is to make those consequences impossible to overlook.
- Match old booking price beats manual comp. If you're going to absorb the upgrade, the toggle is one click and the audit log records the intent clearly. Manual entry in the Comp field is for partial absorption.
- Custom line items survive automatically. Damage deposits, trip protection, manual pricing adjustments — they all carry across. Don't re-add them after the change.
- Coupons may quietly disappear. If a coupon was restricted to the old activity, it'll be dropped. The Preview warns you when revalidation will run; check the Effective change to confirm.
- Force is for power users. Most operators should never need it. When you do use it, the audit log records exactly what conflicts were waved through.
Common questions
Can I change the activity on a canceled booking? No. Cancel-state is a hard invariant — Force override doesn't unlock it. Move the booking back to Pending or Confirmed first.
Can I move a booking to a different location? No. Locations have their own timezones, fee configurations, and equipment inventories. A cross-location move would corrupt all three. Create a new booking at the other location and cancel the original.
What happens to my custom line items? They survive. The system preserves any operator-added line items (Custom, Custom1–10, Pricing Adjustment, Trip Protection, Tip). The Preview shows the count so you can confirm.
Will the customer be notified? The activity change doesn't auto-send a notification. If you want the customer to know, resend the booking confirmation email after the change or message them directly.
The new activity is more expensive — how do I keep the price the same? In the Preview's Price Difference section, tick Match old booking price. Resytech writes a pricing adjustment for the difference so the customer pays exactly what they paid before.
The customer's payment is captured but the activity change leaves a refund-owed state. What now? With Adjust balance automatically on (the default), the booking's balance will be negative and you can issue a refund from the Payments tab. If you turned it off in Advanced, reconcile manually — the new grand total and old captured payment are both visible.
Can I switch to an unpublished activity for testing? Not by default. Use Force override in the Advanced section. The override is logged in the audit trail.