ZenotiHelp

Quick Book β€” Service Data Model (New Kiosk)

ZTZenoti Docs Team Updated October 19, 2026 10 min readGuide

The Quick Book feature on the new kiosk allows guests to rebook services from a previous visit in a single step. This article explains how each service entry in the Quick Book list is structured, which fields control what guests see and can select, and how the data round-trip supports accurate wait-time and add-on handling during the Quick Book flow.

Important: Quick Book is a legacy kiosk feature. On the new kiosk, Quick Book strings exist in the codebase but the feature does not surface in the guest flow. Do not enable or document Quick Book as available to guests using the new kiosk. For legacy kiosk Quick Book, see Quick Book β€” Rebook Previous Services on the Kiosk.

Audience: Zenoti administrators and implementation consultants who need to understand how Quick Book service entries are constructed, which fields gate service availability, and how optional display data is handled when booking history is incomplete.


On this page


Before you begin

  • Quick Book is supported on the legacy kiosk only. The new kiosk does not present Quick Book to guests.
  • To understand the full service booking flow on the new kiosk, see Book services at new kiosk.
  • Familiarity with how services are configured in the service catalog is helpful. For service pricing and configuration, see service pricing and configuration.
  • No special permissions are required to read this reference. Admin kiosk settings require standard Edit permission on the Organizations security object.

How a Quick Book service entry is structured

When a guest reaches the Quick book section of the legacy kiosk, the kiosk retrieves the guest's booking history and assembles a list of previously booked services. Each entry in that list is a single service record that carries all the information the Quick Book screen needs to present the service, determine whether it can be offered, pre-populate the guest's prior selections, and calculate timing.

Each service entry contains:

  • A set of required fields that are always present, regardless of booking history completeness.
  • A set of optional display fields that are populated from the guest's history when available and omitted when the data is not present.
  • A nested add-on list when the original booking included add-on services.

The sections below describe each group in detail.


Required fields and what they control

The following fields are always present on every Quick Book service entry. They govern booking logic, display behavior, and eligibility.

Field What it controls
appointmentId Links this Quick Book entry to the original appointment it was drawn from.
id The unique identifier for the service. Used to look up the service in the catalog when the guest selects it.
hasAddons Indicates whether add-on services were attached to this service in the original booking. When true, the Quick Book flow prompts the guest to review or re-add those add-ons.
isAddon Marks whether this entry is itself an add-on to a parent service rather than a standalone service.
isMandatory Indicates whether the service is required as part of a package or bundle and cannot be deselected.
requestedTherapistGender Stores the provider gender preference the guest specified in the original booking, so the same preference can be pre-selected in the new booking.
parentAppointmentId Identifies the parent appointment when this service was booked as part of a group or linked appointment.
isVariant Indicates whether this service entry represents a specific variant (for example, a 60-minute versus 90-minute version of the same service).
hasVariant Indicates whether the service has variants available, so the Quick Book screen can prompt the guest to choose or confirm a variant.
canBook Controls whether this service appears in the Quick Book list at all. See How the canBook flag controls service availability.
parentId Identifies the parent service when this entry is an add-on or variant child.
parentShowInCatalog Indicates whether the parent service is visible in the service catalog. Used to determine whether the parent can be shown alongside child entries.
enableCatalogFrequency Indicates whether catalog frequency limits are active for this service.
catalogFrequency Stores the booking frequency constraint (for example, once per 30 days) so the Quick Book flow can enforce the same limit as the standard catalog.
enforcePreRequisites Indicates whether this service has prerequisite services that must be booked or completed first.
clubPreRequisites Indicates whether prerequisite services can be grouped together in a single booking rather than requiring separate visits.
showInCatalog Indicates whether this service is currently visible in the service catalog. A service hidden from the catalog is also excluded from Quick Book.
hasFinishingServices Indicates whether finishing services (such as a blow-dry added after a color treatment) are attached to this service.
includesTax Indicates whether the service price shown to the guest already includes tax, controlling how the price is displayed on the confirmation screen.
serviceDuration Stores the duration of the service in minutes. See How service duration is preserved through the Quick Book flow.
skipTherapistSelection When true, the Quick Book flow bypasses the provider selection step for this service and assigns the next available provider automatically.
allowDirectBooking Carries the service's Sell this service as a part of a package or membership only setting, which decides whether the guest must hold a package or membership benefit that covers the service before it can be booked.
authorizeAllowDirectBooking Carries the service's choice for a booking when the guest's package or membership balance is not enough β€” Block or Allow with warning.
isAmenity Indicates whether this service is classified as an amenity (a complimentary or included service) rather than a billable service.
capacityConsumption Records the capacity units this service consumes, used to check room or resource availability when the guest initiates a Quick Book.

Optional display fields

The following fields are present on a Quick Book service entry only when the data is available from the guest's booking history. When the data is absent, the field is omitted (null) rather than defaulting to a placeholder value. The Quick Book screen handles both states gracefully β€” it displays the value when present and renders without it when absent.

Field When populated What it displays
name When the service name can be resolved from the catalog at the time the history is loaded. The service name shown in the Quick book list.
displayName When the service has a separate display name configured in the catalog. Overrides name as the guest-facing label when present.
selectedTherapist When the guest requested a specific named provider in the original booking and that provider is still active. Pre-selects the same provider in the new booking's provider picker.
selectedAddons When the original booking included add-on services. Pre-populates the add-on list for review during the Quick Book flow. See Add-on services in Quick Book.
price When a price can be resolved for the service at the time the history is loaded. Displays the service price in the Quick book list alongside the service name.

Note: The Quick Book screen displays the Quick book heading and shows the service name and price when both name and price are present. When either field is absent β€” for example, if the service price varies by provider and no provider has been selected yet β€” the screen renders the entry without the missing value rather than blocking the guest from selecting the service.


Add-on services in Quick Book

When a guest's original booking included add-on services, the selectedAddons field on the parent service entry carries the full list of those add-on service records. Each add-on in the list is itself a service entry with the same field structure as the parent.

This nesting means the Quick Book flow can pre-populate the guest's complete prior booking β€” the primary service and all its add-ons β€” in a single step. The guest sees the add-ons already selected and can confirm or remove them before proceeding.

The hasAddons flag on the parent entry signals to the Quick Book screen that an add-on list is present. The screen uses hasAddons to decide whether to show the add-on review step. If hasAddons is false, the add-on review step is skipped even if selectedAddons is present for another reason.

Note: Each add-on entry in selectedAddons also carries its own canBook flag. An add-on with canBook = false is not offered to the guest even if it was part of the original booking. For details, see How the canBook flag controls service availability.


How the canBook flag controls service availability

The canBook flag is the single control that determines whether a service from the guest's booking history appears in the Quick book list.

  • When canBook is true, the service is eligible to appear in the Quick Book list and can be selected by the guest.
  • When canBook is false, the service is excluded from the Quick Book list entirely β€” it does not appear as an option regardless of whether it is in the guest's booking history.

A service may have canBook = false for several reasons, including:

  • The service has been deactivated or removed from the catalog since the guest's last visit.
  • The service is not available at the current center on the current day.
  • The service requires a prerequisite that has not been satisfied.
  • The service is flagged as not eligible for self-service booking at the kiosk.

Important: Because canBook is evaluated at the time the Quick Book list is built β€” not at the time of the original booking β€” a service that the guest booked previously may not appear in Quick Book if its eligibility has changed. This is expected behavior and is not a configuration error.


How service duration is preserved through the Quick Book flow

The serviceDuration field records the duration of the service in minutes and is carried through the entire Quick Book data round-trip without modification. This field is used specifically by the wait-time calculation that runs during Quick Book confirmation.

When a guest selects a service in Quick Book and proceeds to confirmation, the estimated wait time shown on screen is calculated using serviceDuration from the Quick Book entry β€” the same value that was recorded for the original booking. This ensures that the wait-time estimate the guest sees during Quick Book is consistent with the timing used when the appointment was first created.

Note: If the service duration has been updated in the service catalog since the guest's last booking, the serviceDuration in the Quick Book entry may differ from the catalog's current duration. The Quick Book flow uses the preserved value to maintain consistency with the original booking's timing. The updated duration applies to new bookings made through the standard catalog flow.


Tips

  • When a service stops appearing in a guest's Quick Book list, check the canBook flag first. The most common cause is that the service has been deactivated or its availability at the center has changed.
  • If a guest's previously booked provider does not appear pre-selected in Quick Book, verify that the provider is still active at the center. The selectedTherapist field is only populated when the provider is active at the time the history is loaded.
  • Services with variants use both isVariant and hasVariant to control the Quick Book prompt. If hasVariant is true, the guest is prompted to confirm or choose a variant even in Quick Book. Ensure that variant configuration in the service catalog is current to avoid unexpected prompts.
  • The catalogFrequency and enableCatalogFrequency fields ensure that frequency limits you configure in the service catalog are also respected in Quick Book. If a guest cannot select a service they previously booked, frequency limits are a likely cause.
  • For service pricing and configuration details that affect which fields are populated at Quick Book time, see service pricing and configuration.

Troubleshooting

A service from the guest's last visit does not appear in the Quick Book list.

Check the following in order:

  1. Confirm that canBook is true for the service. A service with canBook = false is excluded from the list regardless of booking history.
  2. Confirm that showInCatalog is true for the service. Services hidden from the catalog are also excluded from Quick Book.
  3. Check whether catalog frequency limits are active (enableCatalogFrequency is true) and whether the guest has exceeded the allowed booking frequency (catalogFrequency).
  4. Verify that the service is active and available at the center on the current day.

The service name or price is missing from the Quick Book entry on screen.

The name and price fields are optional and are omitted when the data cannot be resolved. Possible causes:

  • The service has been renamed or repriced in the catalog since the guest's last visit. The Quick Book screen renders without the missing value rather than showing an error.
  • The service price varies by provider and no provider has been pre-selected at the time the Quick Book list is built.
  • For guest-facing display issues, see New kiosk FAQ.

Add-ons from the original booking are not pre-populated in Quick Book.

Verify the following:

  1. Confirm that hasAddons is true on the parent service entry. If false, the add-on review step is skipped.
  2. Confirm that each add-on in selectedAddons has canBook = true. Add-ons with canBook = false are excluded even if they were part of the original booking.
  3. Confirm that the add-on services are still active and available at the center. Deactivated add-ons are excluded from the list.

Was this article helpful?
Your feedback helps us improve our documentation.