WooCommerce subscriptions: setup and renewals 2026

Set up WooCommerce subscriptions with a supported payment route, then check first orders, renewals, customer changes and cancellation against the records.

WooCommerce subscriptions need a recurring-payment extension, a compatible payment method and a renewal process that produces an order your team can fulfil. For the official WooCommerce Subscriptions extension with Stripe card payments, set the billing schedule in WooCommerce and reconcile each renewal against its payment and order records.

An active subscription records an ongoing agreement. Dispatch still needs a paid order and available stock. Automatic renewals can continue when stock reaches zero, so stock shortages need an explicit operational response.

Choose the supported subscription components

WooCommerce core supplies the store and order system. The official WooCommerce Subscriptions extension adds recurring agreements and renewals. YITH WooCommerce Subscription is a separate subscription plugin with its own settings and payment compatibility. Instructions for one WooCommerce subscription plugin don’t establish what another supports.

This procedure uses the official extension and WooCommerce Stripe gateway with card payments. WooCommerce’s Stripe integration uses saved payment tokens. Its subscription agreements live in WooCommerce, and individual charges appear under Payments in Stripe. A missing entry in Stripe Billing’s subscription list therefore doesn’t establish a missing agreement.

Before configuring products, prepare the following:

  • An administrator who can install and activate extensions and authorise the payment connection. Give daily support staff only the order and subscription access their work requires.
  • Compatible installed versions of WooCommerce, Subscriptions and the payment extension. WooCommerce’s requirements policy generally supports the current and previous WooCommerce minor versions. Read the installed release’s requirements before updating.
  • A Stripe account enabled for the store’s payments, with the gateway connected in the correct test or live mode. Use test mode for rehearsal.
  • A written billing unit: one specified product quantity per weekly or monthly charge, for example. Separate any shipping charge, tax treatment, initial fee and trial from that recurring amount.

The payment gateway compatibility guide distinguishes automatic payments from manual renewals. It also lists support for changes to payment dates, amounts and payment methods. Stripe card renewals support automatic collection, but that doesn’t make every enabled checkout method equivalent. A manual renewal requires the customer to pay a pending renewal order.

Compare extension licensing and renewal terms, payment-processing fees, connector costs and the staff time needed for exceptions. A lower plugin cost can leave more manual renewal work.

Create the product and renewal rules

Use one product and a plain monthly schedule for the first rehearsal. The following steps follow WooCommerce’s documented subscription-plan interface, which supports ordinary products alongside the older dedicated subscription product types.

  1. Activate Subscriptions and connect the Stripe gateway under WooCommerce’s payment settings. Confirm card payments are enabled in the intended mode before exposing a subscription product.
  2. Open WooCommerce > Settings > Subscriptions. Leave automatic payments enabled for this automatic-card route. Decide whether to accept manual renewals as an additional option. Save the settings.
  3. Create a simple physical product, such as one bag of coffee. Enter its stock, shipping and tax settings. In Product data > Subscriptions, choose Create custom subscription plans.
  4. Set Frequency to one month and Align renewal to Do not align. Enter the recurring price using the plan’s price option. For this rehearsal, leave out a trial and signup fee. Leave expiry disabled for an agreement that continues until cancelled.
  5. Save the product, then inspect its purchase options and recurring total on the storefront. Compare checkout’s first payment and recurring amount with your intended offer before placing the test order.
  6. Complete checkout as an ordinary customer and open My Account > Subscriptions. Confirm the customer can see the agreement and next payment. Subscriptions requires a customer account even if ordinary orders allow guest checkout.

WooCommerce’s WooCommerce subscription plan instructions explain the price and expiry options. The general settings guide covers renewals and customer roles. Existing stores can retain dedicated Simple Subscription or Variable Subscription products, but WooCommerce recommends subscription plans for new products.

The agreement’s schedule controls the next billing event. A renewal order records that period’s payment and fulfilment work. According to WooCommerce’s stock-management guide, processing renewal orders reduces product stock. Automatic renewals can take stock below zero. Assign someone to suspend affected subscriptions or resolve supply before the next charge if stock is unavailable.

Check the first payment and renewal

Consider this fictional coffee subscription. The customer buys one bag per month with an immediate first payment and automatic card renewals. The following is a record-checking example, not a transaction result.

EventRecords to reconcileDispatch decision
Initial purchaseCustomer account, subscription agreement, parent order and successful gateway paymentRelease the first bag once the paid order and available stock agree
Next billing eventSubscription schedule and its linked renewal orderWait for the payment outcome before releasing another bag
Successful renewalGateway payment reference, paid renewal order and updated next paymentRelease one renewal shipment, with its own fulfilment reference
Failed or uncertain renewalExisting renewal order, gateway outcome, order notes and any scheduled retryHold dispatch and resolve the existing attempt before retrying

WooCommerce’s renewal process creates an order for each renewal. Automatic collection uses the saved payment method. Manual renewal instead asks the customer to log in and pay.

If a renewal appears late, inspect the subscription’s scheduled action and related order before creating another order. WooCommerce documents scheduled-action and payment-token failures in its subscriptions troubleshooting guide. A gateway success with an unpaid store order needs reconciliation, not an immediate second charge.

If the gateway reports a decline, inspect whether a retry is already scheduled. A customer payment-method update must apply to the subscription used for future renewals. After recovery, confirm one successful payment for the period, one paid renewal order and one warehouse instruction. An order marked paid doesn’t establish that a parcel has left the warehouse. Use the fulfilment or carrier record for that answer.

Apply changes and cancellation correctly

Customers manage subscriptions through My Account > Subscriptions > View. WooCommerce documents WooCommerce customer account instructions for address and payment-method changes, renewal payments and cancellation. Suspension availability depends on store settings, while some changes depend on gateway support. Inspect those actions using a customer account because an administrator can see controls hidden from customers.

For an address change, inspect the next renewal’s delivery address and any order already open. Treat the open order as separate work for fulfilment staff. For a product change, confirm the agreement’s items and recurring total before explaining what the next charge buys.

WooCommerce’s cancellation procedure distinguishes Pending Cancellation from immediate cancellation. Pending Cancellation preserves subscription benefits until the prepaid period ends. Cancelling an agreement alone is insufficient evidence of a refund or a stopped parcel. Check the related order, payment adjustment and fulfilment status separately.

A support reply can state, for example, that future renewal is stopped while an already-paid order remains awaiting dispatch. It must cite the agreement’s status and the relevant order internally. Promise a refund only after an authorised refund has a confirmed payment record. The broader subscription management guide explains how to assign those responsibilities.

Connect Klaviyo to subscription states

Klaviyo’s WooCommerce subscription-data guide recommends Tribe’s premium Klaviyo Toolkit for subscription events. Enable the required events in that connector. Its metrics appear after events occur, and historical events aren’t automatically backfilled. A purchase metric alone cannot establish that a subscription remains active.

Match the Klaviyo profile to the store customer and subscription identifier. Check channel consent separately before sending marketing. Confirm that the subscription event and the store agreement describe the same person and plan.

For renewal messaging, require a successful-renewal signal tied to its renewal order. Keep a failed or uncertain renewal out of paid-renewal messages. Before sending an upcoming-renewal campaign, check current subscription status and exclude cancelled agreements, including customers whose cancellation happened after they entered the flow. Repeat that check before later messages in the flow.

Accept the connection only when a test purchase reaches the intended profile, cancellation excludes the agreement from renewal promotion and failure handling avoids a paid-order message. Keep payment recovery notices separate from marketing consent and promotional campaigns. Your final check is agreement state, payment outcome and order state agreeing on the action the customer will receive.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup