Skip to main content
Subscriptions turn one-time buyers into recurring customers. This guide covers how to configure, manage, and support subscription products.

​
When to use subscriptions

Subscriptions are a good fit when:
  • You deliver ongoing value (for example, community, regular content drops, or office hours).
  • You want predictable recurring revenue.
  • You’re comfortable managing renewals and cancellations.
If your product delivers value in a single download or course, a one-time purchase might be simpler.

​
Creating a subscription product

  1. In the Pocketsflow dashboard, create a new product.
  2. Choose Subscription or Membership as the product type.
  3. Set:
    • Billing interval (for example, monthly or yearly).
    • Price per interval.
    • Optional free trial length, if supported.
  4. Add access details:
    • How customers join your community or platform.
    • What they can expect each billing period.
Make sure your page and checkout copy clearly communicate that this is a recurring charge.

​
Managing active subscriptions

Once customers subscribe, you’ll be able to:
  • View active, past-due, and canceled subscriptions.
  • See renewal dates and billing history.
  • Identify which product or plan each subscription is tied to.
From the dashboard, you can typically:
  • Cancel a subscription on behalf of a customer.
  • Update certain subscription details, depending on the payment provider’s rules.

​
Handling upgrades, downgrades, and plan changes

If you offer multiple plans:
  • Provide a clear path for subscribers to upgrade or downgrade.
  • Decide whether changes take effect immediately or on the next billing date.
  • Communicate how pricing and access change when switching plans.
Document any special rules (for example, prorated charges) on your pricing and FAQ pages.

​
Failed payments and dunning

When a renewal payment fails:
  • The subscription may move to a past due or incomplete state.
  • Pocketsflow or your payment provider may retry the charge automatically.
Best practices:
  • Set up email notifications for upcoming renewals and failed payments if available.
  • Provide clear instructions for updating payment details.
  • Decide how long you’ll continue providing access while payments are failing.

​
Cancellations and refunds

Make your cancellation policy clear:
  • Where customers can cancel (for example, from a customer portal or by contacting support).
  • Whether cancellations take effect immediately or at the end of the billing period.
  • How you handle refunds on recent renewals.
For more detail from a buyer’s perspective, see Managing subscriptions and Refunds.

​
Webhooks for subscriptions

If you use webhooks, subscription events can drive:
  • Access control in external systems.
  • Notifications in your own tools (for example, Slack or CRM).
Common events include:
  • subscription.created
  • subscription.updated
  • subscription.canceled
  • invoice.payment_succeeded
  • invoice.payment_failed
For details, see Webhook events.

​
What’s next