Tariff Expiration Policy in IZI
Tariff Expiration Policy in IZI: Five Ways to Set a Time Limit
Section titled “Tariff Expiration Policy in IZI: Five Ways to Set a Time Limit”Every tariff in IZI has an Expiration Conditions section — a required set of rules that define when a purchased tariff becomes unavailable to the customer. When multiple conditions are configured, IZI applies OR logic: the tariff expires as soon as the first condition is met. A tariff with no conditions cannot be placed on sale.
Five condition types are available:
| Condition type | CRM label | Triggers when |
|---|---|---|
TIME_FROM_PURCHASE | Time from purchase | N minutes/hours/days after payment |
TIME_FROM_FIRST_USE | Time from first use | N minutes/hours/days after the first session starts |
TOTAL_PLAY_TIME | Total play time | After N minutes/hours of accumulated gaming time |
USES | Session count | After N sessions are started |
FIXED_DATE | Fixed date | At the start of the specified calendar day (exclusive) |
By mixing these rules you can manage the lifecycle of any tariff — from a single-entry hourly slot to a long-term multipass with a dual safety net against indefinitely held balances.
Time from Purchase
Section titled “Time from Purchase”The Time from Purchase condition starts a countdown the moment payment is processed. The tariff expires after the configured interval whether or not the customer has visited at all.
When to use: hourly tariffs that should burn if unused on the same day; promotional tariffs with a hard validity window.
Time units: minutes, hours, days.
CRM preview example: a value of 3 with unit days shows the hint “Tariff expires 3 days after purchase.”
Technically, expiresAt is computed at order creation: purchase date + N × unit_in_seconds. Purchasing multiple units of the same tariff does not extend the deadline — expiresAt is independent of quantity.
Time from First Use
Section titled “Time from First Use”The Time from First Use condition defers the countdown until the customer actually starts their first session. A customer can purchase a tariff today and begin the window when they first arrive — days or weeks later.
When to use: multi-day passes where the customer buys in advance; flexible weekly or monthly packages where penalising early purchase would hurt retention.
Time units: minutes, hours, days.
CRM preview example: 7 days — “Tariff expires 7 days after first use.”
Unlike TIME_FROM_PURCHASE, the window is fixed regardless of how many units were purchased: the countdown always starts on first use and runs for exactly the configured duration.
Total Play Time
Section titled “Total Play Time”The Total Play Time condition accumulates net gaming time across every session the customer plays on that tariff. The tariff closes once the cumulative total reaches the configured limit.
When to use: multipasses sold by volume of play time (5 hours, 10 hours, etc.); corporate packages where visitors need a fixed block of time across multiple visits.
Time units: minutes, hours.
Scaling: when a customer purchases N units of the tariff the limit multiplies by N. Two 5-hour multipasses become a single 10-hour balance.
CRM preview example: 300 minutes — “Tariff expires after 300 minutes of total play time.”
This condition pairs naturally with TIME_FROM_FIRST_USE: a 10-hour multipass plus 30 days from first use closes when either the play time runs out or the period ends — whichever comes first.
Session Count
Section titled “Session Count”The Session Count condition caps the number of times a session can be started on a single tariff purchase. Each session start decrements the counter by one.
When to use: single-entry tariffs (value = 1); visit-based passes for N visits regardless of session length.
- Value = 1 — strictly single-use: one payment, one session.
- Value > 1 — visit pass: the customer returns as many times as the value allows.
CRM preview example: 5 sessions — “Tariff expires after 5 sessions.”
The session count field appears without a time-unit selector because no unit is needed — it is a plain integer count.
Fixed Date
Section titled “Fixed Date”The Fixed Date condition sets a specific calendar deadline shared by every holder of that tariff. All copies of the tariff become invalid simultaneously at the start of the specified day (the date is exclusive, not inclusive).
When to use: promotional offers with a shared end date; seasonal packages; event tariffs for tournaments or openings.
Key detail: the date is evaluated in the club’s local time zone. The CRM date picker prevents selecting a past date — the minimum is automatically set to tomorrow.
CRM preview example: “Tariff valid until 31 December 2026 (exclusive)” means the tariff closes at midnight on 31 December in the club’s time zone.
Fixed Date is often combined with other conditions: an event tariff for 3 hours of play plus a fixed end-of-event date means the customer either uses the hours or the tariff closes after the event — whichever comes first.
How to Configure Expiration Conditions in the CRM
Section titled “How to Configure Expiration Conditions in the CRM”- Go to Catalog → Tariffs and click Create tariff or open an existing one.
- Scroll to the Expiration Conditions section (required, marked with an asterisk).
- Click Add condition — a dropdown with five types appears.
- Select a type. Depending on the choice, additional fields appear:
- For
TIME_FROM_PURCHASE,TIME_FROM_FIRST_USE,TOTAL_PLAY_TIME— a numeric field plus a time-unit selector. - For
USES— a numeric field only (no unit needed). - For
FIXED_DATE— a date picker.
- For
- IZI shows a human-readable preview below each condition — verify the logic before saving.
- Click Add condition again if you need a second rule.
- Save the tariff.
Each condition type can be added only once per tariff. Duplicate types are greyed out in the dropdown until the existing one is removed.
Combining Rules: OR Logic
Section titled “Combining Rules: OR Logic”When a tariff has multiple expiration conditions, IZI triggers on whichever condition is satisfied first.
Common combinations:
| Scenario | Rules |
|---|---|
| Multipass with a deadline | TOTAL_PLAY_TIME 600 min + TIME_FROM_FIRST_USE 30 days |
| Visit pass with a time window | USES 5 + TIME_FROM_PURCHASE 60 days |
| Promotional event package | TOTAL_PLAY_TIME 180 min + FIXED_DATE 2026-12-31 |
| Single-entry hourly slot | USES 1 |
Combinations protect the club from indefinitely held balances: a customer cannot buy a pass and carry it for years. The condition is also transparent to the customer — “10 hours or 30 days, whichever comes first” is easy to communicate at the point of sale.
Related Settings
Section titled “Related Settings”Expiration conditions work alongside other tariff parameters:
- Sales policy — controls where and when a tariff can be purchased. A tariff with no expiration conditions fails the
purchasablefilter and will not appear in the sales catalog. - Refund policy — defines what happens to the unused balance when a tariff expires early or is closed: preserve it, return it to the bonus balance, or forfeit it.
- Tariff schedules — define when a tariff is available for active use. Schedules and expiration conditions are independent mechanisms that can be used together.
Frequently asked questions
What are tariff expiration conditions in IZI?
Expiration conditions are rules that determine when a purchased tariff becomes unavailable to a customer. IZI supports five types: time from purchase, time from first use, total play time, session count, and fixed date. When multiple conditions are set, the tariff expires as soon as any one of them is triggered — OR logic.
What does Time from Purchase mean?
The tariff expires a set number of minutes, hours, or days after payment — regardless of whether the customer has used it at all. This suits hourly tariffs or promos with a hard usage window.
How is Time from First Use different from Time from Purchase?
TIME_FROM_FIRST_USE starts the countdown only when the customer launches their first session. A customer can buy a tariff today and begin the clock next week. This is ideal for multi-day passes where you do not want to penalise early buyers.
How does the total play time limit work?
The TOTAL_PLAY_TIME rule sums net gaming time across all of the customer's sessions on that tariff. The tariff closes when accumulated time reaches the limit. When multiple units of the tariff are purchased, the limit scales proportionally.
What is the session count condition?
The USES rule caps the number of sessions a customer can start. A value of 1 means a single-entry tariff: one payment, one session. A value of N creates a visit-based pass for N sessions regardless of their individual length.
When should I use a fixed expiration date?
FIXED_DATE sets a specific calendar day after which the tariff is no longer valid for any holder. The date is exclusive: the tariff closes at the start of that day in the club's local time. Use it for seasonal promos or event tariffs with a shared deadline.
Can I combine multiple expiration conditions?
Yes. A tariff can have several conditions at once. IZI applies OR logic — whichever condition is met first closes the tariff. For example, a multipass for 10 hours plus 30 days from first use expires when either the play time runs out or the period ends, whichever comes first.
What happens if no expiration condition is set?
A tariff without any expiration condition cannot be listed for sale. IZI CRM will show an error ('At least one expiration condition is required'), and the purchasable filter excludes such tariffs from the sales catalog automatically.
What time units are available?
For TIME_FROM_PURCHASE and TIME_FROM_FIRST_USE you can choose minutes, hours, or days. For TOTAL_PLAY_TIME the options are minutes and hours. The USES condition takes a plain count, and FIXED_DATE uses a date picker. All unit selectors appear inline in the tariff form.
How do I view the expiration status of a customer's tariff?
Open the customer profile, go to the Tariffs section, and select the tariff. The card shows the expiration date (if applicable) and the remaining hours or sessions.
Do expiration conditions affect refund behaviour?
No — expiration conditions define when a tariff closes, while the refund policy defines what happens to the unused remainder at that point (preserve, return to bonus balance, or burn). These are two independent settings on the same tariff.