Configure redemption controls
Redemption controls are admin-configured policies that shape how front desk staff apply package benefits at checkout. They include limits on how often a guest can redeem, where redemption is allowed, whether services must be used in a specific order, and how edge cases (same-day sale, no-show fees, transferred credits) are handled.
Day-to-day staff redemption procedures are documented in Redeem package benefits. This article covers the admin configuration side.
Audience: Administrators and managers who configure package redemption policies.
On this page
- Before you begin
- Redemption frequency
- Cross-center redemption
- Sequential service order
- Same-day purchase and redemption
- No-show and cancellation fees paid from packages
- Transferred credits
- Honoring benefits past expiry
- Tips
- Troubleshooting
- Related articles
Before you begin
Permission: Edit under Packages in the Administrator section of the security role — Allows configuring redemption policies on packages.
- Several redemption controls depend on organization-level settings (managed by your Zenoti administrator). Confirm the settings with your admin before relying on a control.
Redemption frequency
The redemption frequency control enforces a minimum time between benefit redemptions. For example, setting frequency to 7 days means the guest can redeem once per calendar week, regardless of remaining balance.
- Set the frequency on the benefit in the package (see Configure package benefits).
- The Frequency Scaling Factor refines the calculation. For example, a factor can compress or expand the frequency window per service.
Cross-center redemption
Cross-center redemption is a two-tier check:
- An organization setting must globally enable cross-center package redemption.
- The package-level redemption restriction must permit the redemption at the target center. The restriction accepts three policies: allow redemption at any center; restrict to the center where the package was sold; restrict to centers within the same zone.
Both checks must pass. If either is off, the redemption is blocked.
Redemption during appointment booking
The Allow package redemption at the time of appointment booking setting controls when package benefits can be applied relative to the appointment:
| Appointment day | Setting value | Redemption behavior |
|---|---|---|
| Current date | Enabled | Redemption allowed at checkout |
| Current date | Disabled | Redemption allowed at checkout |
| Future date | Enabled | Redemption allowed immediately after booking (before the appointment occurs) |
| Future date | Disabled | Redemption allowed during checkout at time of payment |
Configure at: Configuration > Packages > "Enable package redemption at the time of appointment booking".
When cross-center redemption is disabled
When the organization setting that enables cross-center package redemption is disabled, the following behaviors apply:
- The Package indicator on the Appointment Info panel appears only if the guest purchased a package at the current center and the package is active.
- The Appointment block shows the package icon only if the guest purchased a package at the current center.
- Clicking the package link in the Appointment Info panel shows all active packages for the guest, but the option to redeem appears only for packages purchased at the current center.
- Auto-apply at checkout triggers only for packages purchased at the current center.
- The POS screen shows only active packages purchased at the current center.
- Partial payments are allowed only at the center where the package was originally purchased.
Sequential service order
When services have Order Number values assigned (see Configure package benefits), guests must redeem services in the specified sequence:
- Services with Order Number
-1can be redeemed in any order. - Services with a positive integer must be redeemed lowest-to-highest. If the guest tries to skip ahead, Zenoti blocks the redemption with a message identifying which lower-ordered service must be completed first.
Same-day purchase and redemption
Some organizations configure Zenoti to block redemption of a package on the same calendar day it was sold. Intended behavior: prevent accidental re-redemption by staff processing both the sale and the appointment invoice in one session.
When the block is active, staff can use the previous day's date as the redemption date on the invoice. Consult your organization's policy on back-dating.
No-show and cancellation fees paid from packages
Package benefits can be used to pay no-show and cancellation fees when a matching package is available on the guest's profile. Zenoti auto-applies a qualifying package to cover the fee; if no automatic match occurs (e.g., the fee amount exceeds the package rate), staff can resolve manually or escalate to an administrator.
Transferred credits
Service credits transferred from one guest to another (see Manage package targets) are redeemable at checkout like native credits. The invoice shows the package rate (often $0) as the applied price. Transfers are subject to permissions and organization settings.
Honoring benefits past expiry
An expired package with remaining benefits can be extended so staff can honor the unused benefits:
- Open the guest's profile and navigate to the Packages tab.
- Open the expired package and edit the expiration date.
- Set a new future date.
- The package becomes redeemable again through the new expiry.
Extensions are logged on the package's transaction log. For repeat extensions, see Extend, freeze, and unfreeze a package.
Tips
- Document the organization's same-day and cross-center policies in a front-desk reference guide. Staff confusion on these controls is the most common source of blocked redemptions.
- Set sequential ordering sparingly. It is strict by design — a guest who misses a lower-ordered service at one visit cannot catch up at the next. Use only when the order truly matters clinically or programmatically.
- Audit expiry extensions quarterly. A pattern of frequent extensions may indicate a pricing or benefit-mix issue.
- Test cross-center redemption in a staging center before enabling organization-wide. The interaction between org setting and package-level restriction is prone to misconfiguration.
Troubleshooting
- "Frequency rule is blocking a legitimate redemption." Confirm the frequency value on the benefit matches the intended policy. Some organizations use frequency for marketing cadence rather than strict enforcement — those values should be lenient.
- "Cross-center redemption is blocked even though the org setting is on." Check the package-level redemption restriction value; it may be set to "restrict to selling center" even though cross-center is on globally.
- "A sequential service cannot be skipped for a valid business reason (guest illness)." Consider whether sequential enforcement is the right model. If the business reason is rare, override via a one-time adjustment; if it is common, remove sequential ordering.
- "Same-day sale and redemption is needed but blocked." Either adjust the organization configuration to allow same-day, or use the previous date on the redemption invoice.