Configure scheduled payments
Scheduled payments let guests pay for a package in installments over time instead of paying the full amount at purchase. Zenoti collects each installment automatically on its due date from the guest's saved payment method.
Scheduled payments and auto-renewal are independent features — you can use scheduled payments without auto-renewal, and vice versa. Auto-renewal is documented separately in Configure auto-renewal.
Audience: Administrators and managers who configure package billing options.
On this page
- Before you begin
- Steps
- Configure installments
- Review the payment schedule
- Bulk charge pending collections
- Worked example
- Tips
- Troubleshooting
- Related articles
Before you begin
Permission: Edit under Packages in the Administrator section of the security role — Allows configuring scheduled payment plans.
- The organization setting that enables scheduled payments must be active. The scheduled payments configuration is unavailable when the setting is off.
- The package must already exist. See Create a series package.
- A saved payment method (card on file or equivalent) is required for automatic collection. Guests without a saved payment method will have collections fail on their due date.
- Commission type restriction: Scheduled payments cannot be enabled when the package's Commission Type is set to Flat amount or Percentage of revenue. If these commission types are selected, the scheduled payments configuration is blocked. Adjust the commission type before enabling scheduled payments. Additionally, item-level commissions are not supported for series packages with scheduled payments — these are product-enforced restrictions.
Steps
Configure installments
Open the package and locate the scheduled payments configuration on the General tab.
Configure the installment fields:
Field Description Number of Installments Total number of payments the guest makes, including the first payment collected at purchase. First Payment Amount Amount collected at purchase. Can equal the standard installment, or a larger initial payment to secure commitment. Payment Frequency Numeric count (for example, 1,2,4) combined with Frequency Type to form the cadence.Frequency Type Unit — days, weeks, or months. For example, 1frequency +month= monthly;2frequency +week= every two weeks.Click Save.
Review the payment schedule
After configuring installments, Zenoti generates a payment schedule showing each installment's date and amount. Staff can view this schedule from the guest's package details after sale.
Remaining balance after the first payment is split evenly across the remaining installments. For example: $600 package, 6 installments, $150 first payment → 5 subsequent installments of $90 each, collected on the configured cadence.
Bulk charge pending collections
Administrators can manually trigger pending scheduled collections in bulk from the Packages Payment report:
- Open the Packages Payment report.
- Filter to pending scheduled payments.
- Select payments with the checkboxes.
- Click the bulk charge control to process all selected payments.
Successful charges update the package balance. Failed charges remain pending and are retried per the organization's retry policy.
Worked example
- Package price:
$600 - Number of Installments: 6
- First Payment Amount:
$150 - Payment Frequency:
1, Frequency Type:month
Result: guest pays $150 at purchase, then $90 per month for 5 months. Total: $150 + (90 × 5) = $600.
Tips
- Set First Payment Amount higher than later installments to secure commitment. A 25%-of-total first payment is a common choice for multi-month packages.
- Match frequency to validity. A 3-month package should not have a 6-month payment schedule — installments that extend past expiry invite chargebacks.
- Confirm card-on-file before you sell. Scheduled payments without a saved method fail the first collection.
Troubleshooting
- "Scheduled payments are not being collected." Check: (1) the organization setting is still active, (2) the guest's saved card is valid (not expired), (3) the package is not frozen. Frozen packages pause collections.
- "A scheduled payment failed and the guest was not notified." Notification delivery depends on the organization's notification templates. See Configure package notification templates.
- "The guest wants to change their payment schedule." Editing an existing schedule may require additional permission depending on the organization's payment-schedule authorization setting. See Configure package settings.
- "The guest wants to pay off the balance early." Use the guest's package details to manually collect the remaining balance. Future installments are cleared automatically.