WooCommerce subscription products let a store sell products or services through recurring payments instead of a single checkout transaction. In practice, the recurring offer is configured through subscription plans in the product editor, with settings for price, billing frequency, trials, fees, discounts and duration. This makes subscriptions useful for repeat deliveries, ongoing services and other offers where the customer pays according to a defined schedule.
A reliable setup requires more than entering a recurring price. Before publishing, decide whether renewals should be automatic or manual, check the capabilities of the selected payment gateway, and prepare an isolated environment for testing. The workflow below explains how to create a simple plan, configure variable subscriptions or grouped products, and validate renewal behavior before customers use the store.
What You Need Before Creating Subscription Products
Recurring products and services are configured with the WooCommerce Subscriptions extension rather than WooCommerce alone. Before creating a plan, identify the product structure, the required renewal model and the payment method that will process future charges. The exact gateway extension and its documented capabilities matter because support for automatic renewals, payment-date changes, trials and other subscription features can differ.
Choose the Renewal Model
WooCommerce Subscriptions supports automatic and manual renewal payments, but these models do not provide the same customer experience. Automatic recurring payments require a gateway that supports the relevant recurring-payment capability. Manual renewal support means that the customer may need to complete a renewal payment; it is not equivalent to unattended recurring billing. Define the required workflow first, then check the documentation for the exact gateway extension and version used by the store.
Prepare a Controlled Test Setup
Use a staging site or another isolated test environment for renewal, payment-failure, conflict and scheduled-action testing. Do not use real customer payment details for testing; use the payment gateway’s supported test or sandbox mode where available. Plan to review orders, statuses, customer emails, scheduled actions and logs so that a successful checkout is not mistaken for a fully tested subscription lifecycle.
How to Create a Simple Subscription Product
The core setup takes place in the product editor. Create or edit a product, open the Product data panel and use the Subscriptions area. Depending on the selected configuration, the product can use storewide subscription plans, a product-specific custom plan, or remain available only as a one-time purchase. Select the structure that matches the offer before entering commercial terms.
Select the Product and Plan Structure
Begin with the product or service that customers will purchase. In the Product data panel, open the Subscriptions settings and choose the applicable plan arrangement. A storewide plan can provide a shared configuration, while a custom plan can define settings specifically for that product. Keep one-time purchase availability separate from subscription purchase availability: allowing both creates a different customer choice from selling the subscription alone.
For a basic recurring offer, the product-specific plan is often the clearest place to define the price and schedule. Do not assume that a plan configured for one product automatically describes every other product in the catalogue. Review the customer-facing purchase option and the relationship between the initial order and later renewals.
Configure and Publish the Offer
Set the recurring price and billing schedule, then add only the optional settings required by the offer. These may include a signup fee, free trial, discount, expiration rule or renewal-date alignment. Complete the normal product information before publishing. Review the checkout language and the resulting purchase flow, and publish only after the selected gateway and the planned renewal process have been tested in a controlled environment.
Billing Plans, Prices, Trials and Expiration
The plan’s billing settings determine both what the customer pays and how the subscription continues after the initial purchase. WooCommerce Subscriptions distinguishes the billing period from the overall subscription length, so these settings should be considered separately. A recurring plan may continue indefinitely, or it may stop after a defined number of payments.
Set Recurring Price and Frequency
Billing frequency can be configured with a number and a period such as day, week, month or year. The combined interval documented for subscription plans cannot exceed ten years. Choose a schedule that accurately describes the customer offer rather than treating the interval as a cosmetic label.
Pricing can be based on the product price with an optional percentage or fixed discount. Alternatively, the plan can use an independent custom recurring price. These choices affect how the recurring amount is controlled, so check the resulting amount at checkout and in the renewal order. Keep the billing period separate from subscription duration: a plan billed monthly for a specified number of payments is not configured in the same way as a plan that bills monthly until cancelled.
Define Trials, Fees and Duration
Subscriptions renew indefinitely by default unless the plan is configured to expire after a specified number of payments. The total-payment count includes the initial purchase, which is important when translating a commercial offer into a payment limit. Review this count carefully so that the configured duration matches the intended customer experience.
A plan can include a one-time signup fee and a free trial defined by a number and period. Renewal-date alignment is optional. If dates are not aligned, renewals are based on the subscriber’s purchase date. Alignment may be useful where a store needs a shared schedule, but it should be selected only when it reflects the actual fulfilment and billing process. Do not imply that every payment gateway supports every trial or payment-date option.
Variable Subscriptions, Bundles and Composite Products
Subscription plans are not limited to a single unchanging product configuration. WooCommerce Subscriptions documents plans for simple, variable, bundle and composite products. The available structure should reflect how customers select the offer and how the store fulfils it, while each grouped-product path should be tested independently.
Use Variations for Options or Tiers
Variable subscriptions can present different options or tiers through product variations. Each variation can have additional subscription product settings where applicable, allowing the store to distinguish recurring choices within one product. For example, the variation structure can represent different customer selections without treating all options as one identical plan.
Review the subscription settings at variation level and test each important path through checkout and renewal. Confirm the selected variation, recurring amount, schedule and customer-facing purchase information. Do not assume that testing one variation proves that every other variation behaves identically.
Plan for Bundles and Composite Products
WooCommerce Subscriptions documentation includes subscription plans for bundle and composite products. However, the exact customer experience and supported behavior may depend on the relevant product extension. A grouped product can involve additional selection or configuration steps, so its checkout and renewal flow should not be inferred solely from a simple subscription test.
Verify the specific bundle or composite extension used by the store and test the complete grouped-product workflow in staging. Do not present compatibility with an unspecified third-party extension as confirmed. Check the resulting order, subscription status and fulfilment behavior for the actual configuration customers will use.
Choosing a Payment Gateway for Recurring Payments
Payment gateway selection should follow the renewal model and the features required by the plan. The documented gateway guidance distinguishes basic and advanced subscription capabilities, and support may differ between listed extensions and third-party or independently distributed integrations.
Match Gateway Capabilities to the Plan
Write down the required renewal behavior before choosing a gateway: automatic or manual renewals, trials, saved payment methods, payment-date changes or other subscription-management functions. Then check the exact gateway extension and version. Confirm automatic recurring-payment support if the store requires unattended renewals. Do not infer compatibility with a particular theme, hosting provider or additional extension from general WooCommerce Subscriptions documentation.
Payment-date changes are especially relevant to accelerated renewal testing. If the gateway does not support the required date changes or imposes minimum billing-period restrictions, the documented test action may not work. In that case, the store may need to wait for the gateway’s normal schedule instead of treating the limitation as a failed product configuration.
How to Test Renewals Before Going Live
Testing should cover the complete customer journey, not only the first payment. Create a test subscription with the intended gateway and record the subscription identifier. Then trigger a renewal using the available documented method and compare the result with the expected lifecycle.
Trigger a Test Renewal
For an active subscription using a payment method that supports payment-date changes, use the Process Renewal action from the subscription editor. This is the simplest documented way to initiate an automatic renewal test. The action is available only for eligible active subscriptions and supported payment methods.
An alternative is to run the relevant pending scheduled subscription payment action from the scheduled-actions tools. The appropriate method depends on the test setup and gateway behavior. If the gateway has date-change limitations or minimum billing-period restrictions, an accelerated renewal may not work; use the gateway’s normal schedule where necessary.
Review Results and Investigate Failures
After triggering the test, verify the renewal order, payment result, subscription status and next scheduled payment. Check customer emails and relevant WooCommerce or gateway logs. Test the initial checkout, trial transition when applicable, renewal order creation, payment success, failed payment handling, cancellation, inventory and fulfilment behavior.
When a renewal stalls, inspect order notes, WooCommerce logs, failed scheduled actions, plugin compatibility and server logs. Use conflict testing in staging when diagnosing stalled renewals. A successful manual action does not prove that every production renewal scenario is supported, so record the tested gateway, product structure and result before launch.
Setting up WooCommerce subscription products is a sequence: choose the product structure, define the recurring price and billing terms, configure trials or duration, and verify the payment gateway’s capabilities. Variable subscriptions, bundles and composite products require testing of their specific customer paths rather than assumptions based on a simple product. Before launch, validate checkout, renewal, emails, statuses, scheduled payments and failure handling in an isolated environment. The supplied documentation does not establish compatibility with every gateway, theme, host or additional extension, and market-specific recurring-payment obligations require separate review. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.