How billing and subscription management works

Documentation
, , , ,
1

How billing and subscription management works

This guide explains full subscription operations, including upgrades, cancellations, renewal behavior, and feature entitlement changes.

Required access: Account with an active or historical paid subscription.

When to use billing management

Use this when you need to upgrade, cancel, verify renewal status, or check plan-level feature access.

Before changing your plan

Before upgrading or canceling:

  1. List features your team currently uses (bulk, site manager, sublicenses).
  2. Check current usage against limits.
  3. Identify environments or workflows that could be affected.
  4. If canceling, schedule transition before end of billing period.

How to manage billing

  1. Open your subscription management area.
  2. Review current plan and renewal details.
  3. Upgrade or cancel based on your operational needs.
  4. Confirm plan change state.
  5. Confirm feature availability in dashboard usage cards.

Verification checklist

After any plan change:

  • Plan label/status is correct
  • Expected feature badges are enabled/disabled
  • License workflows continue to function
  • Team is informed about any changed limits

What happens after plan changes

  • Upgrades unlock newly included features.
  • Cancellations typically apply end-of-term behavior.
  • Feature access updates are reflected in dashboard limits and badges.

Troubleshooting

If billing status is stale, retry from your subscription page and contact support with timestamp and account email.

Related guides

  • How to bulk download and install products
  • How to activate your license

Exact route paths

  • /dashboard/billing
  • /dashboard

Expected UI state after each step

  • Step 1: Current plan and renewal status are visible on billing page.
  • Step 2: Upgrade/cancel controls match account eligibility.
  • Step 3: Post-change status reflects selected plan.
  • Step 4: Feature badges/limits update in dashboard usage panels.

Screenshot map (step-level)

  1. Billing workflow context

  2. Dashboard entitlement confirmation

Operational objective

Complete the “How billing and subscription management works” workflow with predictable outcomes, clear auditability, and repeatable execution quality across team members and projects.

Acceptance criteria (all must pass)

  • The workflow can be completed without missing permissions or blocked route access.
  • All required dashboard routes load successfully for the active account.
  • The expected UI states are visible in the same order as documented.
  • At least one end-to-end validation confirms the process works in practice.
  • Evidence artifacts are captured for support and audit handoff.

Routes that must be reachable during validation:

  • /dashboard/billing
  • /dashboard

Failure modes and exact remediation

  • Permission failure: Recheck plan/license entitlements and retry after session refresh.
  • Route loads but action is missing: Confirm feature flags/plan gates and selected context (site/license).
  • Action runs but state does not update: Refresh, re-open the relevant page, and verify from history/log view.
  • Partial success in multi-step operations: Retry only failed sub-steps and preserve successful state.
  • Cross-page mismatch: Reconcile with dashboard history and capture timestamps before escalation.
  • Persistent failure after one controlled retry: Open support ticket with full evidence package.

Evidence package for support escalation

Collect all items before escalating:

  • Account email and user role
  • Affected route path and exact action taken
  • Site URL, product/license identifier (if relevant)
  • Timestamps for first failure and latest retry
  • Expected result vs actual result
  • Screenshot set listed below

Screenshot evidence checklist

  • Step 1: Billing workflow context
  • Step 2: Dashboard entitlement confirmation
  • One screenshot with visible timestamp (system clock/browser tab)
  • One screenshot showing route context or breadcrumb
  • One screenshot showing final persisted result
  • Replace any generic placeholder/demo visuals with real environment captures

FAQ

Can I skip steps if I already know this workflow?

Skip only after all acceptance criteria still pass. If any criterion fails, run the full sequence exactly as documented.

Should I run this in production first?

Use staging first for medium/high-impact changes. Promote to production only after validation evidence is complete.

What if my screen does not match the guide exactly?

UI can vary by plan and feature access. Validate route access, plan gates, and expected state outcomes instead of pixel-perfect layout.

How many retries should I perform before escalation?

Run one controlled retry after checklist validation. If failure persists, escalate with full evidence to avoid hidden side effects.

Who owns this guide operationally?

Billing Operations owns this guide and its periodic review cycle.

Guide metadata

  • Difficulty: Beginner
  • Estimated completion time: 10-20 minutes
  • Owner: Billing Operations
  • Last reviewed: 2026-03-18