⚙️ Service Configuration Page Settings Explained

On the Service Configuration Page, you control how customers select dates, how far in advance bookings can be made, and the buffer time you need before and after each booking. Each setting below includes clear explanations and real examples so even non-technical users can understand exactly how each option works.

⛔ Cutoff Days

What it does:
Cutoff Days determine how close to today a customer can book. This helps prevent last-minute bookings if you need preparation time.

🟦 Info
Cutoff Days represent how many days in advance a booking must be made.

How it works:

• The value you enter is the number of days required before the booking date.

• Any date inside that window becomes unavailable.

Examples:

• Cutoff = 1 → customers can book starting tomorrow.

• Cutoff = 0 → customers can book today (same-day bookings allowed).

📅 Future Days

What it does:
Future Days determine how far into the future customers can book, helping you control long-range scheduling.

🟧 Default Behavior
If this field is left blank, the system automatically allows bookings up to the maximum limit of 712 days (nearly 2 years).

How it works:

• Enter a number to set the maximum days ahead customers can choose.

• Leave it blank to enable the full 712-day window.

Examples:

• Future Days = 7 → customers can only book within the next 7 days.

• Future Days = 60 → availability is limited to 60 days ahead.

• Blank → customers can book up to 712 days into the future.

🚚 Lead Time

(sometimes referred to as buffer time)

What it does:
Lead Time adds extra days before a booking begins. This allows you time to prepare—such as gathering materials, packing, or scheduling staff.

🟩 Default
Lead Time defaults to 0 days, meaning no preparation buffer is added unless you enter one.

🟦 Note
Lead Time cannot be set per variant.

How it works:
When a customer selects a start date, the system blocks off the necessary preparation days before that date.

Example:
If Lead Time = 2 and the customer chooses January 5, the system reserves January 3–4 for preparation.

🧹 Lag Time

(sometimes referred to as buffer time)

What it does:
Lag Time adds extra days after a booking ends, giving you time to clean, reset, or prep for the next customer.

🟩 Default
Lag Time defaults to 0 days, unless you enter a buffer.

🟦 Important
Lag Time is not visible to the customer.
Only the merchant can see these extra days inside the booking details.

🟦 Also Important
Lag Time cannot be set per variant.

Example:
If a service is booked Jan 1–5 and Lag Time = 3, the system blocks Jan 6–8 for turnaround time.
Customers will simply see these days as unavailable.

📂 Date Range Section

The following settings—Minimum, Maximum, and Count—appear in the Date Range section of the Service Configuration Page.

🟥 Requirements
These settings only apply when:
1. Booking Type is set to Product, and
2. Your Booking Widget allows customers to select a date range.

🔽 Minimum

What it does:
Minimum sets the fewest number of days a customer must select when choosing a date range.

How it works:
If the customer selects fewer days than the minimum allows, the system blocks the selection.

Example:
If Minimum = 2, customers must book at least 2 days.

🔼 Maximum

What it does:
Maximum sets the largest number of days a customer is allowed to choose when selecting a date range.

How it works:
Customers cannot select a range longer than the maximum limit you set.

Example:
If Maximum = 14, customers may book up to 14 days, but no more.

🔢 Count (Days vs. Nights)

What it does:
Count determines whether the booking duration is calculated in Days or Nights.

How it works:

• Days → Calculates the number of full days selected.

• Nights → Calculates the number of overnights between the selected dates.

Examples:

• Days: Jan 1–3 = 2 Days

• Nights: Jan 1–3 = 2 Nights