WooCommerce Subscriptions Setup and Integration

WooCommerce Subscriptions Setup Turnkey

Imagine: a customer buys access to your online service, and a month later stops paying because the store didn't auto-charge. Every month you lose up to 40% of recurring revenue. Standard WooCommerce can't charge on a schedule. You need the paid WooCommerce Subscriptions plugin (costs $199/yr for single site, $399/yr for up to 5 sites). It adds the 'Subscription' product type, lets you set intervals, trial periods, and automatic payments via supported gateways. Without it, you must invoice manually or build a custom CRM integration.

We have configured subscriptions for 50+ projects — from food delivery to SaaS. Over 5 years, we identified common mistakes and found optimal configurations. For example, Stripe via WooCommerce Payments yields a 97% conversion rate on automatic payments when webhooks are set properly. That's 1.4 times better than manual invoicing (70% conversion). With an average check of $50/month and 100 subscribers, automation saves $1,500 per year by reducing churn. Our guaranteed recurring payment setup ensures you never miss a payment.

How WooCommerce Subscriptions Works

The plugin introduces the product types simple subscription and variable subscription. For each product you set: billing period (every N days/weeks/months/years), billing interval, free trial, and sign-up fee (one-time payment on activation). Technically, the plugin creates additional wcs_* database tables and extends wp_posts to store subscription data, schedules, and payment method tokens.

Choosing a Payment Gateway for Auto-Recurring Payments

WooCommerce Subscriptions requires a gateway that supports automatic recurring payments. Not all gateways do — they must explicitly declare support via the supports hook:

$gateway = WC()->payment_gateways()->get_available_payment_gateways()['stripe'];
if ( $gateway->supports( 'subscriptions' ) ) {
    // gateway supports auto-recurring
}

Compatibility table for popular gateways:

If the gateway doesn't support automatic recurring, the subscription falls back to manual renewal: the customer receives an invoice and pays manually. Conversion drops by 30%.

What to Do If Payments Don't Process?

The most common problem: the payment gateway doesn't support tokenization. Symptoms: Stripe/PayPal work, but a local gateway doesn't. Solution: verify that the gateway plugin declares $this->supports[] = 'subscriptions'.

The second cause: cron jobs aren't running. WCS uses WP-Cron for renewal payments. On hosts where built-in cron is disabled, set up a system cron:

*/5 * * * * www-data wget -q -O /dev/null "https://example.com/wp-cron.php?doing_wp_cron"

Alternatively, use Action Scheduler (included in WCS) with an external trigger. Action Scheduler is more efficient than system cron: it automatically retries failed attempts and consumes fewer resources. For loads over 1,000 subscriptions, we recommend it.

Typical Mistakes in Subscription Setup

1. Incorrect retry count: default is 3, but if customers frequently complain, increase to 5.
2. Missing trial period testing: ensure that after the trial ends, the payment fires.
3. Misconfigured webhooks: check that the webhook URL is externally accessible and processes invoice.payment_succeeded events.
4. Currency mismatch: if the subscription is in USD but the gateway only supports EUR, payments will fail.
5. Ignoring Action Scheduler: on high loads, WP-Cron causes delays.

How to Integrate Subscriptions with WooCommerce Memberships

Subscriptions often pair with Memberships: a paid subscription activates a membership that grants content access. The link is configured in WooCommerce → Memberships → Membership Plans → Edit Plan → Grant Access. We design this link so that when a subscription is canceled, access is automatically revoked.

Comparison of setup options:

What Is Included in the Work (Deliverables and Support)

1. Analysis — review of business model, plan selection, trial period calculation.
2. Gateway integration — registration, plugin installation, card tokenization.
3. Subscription product creation — price, interval, trial, sign-up fee.
4. Memberships integration — linking subscription → role → content access.
5. Full cycle testing — checkout, payment, notifications, cancellation.
6. Documentation — API hooks, manager instructions, troubleshooting guide.
7. Team training — 2-hour session on managing subscriptions in the admin panel.
8. Ongoing support — 30 days post-setup for any issues.

Installation and Basic Configuration

1. Download the plugin from WooThemes, install via Plugins → Add New → Upload Plugin.
2. Activate the license key in WooCommerce → Subscriptions → License.
3. In WooCommerce → Settings → Subscriptions set: mixed checkout, maximum failed payments (usually 3), email templates.

Creating a Subscription Product

Products → Add New
→ Product type: Simple subscription
→ Subscription price: period and amount
→ Free trial: 7 days
→ Sign-up fee: 0
→ Expire after: Never

For multiple plans, use Variable subscription with attributes.

Hooks for Customization

add_action( 'woocommerce_subscription_renewal_payment_complete', function( $subscription, $last_order ) {
    $user_id = $subscription->get_user_id();
    $plan    = $subscription->get_items();
    // update user role, send bonus
}, 10, 2 );

add_action( 'woocommerce_subscription_status_cancelled', function( $subscription ) {
    $user_id = $subscription->get_user_id();
    // revoke access, notify team
} );

Timeline and Pricing

Basic setup with one tariff and Stripe — 1–2 business days. Multiple tariffs, upgrades, Memberships — 3–5 days. Pricing is individual. Order setup now — we will select the optimal configuration. Get a consultation on payment gateways and tariffs. Our certified team guarantees smooth integration and ongoing support.

WordPress Development: Custom Themes, Plugins, and WooCommerce

A client arrives with a ready-made WordPress site—first thing in DevTools: 47 active plugins, page weight 6.8 MB, TTFB 2.4 s, five conflicting jQuery versions in the console. That's not rare; it's the standard for a "finished" site grown from a template into something alive but unmanageable. We solve such problems end-to-end—from audit to deployment. Get in touch—we evaluate your project in one business day.

WordPress holds 43% of the CMS market (Wikipedia)—not because it's perfect, but because it's predictable, extensively documented, and has an ecosystem for any task. The engineer's job is to use that ecosystem carefully, not turning the site into a dependency dump. We help find balance between functionality and performance, drawing on 10 years of experience and 80+ completed projects.

What are common architectural problems in WordPress?

Render-blocking from plugins

Plugin A loads jQuery 3.6, Plugin B loads jQuery 1.12, the theme has its own jQuery Migrate. The result: wp_enqueue_scripts delivers three different library versions, rendering blocked 800 ms before main content parsing. Solved with wp_dequeue_script, centralized dependency control, and defer/async for non-critical scripts.

N+1 queries and their solution

A developer wrote WP_Query in a loop—each post generates a separate SQL query. On a page with 20 posts, that's 21+ database queries. MySQL lags, server heats. Fixed with post__in plus prefetch, or switching to wpdb->get_results() with JOIN. Query Monitor is the first diagnostic tool.

WooCommerce under load

A store with 15,000 SKUs, no object caching, no Redis—at 200 concurrent users wc_get_product() kills the database. WordPress transients don't help: they write to DB, increasing load. The real solution is Redis via wp-redis or Memcached, plus wp_cache_set()/wp_cache_get() in custom code.

How to choose architecture: headless or monolithic?

The choice depends on performance requirements and interface complexity. Headless (REST API / WPGraphQL + Next.js) gives up to 50% TTFB improvement and frontend isolation, but requires more complex infrastructure. Monolithic themes are easier to maintain for content projects where SEO is critical and direct access to WP Rewrite is needed. We help determine the optimal option during audit. Switching to headless improves LCP by 2.5x compared to monolithic with proper caching—confirmed on 30+ projects.

How do we push LCP under 2.5s for production WordPress sites?

Achieving green Core Web Vitals requires systematic work: remove render-blocking resources (inline critical CSS, defer non-critical JS), serve WebP via <picture> with srcset, prefetch LCP image with fetchpriority="high", and implement Redis-backed full page caching. On stores, additionally prefetch WC_Product objects and disable plugin enqueues on irrelevant pages. Our audit reports baseline LCP, CLS, INP values and gives exact steps to hit Google thresholds.

Stack and approaches in WordPress development

Theme development. We do not use page builders like Elementor for product sites—they generate bloated HTML and lock clients into the visual editor forever. A custom theme based on _s (underscores) loads 4x faster than an Elementor theme. Instead: custom theme or block theme for Full Site Editing, Tailwind CSS via Vite, TypeScript for complex JS.

Gutenberg and block development. Since WordPress 5.0, Gutenberg is not just an editor—it's a platform. We develop custom blocks using @wordpress/scripts, register them with register_block_type() and block.json. Server-side rendering via PHP for SEO-critical blocks, client-side for interactive ones. Inner Blocks for composite components.

REST API and headless. WordPress as headless CMS via WP REST API v2 or WPGraphQL. Typical setup: WordPress on subdomain cms.example.com, Next.js frontend on main domain. ISR (Incremental Static Regeneration) for blog pages—page regenerates in background on request after revalidate expires, without blocking the user. For authenticated requests—JWT via jwt-authentication-for-wp-rest-api or Application Passwords (built-in since WP 5.6). More about REST API—Wikipedia.

WooCommerce. Extend via hooks and filters—never modify core files. Custom product types via WC_Product extension. For complex pricing logic—woocommerce_get_price_html and woocommerce_product_get_price. Payment gateways written from scratch, inheriting from WC_Payment_Gateway. Integration with 1C via CommerceML or custom REST endpoint.

Performance. Required stack: Redis Object Cache + Full Page Cache (LiteSpeed Cache or WP Rocket) + CDN for static files + WebP via add_image_size() with conversion. Native lazy load (loading="lazy") plus custom for critical images above the fold—preload with <link rel="preload">.

Case study: WooCommerce store, LCP 9.2s → 1.8s

From our practice: an electronics store, 40,000 SKUs, WooCommerce + custom theme. PageSpeed Insights: LCP 9.2s, CLS 0.41, INP 680ms.

Diagnosis:

• Hero image 3.8MB JPEG, unoptimized, no srcset
• 23 plugins loading JS/CSS on every page, including product pages
• wc_get_product() called 60 times on a category page without caching
• Fonts loaded via Google Fonts (additional DNS lookup)

What we did:

• Hero—WebP 180KB, <img fetchpriority="high" decoding="async">, srcset for 3 breakpoints
• Conditional plugin loading with is_product(), is_cart(), is_checkout()—removed 80% of unnecessary JS
• Redis Object Cache, WC_Product prefetch via wc_get_products() with include
• Fonts—self-hosted via @font-face, font-display: swap
• CLS fixed with aspect-ratio on all product card images

Result: LCP 1.8s, CLS 0.04, INP 140ms. Core Web Vitals—green. Client reduced hosting costs by 240,000 rub/year after moving to a cheaper plan made possible by reduced load. Additionally, replacing 10 plugins with one custom one saved another 80,000 rub/year on licenses.

Work process

1. Audit and analytics. Analyze existing codebase, competitors, technical requirements. For new sites—semantic core, UX prototyping.
2. Architecture. Decide: monolithic or headless. Define Custom Post Types, Custom Fields (ACF or native register_meta()), taxonomies.
3. Development. Local environment: Docker (nginx + php-fpm + MariaDB). Git with pre-commit hooks for PHP CS Fixer and ESLint. Deployment via WP-CLI + SSH or Buddy.works CI/CD.
4. Testing. PHPUnit for custom plugins. Playwright for E2E critical scenarios (add to cart → checkout → confirmation). Lighthouse CI in pipeline—fail if Performance Score < 85.
5. Deploy and support. Staging via WP Stagecoach or manual clone. Monitoring—UptimeRobot + Sentry for PHP errors. Plugin updates—via WP-CLI in test environment first.

What you get as a result

• Fully custom theme or modification of existing one
• Configured object caching (Redis/Memcached) and Full Page Cache
• Optimized media files (WebP, srcset, lazy load)
• Code structure documentation and update instructions
• Training for content managers on Gutenberg blocks
• 30-day uptime guarantee after deployment
• Access to repository with full change history

Timeline benchmarks

Pricing is calculated individually after requirements audit. Contact us for a preliminary estimate.

Common mistakes in WordPress development

• Directly editing theme files—all changes lost on theme update. Use a child theme or fully custom theme.
• update_post_meta() in a loop—each call is a separate UPDATE. For bulk operations use $wpdb->update() or update_metadata_by_mid().
• Disabled WP_DEBUG during development—hidden PHP Notices clutter error log and often indicate real issues.
• Storing media in Git—wp-content/uploads in .gitignore, sync via WP-CLI media import or rsync.
• No limit on WP_Query—posts_per_page => -1 on a page with thousands of posts guarantees a timeout.

Why trust WordPress development to professionals?

We have been on the market for over 10 years, completed 80+ projects, hold certifications from Automattic, and have experience with WooCommerce on high-traffic sites. Our solutions account for all nuances: from plugin compatibility to Core Web Vitals requirements (Google recommendations). After project completion you get a documented, tested, and scalable platform.

For a consultation and evaluation of your project—contact us. We respond within one hour during business hours. Get a free preliminary audit today.