ZenotiHelp

Check retail vs. consumable demand

ZTZenoti Docs Team Updated October 12, 2026 8 min readGuide

AI Inventory Manager tracks demand differently for retail and consumable products because each type reaches the guest through a different mechanism β€” retail products are sold at the Point of Sale, while consumable products are used during service delivery. Understanding how daily usage is counted for each type helps you interpret the Predicted daily usage values in the action grid and explainability panel, and explains why two products with similar on-hand quantities may have very different reorder urgency.

Audience: Center managers and inventory owners who review AI Inventory Manager recommendations and want to understand how demand signals are calculated.

Before you begin

Permission: Add or Edit (on the Inventory security object) β€” required to view and act on demand data.

  • AI Inventory Manager must be active for your organization. If you do not see Demand analytics or Inventory overview in the navigation, contact your administrator.
  • You need Add or Edit access on the Inventory security object to view and act on demand data.
  • Familiarize yourself with the difference between Retail and Consumable product types as configured in your product master. AI Inventory Manager uses the product type assigned there to determine which demand-counting rule applies.

Availability: AI Inventory Manager is in Beta. Contact your Zenoti Customer Success Manager to enable it for your organization.

Steps

Where the daily-usage number comes from β€” transaction-type fields

The most common question about AI Inventory Manager is "where does the daily-usage number come from?" The table below is the short answer: it shows exactly which transaction types feed the Predicted daily usage figure for each product type, and which are ignored. Read the sections that follow for the detail behind each rule.

Transaction type Retail Consumable
POS sales to guests Counts Does not count
Employee checkouts Does not count Counts
BOM auto/manual consumption on service completion Does not count Counts
Negative stock adjustments Does not count Counts
Negative audit corrections Counts (untracked consumption) Counts (untracked consumption)
Returns from guests Does not count Does not count
Transfers out Does not count Does not count
Write-offs Does not count Does not count
Positive stock adjustments Does not count Does not count
Voided sales Does not count Does not count
Vendor returns Does not count Does not count

Tip: Use the Type filter in the action grid to view only Retail or only Consumable products at once. This makes it easier to review demand signals for one product category at a time. See Use the action grid and filters for filter instructions.

Understand how retail demand is counted

Retail products are sold directly to guests at the Point of Sale (POS). AI Inventory Manager counts daily usage for retail products using only confirmed POS sales.

The following transaction types count toward retail daily usage:

  • POS sales to guests

The following transaction types do not count toward retail daily usage:

  • Returns from guests
  • Transfers out to another center
  • Write-offs
  • Positive stock adjustments
  • Voided sales

Note: Negative audit corrections β€” where a stock count reveals fewer units than the system recorded β€” do count toward retail daily usage as untracked consumption. These corrections indicate that product left the center without a recorded sale.

To see the demand signal for a retail product:

  1. Navigate to AI Inventory and open the Inventory overview tab.
  2. In the action grid, locate the product you want to review.
  3. In the Type column, confirm the product is classified as Retail.
  4. Click the Why this? link on the product row to open the explainability panel.
  5. In the Inputs part of the panel, review the Daily usage value β€” this reflects the retail demand calculation described above.

Understand how consumable demand is counted

Consumable (professional) products are used during service delivery rather than sold at the Point of Sale. AI Inventory Manager counts daily usage for consumable products from service-related consumption events.

The following transaction types count toward consumable daily usage:

  • Employee checkouts
  • Bill-of-materials (BOM) auto-consumption recorded when a service completes
  • BOM manual consumption recorded when a service completes
  • Negative stock adjustments
  • Negative audit corrections

The following transaction types do not count toward consumable daily usage:

  • Transfers out to another center
  • Write-offs
  • Positive stock adjustments
  • Vendor returns

Note: Unlike retail products, consumable demand includes both employee checkouts and BOM consumption events. If your center uses BOM-linked services, the consumable daily usage figure will reflect actual product use per service completion.

Forward demand from scheduled appointments

For consumable and injectable products, AI Inventory Manager looks beyond past consumption. It reads the scheduled service appointments on your calendar, together with the bill-of-materials (BOM) quantities each booked service will consume, and factors this forward demand into the Predicted daily usage figure. Because injectables and consumables are committed the moment an appointment is booked β€” well before the product is drawn down β€” this lets the forecast anticipate an upcoming period of heavy demand rather than reacting only after stock has already been used.

For example, a medical spa with a week of heavily booked injectable appointments sees its predicted daily usage for those products rise ahead of the appointments, so the reorder recommendation reflects the committed demand in time to place an order. Retail products, which are sold at the Point of Sale rather than booked in advance, do not carry this forward-demand signal β€” their daily usage is derived from completed sales only.

To see the demand signal for a consumable product:

  1. Navigate to AI Inventory and open the Inventory overview tab.
  2. In the action grid, locate the product you want to review.
  3. In the Type column, confirm the product is classified as Consumable.
  4. Click the Why this? link on the product row to open the explainability panel.
  5. In the Inputs part of the panel, review the Daily usage value β€” this reflects the consumable demand calculation described above.

Understand base daily usage and the AI-adjusted figure

Regardless of product type, AI Inventory Manager computes demand in two layers:

Base daily usage is the straightforward historical average: total units consumed over the trailing 90 days, divided by 90. This is the starting point for all demand calculations.

Predicted daily usage is the AI-adjusted figure shown in the action grid and explainability panel. The model adapts the base daily usage to account for:

  • Day-of-week patterns (for example, higher weekend demand at a busy center)
  • Growth or decline trends in recent consumption
  • Seasonality and holiday effects
  • Active promotions
  • For consumable and injectable products, forward demand from scheduled appointments and their BOM quantities (see Forward demand from scheduled appointments above)

The Predicted daily usage column in the action grid always shows the AI-adjusted figure, not the raw 90-day average. When you open the explainability panel for a product, the Inputs part shows the Daily usage value that feeds into the reorder math.

Note: The reorder point, days of stock cover, target stock, and suggested order quantity are calculated using transparent, deterministic arithmetic on top of the predicted daily usage figure β€” they are not themselves AI-computed. See Calculate reorder levels and suggested quantities for the full calculation.

Worked example: A center sells a shampoo as both a retail product (guests buy it to take home) and uses a separate consumable SKU of the same shampoo for in-service use. In a given 90-day period, the retail SKU records 180 POS sales and 10 guest returns. The retail daily usage is 180 Γ· 90 = 2.0 units/day (returns are excluded). The consumable SKU records 270 BOM consumption events over the same period. The consumable daily usage is 270 Γ· 90 = 3.0 units/day. The AI model may adjust both figures upward or downward based on trend and seasonality before displaying them as Predicted daily usage in the action grid.

Tips

  • Check the product type before investigating a low demand signal. If a consumable product shows unexpectedly low daily usage, verify that BOM links are configured for the services that use it. Unlinked services will not generate BOM consumption events, and demand will be understated.
  • Negative audit corrections affect both product types. If your center regularly records negative audit corrections, investigate whether product is leaving the center without a recorded transaction. Reducing untracked consumption improves the accuracy of the base daily usage calculation.
  • Use the Demand analytics tab for trend context. The Demand analytics view shows demand over time, which helps you distinguish a genuine decline in consumption from a data gap caused by missing BOM links or unrecorded checkouts. See Review demand analytics.
  • The 90-day window is fixed. Base daily usage always uses the trailing 90 days. If your center opened recently or a product was introduced fewer than 90 days ago, the base figure will reflect a shorter history, and the confidence tier will likely be T3 β€” Low or T4 β€” Very Low. See Check confidence scores and tiers for guidance on interpreting low-confidence recommendations.
  • Settings changes take effect at the next nightly refresh. If you update reorder coverage, lead time, or safety days after reviewing demand figures, the updated recommendations will appear the following day β€” not immediately.

Troubleshooting

  • The Predicted daily usage for a retail product seems too high. Check whether negative audit corrections have been recorded for the product recently. Negative audit corrections count as untracked consumption and increase the daily usage figure. Open the explainability panel (Why this?) and review the Inputs part to see the demand figure feeding into the calculation. If audit corrections are inflating demand, investigate whether product is being consumed or removed without a recorded POS sale.
  • A consumable product shows zero daily usage even though it is used in services. Zero daily usage means no qualifying consumption events were recorded in the trailing 90 days. The most common cause is that the product is not linked to a bill of materials for the services that use it, and employees are not recording checkouts. Verify BOM configuration in the product and service master data (see the inventory category for product master setup). When daily usage is zero, the reorder level is also zero and no reorder alert fires β€” the product is flagged as Slow Moving instead.
  • A consumable product's daily usage does not reflect a recent increase in service volume. The base daily usage is a 90-day trailing average, so a recent spike in service volume will take time to be fully reflected. The AI-adjusted Predicted daily usage accounts for growth trends and forward demand from booked appointments, and may already be higher than the raw average. Open the explainability panel and compare the Daily usage input with the Predicted daily usage shown in the action grid to see whether the model has adjusted upward.
  • A retail product's daily usage dropped after a promotion ended. This is expected behavior. The AI model factors promotions into the Predicted daily usage adjustment. When a promotion ends, the model reduces the forward-looking adjustment. The base daily usage (90-day average) will also gradually decrease as the high-volume promotion days roll out of the trailing window.
  • The Type column shows an unexpected classification for a product. AI Inventory Manager uses the product type set in the product master. If a product is classified as Retail when it should be Consumable (or vice versa), the wrong demand-counting rule is being applied. Correct the product type in the product master β€” the updated classification will be reflected at the next nightly refresh.
Was this article helpful?
Your feedback helps us improve our documentation.