Membership freezes: pause the member, keep the billing honest

What does the freeze capability do?

It gives operators a retention tool that does not create billing debris. A member pausing for injury or travel gets an accurate, previewed financial change; the operator keeps the mandate and the relationship; and nobody spends month-end unwinding wrong charges.

• A freeze is a record. Request date, start date, optional end date, and whether it was member-requested or staff-created. Everything else derives from it.
• Fee replacement, not patching. Billing dates inside the window produce the freeze fee instead of the recurring fee, through the same billing machinery, with add-ons, ad-hoc charges, and discounts suspended for the duration.
• Traceable charges. Each freeze-period charge references the freeze that produced it, so “why was I charged this?” is answered from the record.
• Preview before commit. The freeze runs through the identical lifecycle logic in a non-persisting mode first, returning the exact charges and resulting state for the member to confirm.
• Derived status. Active, frozen, and cancelled are computed from the freeze and cancellation records, including a grace date marking when the current freeze ends. Editing the freeze’s dates updates status and billing with no secondary edits.

Where the freeze fee is configured

Freeze fees are prices, and they are modelled with the same depth as every other fee: set per package per site alongside the recurring and joining fees, captured per member at signup so later list-price changes respect existing agreements, and changeable on a future effective date through scheduled price changes.

Why it matters

A freeze is the alternative to a cancellation, which makes it a revenue feature. The operational difference between a flag-based freeze and a record-based one is the difference between manual refunds, forgotten end dates, and disagreeing status fields on one side, and a previewed, self-resolving, auditable pause on the other. The freeze fees themselves flow through the Billing Engine’s recurring collection, and the companion guide below sets out the full design with demonstration tests for evaluating any membership product.