Headless WooCommerce checkout powered by Next.js — keep all payment gateways, shipping methods, and coupons working seamlessly.

Jason Bahl

WPGraphQL for ACF

WPGraphQL for ACF seamlessly integrates Advanced Custom Fields with WPGraphQL.

bebjakub

On-Demand Revalidation

Next.js On-Demand Revalidation for Wordpress on post updates, revalidate specific paths and tags on post updates.

Dropndot Solutions

Content Revalidation Tracker

Auto-triggers frontend revalidation on post, page, user, or taxonomy updates. Ideal for Next.js and headless WordPress setups.

rickey29

FlxWoo transforms your WooCommerce checkout into a modern, blazing-fast experience powered by Next.js, without breaking any existing functionality.
Instead of rebuilding checkout logic in JavaScript (and losing critical features), FlxWoo bridges WordPress/WooCommerce with a Next.js rendering engine. Your store keeps using:
<ul>
<li>✅ All payment gateways – Stripe, PayPal, Square, Klarna, local gateways, etc.</li>
<li>✅ Shipping methods & rates – All WooCommerce shipping plugins work</li>
<li>✅ Coupons & discounts – Smart coupons, dynamic pricing, etc.</li>
<li>✅ Tax calculations – WooCommerce Tax, TaxJar, Avalara, etc.</li>
<li>✅ Checkout extensions – Order bumps, upsells, custom fields, etc.</li>
</ul>
Perfect for agencies and developers who want a modern, custom-designed frontend without rewriting critical WooCommerce logic.
<h3>How It Works</h3>
<ol>
<li>Plugin installed → Detects WooCommerce cart/checkout/thank-you pages</li>
<li>Data collected → Aggregates cart, checkout config, and order data from WooCommerce</li>
<li>Sent to Next.js → Transmits data to your Next.js renderer via secure REST API</li>
<li>HTML returned → Next.js generates custom-designed HTML with Tailwind CSS</li>
<li>Graceful fallback → If Next.js unavailable, displays native WooCommerce templates</li>
</ol>
<h3>Key Features</h3>
<ul>
<li>🚀 Modern checkout design – Custom Tailwind CSS templates, fully responsive</li>
<li>🔒 Secure by default – Strict CSP headers, XSS protection, PII sanitization</li>
<li>⚡ Lightning fast – Server-side rendering, optimized payload (30-40% reduction)</li>
<li>🔄 Zero breaking changes – All WooCommerce plugins keep working</li>
<li>🎨 Professional templates – Conversion-optimized design, enterprise customization available</li>
<li>📱 Mobile-optimized – Responsive design, touch-friendly UI</li>
<li>🛡️ Production-ready – CORS handling, fallback mechanism, error recovery</li>
<li>🔧 Developer-friendly – REST API endpoints, TypeScript types, comprehensive docs</li>
<li>⚙️ Admin settings page – Easy configuration via WordPress admin (v2.1.0)</li>
<li>🏥 Health monitoring – Real-time system status and connectivity checks (v2.1.0)</li>
<li>🛡️ Rate limiting – API abuse protection with GDPR-compliant logging (v2.1.0)</li>
<li>📊 Error monitoring – Automatic issue tracking with PII sanitization (v2.1.0)</li>
</ul>
<h3>What’s Included</h3>
This Plugin (flx-woo – Open Source): 
– REST API endpoints (<code>/wp-json/flx-woo/v1/</code>) 
– WooCommerce data aggregation 
– Rendering proxy with fallback 
– CORS configuration (zero-config for most setups) 
– PII sanitization for logs 
– MIT License – freely available on WordPress.org
FlxWoo SaaS Renderer (Free During MVP – Closed Source): 
– Hosted Next.js rendering service 
– Modern cart, checkout, and thank-you pages 
– Professional design with Tailwind CSS 4 
– Automatic updates and security patches 
– 99.9% uptime SLA 
– Currently FREE to use – No signup or payment required during MVP phase 
– Note: The Next.js renderer is NOT open source and cannot be self-hosted
<h3>Requirements</h3>
<ul>
<li>WordPress 6.0 or higher</li>
<li>WooCommerce 8.0 or higher</li>
<li>PHP 8.0 or higher</li>
<li>FlxWoo SaaS renderer (automatically configured, currently free)</li>
</ul>
<h3>Why FlxWoo?</h3>
Most headless WooCommerce setups fail at checkout — payment gateways stop working, shipping calculations break, and coupons disappear. Developers end up rebuilding everything in JavaScript, which is expensive, time-consuming, and error-prone.
FlxWoo solves this by keeping WordPress/WooCommerce in control of business logic while Next.js handles only the presentation layer. You get a modern frontend without the risk.
<h3>Privacy</h3>
This plugin transmits data to an external service. Here’s what you need to know:
<h4>What Data Is Transmitted</h4>
When customers visit cart, checkout, or order confirmation pages, FlxWoo transmits the following data to the FlxWoo SaaS rendering service:
Cart Data: 
* Product details (name, SKU, price, quantity, images) 
* Cart totals (subtotal, tax, shipping, discounts) 
* Applied coupons and fees 
* Stock status and product variations
Checkout Data: 
* Available payment gateways (name and ID only – NO payment credentials) 
* Available shipping methods 
* Checkout form fields and validation rules 
* Customer billing/shipping addresses (if logged in)
Order Confirmation Data: 
* Order details (order number, status, totals) 
* Ordered items and quantities 
* Billing/shipping addresses 
* Customer email
Site Metadata: 
* Site name and URL 
* Currency settings 
* Locale and formatting preferences
What Is NOT Transmitted: 
* Payment credentials, API keys, or secrets 
* Credit card numbers, CVV codes, or payment tokens 
* Passwords or authentication tokens 
* Any data from pages other than cart/checkout/thank-you
<h4>Where Data Is Sent</h4>
Data is transmitted via HTTPS to the FlxWoo SaaS rendering service, a third-party service operated by FlxWoo.
Configuration (v2.1.0+): 
* Renderer URL is configurable via: WP Admin > WooCommerce > FlxWoo > Settings 
* Can also be set via <code>FLX_WOO_RENDERER_URL</code> constant in wp-config.php 
* Contact your site administrator for the specific renderer URL configured on your site
Purpose: Generate optimized HTML for cart, checkout, and order confirmation pages
Data Retention: No permanent storage. Data is processed in memory during page rendering (milliseconds) and immediately discarded.
Security: All transmission uses encrypted HTTPS connections with strict CORS policies and Content Security Policy headers.
Error Monitoring (Optional, v2.1.0+): 
* The Next.js renderer may send error reports to Sentry.io for debugging and reliability monitoring 
* All PII is automatically sanitized before transmission: 
 – Emails masked as <code>j***@example.com</code> (keeps domain for debugging) 
 – Phone numbers masked except last 4 digits 
 – Names, addresses, and sensitive data automatically redacted 
 – Passwords, tokens, credit cards completely removed 
* WordPress plugin does NOT send data to external error monitoring services 
* All WordPress logs remain local to your installation
<h4>External Service Information</h4>
Service Name: FlxWoo SaaS Renderer 
Service Provider: FlxWoo (operated by Rickey Gu) 
Service Purpose: HTML rendering for WooCommerce pages 
Service URL: Configurable via <code>FLX_WOO_RENDERER_URL</code> constant 
Privacy Policy: See PRIVACY.md in plugin directory or visit <a href="https://flxwoo.com/privacy" rel="nofollow ugc">flxwoo.com/privacy</a>
<h4>GDPR & Privacy Compliance</h4>
Legal Basis: Processing is necessary for contract performance (GDPR Article 6(1)(b)) – rendering the checkout pages you’ve requested.
User Rights: 
* Right to Access – Data available through WooCommerce’s data export tools 
* Right to Deletion – Use WooCommerce’s built-in data erasure features 
* Right to Object – Contact site administrator to disable FlxWoo
No Cookies: FlxWoo does not set any cookies. Standard WooCommerce session cookies remain in use.
PII Protection: Development logs automatically sanitize personally identifiable information (emails, phone numbers, IP addresses).
<h4>Your Responsibilities</h4>
As a site owner using this plugin:
<ol>
<li>Update Your Privacy Policy: Inform customers that cart/checkout data is transmitted to FlxWoo’s rendering service</li>
<li>Obtain Consent: Ensure your privacy policy covers this data transmission (required in some jurisdictions)</li>
<li>Keep Updated: Regularly update WordPress, WooCommerce, and FlxWoo for security patches</li>
</ol>
Suggested Privacy Policy Text:
<blockquote>
Our website uses FlxWoo to provide an optimized checkout experience. When you view your cart or checkout, your cart data and product selections are temporarily transmitted to FlxWoo’s rendering service via encrypted HTTPS connection. This data is processed in real-time and is not permanently stored.
</blockquote>
<h4>More Information</h4>
For complete privacy details, see: 
* PRIVACY.md – Full privacy policy in plugin directory 
* FlxWoo Website – <a href="https://flxwoo.com/privacy" rel="nofollow ugc">flxwoo.com/privacy</a> 
* Contact – rickey29@gmail.com for privacy inquiries
Note: This plugin is designed with privacy-first principles. All data transmission is necessary for functionality, occurs over encrypted connections, and involves no permanent storage.
<h3>Support</h3>
Author: Rickey Gu 
Website: <a href="https://www.flxwoo.com/" rel="nofollow ugc">flxwoo.com</a> 
Email: rickey29@gmail.com 
WordPress: <a href="https://wordpress.org/plugins/flx-woo/" rel="ugc">wordpress.org/plugins/flx-woo</a> 
Demo: <a href="https://demo.flxwoo.com/" rel="nofollow ugc">demo.flxwoo.com</a>
Need Help? 
* Report bugs: <a href="https://wordpress.org/support/plugin/flx-woo/" rel="ugc">WordPress Forums</a> 
* Feature requests: <a href="https://wordpress.org/support/plugin/flx-woo/" rel="ugc">WordPress Forums</a>

Alternatives to FlxWoo

Top alternatives