WooCommerce as SaaS Platform

Joshua Maurer

Web Developer & Freelancer

February 17, 2026

WooCommerce can be extended with a custom plugin into a complete SaaS platform with subscription billing, automated license management, and access control – without custom cloud infrastructure.

For the SVE Tool ("Sowas von einfach" / "So simple") by Michael Lösel, I implemented exactly that: A price calculation tool for hair salons, where each salon purchases an annual license and chooses one of six tiers based on employee count. Instead of building a separate SaaS backend with Stripe Billing and cloud hosting, the entire system runs on a single WordPress installation.

In this article, I'll show how it works technically, what it cost, and when WordPress makes sense as a SaaS backend.

Can you run a SaaS product with WooCommerce?

Yes. WooCommerce comes with the foundation for recurring billing through the WooCommerce Subscriptions plugin. What's missing – license management, access control, and automatic activation – can be added with a custom plugin.

The situation with the SVE Tool was different. The operator knows WordPress, wants to manage tiers and content himself, and doesn't need a system for a hundred thousand users. WooCommerce provides payment processing, customer management, and the admin dashboard – all that's missing is the bridge between "customer paid" and "customer has access to the tool".

That bridge is exactly what the custom plugin provides.

What was the starting point for the SVE Tool?

The SVE Tool is an online calculation tool for hair salons. It helps salon owners calculate their prices correctly – based on employee count, fixed costs, and services.

The tool needed a license and billing system with the following requirements: Each salon purchases an annual license. The license is tiered by employee count – six tiers for salons with 0, 2, 5, 10, 15, or 30 employees. Billing runs automatically through WooCommerce Subscriptions, and when it expires or is cancelled, access is restricted.

It was also important that Michael can manage the system himself: Edit texts, change email content and intervals, create coupons, configure upgrade discounts, and add new tiers if needed. All through the WordPress backend, without having to call a developer.

How does license management work technically?

The license is linked directly to the WordPress user account – no separate license keys. Instead of generating and managing UUID-based keys, the plugin stores license data as WordPress user meta.

Specifically, four fields are stored per user:

• sve_license_active – whether the license is active (yes/no)
• sve_license_expiry – when the license expires (Unix timestamp)
• sve_license_level – which tier the salon has (1-6)
• sve_license_sku – which product was purchased (e.g., sve-licence-5-1y)

Standard WordPress functions like get_user_meta() and update_user_meta() are sufficient for all queries – no custom database tables, no migrations.

How does the tool check if a user has access?

The SVE Tool runs as a WordPress plugin on the same installation as the shop. This eliminates the need for an external REST API – access checking happens directly server-side via PHP.

The central function is SVE_Access_Control::check_access($user_id). It checks whether the license is active and whether the expiry date is in the future. It returns an access mode:

• full – full access, salon can create and edit calculations
• readonly – license expired, old calculations are viewable but no new ones possible
• none – no access

In the frontend, an AJAX endpoint checks access status, secured via WordPress nonces.

How does subscription billing work and what happens on cancellation?

WooCommerce Subscriptions handles all subscription management. Each license tier is set up as a WooCommerce Subscription product with annual billing. On purchase, the license is automatically activated in the user profile.

The plugin hooks into the subscription lifecycle via WordPress hooks. On successful renewal, sve_license_expiry is extended by one year. On cancellation, sve_license_active is set to no and the expiry date to 0. The salon then automatically switches to readonly mode.

What can the operator manage themselves?

The operator is not a developer, but he can manage the SVE Tool completely independently via the WordPress backend.

This was a central requirement from the start. A system where the operator needs a developer for every text change doesn't work long-term – especially not for a product that's actively being developed and marketed.

What data does the system provide to the operator?

Beyond pure license management, the backend contains an anonymized analysis of all user data. The operator can view average values across all salons – for example, average calculation values, frequently chosen price structures, or patterns in staffing.

The data is fully anonymized: It's not possible to see which salon has which values. But the aggregated statistics provide valuable insights that directly inform the tool's continued development.

What did development cost – and what would the alternative have cost?

The entire development of the license system, access control, and admin interface took four weeks part-time. Costs were in the low four-figure range.

For comparison – a classic SaaS solution with separate frontend, custom backend, Stripe Billing integration, and cloud hosting would have cost significantly more:

The biggest advantage isn't just the price. It's the fact that Michael immediately had a complete backend – product management, customer management, email delivery, coupon system, order overview. All of that comes free with WordPress and WooCommerce. With custom development, each of these features would have had to be built separately.

When is WooCommerce sensible as a SaaS backend – and when not?

WooCommerce is suitable as a SaaS backend for products with up to a few thousand users, a manageable tier structure, and an operator who knows WordPress. For real-time features, complex team permissions, or scaling to tens of thousands of users, custom development is the better choice.

WooCommerce works well when:

• The product has a few hundred to a few thousand users
• The operator wants to manage the backend themselves and knows WordPress
• The tier structure is manageable – with the SVE Tool it's six tiers, that's ideal
• Standard payment methods like PayPal or Stripe are sufficient
• The budget is limited and the product needs to go live quickly

For the SVE Tool, WooCommerce was the right choice. The product is growing organically, user numbers are in the triple digits, and the operator has full control over their system. Not every SaaS needs a Kubernetes infrastructure.