Configure package settings
Organization-level settings control how your series and day packages operate β from benefit application rules and freeze policies to financial rules, refund behavior, and scheduled payment options. This article describes each setting area and where to configure it.
Audience: Administrators who manage organization-wide package configuration.
On this page
- Before you begin
- Essential package settings
- Package actions
- Package financials
- Redemption gated by amount paid β not by sessions remaining
- Configuration pages
- Related articles
Before you begin
Permission: Edit under Packages in the Administrator section of the security role β Required to modify package settings.
- You must have access to Configuration > Packages at the organization level.
Availability: Package features must be enabled for your organization. When they are not enabled, the Packages menu items do not appear.
Essential package settings
Core toggles that control package behavior across your organization. Navigate to Configuration > Packages.
| Setting | Description |
|---|---|
| Enable package forms | Enable digital form submission for packages using the Zenoti Mobile App. Configure at the center level (not at the organization level) β navigate to the Configuration icon at the center level to find this setting. When enabled, print-based offline forms are no longer supported for packages at that center; all form submissions use the digital workflow. Note: This is the only package setting configured at the center level β all other settings on this page are organization-level. |
| Allow editing package payment schedules from POS | Allow front-desk staff to edit package payment schedules from the POS. Staff can change: (1) date of payment, (2) amount to be paid, and (3) card used for payment. Zenoti recalculates balance amounts and the next payment date based on any changes made. After enabling, an authorization sub-setting becomes available. |
| Allow editing package payment schedules from POS with authorization | Require authorization to edit payment schedules from the POS. When enabled, the staff member must have the Edit_PaymentSchedulePOS check box under Packages in the Administrator section of their security role. Configure at: Configuration > Security > Security roles > the role > Permissions > Administrator > Packages > Edit_PaymentSchedulePOS. Only available when Allow editing package payment schedules from POS is enabled. |
| Enable redemptions on open package | Allow service redemptions against packages that have not yet been fully paid. When this setting is off, redemption is gated by the amount paid β see Redemption gated by amount paid β not by sessions remaining below. |
| Auto-apply package benefits at checkout | When enabled, Zenoti automatically applies a matching package benefit to a service on the invoice at checkout, reducing the invoice total. When disabled, the cashier manually selects which package to redeem against. |
| Service category for day packages | Allow Business Type and Service Category to be assigned when creating day packages and bundles. This setting controls field visibility on the bundle details page as well β not only day package creation. When disabled, both fields are hidden across day packages and bundles. |
| Day package in series package | Allow day packages to be included as items within series packages. When enabled, guests can redeem those embedded day packages from the Appointment Book and the Webstore. One-way door: Cannot be disabled after enabling. |
| Service Bundle day packages | When enabled, a separate Bundles menu item appears in the packages navigation, allowing creation and management of service bundle day packages. This is an organization-level toggle; when it is off, the Bundles menu item is hidden and service bundle day packages cannot be created or sold. Contact your administrator to activate this capability if it is not visible. |
Package actions
Refund rules
| Setting | Description |
|---|---|
| Multiple refunds | Allow individual service refunds for packages containing multiple services. When disabled, only a single refund transaction is allowed per package. |
| Benefit-level refunds | Allow refunds at the individual benefit or service level rather than requiring a full package refund. |
Freeze rules
Configure at: Configuration icon > Packages > Package actions > Freeze rules
The Freeze packages master toggle must be on before any of the sub-settings below take effect.
| Setting | Description |
|---|---|
| Freeze packages | Master toggle for package freeze capability. When disabled, the Freeze and Unfreeze actions are hidden from the package details panel and all settings below have no effect. |
| Freeze packages when guests are inactive | Automatically freeze a package when the guest has been inactive for the configured number of months (minimum 1). Enter the inactivity period in the "After how many months of the guest being inactive should the package be frozen (in months)?" field. A guest is considered inactive if no invoices were created, and no payments were made, and no appointments had a start time during the specified period. |
| Freeze package upon payment dispute | Automatically freeze the package when a payment dispute is raised on one of its collected payments. Sub-setting: "Enable automatic unfreeze if business wins dispute" (Default: On) β controls whether the package automatically unfreezes when the dispute is resolved in the business's favor or when the guest withdraws all disputes. |
| Freeze package upon payment failure | Automatically freeze the package when a scheduled payment attempt fails. Sub-setting: "Enable automatic unfreeze when payment conditions met" (Default: On) β controls whether the package automatically unfreezes when the failed payment is later collected successfully. |
| Allow users to set a package unfreeze date at the time of freezing | When enabled, staff can choose how the package should unfreeze when they manually freeze it: select a calendar date ("Unfreeze on"), enter a number of days ("Unfreeze after"), or choose manual unfreeze (no automatic option). |
Payment dispute resolution β three outcomes
When a package is frozen due to a payment dispute, three outcomes determine whether the package automatically unfreezes:
| Dispute outcome | Package behavior |
|---|---|
| Business wins the dispute | Package automatically unfreezes (when "Enable automatic unfreeze if business wins dispute" sub-setting is On) |
| Guest withdraws all disputes related to the package | Package automatically unfreezes (same sub-setting) |
| Guest wins any dispute | Package remains frozen for manual review β staff must manually unfreeze; this is a protective default |
Note: The full-form setting labels ("Freeze package upon payment failure", "Freeze package upon payment dispute") are the official UI labels. Do not use the short forms "Freeze on payment failure" or "Freeze on payment dispute" β those do not match the product UI.
Automatic package closure
Zenoti closes a package automatically when the guest consumes all of its benefits while the package is still within its validity period. The status changes to Closed and the package stops appearing in the point-of-sale list. The change can take a few moments to appear.
Closure is controlled per package, not organization-wide, and it is optional. It applies only to packages created with the Close package when all benefits are consumed option selected. Clear that option on a package if you want the package to stay Active after the last benefit is used.
Important: Closure is not expiry. A package whose validity period ends becomes Expired, never Closed. The two statuses are tracked separately.
Closure is reversible automatically. If the redemption that consumed the last benefit is undone β for example, by reopening the invoice β the package returns to Active.
There is no standalone cancel action for a package that has already been sold. The refund flow is the only staff-initiated way to close a sold package. See Refund a package.
Guest communication (expiry reminders)
| Setting | Description |
|---|---|
| Email package expiry | Send email notifications to guests before their package expires. |
| Create opportunity on expiry | Automatically create a sales opportunity when a package nears expiry, enabling follow-up by sales staff. |
| Days to remind | Number of days before (or after) expiry to send the reminder notification (maximum 365). |
| Expiry reminder timing | Choose whether to send the reminder before or after the package expiry date. |
Package financials
Pricing and discounts
| Setting | Description |
|---|---|
| Center price change (Allow package price changes when versioning is disabled) | Allow centers to update the sale price and tax group for packages when package versioning is off. With versioning off, a price change updates the package in place instead of creating a new version. Requires the Edit permission on Packages β unlike most other settings, which require only Administrator mode, this setting requires the Edit check box under Packages in the Administrator section of the security role. Refunds and scheduled collections on existing sales continue to use the price at time of purchase. This setting appears only when package versioning is off for your organization. If you do not see it, versioning is on and a price change already creates a new version. |
Sales rules
How package versioning affects existing sales. Package versioning is an organization-level mode with two states. It is not a pricing rule β it decides what a catalog edit does to packages guests already own.
Versioning What a catalog edit does On (the default) Saving a change creates a new version of the package. Guests who already bought it stay on the version they bought, and keep its price and benefits. Off The change updates the package in place and applies to current and future guests alike. Editing the current version does not reach earlier sales. To change what a guest who already owns the package is entitled to, work on that guest's sold package in their profile rather than on the catalog entry.
Versioning is not set on this page. The Center price change setting above appears only when versioning is off β if you do not see that setting, your organization is using versioning. For how pricing behaves under each mode, see Configure package pricing.
| Setting | Description |
|---|---|
| Package targets | Enable package sales targets for tracking sales performance. |
| Card-on-file requirement | Controls whether a card on file is mandatory or optional for scheduled payments. When set to mandatory ("When scheduling package payments" = "Card on file is mandatory"): scheduled collections run automatically without staff intervention. Impacts and considerations: Adding a card on file automates scheduled collections and simplifies the checkout process. However, the processing fees involved are higher. |
| Enforce category | Require a category to be assigned when creating packages. |
| Offer packages | Enable promotional offer packages (packages with free services). Offer packages are primarily intended for in-store purchase but are also available on the Webstore once this setting is active. |
| Enable one-time offer for packages | Enable one-time offer pricing for packages β special promotions available only once to specific guests. One-way door: Once you create at least one one-time offer package, you cannot turn off this setting. Enabling the setting alone (without creating an offer package) still allows disabling. See One-time offer packages β rules and considerations below. |
| Scheduled payments | Enable installment-based scheduled payments for Series and Custom packages (including Offer and Template sub-types). When enabled, configure the number of installments, frequency, and first payment amount. One-way door: This setting cannot be turned off after enabling. |
| Non-first-charge refund on scheduled | Allow a custom payment to be added when closing a scheduled package upon refund. When enabled, staff can add a new payment type to clear any pending installment before processing the refund. One-way door: Cannot be turned off after enabling. |
| Auto-estimate validity (validity models) | Enable selection of package validity models during package creation (fixed value, sum of service frequencies, and so on). One-way door: Cannot be turned off after enabling. |
One-time offer packages β rules and considerations
One-time offer packages have several specific rules that differ from regular packages. Turn on the Enable one-time offer for packages setting before configuring these.
Core rule: sold only once per guest
After configuring a package as a one-time offer, you can sell it only once to an individual guest. Every other OTO behavioral rule below derives from this single constraint.
Package type restriction
One-time offer packages can only be configured for series packages. Custom, day, and offer packages cannot be configured as one-time offers. When creating or editing a package, the one-time offer option is available only when the package type is series.
Two eligibility types
When creating a one-time offer package, choose one eligibility type:
| Eligibility type | Who can purchase |
|---|---|
| For new guests only (the option reads For new guests when the package form first loads) | Guests who have neither a closed invoice in their profile nor a package or membership added to their profile (even if the invoice for that package/membership is not yet closed). A guest with a package or membership added but an open invoice is still treated as an existing guest. |
| For new and existing guests | Any eligible guest β existing guests may purchase. |
Locks after the first sale
Two things are editable on a configured OTO package β but only until the package is sold to the first guest. After the first sale:
- You cannot disable the one-time offer on that package (the OTO flag is locked on)
- You cannot change the eligibility type from "For new guests only" to "For new and existing guests"
Limits and restrictions
- A guest can purchase each one-time offer only once. They may purchase different one-time offers.
- If an invoice with a one-time offer exists for a guest, they cannot purchase the same one-time offer through another invoice.
- When two guest profiles are merged and both have purchased the same OTO, the merged profile retains only one usable OTO instance.
- You cannot edit an existing package that has been sold to at least one guest to make it a one-time offer. The OTO flag must be set before the first sale.
- Setting persistence: You cannot turn off the one-time offer setting even if the package expires or is deleted.
- If the Enable redemptions on open package setting is enabled, guests can redeem their one-time offer credits on the same open invoice.
Credit transfer
If the Transfer Service Credits setting is enabled on the package, service credits from a one-time offer package can be transferred to another guest β using the same workflow and eligibility rules as regular package credit transfers.
Auto-renewal
A one-time offer package can only be renewed into a membership or package that is not a one-time offer. Renewing an OTO into another OTO is not permitted.
Channel availability
Guests can purchase a one-time offer through the Webstore, CMA (Customer Mobile App), or Point of Sale.
Custom package flow
| Setting | Description |
|---|---|
| Template selection | Controls whether template selection is mandatory or optional when creating custom packages. Configured under "When creating custom packages" with two option values: "Template selection is mandatory" (staff must pick a template; the Add Category option is hidden) or "Template selection is optional" (staff may create a package without a template). |
| Pre-load services | Automatically load available services in the custom package builder. |
| Pre-load products | Automatically load available products in the custom package builder. |
| Business unit requirement | Require business unit selection when creating custom packages. |
| Service credit transfer | Enable transfer of service credits between packages. |
Scheduled payment defaults
When scheduled payments are enabled, you can set organization-wide defaults:
| Setting | Description |
|---|---|
| Schedule frequency | Default frequency value for installment schedules. |
| Frequency Type | Default unit for frequency: days, weeks, or months. |
| Number of installments | Default number of payment installments. |
| First payment amount | Default first payment amount for scheduled packages. |
Revenue
| Setting | Description |
|---|---|
| Revenue recognition | Enable deferred revenue recognition for packages, spreading revenue over the package validity period instead of recognizing it at the point of sale. |
| Expired balance as revenue | Recognize the remaining balance of expired packages as revenue. |
Redemption gated by amount paid β not by sessions remaining
When the Enable redemptions on open package setting is off, Zenoti gates redemption by the amount paid, not by the number of unused sessions shown on the package.
How the calculation works
Zenoti derives a per-session unit price by dividing the total package price by the total number of sessions in the package. It then compares the cumulative amount paid so far against the value of sessions already redeemed. A guest may redeem one additional session only when the payments collected so far cover the cost of that next session.
Example: A guest purchases a 5-session series package priced at $500 (unit price: $100 per session). After paying $200, two sessions are covered. If the guest has already redeemed two sessions, the next redemption attempt is refused β even though three sessions still appear as unused on the package β because the $200 paid does not yet cover a third session.
The refusal message
When a redemption is blocked for this reason, the system displays a message indicating that the package cannot be redeemed because the payment made so far does not cover the next session. If you encounter this message and the guest has unused sessions, check whether the package has outstanding scheduled payments.
How to lift the restriction
Turn on the Enable redemptions on open package setting (navigate to Configuration > Packages > Essentials) to allow guests to redeem benefits before the package is fully paid. When this setting is on, Zenoti does not apply the per-session payment check and allows redemption up to the total number of sessions in the package regardless of payment status.
Important: Enabling Enable redemptions on open package is an organization-wide change. Confirm with your finance team before enabling, as it allows benefit delivery ahead of full payment collection.
Configuration pages
These settings are managed through embedded configuration pages accessible from the package settings area.
| Page | Description |
|---|---|
| Package categories | Create and manage package categories. Categories help organize packages by type or purpose. Available at organization, zone, and center levels. |
| Package tags | Create and manage tags for packages. Tags enable filtering and catalog publishing. Available at organization, zone, and center levels. |
| Package tag groups | Create and manage tag groups that organize related tags. Available when digital catalog publishing is enabled. |