Comp OS Cancellation Playbook

Comp OS Cancellation Playbook

This playbook covers the two cancellation modes available for the Comp OS add-on and the steps to follow for each.

When to Cancel

Cancellation Options

Navigate to Gyms → [Gym Name] → Billing & Subscription → Comp OS Add-On card. If the subscription is active, you'll see a Cancel Subscription button, or toggle the switch OFF. Both open the cancellation dialog.

Option 1: Cancel Now

StepWhat Happens
1The Comp OS Stripe subscription item is removed immediately (with proration)
2The subscription status is set to cancelled
3The comp_os feature flag is disabled for the gym
4The gym loses access to the Comp OS workspace immediately
5A platform activity log entry is recorded

Use when: Immediate termination is required (e.g. contract breach, gym closure, or gym explicitly requests same-day cancellation).

Option 2: Cancel On (Scheduled)

StepWhat Happens
1A future cancellation date is recorded on the subscription
2The gym retains full Comp OS access until that date
3Any billing cycles due before the cancellation date are still processed normally
4On the cancellation date, the daily billing sync removes the Stripe item (no proration), sets status to cancelled, and disables the feature flag
5A platform activity log entry is recorded at both scheduling and execution time

Use when: The gym wants to finish out a billing period, has upcoming competitions to complete, or needs a grace period.

Scheduled Cancellation Visibility

When a cancellation is scheduled, the Comp OS card displays an amber banner showing the scheduled date. This is visible to all platform staff viewing the gym's billing tab.

Post-Cancellation

Escalation

If a cancellation cannot be processed (e.g. Stripe errors, missing subscription data):

  1. Check the Activity Log & Error Monitoring in Platform Settings for edge function errors
  2. Verify the gym's Stripe subscription ID is valid
  3. If the Stripe item was already manually removed, update the subscription status to cancelled directly
  4. Raise a support ticket internally if the issue persists