This note shows why subscription coverage had to behave like a lifecycle rather than a mutable status field.
Gym memberships renew, pause, refund, expire, and combine with add-ons over time.
If the active subscription row is mutated directly for every operational event, past commitments and future coverage quickly become ambiguous.
The system needed membership logic that staff could reason about during real operational work, not just during ideal purchases.
Freeze requests, queued renewals, and plan changes all compete for the same future coverage window.
Direct mutation creates questions like whether a subscription is still the same contract after several timeline-changing edits.
Older purchases must preserve the contract that was bought, even if the plan definition changes later.
Keep one active subscription and one queued subscription, then reconcile lifecycle events explicitly instead of mutating a single subscription record into impossible states.
Model coverage with one active subscription and one queued next subscription rather than an open-ended list of silent mutations.
Lifecycle reconciliation decides how freezes, refunds, add-ons, and queued renewals alter the timeline.
Versioned plan references preserve the historical contract instead of letting old subscriptions inherit new plan behavior by accident.
Freeze compatibility was designed into the lifecycle model so date shifts and queued coverage remain coherent.
Staff can understand current coverage, next coverage, and exceptional cases without decoding a mutated history.
Operational events become timeline decisions instead of status toggles.
Later systems such as freeze handling and payment activation have a clearer surface to integrate with.
The lifecycle model requires more explicit reconciliation logic than a single mutable subscription row.
Timeline management becomes a first-class part of the system.
That extra logic is worthwhile because it removes many ambiguous subscription states.
AI-assisted implementation. Architecture, decisions, tradeoffs, and UX ownership were mine.
Instead of setting subscription status to "frozen," the freeze system represents freezes as policy-bound ledger entries that shift coverage dates and preserve auditability.
The challenge was making Razorpay, Cashfree, and manual payments behave the same way operationally.
These notes are part of larger systems work. You can return to the related project context or reach out if you need someone who can reason through workflows, authorization, and operational software without making them harder to operate.