ZenotiHelp

Configure batch and expiry tracking

ZTZenoti Docs Team Updated August 24, 2026 4 min readHow-to

Audience: Administrator

Zenoti's batch and expiry tracking feature lets you track products at the batch level and monitor expiry dates across the inventory lifecycle. This is especially valuable for businesses handling medical consumables, injectables, skincare, and other perishable or high-value items.

This article covers how to turn batch tracking on for your organization and for individual products. The configurable expiry alert window (for example, 30 / 60 / 90 / 180 days) is owned by Alerts and notifications per.


On this page


Prerequisites

Permission: Edit (under Inventory) — Allows configuring batch tracking on the product edit form.

  • Your organization must be on the on-hand quantity model. Batch tracking is not available in the store-and-floor model. See Switch to the on-hand quantity model if you are not yet on that model.
  • Batch tracking must be enabled at the organization level by Zenoti. To have it turned on, open a support ticket via the Zenoti Help Center — your Zenoti representative can also enable the feature for you.
  • Batch tracking is then enabled per product, not globally.

What batch tracking gives you

With batch tracking enabled, you can:

  • Prevent the use of expired products and reduce wastage.
  • Trace products back to their source batch for compliance and recall purposes.
  • Monitor near-expiry inventory across all centers.
  • Follow a FEFO (First Expiry First Out) consumption model during checkout and automatic consumption, prioritizing batches closest to expiry.

Steps

Enable batch tracking for a product

  1. Go to Inventory > Products.
  2. Select the product you want to track by batch.
  3. On the product edit form, enable the Batch Tracking option.
  4. Select Save.

Once enabled, the system prompts for batch assignment on every stock-in or stock-movement event for that product, including:

  • Purchase order (PO) deliveries
  • Transfer order (TO) dispatch and delivery
  • Opening stock entry
  • Stock adjustments
  • Product checkouts
  • Product conversions
  • Bundle and unbundle operations

Example: A medical spa enables batch tracking on a high-value filler product. The next PO delivery of that product prompts the receiving user to enter each vial's batch number and expiry date. During a checkout, Zenoti automatically selects the batch with the earliest expiry (FEFO). The near-expiry report then surfaces any batch with less than 60 days to expiry so the center can plan promotions or returns.

Set the expiry alert window

The expiry alert window (30 / 60 / 90 / 180 days or custom) is configured in the inventory alerts and notifications settings. See Alerts and notifications for the procedure — this article does not duplicate it.

Rollout and migration

When you enable batch tracking on a product that already has stock, existing stock is retained as untracked until the next stock-in event (for example, the next PO delivery). You cannot retroactively assign batch numbers to historical stock.

Plan the rollout per product:

  1. Use up or audit out any existing untracked stock on the product, or accept that it will coexist with batch-tracked stock for a short period.
  2. Enable batch tracking on the product.
  3. Receive the next PO delivery with batch and expiry data.
  4. From that point forward, all stock for the product is batch-tracked.

Turning batch tracking off

If you disable batch tracking on a product, the batch-assignment dialog no longer appears for future events. Historical batch data is retained in the stock ledger and inventory-traceability report for audit purposes.

Reports impact

Batch tracking feeds several reports:

  • Near expiry report — lists batches approaching their expiry date so you can plan returns, promotions, or write-offs.
  • Inventory traceability report — traces a batch back to its source PO and forward to every transaction that consumed it; essential for compliance and recall audits.
  • Stock ledger — shows batch-level movements for batch-tracked products in addition to the product-level totals.
  • Cost of goods — reflects the cost assigned to each batch at the time of consumption.

Tips

  • Start with one or two high-value or high-risk products (for example, injectables, prescription skincare) rather than turning it on for the whole catalogue at once. This lets your receiving team learn the batch-entry flow without operational disruption.
  • Always capture the expiry date at PO delivery — once the product is on the shelf, recovering the original expiry is much harder.
  • Review the near-expiry report weekly so you can act on batches while there is still time for promotions or returns.
  • Zenoti recommends verifying products that expire within the next 12 months. Configuring the alert window to 180 days (the maximum preset) and reviewing the near-expiry report regularly gives enough lead time to plan promotions, returns, or write-offs before products become unsellable.
  • Train your receiving team on FEFO: the oldest-expiring batch must be consumed first, not necessarily the oldest-received batch.

Troubleshooting

  • The Batch Tracking toggle does not appear on the product edit form. The organization does not have batch tracking enabled. Open a support ticket via the Zenoti Help Center to have it turned on, or contact your CSM.
  • Batch Tracking toggle exists but cannot be enabled. Your organization is on the store-and-floor model. Switch to the on-hand quantity model first — see Switch to the on-hand quantity model.
  • A transaction is blocked with "negative batch balance" error. The transaction would cause a batch to go below zero. Correct the quantity, split the transaction across batches, or receive additional stock into that batch first.
  • Stock adjustment does not prompt for a batch. The product is not batch-tracked, or the adjustment was created before the toggle was enabled. Check the product's current batch-tracking state on the product form.
  • FEFO consumption picked the wrong batch. Verify the expiry dates recorded on each batch. FEFO uses the stored expiry date — if a batch was entered with an incorrect date, FEFO will honour it.
Was this article helpful?
Your feedback helps us improve our documentation.