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>

FlxWoo

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

Jason Bahl

WPGraphQL for Advanced Custom Fields is a free, open-source WordPress plugin that adds ACF Fields and Field Groups to the WPGraphQL Schema.
<h4>Create ACF Field Groups</h4>
Create ACF Field Groups and Fields using the ACF User Interface, register them with PHP, or leverage ACF local JSON. Each field group and the fields within it can be configured to “Show in GraphQL.”
<h4>Query your fields with GraphQL</h4>
Once your field groups and fields are configured to “Show in GraphQL,” they become available in the GraphQL Schema for querying.
<h4>Supported Field Types</h4>
WPGraphQL for ACF provides support for most built-in field types of ACF (free & PRO) and extends support to most field types from ACF Extended (free & PRO).
<h3>Updating</h3>
If you are updating from WPGraphQL for ACF v0.6.* or older, check out the <a href="https://acf.wpgraphql.com/upgrade-guide" rel="nofollow ugc">Upgrade Guide</a>
For non-major version updates, automatic updates usually should work smoothly, but we still recommend you back up your site and test on a staging site.
Before updating WPGraphQL for ACF, review the release notes on <a href="https://github.com/wp-graphql/wpgraphql-acf/releases" rel="nofollow ugc">GitHub</a>.
We follow Semantic Versioning (Semver) for meaningful releases:
<ul>
<li>MAJOR version for incompatible API changes,</li>
<li>MINOR version for backwards-compatible functionality additions,</li>
<li>PATCH version for backwards-compatible bug fixes.</li>
</ul>
Learn more about Semver at <a href="https://semver.org" rel="nofollow ugc">semver.org</a>.
<h3>Support</h3>
<ul>
<li><a href="https://github.com/wp-graphql/wp-graphql/discussions" rel="nofollow ugc">General Help Requests</a>: For general questions and help requests, create a new topic in Github Discussions</li>
<li><a href="https://join.slack.com/t/wp-graphql/shared_invite/zt-3vloo60z-PpJV2PFIwEathWDOxCTTLA" rel="nofollow ugc">Slack Community</a>: The WPGraphQL Slack is a great place to communicate in real-time. Ask questions, discuss features, get to know other folks using WPGraphQL.</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/issues/new?assignees=&labels=&projects=&template=bug_report.yml" rel="nofollow ugc">Bug Reports</a>: Report a bug in WPGraphQL</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/issues/new?assignees=&labels=&projects=&template=feature_request.yml" rel="nofollow ugc">Feature Requests</a>: Suggest an idea, feature, or enhancement for WPGraphQL.</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/security/advisories/new" rel="nofollow ugc">Report a Security Vulnerability</a>: Report a security vulnerability.</li>
</ul>
<h3>FAQs</h3>
Does this work with ACF Extended?
Yes! WPGraphQL for ACF allows you to query for (most) fields created with ACF Extended.
Can I filter and sort queries by ACF Fields using WPGraphQL for ACF?
At this time WPGraphQL for ACF does not support filtering or sorting queries by ACF Fields. “Meta Queries” are often very expensive to execute, so we currently do not support filtering by ACF fields out of the box, but are exploring options for supporting it without the performance penalty.
I think I found a bug, where do I report it?
If you think you found a bug, please open an issue on <a href="https://github.com/wp-graphql/wpgraphql-acf" rel="nofollow ugc">GitHub</a>. The more details you provide in the issue, and the more clear your steps to reproduce are, the higher chances we will be able to help.
Can I use ACF Free or Pro with WPGraphQL for ACF?
Yes! WPGraphQL for ACF works great with ACF Free and Pro. The Pro version of ACF has some additional features, such as Flexible Content Fields, Repeater Fields and Options Pages that are supported by WPGraphQL for ACF.
Do I have to use Faust.js to use WPGraphQL for ACF?
No! While <a href="https://www.wpgraphql.com" rel="nofollow ugc">wpgraphql.com</a> and <a href="https://acf.wpgraphql.com" rel="nofollow ugc">acf.wpgraphql.com</a> are built using <a href="https://faustjs.org/" rel="nofollow ugc">Faust.js</a> and Next.js, you can use WPGraphQL for ACF with any GraphQL client, including Apollo, Relay, Urql, etc.
I have an ACF Extension that adds a new field type, will it work with WPGraphQL for ACF?
WPGraphQL for ACF supports the field types that come with ACF (Free and PRO) as well as the field types in ACF Extended (Free and PRO). Support for additional field types can be added by using the “register_graphql_acf_field_type” API.
Do I need WPGraphQL and ACF to be active to use this?
This plugin is a “bridge” plugin that brings functionality of ACF to WPGraphQL. Both WPGraphQL and ACF need to be installed and active in your WordPress installation for this plugin to work.
How much does WPGraphQL for ACF cost?
WPGraphQL for ACF is a FREE open-source plugin. The development is sponsored by <a href="https://wpengine.com/atlas" rel="nofollow ugc">WP Engine Atlas</a>.
Does WPGraphQL for ACF support GraphQL Mutations?
GraphQL Mutations are not yet supported. We are working on adding support for Mutations in the future. We are waiting for the GraphQL “@oneOf” directive to be merged into the GraphQL spec before we add support for Mutations.
Does this work with Field Groups registered in PHP or JSON?
Yes! You can register ACF Field Groups and Fields using the Admin UI, PHP or JSON. WPGraphQL for ACF will detect the Field Groups and Fields and add them to the GraphQL Schema. If using PHP or JSON, you will need to set the “show_in_graphql” setting to “true” to expose the Field Group and Fields to the GraphQL Schema. There might be other settings that need attention at the field group or field level that might impact the schema or field resolution.
<h3>Privacy Policy</h3>
WPGraphQL for Advanced Custom Fields uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect telemetry data upon user confirmation, helping us troubleshoot problems and improve the product.
The Appsero SDK doesn’t collect data by default and only starts gathering basic telemetry data when a user allows it via the admin notice. No data is collected without user consent.
Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses data</a>.

WPGraphQL for ACF

WPGraphQL for ACF seamlessly integrates Advanced Custom Fields with WPGraphQL.

FlxWoo vs WPGraphQL for ACF