CartFlows
CartFlows builds landing, checkout and upsell steps as a flow inside WooCommerce. It is a thin layer over a store you already own — which is both the reason to use it and the limit of what it can do.
CartFlows is a routing layer, not a store. WooCommerce still holds the products, the orders, the tax and the customers; CartFlows decides which page a buyer sees at each step and inserts offers along the way. Understanding that division answers most questions about what it can and cannot do.
What a flow is
A flow is an ordered set of steps, each a page:
- Landing — the sales page for one product or offer.
- Checkout — a custom checkout with the fields you choose, not the standard WooCommerce page.
- Upsell or downsell — an offer after payment, accepted without re-entering card details.
- Thank you — a confirmation page you control, with next steps.
Two of those are things WooCommerce cannot do on its own: a checkout designed per product, and a charge after the order without a second checkout. The other two are pages any builder makes.
What the free tier covers
The free plugin builds flows and steps, imports templates and gives you the custom checkout. The revenue features — order bumps, one-click upsells, A/B testing and funnel analytics — are paid.
That matters because the free tier's value is mostly cosmetic: a nicer checkout than the default. If the reason you are installing CartFlows is to raise average order value, you are buying the paid tier. Budget for it up front rather than building on the free version and rediscovering the paywall.
The gateway constraint
One-click post-purchase upsells require a gateway that can charge a stored payment method without fresh authorisation, and support is not universal. Regional authentication rules also affect what can be charged without the customer present.
Confirm your gateway supports it before designing a funnel around upsells. This is the single most common disappointment with any funnel plugin, CartFlows included. The gateway landscape is covered in WooCommerce payments.
CartFlows or FunnelKit
They occupy the same category and differ in emphasis.
| CartFlows | FunnelKit | |
|---|---|---|
| Centre of gravity | Flow and page structure | Checkout optimisation and automation |
| Built-in email automation | No | Yes |
| Cart abandonment | Add-on or external | Included in the paid tier |
| Feel | Lighter layer over Woo | Deeper replacement of the checkout |
Choose CartFlows when you want funnel structure and will handle email in a platform you already pay for. Choose FunnelKit when you want the cart-abandonment and post-purchase sequences in the same place as the funnel. Do not run both — two plugins claiming the checkout route produces a store nobody can debug.
The page builder relationship
CartFlows builds steps using whatever builder you run, and its templates come in builder-specific flavours. That is convenient and it means each funnel page carries the builder's assets on the most conversion-sensitive pages on the site.
Two implications. Your funnel inherits your builder's lock-in — see page builders — and the template you import is designed for a generic product, so treat it as a starting layout rather than a finished page. What actually makes these pages convert is in WordPress landing pages.
What it does not fix
- Traffic. A funnel converts visitors you already have; it does not produce them.
- A weak offer. Bumps and upsells amplify an offer that works and expose one that does not.
- Checkout problems. If the standard checkout misbehaves, a custom one built on the same store misbehaves too — checkout not working first.
- Shipping and tax complexity. Those remain WooCommerce settings, including shipping setup.
The lock-in, stated plainly
Mild on data, real on structure. Orders, products and customers survive removal untouched. What does not survive is the flow itself: steps, bumps, upsell logic and the routes between pages, none of which has an equivalent to migrate into.
The practical protection is to keep the standard WooCommerce checkout page functional rather than deleting it. When a funnel misbehaves during a sale — and it will, eventually — a working default checkout is the difference between reduced conversion and no orders at all.
Common mistakes
- Designing around upsells before verifying the gateway.
- Deleting the default checkout page.
- Running two funnel plugins at once.
- Importing a template and shipping it unedited, generic copy included.
- Not testing the whole flow with a real payment, including refund and the confirmation email — an untested funnel usually breaks at the step nobody looked at, and emails not sending is a frequent one.
Deciding
CartFlows is worth it for a store selling a small number of focused offers, with enough order volume that a few percent of average order value covers the licence, and a gateway that supports post-purchase charges. It is not worth it for a broad catalogue where buyers browse rather than enter through a single offer — there, the same effort spent on product pages and filtering returns more.
Frequently asked
- Yes. It builds flows around WooCommerce products, checkout and orders. Without a store there is nothing for it to sell, and a landing page plugin would be the right tool instead.
- Flow and step building, a custom checkout step, and the template imports. Order bumps, one-click upsells, A/B testing and the analytics that make any of it measurable are in the paid tier.
- Yes. Products, orders and customers are WooCommerce records and are untouched. What disappears is the funnel: the custom checkout steps, bumps, upsells and the routes between them.