How to Read the IZI Changelog
How to Read the IZI Changelog
Section titled “How to Read the IZI Changelog”The IZI changelog is the official record of every platform change: new features, bug fixes, and behavioral updates. Each entry tells you what changed, which module it belongs to, and — critically — whether your club needs to take any manual action before things work as expected.
Most updates deploy automatically with zero configuration on your side. The ones that do require action are flagged explicitly so nothing slips through unnoticed.
Entry Structure
Section titled “Entry Structure”Every changelog record contains the same five fields:
Title: a short name for the feature or fix.
Category: which part of the platform the change belongs to.
| Category | What it covers |
|---|---|
| CRM | Changes in the web interface used by admins and owners |
| IZI Mobile App | Changes in the client-facing mobile application |
| Analytics | New reports, filters, and metrics |
| Warehouse | Inventory and stock management module |
| Tariffs | Tariff setup, schedules, and zone configuration |
| API | Integration changes relevant to developers |
| Fix | Bug resolved in system behavior |
Description: what changed and how it now behaves.
Where to find it: the path inside the CRM or app where the new feature appears.
Action required: if your club needs to reconfigure something, it is stated explicitly here.
What “Action Required” Means
Section titled “What “Action Required” Means”The majority of IZI updates are automatic — the platform updates, your club benefits immediately, nothing to do. A minority of entries carry an “Action required” notice. This happens in three situations:
- A new feature ships disabled by default — you need to turn it on in settings.
- An existing feature changes behavior — you need to verify your current settings still reflect your intent.
- A new integration becomes available — you need to connect it for it to take effect.
These entries are always phrased as: “Action required: [specific step to take].” If an entry has no such label, no intervention is needed.
Release Cadence
Section titled “Release Cadence”IZI does not follow a fixed release schedule. Major feature releases happen roughly every 4–8 weeks. Patches and bug fixes ship as needed, independently of the major cycle.
Notifications about significant updates appear in the Notifications section of the CRM. If the club owner has enabled email notifications, an alert also arrives by email.
Versioning
Section titled “Versioning”IZI does not use semantic versioning (v1.2.3) for the user-facing platform. The changelog is organized chronologically by date. For API versioning, see the developer documentation.