Creating subscription plans

Create subscription plans under Monetization → Catalog → Subscriptions. A plan describes what a customer receives and the monthly or annual price. Before offering it, check the saved plan, the customer checkout, and the access the customer gets after subscribing.

Prepare your first plan on a test site. The editor autosaves, and a new plan starts Active, Public, and priced at zero. There is no separate Publish button that holds a new plan back from customers.

Prepare the subscription setup

You need permission to manage subscriptions. If the Subscriptions tab is missing, ask your administrator to enable the Subscriptions commerce workflow in Pay hub → Overview → Commerce workflows. If the page shows Enable subscriptions, use Open Pay hub to review the setup.

Have these details ready before choosing Add plan:

• The plan name and a short description of who it is for.
• The monthly charge and the total annual charge, in USD.
• The features and access included with the plan.
• The payment method customers will use and a supported test setup.
• The customer page where the plan should appear.

For Stripe payments, complete Connecting Stripe. A payment connection alone does not confirm that a particular plan is ready to buy.

If your site already offers recurring products through Catalog → Products, ask your administrator which plans feed the customer chooser before adding another one here. Existing paid catalog plans can take precedence, so a plan saved under Subscriptions may not appear in that chooser.

Add the plan and verify it saved

1. On the test site, open Monetization → Catalog → Subscriptions and choose Add plan.
2. In the expanded card, enter the Plan name, Description, and Button text.
3. Enter Monthly price (USD) and Annual price (USD). Review both before allowing customers to select the plan.
4. Clear Active (available for purchase) and Public (shown in plan selection) while the plan is being prepared.
5. Wait for autosave, then reload the page and reopen the plan to check the saved values.

If plan cards disappear after saving: the changes may still be saved. Stop editing and reload the page before making another change. Do not choose Add plan again to replace a missing card; that can replace the previously loaded plan list. If the expected plans do not return, ask your administrator to check the saved settings.

Reload and verify after each round of edits. Wait for a successful save before leaving, and resolve any Failed to save subscription settings message before continuing.

Set monthly and annual prices deliberately

The prices are separate amounts. For example, Monthly price (USD) of 12 means $12 for a monthly period; Annual price (USD) of 120 means $120 for the year. Enter the annual total, not its monthly equivalent.

Zero can offer a free plan for that billing interval. It does not mean “hide this interval.” Do not leave one price at zero merely because you only intend to sell the other interval; ask your administrator to configure and verify the intended choices.

Clearing a price field does not reliably remove its saved value. The field can restore the previous number when you leave it. Enter the intended amount explicitly and check it again after reloading.

If the plan uses an existing Stripe recurring price, confirm that the checkout amount and billing interval match your offer. Editing the displayed USD amount does not by itself update that Stripe price or the billing terms of existing subscribers.

The Enable Solana subscriptions option requires separate recurring-payment setup. Its token amounts, billing periods, and wallet details are not filled in by the USD price fields. Use it only with an administrator who can configure and test the complete subscription flow. See Accepting supported crypto payments for the site's general crypto setup.

Describe the offer and check its presentation

Use Feature highlight for the short statement above the feature list. Choose + Add feature to add each benefit, and use the remove control beside a feature to delete it. Mark as Popular (featured styling) highlights the plan visually.

Feature text describes the offer. It does not configure access to protected pages, usage limits, services, or other benefits. Arrange those separately and test them with a customer account.

The up and down arrows move cards in the editor. Check the customer page before relying on that order; the chooser may retain a different saved order. Ask your administrator to correct the customer order if it does not match.

Under Plan page, the Buyers see preview shows the heading, subheading, badges, and optional footer. Badges and footer contains Popular plan badge, Annual savings badge, and Footer notice (optional).

Changes to Plan page text appear in the preview but are not saved by those fields. Give the finished wording to your site administrator to apply, then check the public plan page before sharing it.

Check every savings claim against your prices. The default “2 months free” text is a label, not a calculation or a discount. With $12 monthly and $120 annually, the annual saving is $24; different prices may need different wording.

Control availability before launch

Active and Public have different jobs. Active makes the plan eligible for purchase; Public makes it eligible for the standard plan chooser. The standard chooser requires both. A private plan is not automatically an invitation-only purchase flow.

Do not use Limit quantity available as your only protection for a limited membership. The controls appear when the Inventory workflow is enabled, but the standard subscription chooser does not enforce that plan quantity limit. Have your administrator arrange and test a supported enrollment limit before advertising a fixed number of places.

When the plan and payment setup are ready, have your administrator apply the verified configuration to the live site. Check both billing intervals and the intended customer page before announcing the plan.

Test selection, payment, and access

Use a test customer account and a supported test payment setup.

1. Open the customer plan chooser and confirm the plan name, price, currency, billing interval, and available payment options.
2. Select the plan and check the final checkout terms. Repeat for each billing interval you offer.
3. Complete a test subscription and confirm it appears for the same signed-in customer with the expected status and renewal period.
4. Open the included content or service as that customer. Confirm access works, then check that an account without the plan cannot use it.
5. Test an abandoned or failed checkout. Confirm it does not grant paid access, and verify the cancellation and renewal behavior your offer promises.

If you intentionally offer a free plan, test its selection and access separately. A successful free selection does not test paid billing.

A plan card or a payment success page alone is not enough to confirm the whole setup. Check the subscription record and the actual customer experience. See Test the complete buyer journey.

Change or retire an existing plan

Before changing a live price or included benefit, identify the subscribers who use the plan and decide how their existing terms will be handled. Check new purchases and existing subscriptions separately after the change.

To stop offering a plan from this editor, clear Active and verify it is no longer selectable. Clearing Public removes it from the standard chooser, but does not cancel existing subscriptions.

Delete plan asks for confirmation and removes the plan and its configured features from subscription settings. Deleting the plan is not a subscriber-cancellation workflow. Resolve existing subscriptions and access requirements before deleting a plan that customers have used.

Troubleshoot a missing or unusable plan

• Add plan is unavailable: review the subscriptions setting in Pay hub.
• Cards disappear after saving: reload before making another edit; do not add replacement plans from the empty view.
• The plan is missing from the customer chooser: check the saved Active and Public settings, the selected billing interval, and whether recurring catalog products supply that chooser.
• A paid plan has no usable payment option: ask your administrator to check its recurring-payment setup and test checkout.
• The page copy looks right in the preview but reverts: have your administrator save and verify the copy through the supported settings tools.
• Payment succeeds but access is missing: check the signed-in account, subscription status, and the access configured for that plan.

For help, provide the plan name or ID, billing interval, customer-page URL, expected result, and visible error. See Getting help and reporting a problem.