rickey29

<p><strong>FlxWoo</strong> is a premium WooCommerce extension that improves cart, checkout, and order confirmation page performance by delegating <strong>UI rendering</strong> to an external rendering service, while keeping <strong>WooCommerce fully responsible for all business logic</strong>.</p>
<p>FlxWoo is a <strong>product</strong>, not infrastructure. It provides:</p>
<ul>
<li>Optimized checkout UI rendering</li>
<li>Graceful fallback to native WooCommerce templates</li>
<li>Admin dashboard for configuration and monitoring</li>
</ul>
<p>FlxWoo does <strong>not</strong> replace WooCommerce functionality. Payments, shipping, taxes, coupons, validation, and order processing continue to run natively inside WooCommerce.</p>
<p>If the external renderer is unavailable, FlxWoo automatically falls back to standard WooCommerce templates.</p>
<p><strong>Looking for a free, self-hosted alternative?</strong> See <a href="https://github.com/rickey29/flexi" rel="nofollow ugc">FlexiWoo</a> – a free, open-source infrastructure project for developers who want full control over their WooCommerce rendering.</p>
<h3>What FlxWoo Does</h3>
<ul>
<li>Replaces the <strong>visual rendering</strong> of cart, checkout, and thank-you pages</li>
<li>Sends read-only WooCommerce data to a configured rendering service</li>
<li>Displays rendered HTML returned by the service</li>
<li>Falls back safely to native WooCommerce templates when needed</li>
</ul>
<h3>What FlxWoo Does NOT Do</h3>
<ul>
<li>Does not process payments</li>
<li>Does not calculate totals, shipping, or taxes</li>
<li>Does not modify carts or orders</li>
<li>Does not replace WooCommerce checkout logic</li>
<li>Does not store customer data outside WooCommerce</li>
</ul>
<p>FlxWoo is designed to be <strong>non-intrusive</strong>, <strong>reversible</strong>, and <strong>safe for production use</strong>.</p>
<h3>How It Works</h3>
<ol>
<li>A customer visits cart, checkout, or order confirmation pages</li>
<li>FlxWoo collects existing WooCommerce data (read-only)</li>
<li>Data is sent securely to a configured rendering service</li>
<li>Rendered HTML is returned and displayed</li>
<li>If rendering fails, WooCommerce templates are used automatically</li>
</ol>
<h3>Configuration</h3>
<p>After activation:</p>
<ol>
<li>Go to <strong>WooCommerce <span aria-hidden="true" class="wp-exclude-emoji">→</span> FlxWoo</strong></li>
<li>Review connection status</li>
<li>(Optional) Configure rendering service URL and timeout</li>
<li>Save settings</li>
</ol>
<p>All configuration is controlled by the site administrator.</p>
<h3>Fallback Behavior</h3>
<p>FlxWoo includes automatic fallback protection.</p>
<p>If the external rendering service is unavailable:<br />
– Native WooCommerce templates are displayed<br />
– Checkout functionality remains unaffected<br />
– No customer actions are blocked</p>
<h3>Privacy</h3>
<p>This plugin transmits cart and checkout page data to a configured external rendering service in order to generate HTML output.</p>
<p>No payment credentials or authentication secrets are transmitted.</p>
<p>Site owners are responsible for updating their privacy policy to reflect this behavior.</p>
<h3>Support</h3>
<p>Support is handled through the WordPress.org support forum.</p>


FlxWoo

Improve WooCommerce cart and checkout performance using a modern rendering approach with full fallback support.

bebjakub

<p>Next.js On-Demand Revalidation for WordPress on post updates, revalidate specific paths and tags on post updates.</p>
<p>Feel free to create a PR to <a href="https://github.com/Dexerto/on-demand-revalidation" rel="nofollow ugc">plugin Github repo</a>.</p>


On-Demand Revalidation

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

FlxWoo vs On-Demand Revalidation