Understand Max Plan Custom Fields and Exact-Subscription Storage

Understand QCMM Max Custom Fields as reusable definitions and Plan layouts whose values are stored as durable, subscription-specific snapshots.

Definitions, Assignments, and Values Are Different Records

A reusable Custom Field definition supplies the field identity, stable key, type, help/validation settings, and optional choices. A Plan assignment decides where and how that field is used for one Plan. A purchased subscription then receives its own durable value snapshot.

Why QCMM Uses Subscription Snapshots

Custom Field values belong to the exact subscription, not globally to the Joomla user. The snapshot stores the field key, label, type, value/display value, Plan item identity, customer-entry/view/edit policies, repeating-entry limit, and ordering needed to preserve the purchased membership context.

One User Can Have Different Values

If the same Joomla user owns two subscriptions, each subscription has its own Custom Field rows. A value entered for one membership does not overwrite the value for another membership, even when both Plans use the same reusable field definition.

Checkout and Administrator-Created Subscriptions

Customer-entered values are normalized into checkout snapshots and persisted after the free/paid subscription becomes authoritative. Administrator-created subscriptions can receive blank snapshots for the Plan so admin-only or later-fulfilled information still belongs to that exact subscription.

Historical Safety

Retiring or even deleting a reusable definition does not delete historical subscription value snapshots. QCMM deliberately preserves those records so past memberships, reports, fulfillment, and display can retain their original context.

Community Discussion

Want to compare QCMM workflows or share practical tips? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.