ReservKitReservKit

Bookings & Availability

Create the times customers can book, verify the public result, and use Booking Detail for changes that affect capacity or money.

Create recurring bookable times

Open: Availability -> Add Recurring Hours

A recurring schedule is the weekly pattern. ReservKit uses it to create the dated future times customers actually select.

  1. 1

    Choose the activity and day

    Select the activity and the weekday this schedule should repeat.

  2. 2

    Set the time window

    Enter the first start, last check-in or window end, and the interval between customer start times.

  3. 3

    Save the recurring hours

    Save the row, then use Refresh Future Times to fill missing dated openings through the generation window.

  4. 4

    Inspect the calendar

    Move through the next operating dates and confirm that the intended activity and start times appear.

  5. 5

    Inspect the public page

    Open the activity-specific booking link and confirm the same future times are available to a customer.

You are done when

  • The Availability calendar shows the expected dated openings.
  • The public activity page shows the intended future start times.
  • Every offered duration can finish within its configured availability window.

How the window and interval work

For a fixed two-hour activity with a 9 AM to 5 PM window and a 120-minute interval, the expected starts are 9 AM, 11 AM, 1 PM, and 3 PM. For duration packages, each selected duration must fit inside the configured window.

Do not assume that the start-time interval adds a separate setup or cleanup buffer. Include operational buffers in the schedule and duration design, then test the resulting times.

Add a one-time opening

Open: Availability -> Add One-Time Opening

  1. 1

    Choose the activity and date

    Select the activity and the specific operating date that needs an exception.

  2. 2

    Set the opening

    Enter the start time, duration or end behavior shown in the dialog, and the capacity available for this opening.

  3. 3

    Save and compare

    Save the opening, inspect it on the Availability calendar, and confirm it appears on the public activity page.

You are done when

  • The one-time opening appears only on the intended date.
  • The public booking page offers the opening with the expected capacity and price.

Capacity and operator-created bookings

Activity capacity limits the number of guests a slot can hold. Fully booked slots stop appearing as available online, and checkout still checks capacity before creating a paid booking.

Owners, admins, and permissioned team members can use Bookings to create operator-side bookings for a walk-in, phone customer, or internal exception. Verify payment state and customer messaging because an operator-created booking is not the same as a completed public Stripe checkout.

Share a booking link

Open: Settings -> Booking Widget

ReservKit provides all-activity booking links and activity-specific booking links, plus supported iframe snippets for the full booking flow. Dedicated calendar-only or activity-card-only embeds are future options.

  1. 1

    Choose the destination

    Use the Public Booking URL for the full catalog or an activity-specific link for one activity.

  2. 2

    Open it signed out

    Use a private window or another device so the test does not depend on operator access.

  3. 3

    Reach a valid checkout

    Select a future time and guest count and confirm the displayed activity, price, requirements, and total.

You are done when

  • The shared URL opens the correct organization and activity selection.
  • A signed-out customer can reach the expected checkout path on mobile.

Cancel a paid booking correctly

Open: Bookings -> open booking -> Booking Detail

  1. 1

    Review the booking first

    Confirm the booking reference, customer, activity, date, payment state, cancellation policy, and amount before taking action.

  2. 2

    Cancel the reservation

    Use Cancel Booking so ReservKit updates status, releases slot capacity, and sends the supported cancellation message.

  3. 3

    Handle money separately

    If money must be returned, use Issue Refund for an eligible Stripe refund. Use Offline Refund only after money was returned outside ReservKit.

  4. 4

    Verify both systems

    Confirm the final booking state in ReservKit and the payment or refund result in Stripe.

You are done when

  • The booking status and released capacity match the cancellation.
  • The Stripe refund state matches the amount recorded in Booking Detail.
Cancellation does not automatically refund a Stripe charge. Treat reservation status and money movement as two related checks.

Review the Payments guide before issuing a full, partial, or offline refund.

Check-in exception

If a checked-in booking still needs to be cancelled, open Booking Detail and use the cancellation flow so status, capacity, customer messages, and any equipment hold stay aligned.