Bookings

Understand Bookings in Spaces

A Booking reserves one or more Resources for a defined period. In the Spaces marketplace, the customer chooses a Product and Price; the resulting Booking reserves eligible workspace Resources for the requested time.

Products define the commercial offering. Product Tags guide which Resources are eligible, while Availability determines whether a matching Resource can be reserved.

How Bookings are created

Customer-facing Bookings start when a registered Skedular user purchases a Product through the public Spaces experience. Operators can also create Bookings from the organization management interface using Add Booking. The form’s User selector lists Organization members, not marketplace Customers. It also selects the date and time, Location, and available Resources; the form can be opened with a Location, date, or Resource already selected.

Recurring customer arrangements are represented by Subscriptions and their associated recurring Booking instances. See Subscriptions for that workflow.

View and manage Bookings

Operators find Bookings in the organization Bookings area. The list is shown for a selected date range and can be filtered by Locations, customers, and other available booking criteria. Each Booking card exposes the customer, time, Location, assigned Resources, and any marketplace or Subscription context available to the operator.

Open a Booking to edit its supported details. Depending on the Booking type and permissions, operators can edit a private Booking, update its customer or Resources, remove a Booking, remove a recurring series, or manage marketplace payment actions such as Confirm Booking Payment, Reject Booking Payment, and Make Booking Payment Not Required.

Customers and Bookings

For customer-facing Bookings, the person who purchased or created the Booking is a registered Skedular user acting as the Organization’s Customer. That Customer does not need to belong to the Organization. Operators can see the customer identity exposed by the Booking workflow, such as the person’s name and available contact details. See Customers for the full distinction between Customers and Organization members.

Resource assignment and availability

Product Tags identify the Resource pool eligible for a Product. In marketplace Bookings, Spaces matches that pool and reserves the Resource or Resources required by the Price. In Add Booking, the operator selects from the Available resources for the selected Location and time. If no eligible Resource is available for a marketplace request, the Booking cannot be completed.

Operator-created private Bookings use the Available resources results for the selected Location and time. Existing Bookings, opening-hour rules, and other availability rules determine which Resources are offered. Bookings use 15-minute intervals, and one Booking stays within a single calendar day. When a Product purchase creates a Subscription, its scheduled workspace usage is represented by associated recurring Booking instances.

Booking status and payment

Booking and payment state are separate. Marketplace Bookings expose payment statuses such as Pending, Confirmed, or Rejected where payment is required; these describe payment state, not the Booking itself. Card checkout can complete payment through the customer-facing checkout, while other payment paths may leave payment pending until an operator acts. Operators can see the payment state on the Booking and use the available payment actions there.

Where the Booking requires operator payment handling, the available actions include Confirm Booking Payment, Reject Booking Payment, and Make Booking Payment Not Required.

Payment-provider setup, invoices, refunds, payouts, and accounting configuration belong to Billing and payments, not this Booking guide.

Cancel a Booking

Customers can cancel eligible future marketplace Bookings from the customer-facing Booking details. Operators can remove Bookings from the organization Booking workflow, subject to the Booking type and permissions. The applicable Product cancellation policy determines whether a confirmed payment is refundable; cancellation and refund are separate outcomes. See Refunds for refund handling.

When a Booking is cancelled, the reserved Resource is released for the affected booking period. A cancellation does not automatically mean that a refund is created, especially when payment was never confirmed.

Bookings created by Subscriptions

A Subscription is the longer-running commercial arrangement. Its recurring Booking instances represent the scheduled workspace usage for each cycle. Auto-renewal controls whether the Subscription continues into another cycle; it is not a separate way of creating the Subscription itself. Continue to Subscriptions for subscription management.

Next step

Continue to Subscriptions to manage longer-running arrangements and the recurring Booking activity they generate.