ZenotiHelp

Configure auto-renewal

ZTZenoti Docs Team Updated September 5, 2026 3 min readHow-to

Auto-renewal automatically creates a new package for the guest when their current one expires, keeping continuity for returning customers. Auto-renewal is independent from scheduled payments — you can enable either, both, or neither.

Compliance note. Automatic recurring billing is regulated in many jurisdictions (for example, ROSCA in the United States, similar consumer-protection laws in the EU and Australia). Organizations should ensure guest consent is captured and that a clear cancellation path is available. Zenoti handles the billing mechanics; the organization is responsible for disclosure and cancellation-request handling.

Audience: Administrators and managers who configure package renewal options.


On this page


Before you begin

Permission: Edit under Packages in the Administrator section of the security role — Allows configuring auto-renewal.

  • The package must already exist. See Create a series package.
  • A saved payment method is required. Auto-renewal fails silently when no card is on file.
  • Decide whether renewal should use a discount. Offering a small renewal discount increases retention but reduces per-cycle revenue.

Steps

Enable auto-renewal

  1. Open the package and select the Renewal section on the package edit page.

  2. Enable the Auto-Renew option.

  3. Configure:

    Field Description
    Auto-Renew When enabled, Zenoti automatically creates a new package when the current one expires.
    Renewal Discount A discount percentage applied to the renewal price. For custom packages, this is the discount applied to the renewal of the custom package.
  4. Click Save.

What happens during auto-renewal

This section describes system behavior — there are no user actions beyond the initial configuration above.

  • Near expiry, the auto-renewal scheduler identifies packages with auto-renewal enabled and initiates renewal.
  • For standard series packages, the system creates a renewal package with the same benefits and pricing (minus any configured Renewal Discount).
  • Bundled products are not copied during auto-renewal. If the original package contained bundled products, those products are not included in the renewed package. Service and product benefits (non-bundled) are renewed normally.
  • One-time offer packages: When a one-time offer (OTO) package is configured with auto-renewal, the renewal target must be a membership or package that is not a one-time offer. Renewing an OTO into another OTO is not permitted — this would allow a guest to receive the same one-time benefit again through renewal chaining.
  • For custom packages, the system recreates the package from the underlying template configuration, applying the configured renewal discount.
  • If the original package had scheduled payments configured, the renewal package inherits the same scheduled-payment cadence and collection amounts.
  • If the initial renewal payment fails, the scheduler may automatically freeze the renewed package pending payment recovery. The organization's notification templates determine whether the guest is alerted.

Disable auto-renewal for an individual guest

If auto-renewal is configured at the package template level but a specific guest wants to opt out:

  1. Open the guest's profile and navigate to their Packages tab.
  2. Open the active package and locate the renewal setting on the guest's instance.
  3. Disable auto-renewal on the instance. Pre-scheduled future payments related to renewal are cancelled.

Individual opt-out preserves the current package's remaining benefits; it only prevents the next cycle.

Tips

  • Test auto-renewal with a staff account before enabling for guests. A dry run surfaces notification-template or payment-gateway issues without affecting paying guests.
  • Use a renewal discount to reward continuity. Even 5–10% can materially improve renewal conversion.
  • Align the renewal cycle with scheduled payments. If the package runs 6 months with monthly payments, configure scheduled payments on the renewal too.
  • Audit guests with auto-renewal at least quarterly. Some will have changed cards, moved, or become inactive.

Troubleshooting

  • "Auto-renewal created a duplicate package." Expected when a manual renewal and the scheduled renewal happen close together. Use the refund workflow to remove the duplicate. Consider disabling auto-renewal if staff routinely manually renew.
  • "The renewed package was frozen immediately." The initial renewal payment failed. Collect payment manually from the guest's package details; the package unfreezes on successful collection.
  • "The guest never received renewal notifications." Confirm the organization's notification templates include renewal events and that the guest's email/phone is current. See Configure package notification templates.
  • "I need to stop auto-renewal for all guests on a discontinued package." Deactivate auto-renewal on the package template, then audit active instances to disable per-guest. Future expiries will not renew; existing renewed packages remain as created.
Was this article helpful?
Your feedback helps us improve our documentation.