Custom Metric β Average Ticket Price (Category)
The Average Ticket Price (Category) metric in ezPulse measures the average net revenue generated per service within a specific service category over a selected time period. Use this metric when setting center-level goals to track category-specific pricing performance and identify trends in service revenue by category.
Note: For conceptual background on how ezPulse metrics work and how they are organized, see ezPulse Overview.
Audience: Organization administrators and center managers who configure center-level goals in ezPulse.
Before you begin
- You must have access to ezPulse. If you have not yet set up access, see User Invitation.
- Your organization must have metric configuration enabled for the Average Ticket Price (Category) metric. To verify which metrics are active for your organization, see Metric Configuration.
- Center-level goals using this metric must be created per center. Confirm you have the appropriate center access before creating goals.
- Review your organization's week start day setting before creating weekly goals, as it determines the boundaries of all weekly time periods. See Organization Settings.
Steps
Understand how the metric is calculated
Before configuring a goal using this metric, confirm that the metric definition matches what you intend to measure.
The Average Ticket Price (Category) metric is calculated as:
Total net sales for a specific service category Γ· Number of services in that category completed in the same period
The following rules apply to this calculation:
- Pretax and pre-tip β The metric uses the net price of each qualifying service. Tax and tip amounts are excluded from the numerator.
- Closed invoices only β Only services on closed invoices are counted. Services on open invoices are excluded from both the numerator (total category sales) and the denominator (number of category services).
- Category scope β Only services belonging to the specific category you select when configuring the goal are included. Services in other categories are excluded.
- Time period accumulation β Both the total category sales and the service count accumulate from the start of the selected time period through the selected date. The metric supports Today, WTD (week-to-date), MTD (month-to-date), QTD (quarter-to-date), and YTD (year-to-date) views.
Important: Weekly time period boundaries are determined by your organization's week start day setting. If your organization's week start day is Wednesday, a WTD view on Friday includes data from Wednesday through Friday only. Verify this setting before interpreting WTD results.
Select the metric when creating a goal
To use Average Ticket Price (Category) in a center-level goal:
- Sign in to ezPulse at
https://ezpgateway.zenoti.com. - Navigate to the goal creation workflow. For step-by-step instructions, see Goal Creation.
- When prompted to select a metric, locate Average Ticket Price (Category) in the Sales metric category.
- Select the service category you want to track. The metric will calculate results only for services in that category.
- Set the time period for the goal. The supported time periods are:
- Week β Accumulates from the organization's configured week start day through the current day.
- Month β Accumulates from the first day of the current month through the current day.
- Quarter β Accumulates from the first day of the current quarter through the current day.
- Year β Accumulates from the first day of the current year through the current day.
- Enter the target value for the metric. This is the average ticket price (in your organization's currency) you want the center to achieve for the selected category.
- Complete the remaining goal definition fields and save the goal as a draft or publish it. For status transition rules, see Goal Status Management.
Note: The metric value displayed on the metrics dashboard reflects the most recent data refresh. Data refresh is backend-driven and occurs on a scheduled basis β there is no manual refresh option.
Verify the metric on the metrics dashboard
After the goal is published and data has refreshed:
- Open the metrics dashboard in ezPulse. For navigation instructions, see Metrics Dashboard.
- Locate the Average Ticket Price (Category) metric card for the center.
- Confirm the displayed value reflects the expected category, time period, and calculation (pretax, pre-tip, closed invoices only).
- Compare the current value against the target value you set in the goal definition.
Tip: If the metric value appears lower than expected, verify that the relevant invoices are closed. Services on open invoices are excluded from the calculation until the invoice is closed.
Worked example
A center manager at a spa wants to track the average ticket price for the Facial service category during the current month.
- Metric: Average Ticket Price (Category)
- Category selected: Facial
- Time period: MTD
- Target value: $85.00
During the current month, the center has completed 40 facial services on closed invoices, with a total net sales amount of $3,200 (pretax, pre-tip). The metric displays:
$3,200 Γ· 40 = $80.00
The center is currently tracking at $80.00 against a target of $85.00. Three open invoices for facial services are not yet included; once those invoices are closed, the metric will update on the next data refresh.
Tips
- When comparing performance across categories, create separate goals for each category rather than relying on a single blended metric. This gives you a clearer view of which categories are driving or lagging average ticket price.
- If you want to track average ticket price across all services (not limited to a single category), use the Average Ticket Price metric instead of the category-specific variant. See Metric Definitions for the full metric catalog.
- Weekly goals are sensitive to your organization's week start day. If you change the week start day, note that the change is not permitted while published weekly goals exist. Plan week start day changes before publishing weekly goals.
- Use the MTD or QTD time period views to identify whether a category's average ticket price is trending up or down within the period, then adjust staffing or promotional focus accordingly.
- When copying an existing goal that uses this metric to a new date range, verify that no conflicting goal exists for the same category and time period in the target range. See Goal Copying.
Troubleshooting
The metric value is lower than expected.
Verify that all relevant service invoices are closed. The Average Ticket Price (Category) metric excludes open invoices from both the sales total and the service count. Ask your front desk team to close any open invoices for services in the tracked category, then wait for the next data refresh.
The metric shows zero even though services were completed.
Confirm that the services are assigned to the correct category in Zenoti. If a service is assigned to a different category than the one selected in the goal definition, it will not appear in the metric. For service category configuration, contact your organization administrator or see the relevant configuration documentation.
The WTD value does not match the date range I expected.
The WTD time period starts on your organization's configured week start day, which may not be Monday. Check your organization's week start day setting in ezPulse. See Organization Settings for details.
The metric card does not appear on the metrics dashboard.
The Average Ticket Price (Category) metric must be active in your organization's metric configuration. If the metric card is missing, ask your organization administrator to verify that this metric is enabled. See Metric Configuration.
The target value field shows a currency symbol I did not expect.
The currency symbol is determined by your organization's currency setting in Zenoti, not by ezPulse directly. The metric value and target value both use the organization's configured currency. For organization-level configuration, see the relevant topic in configurations.