FunnelKit

FunnelKit's proposition is that the default WooCommerce checkout leaves money on the table. It replaces that checkout with a designed one, adds order bumps before payment and one-click upsells after it, and layers cart-abandonment email on top. The proposition is largely true, and the cost is that your revenue path now runs through a plugin.

What it actually does

• Optimised checkout — a custom checkout page with field control, multi-step or single-step layout, and express payment buttons.
• Order bumps — an offer displayed inside the checkout, accepted with one tick.
• One-click upsells — an offer after payment, charged without re-entering card details.
• Funnel pages — landing, checkout, upsell and thank-you pages as a sequence with its own analytics.
• Automations — abandoned cart recovery, post-purchase sequences and win-back email driven by store events.

The order bump is the feature with the best ratio of effort to return. It is a single decision at the moment of highest intent, it does not interrupt anything, and it needs no new traffic.

The good part is the honest part

Two things FunnelKit does that WooCommerce genuinely does not.

Post-purchase upsells that do not re-run checkout. Charging a customer again on a stored payment method, in the same session, without a second checkout form, is not something you assemble from core. That is a real capability.

Store-event automation in the same place as the funnel. Abandoned cart email needs to know cart contents, recovery links and order state. Having that in one system rather than stitched between a store and a mail tool removes a category of breakage.

The constraint nobody reads first: gateways

One-click upsells require a payment gateway that supports charging a saved method without fresh authorisation. That support is not universal, and it varies by gateway and by country — strong customer authentication rules in particular change what can be charged without the customer present.

Verify your gateway before the funnel design assumes upsells exist. This is the single most common way a store buys the plugin for a feature it then cannot use. The wider gateway picture is in WooCommerce payments.

What the free tier covers

The free plugin gives you the checkout and funnel building at a basic level; the paid tier holds order bumps, one-click upsells, A/B testing, the fuller automation builder and the analytics that make any of it measurable.

That split is more aggressive than it first appears, because the free tier's value is mostly the part WooCommerce already does. If the reason you are installing FunnelKit is bumps and upsells, you are buying the paid tier — plan on it rather than discovering it after the free build.

The lock-in, stated plainly

Your orders, products and customers remain WooCommerce records. That is the important reassurance: the store's data is not hostage.

What is inside the plugin:

So the failure mode is not a lost store, it is a store that reverts to a default checkout on the day the plugin goes, with no equivalent to migrate the offers into. For a store whose conversion rate depends on the funnel, that is a meaningful dependency, and it is the reason to keep the standard checkout working rather than deleting the pages.

Where it overlaps with things you may already run

CartFlows occupies the same category with a different emphasis. A page builder can already build the pages. A mail platform can already send sequences, though without cart state. And several checkout-field plugins do the checkout half alone.

Running two of these at once is the mistake to avoid — two systems both claiming the checkout route produce a store where nobody can explain which page a customer sees. Pick one owner for the checkout path.

The performance cost is real too: funnel pages carry the builder's assets plus the plugin's, on the most conversion-critical pages on the site. Measure them the way you would any other page, using speeding up WordPress as the starting point.

Common mistakes

• Designing a funnel around one-click upsells before confirming the gateway supports them.
• Deleting the default checkout page, leaving no fallback when the funnel misbehaves — a common route into checkout not working.
• Running two funnel plugins and losing track of which owns the route.
• Sending abandoned-cart email without checking deliverability, so the recovery sequence lands nowhere; see WooCommerce emails not sending.
• Treating bumps as free money and stacking three of them, which reads as pressure and costs the base order.

Deciding

FunnelKit is worth it for a store with enough order volume that a few percentage points of average order value pays the subscription several times over, and a gateway that supports the post-purchase flow. Below that volume, the same effort spent on product pages, shipping clarity and checkout friction returns more, and it does not add a dependency to the path your money travels down.