Change Activity

Change a booking's activity when a customer wants to switch to a different experience — for example, swapping a 1-hour jet ski rental for a 2-hour pontoon cruise. Resytech walks you through a 4-step wizard that previews every consequence before you commit: equipment changes, addon impact, facilitator reassignment, price difference, and any conflicts.

When to use this

Activity changes are different from rescheduling (same activity, new time). If only the time is changing, use the Reschedule tab instead.

The 4-step wizard

Open the Change Activity dialog from the booking's actions menu. The wizard adapts to what the change actually requires:

Steps 3 and 4 are skipped automatically when they're not needed. Most "switch in place at the same time" changes go Select → Preview → Confirm.

What the Preview shows

The Preview step is the heart of the wizard. It surfaces every consequence before you commit so there are no surprises.

Equipment changes

Each piece of equipment on the booking is classified:

Addon impact

Add-ons attached to Preserved equipment survive. Add-ons attached to Removed equipment are dropped — and the preview lists them explicitly so you see exactly which add-ons (and their pricing) will disappear. Operators frequently miss this when equipment is removed; the explicit addon row makes it impossible to overlook.

Facilitator assignments

Activity-specific facilitator roles don't carry across activities automatically. The preview shows what will happen to each existing facilitator assignment:

Preserved operator line items

A small callout shows the count of operator-added line items (custom charges, pricing adjustments, trip protection, tips) that will survive the change. These don't get regenerated — they ride through the activity change intact.

Soft warnings

The preview surfaces non-blocking warnings the operator should see:

• Minimum-notice window — proposed time is inside the new activity's customer-facing notice cutoff
• Blackout overlap — proposed time overlaps an activity blackout
• Coupon / gift card — will be re-validated against the new activity and may not apply

These are warnings, not blocks — operators are expected to override them deliberately when the situation calls for it.

Pricing controls

The Preview shows the new activity price change computed by repricing the booking against the new activity. Below that, three controls let the operator shape the customer-facing total:

Match old booking price

When the new activity prices higher, check Match old booking price to cap the customer at the original total. Resytech writes a negative pricing adjustment equal to the increase so the customer pays exactly what they paid before. No-op when the new activity prices the same or lower — Resytech never artificially raises a customer's price.

Comp amount

Enter a positive dollar amount to apply an additional discount as a pricing adjustment. Composable with Match — e.g., match the old price and take an extra $20 off.

Adjust balance automatically

On by default. The customer's balance owed is recomputed as GrandTotal − captured payments at commit time, so an increase shows up as money owed and a decrease shows up as a refund-due (negative balance).

The toggle lives in the Advanced section of the Preview step — turn it off only when reconciling outside Resytech (cash refund, third-party platform) or in a multi-step manual accounting flow. The Preview shows a yellow warning when it's off so you remember to reconcile manually in the Payments tab.

If you absorb the full delta with Match + Comp, the Preview replaces the balance narrative with a green "Customer total unchanged — no balance reconciliation needed."

Coupon and gift card revalidation

When the booking carries a coupon or gift card, Resytech revalidates it against the new activity at commit time:

• Valid for the new activity → coupon discount or gift card amount is reapplied to the new pricing
• Not valid for the new activity (e.g., coupon restricted to specific activities) → silently dropped, booking's coupon/gift-card fields are cleared

The preview warns when revalidation will run so you're not surprised by the post-change total.

Suggested time slots

When the new activity isn't available at the current time, the Reschedule step opens with suggested slots already loaded. Slots are grouped by day-bucket for fast scanning:

• Today — same day as the original booking
• This week — within 7 days
• Later — beyond 7 days

Resytech searches a 7-day window first and expands to 30 days if fewer than 3 slots are found, so weekly or seasonal activities don't dead-end with "no slots available". You can also override the date range manually to search any window.

Force override

For situations where Resytech would normally block the change but the operator knows better, tick the Force override conflicts checkbox under the Preview step's Advanced section.

Force unlocks:

• Activity isn't yet published
• Activity isn't available at the proposed time
• Equipment overcommit or other cart-validation failures

Force does not unlock (these are data-integrity invariants):

• Canceled bookings
• Cross-location activity changes (would corrupt timezone / fee / equipment context)
• Negative comp amount (use Manage Line Items to raise a price)

Every overridden conflict is recorded in the booking's event log so incident review can see exactly what was pushed past.

Hard rules

A handful of conditions always block an activity change regardless of operator intent — these would corrupt booking data:

Workflow event

After a successful activity change, Resytech publishes a Booking Activity Changed event to subscribers (CRM sync, calendar feeds, reporting pipelines). The payload includes the old and new activity IDs, old and new times, old and new totals, the price difference, and who made the change.

Audit trail

Every activity change writes an activity.changed event to the booking's event log with:

• Old and new activity UUIDs
• Whether the booking was also rescheduled (and the old/new times)
• Previous and new grand total + balance
• Whether the balance was auto-adjusted
• Match-old-price and comp-amount values, plus the resulting pricing adjustment
• Facilitator changes (Remapped / Dropped / Conflict)
• Whether the change was forced, and a list of overridden conflicts
• The user who performed the change

Related how-to guides

• Change Booking Activity — step-by-step walkthrough
• Reschedule a Booking — when only the time is changing
• Manage Line Items — for custom charges and discounts outside the activity-change flow
• Assign a Facilitator — after an activity change drops a facilitator