Subscriptions

Understand Subscriptions in Spaces

A Subscription is a longer-running commercial arrangement created when a customer purchases a Product Price with a subscription purchase cadence. Its scheduled workspace use is represented by associated Booking instances. A Booking is one reservation for a defined period; a Subscription groups the commercial arrangement and its recurring reservations.

The customer is a registered Skedular user who purchased the Product. Purchasing does not make the Customer an Organization member. See Customers for the full distinction.

When a purchase creates a Subscription

Spaces treats these purchase cadences as subscription cadences: Daily, Weekly, Fortnightly, Monthly, Two months, Quarterly, Four months, Five months, Six months, and Yearly. A Price with one of these cadences is handled as a Subscription purchase; auto-renewal remains a separate option when the Price supports it. A one-time or timed booking Price uses the Booking flow instead.

The purchase cadence sets the length of the Subscription cycle. Recurring Booking instances are materialized for workspace use within that cycle, while the organization’s billing mode and billing cycle determine when invoices are issued. These are related but separate settings. See Products and pricing for configuring Prices.

View and manage Subscriptions

Operators find Subscriptions in the organization Subscriptions area. The list can be filtered by Subscription status and payment status, and is ordered by next renewal. Each row or card can show the Product, Customer, start date, next renewal, renewal setting, quantity, payment method, payment status, and current lifecycle status.

Open a Subscription to review its recurring Booking instances, customer, Product, payment context, renewal details, and cancellation or refund information. Operators can manage eligible payment actions, cancel a Subscription immediately or at the end of the current period where available, and review the associated recurring Bookings.

Subscription lifecycle and payment state

Subscription status and payment status are separate. Operator filters include Active, Cancelled, Expired, Renewal failed, and Paused where those states are present. The interface can also show Ends at period end when cancellation is scheduled.

Payment statuses belong to the recurring Booking or marketplace payment, not to the Subscription lifecycle itself. Operators may see Pending, Confirmed, or Rejected payment states and can use the available payment actions for a recurring Booking. See Billing and payments for payment and invoice workflows.

How recurring Bookings are scheduled

When a Subscription starts, Spaces creates and maintains Booking instances for the current cycle. Instances are added progressively as the cycle is maintained, so operators see current and upcoming instances in the Bookings area and from Subscription details. Each instance keeps its own dates, times, Resources, and payment state while remaining associated with the Subscription.

Booking recurrence and billing cadence are separate. The Subscription purchase cadence determines the cycle, while the recurring flow materializes day-level Booking instances for day-or-longer plans. Skedular generates the first invoice when the Subscription starts for both Upfront and In arrears billing. After that, Upfront invoices follow the configured upfront billing behavior, while In arrears invoices follow the Organization’s billing cycle. The invoice due date is a separate setting that determines when each generated invoice must be paid.

Resource assignment and availability

Subscription Booking instances use the Product’s eligible Resource pool and requested Resource quantity. Resources are assigned to individual Booking instances rather than permanently reserved for the entire Subscription. If the Resource assigned to a future Booking is no longer available, Skedular can use another eligible Resource where one is available. If no eligible Resource can satisfy the required quantity, the future Booking needs operator review; instances with operator overrides are not automatically changed.

Auto-renewal

Auto-renewal is separate from Subscription creation. The customer can choose it when the selected Price supports Subscription auto-renewal, and the Subscription stores that choice. When renewal runs, Spaces reloads the current Product version and looks for compatible pricing for the next cycle. If auto-renewal is off, the current period ends without another renewal; cancellation at period end keeps the current period active before stopping future renewal.

Product and Price changes

Product and Price edits that create a new version apply to new purchases and do not rewrite the active cycle of an existing Subscription. At renewal, Spaces loads the current Product version and matches a compatible auto-renewable Price. If no matching Price remains, renewal fails rather than silently switching to an unrelated Price.

End or cancel a Subscription

For an active Subscription, the interface supports Cancel now and Cancel at period end when those cancellation modes are available. Cancel now prevents new future Subscription billing activity, but does not automatically cancel generated invoices, remove outstanding balances, reverse completed payments, or create a refund. Cancel at period end keeps the current period active and then stops renewal. Disabling auto-renewal is a separate choice that lets the current period finish without starting another one. Cancellation stops future recurring Booking activity according to the selected mode, while past Booking instances remain historical records. Cancellation and refunds are separate decisions; see Refunds for financial outcomes.

Next step

Continue to Billing and payments to configure and manage the payment, invoicing, and accounting workflows associated with commercial Bookings and Subscriptions.