Subscriptions

Subscriptions

Purpose

This page manages recurring billing relationships so teams can track plan state, renewals, and subscription lifecycle changes.

Prerequisites

  • Subscription products/plans should be configured.
  • Payment method/provider integrations should be active.
  • Users need permission to manage subscription records.

Main Actions

  • View subscription status and lifecycle history.
  • Review renewals, plan changes, and cancellations.
  • Inspect billing cycle timing and usage-related details.
  • Apply approved operational/accounting follow-up.

Field/Status Reference

  • Subscription ID: Unique recurring billing reference.
  • Plan: Current subscribed offering.
  • Status: Active, trialing, past due, canceled, etc.
  • Current Period: Billing window start/end.
  • Next Billing Date: Scheduled renewal point.

Workflow

  1. Locate the subscription record.
  2. Review status and current billing period.
  3. Check recent lifecycle events (renew, change, cancel).
  4. Validate related invoices/payments.
  5. Confirm final state and record follow-up if required.

Connections

  • Depends on Payments for renewal settlement outcomes.
  • May create related Orders for upgrades or add-ons.
  • Affects access and entitlement behavior in product workflows.

Common Mistakes

  • Treating canceled and past-due subscriptions the same.
  • Missing effective dates on plan changes.
  • Updating lifecycle states without documenting rationale.

Troubleshooting

  • If status appears wrong, compare local state with provider events.
  • If renewals fail, verify payment method and retry policy.
  • If plan changes look inconsistent, review proration and timing details.

Quick Tips

  • Prioritize past-due subscriptions for rapid follow-up.
  • Check renewal cohorts by date to catch trend issues early.
  • Keep lifecycle notes clear for support and finance handoff.