Setting up subscriptions in WooCommerce is the most direct way to turn one-off sales into recurring, predictable revenue, but in Spain there is one detail that changes everything: the payment gateway. In this complete guide, you will understand which business models fit periodic billing, what you need technically in your store, and why automatic renewal charging with Redsys through tokenization makes the difference compared with solutions that only work with Stripe or PayPal.
Subscriptions in WooCommerce: why recurring revenue changes your business
A business that depends on one-off sales starts each month from zero. One that charges periodic fees starts the month with part of its revenue already committed. That difference, which seems accounting-related, actually affects everything: how you plan stock, how much you can invest in acquisition, and how calmly you manage cash flow.
Recurring revenue brings three concrete advantages. The first is predictability: you know with a fairly good estimate what you will earn next month, because part of your customers renew automatically. The second is customer value: a subscriber who stays for twelve months is worth much more than a single purchase, and that justifies investing more in acquiring and retaining them. The third is ongoing relationship: instead of winning the customer back on every sale, you maintain a bond that gives you data, feedback, and upsell opportunities.
The challenge is that subscriptions in WooCommerce, in order to be billed recurrently in Spain, have their own requirements. It is not enough to install a generic plugin designed for the Anglo-Saxon market: you need the gateway to be able to charge automatic renewals with Spanish banks, invoicing to comply with tax regulations, and VAT to be calculated correctly on every renewal, not just on the first payment.
Which business models fit recurring billing
Not every product lends itself equally to subscription, but the list of those that do is broader than it seems. These are the models that work best with subscriptions in WooCommerce:
- Memberships and private areas: access to a community, a gym, a club, or exclusive content in exchange for a monthly or annual fee.
- Recurring boxes and bundles: the classic monthly shipment of coffee, cosmetics, snacks, or niche products. The customer pays a fee and receives a physical shipment in each cycle.
- Professional services: website maintenance, consulting, technical support, advisory plans, or any retainer billed periodically.
- Software and licenses (SaaS): access to a tool or plugin while the license is active, with automatic annual or monthly renewal.
- Content and training: subscription courses, paid newsletters, resource libraries, or e-learning platforms with ongoing access.
The common denominator is that the customer receives value continuously and, in return, accepts periodic billing. The key question is not so much what you sell, but whether you can offer something that justifies paying month after month without friction. If the answer is yes, subscriptions in WooCommerce fit your catalog.
Comparison table of subscription models
| Model | Typical cycle | Main challenge | Fit in WooCommerce |
|---|---|---|---|
| Membership / club | Monthly or annual | Retain and provide ongoing value | High: fixed fee + restricted access |
| Physical box / bundle | Monthly | Logistics and stock per cycle | High: subscription product + recurring shipping |
| Service / retainer | Monthly or quarterly | Define the scope of the service | High: periodic fee without shipping |
| Software / license | Annual | Managing activations and cancellations | Very high: automatic license renewal |
| Content / training | Monthly or annual | Produce constant content | High: access while the subscription is active |
What you need in WooCommerce to sell subscriptions
Out of the box, WooCommerce sells one-time products. To launch subscriptions in WooCommerce and charge recurrently, you need to add a layer that manages the full subscription lifecycle. These are the essential elements.
Subscription product and billing cycles
The first block is a product type that, instead of being charged once, defines a billing cycle: every week, every month, every quarter, or every year. That cycle determines when the renewal is generated and for what amount. A good system lets you combine fixed fees with one-time sign-up charges (for example, an initial enrollment fee plus the monthly fee) and adjust the total duration or leave it indefinite until the customer cancels. This product is the starting point of any subscriptions in WooCommerce setup.
Free trials and acquisition periods
Trial periods are a powerful conversion lever: the customer enters without paying for a few days and, if they do not cancel, billing starts automatically. For this to work properly, the system must store the payment method from the very beginning, even if nothing is charged yet, so that the first real renewal can be executed without asking the customer for anything. Properly configured, free trials dramatically increase sign-ups for your subscriptions in WooCommerce.
Real automatic renewal
This is the point that separates a serious solution from a simple payment reminder. Automatic renewal means that, when the date arrives, the system charges the customer without them having to do anything: no re-entering the card, no confirmation, no clicking a link. For that to be possible, the gateway must support recurring payments through tokenization. Without that tokenized charge, subscriptions in WooCommerce stop being automatic. And this is where many solutions fail in Spain.
The gateway is everything: Redsys and recurring billing in Spain
Most subscription plugins were created with Stripe and PayPal in mind, which work very well in the international market. The problem is that a large share of Spanish merchants work with a Redsys virtual POS contracted through their bank (BBVA, Santander, CaixaBank, Sabadell, and practically all Spanish banks operate on Redsys). If your subscription plugin does not know how to charge renewals with Redsys, you lose the ability to automate billing with the gateway you already have.
The technical key is called tokenization, or reference payment. When the customer pays for the first time, Redsys returns a reference associated with their card that the merchant can store securely. On each renewal, the system uses that reference to charge again without the customer intervening. It is exactly the mechanism a subscription needs to work unattended, and it is what makes it possible to charge month after month with complete security and in compliance with payment regulations. It is the mechanism that makes subscriptions in WooCommerce charged through Redsys viable.
A subscription without automatic charging is not a subscription: it is a recurring invoice you have to chase manually. Tokenization with Redsys is what turns periodic billing into something unattended and reliable.
It is worth clarifying a common misconception: Bizum is not suitable for recurring payments. Bizum is an excellent system for one-off, immediate payments validated by the user in each transaction, but precisely for that reason it cannot be tokenized or scheduled to charge automatically in the future. For renewals, you need a gateway with reference payment such as Redsys, or alternatively cards through Stripe.
What to look for when choosing a WooCommerce subscription solution
| Aspect | Why it matters | What to look for |
|---|---|---|
| Redsys compatibility | It is the real gateway for most Spanish merchants | Renewal charging through native tokenization |
| Lifecycle management | Sign-ups, cancellations, pauses, and plan changes | Panel for customer and administrator |
| Failed payment recovery | A declined charge should not lose the customer | Configurable automatic retries (dunning) |
| Invoicing and tax compliance | Each renewal generates an invoice with VAT | Integration with invoicing software |
| VAT and VIES | Customers from other EU countries change the VAT treatment | Tax validation also on each renewal |
EHERO WooCommerce Subscriptions: renewals with Redsys natively
EHERO WooCommerce Subscriptions is the solution that addresses Spain’s problem at the root: it charges automatic renewals with Redsys through tokenization (reference payment), working with Spanish banks. Instead of forcing you to set up Stripe or PayPal because your plugin does not understand Redsys, it takes advantage of the virtual POS you already have contracted with your bank. In this way, subscriptions in WooCommerce are charged through your usual bank.
With this solution, you define subscription products with their billing cycles, offer free trials if you want, and let renewals run automatically when the date arrives. The customer pays once, the card is tokenized via the Redsys reference, and from then on billing is unattended. This is how subscriptions in WooCommerce are set up today with the Spanish gateway, also covering the full lifecycle: cancellations, pauses, and status checks from the customer area.
Renewal management and subscription states
In subscriptions in WooCommerce, a subscription is not a charge: it is a lifecycle. Over its existence it goes through several states that the system must manage clearly: active while it is being charged normally, trial before the first real charge, on hold or paused when the customer or administrator temporarily stops it, cancelled when it ends, and expired if a payment fails definitively and is not recovered.
Managing these states well in your subscriptions in WooCommerce is what prevents charging someone who has already unsubscribed or, conversely, stopping charges for someone who is still active. That is why visibility matters for both the administrator and the customer: the customer should be able to view their subscription and cancel it without writing an email, and the merchant should be able to see at a glance who renews, who has failed, and who is about to expire.
Dunning: recovering failed payments
Charges fail more often than you might think. An expired card, a exceeded limit, a temporary insufficient balance: in any subscriber base, a percentage of renewals will not be charged on the first attempt. If you do nothing, that customer is lost even if they wanted to stay with you. The technique to recover them is called dunning.
Dunning consists of retrying the charge automatically according to a schedule: if the renewal fails today, the system tries again after a few days, and so on several times before considering the subscription lost. In parallel, it is advisable to notify the customer by email that their payment did not go through, so they can update the card if the problem is theirs. A good retry strategy recovers a significant portion of charges that would otherwise become silent cancellations. In a subscriptions in WooCommerce portfolio, that rescue makes the difference between growing and stagnating.
The key to good dunning is idempotency: each retry must operate on the same renewal order, not create a new one each time. Otherwise you end up with duplicate orders and the risk of a double charge if two attempts coincide. A well-designed system reuses the pending order and ensures that it is charged only once.
VAT and VIES on renewals
Here is a common mistake: calculating VAT only on the first payment and forgetting renewals. But each renewal is a new transaction for tax purposes, and the applicable VAT may have changed. If you sell to companies in other EU countries, validating the intra-Community VAT number through VIES determines whether the transaction is exempt or not, and that status must also be checked on each cycle, not just when the subscription is created. Tax compliance is an area that subscriptions in WooCommerce cannot neglect.
A typical case: a company customer from another EU country with a valid VAT number is exempt from VAT at sign-up. Months later, if their number is no longer valid, the renewal should no longer be exempt. A system that revalidates tax status on each renewal protects you from invoicing incorrectly and from problems with the tax authorities. The same applies to the VAT rate applicable according to the product and the customer’s country.
Complete your operations: automatic invoicing with EHERO Woo Holded
Charging is only half the job; the other half is invoicing each renewal with tax validity. If you generate dozens or hundreds of recurring charges every month, issuing invoices manually is unworkable. That is why it is worth connecting your store with your invoicing software and letting invoices be generated automatically with each charge.
With EHERO Woo Holded you close the loop: each renewal order generates its invoice in Holded automatically, with the correct tax details and available to the customer. If you want to go deeper into how to set up this part, we have a specific guide on how to integrate Holded with WooCommerce step by step. The combination of recurring billing via Redsys plus automatic invoicing in Holded is the operation that lets you scale without drowning in administrative tasks. It is the piece that completes subscriptions in WooCommerce ready to scale.
Best practices for launching your subscriptions in WooCommerce
Before putting your first recurring product on sale, it is worth being clear about some principles that save headaches:
- Test the renewal charge in real conditions, not just the sign-up. Many problems appear on the second billing, not the first.
- Communicate the price and cycle clearly: how often it is charged, how much, and how to cancel. Transparency reduces chargebacks and complaints.
- Set up dunning from the start: define how many retries and at what intervals, and enable email alerts to the customer.
- Make cancellation easy: a customer who can cancel on their own gets less angry and sometimes comes back. Hiding cancellation generates bank disputes.
- Review tax compliance with your advisor, especially if you sell outside Spain or to intra-Community businesses.
WooCommerce is a solid and flexible base for building subscriptions in WooCommerce that truly work; you can learn more about the platform on the official WooCommerce website. The difference between a project that works and one that causes problems almost always lies in the subscription layer and the gateway you choose for billing.
Frequently asked questions
Can automatic renewals be charged with Redsys?
Yes. EHERO WooCommerce Subscriptions charges renewals automatically with Redsys through tokenization (reference payment), using the virtual POS you already have contracted with your Spanish bank.
Is Bizum suitable for recurring payments?
No. Bizum is designed for one-off payments validated by the user and does not allow the transaction to be tokenized, so it cannot schedule future automatic charges. For renewals you need a gateway with reference payment such as Redsys.
What happens if a renewal fails?
The system applies dunning: it retries the charge automatically after a few days and notifies the customer so they can update their card, recovering part of the payments that would otherwise be lost.
Is each renewal invoiced automatically?
With EHERO Woo Holded, each renewal order automatically generates its invoice in Holded, with the correct tax details and without manual intervention, allowing you to scale volume without extra administrative work.
Conclusion
Selling by subscription is one of the best decisions an online business can make, but in Spain the success of your subscriptions in WooCommerce depends on a factor that many solutions ignore: being able to charge automatic renewals with Redsys. Combined with good lifecycle management, a dunning strategy to recover failed payments, and automatic invoicing that complies with VAT on each renewal, you have a solid and scalable recurring operation. If you want to set all this up on your store with the Spanish payment gateway you already use, take a look at the EHERO WooCommerce Subscriptions listing and take the step toward recurring revenue.