Skip to content

Services & resources

Start in Bookings → Setup. A service is the offer a customer books; a resource is the finite staff, room, vehicle, equipment, location, or pooled capacity needed to deliver it.

Build services and resources separately, then join them with resource requirements. Keeping those concepts separate lets several services share the same staff or equipment without copying schedules.

Create a service

Open Services, choose New service, and set:

  • A customer-facing name, URL-safe slug, description, and booking type.
  • Customer fulfillment: pickup only, pickup or delivery, or delivery required.
  • A period mode:
    • Customer chooses an exact range for rentals or events with flexible start and end times.
    • Fixed duration for appointments with one or more allowed lengths.
    • Fixed named slots for sessions such as “Morning” or “Evening.”
  • The picker increment, timezone, default hours, and setup/cleanup buffers.
  • Capacity, optional party-size limits, minimum lead time, and maximum advance window.
  • Pricing, payment, and approval posture. See Deposits & payment before activating the service.

Keep a service in Draft while configuring it. Active services can be returned to storefronts when their availability permits. Archiving removes a service from active setup while preserving its booking history.

Buffers occupy capacity around the customer-visible period. For example, a 60-minute appointment with 15 minutes after it keeps the resource unavailable for 75 minutes even though the customer sees a one-hour appointment.

Create resources and staff pools

Open Resources & staff pools, choose New resource, and choose the resource type that best describes the constraint. The label is operational; capacity and allocation mode control how it is reserved.

Use:

  • Pooled quantity when interchangeable capacity is enough — for example, four identical rooms or ten class seats.
  • Track exact units when the individual asset matters — for example, a serialized camera or a named vehicle. Add each unit and its identifier; optional SKU and barcode values help your team match the physical asset.

A Staff resource can optionally link to an organization member. This represents that person's bookable availability; it does not change their admin role or permissions. One member's linked staff resources share that member's availability, so overlapping assignments are rejected.

Set capacity to 1 for an exclusive resource. Higher values create a quantity pool. A resource may inherit the organization timezone or use its own valid timezone.

Add resource requirements

Open Resource requirements and add every capacity rule the service needs. A requirement can:

  • name one specific resource, or match any active resource of a type;
  • require a quantity; and
  • let the system choose an eligible resource or require a customer selection when the available-slot response offers choices.

Requirements are evaluated together. A slot is only available when the service window and every required resource have enough capacity.

Recommended setup order

  1. Confirm the store timezone under Settings.
  2. Create resources and exact units.
  3. Create the service and its period/payment posture.
  4. Add the service's resource requirements.
  5. Add recurring availability for both the service and constrained resources.
  6. Add closures under Blackouts.
  7. Search a representative public window before accepting customer bookings.

Who can change setup

Owners and Admins can edit booking setup. Staff can review it, but need the Bookings operations permission group to create or change services, resources, requirements, availability, blackouts, and policies.

Related