WPFunnels Pro - WordPress Plugin

WPFunnels Pro Guide: setting up funnels, checkout, order bumps, and upsells in WordPress

WPFunnels Pro should be treated not as a basic plugin with a few buttons, but as a working control panel for building the customer journey in WordPress. In this guide, we will cover how to prepare your site, which settings to check after installation, how to build a WooCommerce funnel, where to place an offer on the checkout page, how to configure an upsell or downsell, and how to confirm that the final setup actually works.

This article does not repeat the product's short description. It is meant to be practical: from choosing the funnel type to troubleshooting cache issues, page templates, payment gateways, and conditional paths. If you have already installed the plugin, you can move through the sections like an implementation checklist.

The article uses the English names of interface items wherever they matter for accurate navigation in the admin panel: Checkout, Order Bump, Upsell, Downsell, A/B Testing, Save Changes. These are left untranslated so you can match the instructions to the actual product screen more quickly.

What problem the plugin solves and where it makes sense

The core idea behind WPFunnels Pro is to move funnel building directly into WordPress and WooCommerce. Instead of relying on a separate SaaS service, a store owner or marketer gets a visual path made of pages and offers: landing page, checkout, thank you page, order bump, upsell, downsell, lead form, conditional paths, and analytics. This approach is especially useful when the site already runs on WordPress, products are already set up in WooCommerce, and the team wants to adjust the customer journey without building a separate app.

The official materials describe WPFunnels as a builder for lead funnels and sales funnels. In practical terms, that means two different groups of use cases. The first is a lead generation funnel: landing page, opt-in form, thank you page, contact submission, and follow-up through an email service. The second is a commercial WooCommerce funnel: select a product, show the checkout, add an order bump, offer a post-purchase upsell or downsell, and track revenue across the steps.

Who WPFunnels Pro is a good fit for

The plugin is a logical choice for WooCommerce store owners, digital product sellers, course creators, marketers, and agencies that regularly build product journeys for specific campaigns. It is especially useful if you want to do more than just "put up a nice page" and instead manage the logic: which product leads into which funnel, which offer appears at checkout, where the buyer goes after accepting or rejecting an upsell, and which page should be tested in an A/B experiment.

The strongest use case for WPFunnels Pro is a controlled customer journey built around a specific product or product group. For example, a store sells a core bundle, offers a consumable at checkout as an order bump, shows an upgraded bundle after payment as an upsell, and if the customer declines, routes them to a lower-priced downsell. Manually, that kind of flow can easily turn into a disconnected set of pages. In WPFunnels, it stays visible as one connected map.

When another solution may be a better choice

WPFunnels Pro may be unnecessary if the site does not use WooCommerce and you only need a simple contact form. For a single static sales page with a standard "buy" button, a full funnel canvas may also be more than you need. If your team is already deeply invested in another funnel stack, such as FunnelKit or CartFlows, switching only makes sense after checking features, templates, compatibility with your current payment setup, and support for the page builder your team already uses.

There is also an operational factor to consider. A funnel requires more than just a plugin - you also need prepared products, clear offer logic, a test order process, cache exclusions, and someone responsible for analytics. If the team is not ready to maintain those processes, even a convenient visual builder will not solve the problem by itself.

What to check before installation

Before installation, make sure the site fits the scenario you have in mind. WPFunnels works inside WordPress, and commercial sales funnels depend on WooCommerce. If you are building a lead funnel, WooCommerce is not always required. If you are building checkout, order bump, upsell, or downsell flows, your products, payment methods, and core WooCommerce logic should already be in place.

Platform and environment check

The WordPress.org page for the free version of WPFunnels lists the minimum WordPress and PHP requirements, along with current testing status. Those numbers should not be copied into a guide as if they were a permanent compatibility promise, because they change over time. The practical rule is simpler: before rolling anything out, check the plugin page, the changelog, and a staging copy of the site. If the store is business-critical, do not enable a new checkout flow on the live site without running a test order first.

• Make sure your current version of WordPress, WooCommerce, active theme, and PHP are supported by the current version of WPFunnels.
• Update your backup of both the database and files before changing checkout logic.
• On the staging copy of the site, enable the same page builder you plan to use for the funnel pages.
• Prepare a low-cost test product or an internal payment method so you can complete checkout without risking real orders.
• Write down your current cache and optimization settings, because checkout, upsell, downsell, and thank you pages often need to be excluded from caching.

Preparing products and offer logic

A common mistake is starting with funnel design before deciding what is actually being sold at each step. With WPFunnels Pro, it is better to begin with a short outline: the main product, the add-on offered at checkout, the post-purchase offer, the fallback offer, the transition condition, and the expected outcome. This outline is not just for planning - it helps prevent random order bumps that have nothing to do with the purchase itself.

Safe preparation: the main product should make sense on its own, the order bump should complement the purchase, and the upsell should not break the promise made on the checkout page. If the offer looks like a random attempt to raise the order value, people are more likely to reject it, and it becomes harder to diagnose why.

For digital products, check file access and WooCommerce emails. For physical products, check shipping, taxes, and inventory. For courses, verify the connection to LearnDash, Tutor LMS, Creator LMS, or another learning platform only through confirmed documentation. If the integration is not necessary for the first rollout, postpone it: start with a simple WooCommerce funnel that is easy to test.

Installation, the setup wizard, and the first decisions

The basic WPFunnels installation follows the standard WordPress flow: Plugins, Add New, search by name, install, and activate. After the first activation, the documentation shows a setup wizard where you choose the funnel type, page builder, and template. Pro features require the Pro package to be installed, but this guide does not cover purchasing, entering a license key, or bypassing activation. The focus here is on the working settings of an already available product.

In the wizard, do not rush past the funnel type selection. Lead Funnel is designed for contact capture and does not require a full WooCommerce chain. Complete Funnel is intended for sales, checkout, order bump, upsell, downsell, and the thank you page. If you choose the wrong type, you may not "break" the site, but you will waste time rebuilding more than necessary.

Choosing a page builder

WPFunnels supports Gutenberg, Elementor, Divi, Oxygen, Bricks, and compatible builders through shortcodes or dedicated elements. Pick the builder your site actually uses in production. If the designer works in Elementor but the content manager is comfortable with Gutenberg, decide in advance who will maintain the funnel steps after launch. Mixing multiple builders inside the same funnel may sound flexible in theory, but in practice it makes maintenance, styling, and troubleshooting harder.

Importing a template or starting from scratch

The documentation offers two paths: import a ready-made template or start with a blank canvas. A template is convenient for a first launch because it immediately creates the page structure and shows the likely order of steps. Starting from scratch is better if you already have a finished design, unusual logic, or need to build a minimal funnel without extra elements.

For the first test, it is better to choose a simple template or a minimal three-step structure: landing page, checkout, thank you page. Add the order bump and upsell only after the base checkout successfully completes a test order. That makes it much easier to pinpoint which part of the journey is causing an issue if one appears.

Detailed post-installation setup

Do not jump straight into visual design after installation. First, open the WPFunnels settings and review the core logic: funnel type, page builder, template sync, permalink settings, opt-in settings, offer settings, and integrations. These parameters determine which steps are available and how the public pages will behave in a real store.

General: funnel type, builder, and templates

The general settings define the funnel type. Lead Funnel is designed for collecting contacts. Complete Funnel is required for sales through WooCommerce and unlocks a broader set of steps: checkout, order bump, upsell, downsell, and thank you. This is also where you select the page builder. After choosing a builder, use template synchronization so the library loads variants that match the selected editor.

If templates do not appear, do not start manually searching the web for archives. First, check whether the correct builder is selected, whether the settings were saved, whether the server is blocking external requests, and whether admin-side caching is causing a conflict. If the issue keeps happening, it is better to log it as a support case with the WordPress, WooCommerce, WPFunnels, and active builder versions included.

Permalink: step URLs and a clear structure

In the permalink settings, you can keep the default WordPress structure or define slugs for the funnel and its steps. The documentation describes options such as Funnel and Step Slug, Funnel Slug, and Step Slug. The best practical choice depends on the site: if the funnels will be used in advertising and analytics, readable URLs help the team identify steps more quickly and find them in reports.

Do not change permalinks on a live store without testing. After making changes, open the landing, checkout, offer, and thank you pages in a private browsing window, then run a test order. If your site uses redirects, caching, or server-level security rules, problems with the new URL structure may not show up immediately.

Opt-in settings: lead capture forms and spam protection

For lead funnels, check the admin email, notification subject line, and reCAPTCHA v3 if the form is attracting spam. Enabling reCAPTCHA too early without validating the keys can cause the form to stop submitting. For that reason, turn protection on in staging or during a low-traffic period, submit a test lead, and confirm that the contact ends up where you expect.

Offer settings: how upsells and downsells are handled in orders

The Pro offer settings determine whether accepted upsells and downsells are created as separate child orders or added to the main order. This affects accounting, email notifications, analytics, and support workflows. For most smaller stores, it is simpler to maintain a setup where accepted offers are added to the main order, but the decision still needs to be checked against the payment gateway, shipping setup, taxes, and the way your team processes orders.

This section also includes payment settings for offer pages: showing only supported payment gateways and skipping offers for unsupported gateways or free products. Do not disable these limits just to "cover" every buyer. If a gateway does not support a particular one-click flow, it is safer to skip the offer than to end up with a paid primary order and a stalled secondary payment.

Events and integrations: analytics, pixels, and addresses

The Pro integrations section covers Facebook Pixel, Google Tag Manager, and Google Maps API. Connect these only after the base funnel can reliably complete an order. Otherwise, your reports will be filled with false events that are hard to separate from technical tests. For GTM, agree on event names in advance: checkout, order bump, upsell, downsell, purchase. That makes it easier for a marketer to compare data across WPFunnels, WooCommerce, and external analytics tools.

The visual canvas and step logic

The canvas is the main working area in WPFunnels Pro. It turns the funnel from a list of pages into a diagram: which steps come in sequence, where an offer can be added, where a condition can be enabled, and where you can view a link or jump into editing. This matters for team workflows, because the marketer, designer, and administrator all see the same path.

Building from scratch

When you create a funnel from scratch, you set a name and choose the starting structure. If you do not add prepared steps in advance, the result is a blank canvas where steps are added manually. Early on, do not try to build a long chain. Start with a landing page, checkout, and thank you page. Then assign the product to the checkout step, and only after a successful test order should you add upsell, downsell, and conditions.

The documentation shows that new steps can be inserted between existing ones using the plus sign on the connection line. That is convenient when a simple funnel is already working and you later need to add an upsell between checkout and thank you. The key point is this: every new step requires more than a visual block on the canvas. It also needs the page, product, transitions, conditions, and analytics to be checked.

Importing a template

A template speeds up the start, but it does not eliminate the need for review. After import, WPFunnels places the steps in the correct order and opens them on the planning canvas. From there, you still need to assign a real product, rewrite the text, check the layout, replace images, configure checkout fields, and go through the flow as a customer. If the template includes multiple offer pages, you can temporarily disable part of the chain during the first rollout to validate the core sale first.

How to keep a long funnel manageable

A long funnel quickly becomes hard to manage. Use clear step names: not "Page 1" and "Page 2," but "Checkout - starter kit," "Upsell - extended pack," and "Downsell - mini pack." If you enable A/B testing, add the meaning of the variation to the name as well: "Landing - short offer," "Landing - video proof." That makes analysis easier and reduces the risk of accidentally sending traffic to a draft version.

Checkout, product, and order bump: where the main conversion happens

The checkout step is the core of a commercial funnel. The WPFunnels documentation shows that if no product is assigned, the checkout step displays the warning No Product Added. That is a helpful signal: the page design may be finished, but the sale is not actually functional until a product has been selected and the settings have been saved.

Assigning a product to the checkout step

Open the checkout step, go to the product settings, and use Add Product. In the search field, start typing the product name, then select the matching item from the suggestions and click Add. After adding it, review quantity, discount, coupons, and any additional settings. Finish by clicking Save Changes rather than navigating away to another screen.

If the product has variations, first review the WooCommerce product itself: pricing, inventory, attributes, shipping class, taxes, and visibility. The funnel should not hide a product setup issue. If the checkout cannot handle a variable product correctly, look for the cause in the combination of product settings, checkout widget, payment gateway, and WPFunnels version, not only in the page design.

Order bump as a point-of-purchase offer

An order bump appears directly on the checkout page and is meant to add an extra product quickly. A strong bump is directly related to the main purchase: an accessory, extension, consumable, template, consultation, or quick bundle. A weak bump competes with the main product or forces the buyer to reconsider what they are purchasing in the first place.

In WPFunnels, the order bump is configured through the Order Bump tab, the + Add Order Bump button, product selection, title changes, checkbox label, description, template style, placement, colors, and discount settings. In Pro scenarios, you can use multiple bump offers and conditions. Still, start with one. One well-matched bump is easier to validate than three competing offers fighting for attention.

Order bump placement

The documentation lists several positions: before order details, before checkout details, after checkout details, before payment options, after payment options, and pop-up offer. The best choice depends on the product. If the offer helps explain what is included in the order, it can sit near the order summary. If it is an extra warranty or service, placing it before payment often makes more sense. Pop-ups should be used carefully: they are noticeable, but they can also frustrate users and make mobile checkout worse.

Discounts and product replacement

The discount settings support multiple discount types as well as product replacement scenarios. Do not apply a discount automatically unless it genuinely helps the buyer decide. In some cases, it is better to present the bump as a useful add-on without an aggressive discount. If you enable replace product, always run a test order and verify that the correct product, quantity, price, and tax appear in the WooCommerce order.

Upsells, downsells, and conditional paths after checkout

Post-purchase offers are one of the main reasons to use WPFunnels Pro instead of a basic checkout plugin. After the main payment, the customer sees an additional offer. If they accept the upsell, the route can continue down one path. If they decline it, you can show a downsell or send them directly to the thank you page. The visual canvas helps keep that branching logic manageable.

How to add an upsell or downsell

The documentation describes a basic process: create the landing and checkout first, then choose Upsell or Downsell when adding a new step. The new step can be created from scratch or from a template. After that, you need to assign the offer product, design the page, verify the accept and decline buttons, and then connect the next route.

Do not make the upsell simply a more expensive version of the same product if the customer has already chosen the main bundle. It is better to explain the added value: a larger bundle, support, training, a license for more sites, premium templates, an accessory, or an implementation service. A downsell should usually lower the barrier: fewer features, a smaller bundle, a one-time offer, or a basic package.

Conditional journey: when conditions are actually worth using

Conditional paths in WPFunnels Pro can account for offer acceptance or rejection, cart total, amount ranges, billing or shipping country, previous opt-in activity, and other data available at a given step. That is powerful, but it is also easy to overcomplicate. A condition is worth enabling when it changes the meaning of the offer. For example, if the cart total is above a certain threshold, show a premium upsell; if the order bump was declined, offer a lower-priced alternative; if shipping is restricted by country, do not show a physical add-on.

For more complex rules, use + And and + Or carefully. + And means all conditions must be met. + Or means any single condition is enough. A mistake in that logic can cause a customer to never see the intended step or, just as bad, to end up there without a valid reason.

How to test branching

You cannot validate a conditional journey with a single order. You need at least two runs: one where the condition evaluates to true and one where it evaluates to false. If the condition depends on cart value, prepare two test products or two coupons. If it depends on accepting an offer, accept the upsell in one pass and reject it in another. After each run, review not only the public pages but also the order details in WooCommerce.

Practical example: a funnel for a core product and add-on sales

Let us walk through a concrete scenario. Imagine an online store selling a home care kit. The main product is a starter bundle. At checkout, you want to offer a consumable as an order bump, after payment an upgraded bundle as an upsell, and on rejection a mini bundle as a downsell. The goal is to increase average order value without making the main checkout more complicated.

Goal

Build a working path where the landing page explains the starter bundle, the checkout sells the main product, the order bump adds the consumable, the upsell offers the expanded bundle, and the downsell preserves an additional sale if the upsell is rejected. The result needs to be verifiable: products appear correctly in the WooCommerce order, transitions match the defined conditions, and the customer does not re-enter payment details where a one-click offer should apply.

Preparation

• Create or review the main WooCommerce product for the starter bundle.
• Create a product for the order bump and separate products for the upsell and downsell.
• Check the active payment gateway, because not every gateway supports post-purchase offer flows in the same way.
• Prepare the copy: a short landing page promise, the checkout headline, the checkbox label for the bump, the upsell arguments, and the downsell rejection button text.
• Disable caching for the funnel checkout, offer, and thank you pages until testing is complete.

Setup steps

1. Create a Complete Funnel and choose either a template-based start or a minimal structure from scratch.
2. Name the steps so they are easy to distinguish: Landing - starter kit, Checkout - starter kit, Upsell - extended kit, Downsell - mini kit, Thank You.
3. Open the checkout step, add the main product, review quantity, coupon, and discount settings, then click Save Changes.
4. On the Order Bump tab, add the consumable product, set a short title, checkbox label, and place it near order details or before payment options.
5. Add an upsell step between checkout and thank you, assign the extended kit, and design the page with two clear actions: accept the offer or decline it.
6. Add a downsell step for upsell rejection and connect the conditional journey: an accepted upsell goes forward, a rejected upsell goes to the downsell.
7. Configure the thank you page so the customer sees the final order summary and knows what happens next.

Verification

Open the funnel in a private window and place an order as a new customer. In the first run, accept the order bump and the upsell. In the second run, reject the order bump and the upsell, then accept the downsell. After each run, review the WooCommerce order: included products, totals, taxes, shipping, payment status, emails, and notes. If analytics is enabled, confirm that purchase, order bump, upsell, and downsell events are not duplicated.

Quick takeaway: this practical scenario is only complete after two different test paths. One successful checkout does not prove that the conditional journey and offer logic work end to end.

A detail people often miss

If the checkout looks correct but the order bump is not being added to the order, the issue may not be the design at all. It may be caused by product setup, variations, discounts, caching, or a conflict with checkout optimization. That is why it helps to document every test: which products were selected, which checkboxes were clicked, which gateway was used, and which next step was expected on each page.

A/B testing, analytics, and validating the result

WPFunnels Pro should not be run purely on instinct. If you change the landing page, checkout, or offer page, you need to understand what changed in the data. The documentation describes A/B testing as a way to create variants, split traffic, start or pause a test, review stats, and declare a winner. That is useful, but only when the experiment is run with discipline.

How to run a test without chaos

Pick one step and one hypothesis. For example, on the landing page, compare a short offer version against a version that includes social proof. Do not change the headline, price, product, checkout layout, and order bump all at the same time. If too many variables change, you will not know what actually affected conversion rate and revenue.

When creating variants, you can use a template or duplicate the original step. Duplication is useful when you want to change just one element and keep the rest of the page intact. After creating the variant, configure the title and URL slug, assign traffic distribution, lock a percentage to one variant if needed, click save, and only then start the test.

Which metrics to watch

The documentation mentions visits, revenue, and conversion rate for variants. For a WooCommerce funnel, look more broadly: checkout completion, order bump acceptance, upsell acceptance, downsell recovery, average order value, and refund-related warning signs. In some cases, a landing page variant generates more clicks but lower-quality buyers. In others, a checkout with fewer fields improves completion but creates shipping problems because an important field was removed.

When to declare a winner

Do not declare a winner after a few random orders. Wait until the sample size makes sense for your traffic level, and make sure there were no outside influences such as a promotion, email campaign, price change, payment failure, or an unavailable product. Once a winner is chosen, WPFunnels lets you archive the other variants. Before archiving them, save a note about what was tested and why this specific version was selected.

Safe improvements without editing the plugin core

With WPFunnels Pro, you should not edit plugin, theme, or WooCommerce files directly. Those changes will be lost during updates and can break checkout. It is safer to rely on layout settings, cache exclusions, and small CSS changes through a child theme, the Customizer, the Site Editor, or a snippets plugin. Code is only worth using when it solves a small visual problem and can be rolled back easily.

A small CSS tweak to make the order bump easier to read

If the order bump looks too subtle in your theme, you can add a soft highlight to the container. Before inserting anything, inspect the actual block class in the browser because the markup can vary across templates and versions. Below is an example that should be adapted to the real selector used on your checkout page.

/* Add this in a child theme or a safe CSS snippet.
   Before publishing, inspect the actual order bump class. */
.wpfunnels-order-bump,
.wpf-order-bump {
  border: 1px solid #f4a340;
  background: #fff8ef;
  border-radius: 8px;
  padding: 16px;
}

.wpfunnels-order-bump label,
.wpf-order-bump label {
  font-weight: 600;
}

The check is simple: open the checkout on desktop and mobile, tick the checkbox, make sure the order total changes, and then run a test order. If the visual result is worse or the selector affects unrelated blocks, remove the snippet and clear cache. CSS should only improve visual clarity, not alter checkout logic.

Cache compatibility as a required setting

The most useful technical improvement for WPFunnels is not code - it is proper cache exclusions. Exclude the funnel checkout, upsell, downsell, and thank you pages from page cache. If JavaScript optimization is enabled, do not combine or defer scripts that the checkout refresh depends on. After every change, run a test: add a product, accept the bump, complete payment, accept or reject the upsell, and open the thank you page.

When WPFunnels Pro is the right choice

WPFunnels Pro is worth using when you want to manage the customer journey inside WordPress and WooCommerce: build a checkout around a specific product, add a relevant order bump, show a post-purchase upsell, configure a conditional journey, validate the results, and improve pages based on data. It is not a substitute for sales strategy, but it is a practical tool for putting that strategy into technical execution.

Before going live, run through a short final checklist: the correct funnel type is selected, the main product is assigned, the order bump is added to the order, the upsell and downsell follow the intended conditions, the pages are excluded from cache, the payment gateway supports the chosen flow, the WooCommerce order looks correct, and analytics is not duplicating events. If all of that is confirmed, you can download WPFunnels Pro and move on to testing it on your copy of the site.

A good funnel does not have to be long. Start with a simple structure that is easy to explain and validate. Then add Pro features one at a time: first the order bump, then the upsell, then the conditional path, and only after that A/B testing. That order reduces errors and makes it easier to see which settings actually affect sales.