FunnelKit Order Bumps - WordPress Plugin

How to Set Up FunnelKit Order Bumps for WooCommerce

FunnelKit Order Bumps lets you add a short extra offer to your WooCommerce checkout page that the customer can accept right before payment. This guide focuses on practical use rather than a promotional overview: how to prepare your store, create your first bump, choose a placement, configure the copy, display rules, products, discount, result checks, analytics, and troubleshooting.

The main purpose of this tool is to raise average order value without adding an extra step between cart and payment. But it is also easy to get an order bump wrong: show the wrong product, place the block in an awkward spot, make the discount unclear, enable pre-selection where it feels intrusive, or forget to exclude checkout from cache. That is why every key step below is tied to validation: what should change in the admin area, what the customer should see, and which symptom means the setup needs to be fixed.

This guide is written for WooCommerce store owners, marketers, and webmasters who already have a working site and want to test checkout upsells carefully. If you are still building the store, first stabilize your products, payments, shipping, taxes, and WooCommerce emails, then come back to order bumps. That makes the outcome easier to measure and safer to roll back.

Where an Order Bump Helps and Where It Just Gets in the Customer's Way

Order bumps work best when the extra product is clearly related to the main purchase and does not require a long decision. By the time the customer reaches checkout, their attention is limited. That is not the right moment to offer a complex bundle of options, an expensive product that needs separate explanation, or an item that changes the meaning of the order. A good bump supports one simple idea: the customer is almost done, and there is a small add-on nearby that makes the order more useful, more complete, or more convenient.

In WooCommerce, that usually means an accessory, consumable, warranty package, upgraded configuration, packaging option, digital add-on, service, express shipping, gift option, training material, or upgrade to the base product. FunnelKit Order Bumps matters because it goes beyond a static block. The documentation confirms skins, text and style controls, placement options for standard and mobile checkout, display rules, multiple bump offers, variable products, cart item replacement, limits on how many bump blocks are shown, analytics, and A/B experiments inside Funnel Builder.

A weak use case looks very different. For example, a store sells a niche technical product but shows a random popular item in the bump. The customer does not see the connection, the block starts to feel like noise, and overall conversion may drop. The same thing happens when the offer competes with the main product, makes the cart feel visually heavy, or requires a long explanation. An order bump should be a short, relevant decision next to a purchase that has already been made, not a second storefront inside checkout.

Common Cases Where the Plugin Makes Sense

In a store that sells physical goods, an order bump works well for accessories and purchase protection: a case for a device, a filter for a coffee machine, gift wrap, a spare part, an extended warranty, or a care kit. In a digital store, it might be a template, mini-course, extended license for a related asset, checklist, or setup package. In a service-based WooCommerce setup, useful offers include priority handling, consultation, expanded support, or an extra option tied to the order.

If your store already has clear product pairings, FunnelKit Order Bumps lets you move part of that strategy to the final step of the purchase. But the move should not be automatic. A related product on the product page and a bump on the checkout page serve different purposes. On the product page, the user is still comparing and evaluating. At checkout, they need to understand quickly why they should add the item, what it costs, whether shipping changes, and whether they can decline it with a single action.

When a Different Upsell Format Is Better

An order bump may be the wrong choice if the offer is expensive, needs demonstration, has many options, or depends on consultation. In those cases, a separate upgrade page, a one-click post-purchase upsell, a bundle on the product page, or a personalized recommendation in email usually works better. FunnelKit supports other funnel elements as well, so an order bump does not have to do everything. Its strength is a small, contextual offer that can be accepted quickly.

There is also an ethical issue to consider. Pre-selecting the bump by default is technically possible in the settings, but it should be used carefully. If the product is added to the mini cart automatically and the customer does not notice until payment, the store may gain support complaints instead of trust. For most stores, it is safer to start with a normal unchecked state and measure acceptance based on an intentional click.

Practical rule of thumb: if the value of the bump cannot be explained in one short line next to the checkbox, that product probably does not belong in an order bump. Simplify the offer first, then test the placement and the copy.

What to Check Before Installing It on a Live Store

FunnelKit Order Bumps runs inside WooCommerce and FunnelKit Funnel Builder, so the quality of the underlying checkout page matters just as much as the bump itself. Before installation, verify the core purchase flow: the product is added to cart, shipping is calculated, a payment method is available, the order email arrives, the order status changes predictably, and the thank-you page opens without errors. If that flow is already unstable, an extra block will only make troubleshooting harder.

You should also confirm what has replaced your standard checkout page. FunnelKit lets you create Store Checkout, which acts as the global checkout experience for the store, and attach order bumps to it. If the store uses a custom checkout from another theme, builder, or standalone plugin, first make sure it is not overriding WooCommerce templates or conflicting with FunnelKit. FunnelKit documentation includes sections on checkout page compatibility, caching, and popular builders, but your exact site stack still needs to be tested on a copy.

Minimum Checklist Before the First Bump

• WooCommerce can place a test order without errors. Check a simple product, shipping, tax, payment, and the order email.
• FunnelKit Funnel Builder is active and opens in the admin area. If the dashboard shows a REST API connection error, fix that first instead of building a bump blindly.
• The checkout page is not cached like a normal static page. Aggressive caching can show stale cart contents or break dynamic checkout elements.
• The bump product is published, purchasable, and in stock if inventory is tracked. A hidden or unavailable product will not produce a reliable outcome.
• Your theme is not hiding important checkout areas with its own styles. Pay special attention to the mini cart, payment methods block, and the area near the place order button.
• You have a rollback path. In most cases, it is enough to disable the specific bump, turn off the experiment, or temporarily deactivate the related funnel without deleting the order or the products.

If you are working on a live store, start with a single test bump for a low-risk or internal product and show it only under a narrow rule. For example, show it only for one main product, only in one category, or only inside a copied checkout funnel. That lets you validate the mechanics without risking an unfinished offer being shown to all customers.

Why Cache and Security Come Before Design

The appearance of the bump matters, but correct checkout behavior matters more. FunnelKit relies on WooCommerce data and its own API requests in the admin panel. If a caching plugin, CDN, server cache, or firewall interferes with checkout pages or the REST API, you may see symptoms that look like a design issue: the bump does not appear, the block shows in the wrong place, the panel does not load, or analytics stay empty. In reality, the cause may sit in the cache or security layer.

So before you fine-tune the details, exclude checkout pages from cache according to the documentation for your caching plugin and FunnelKit's guidance. For FunnelKit admin errors, the documentation specifically references the /wp-json/funnelkit-app/ path: if a security plugin, firewall, or server protection blocks that namespace, the dashboard may show a communication failure. Do not disable security permanently just for testing. First review the block logs, allow the exact path, and open the panel again.

How the First Order Bump Is Created in Funnel Builder

The work starts not on the product page, but inside the checkout funnel. In FunnelKit documentation, the basic flow looks like this: after adding a checkout page to the funnel, the user clicks Add Order Bump, enters an internal bump name, imports a skin, selects a product, and then moves through the design, product, rules, and settings tabs. On a real store, it helps to think of this not as a button sequence but as a chain of decisions: where the bump lives, which product it offers, how it looks, who sees it, and how it is validated.

The internal bump name is not visible to the customer, but it matters for analytics and maintenance. A label like Case for camera checkout bump or Gift wrap for premium box is much more useful than Bump 1. A month later, you will be reviewing reports, A/B variants, display rules, and multiple offers. A clear name saves time and reduces the chance of editing the wrong block.

Creating the Entry and Choosing a Skin

Once you click Add Order Bump, FunnelKit creates a separate element under the checkout page. The next step is importing a skin. The skin defines the starting layout and visual style of the block: where the checkbox or selection button appears, how the headline is highlighted, where the image sits, what the border looks like, and how the offer is framed. You can change the skin later, but for the first setup it is better to choose one that does not fight your store theme or force the customer to relearn the interface.

For an initial launch, choose a calm skin: a clear area, noticeable checkbox, short headline, small product image, and price or value without clutter. A bold skin can work for a promotion, but it should not overpower the payment fields. If checkout is already dense, a minimalist option is usually safer. The goal of the first launch is to get honest acceptance data, not to win a banner contest.

Adding the Product and Defining the Basic Pricing Setup

In the product tab, choose the product that will be added to the order. FunnelKit supports simple products, variable products, and in some cases subscription products, as long as the matching WooCommerce setup is already configured on the site. You can also set a discount and quantity at the offer level. The key here is not to mix merchandising decisions with visual ones. First decide what is being added and why, then shape the copy and emphasis around it.

If the product has variants, do not hide that choice. FunnelKit documentation shows merge tags such as {{product_short_description}} and {{variation_attribute_html}} so the customer can see the selection button and the chosen variation. This is critical for products with size, color, configuration, or subscription period options. If the user accepts the bump without understanding which version they selected, you will end up with support requests and cancellations.

Do Not Publish Too Early

Do not publish the bump immediately after selecting the product. First go through the Design, Products, Rules, and Settings tabs. Even if a field looks optional, it affects validation. For example, desktop and mobile placement can differ; display rules can hide the block in your test case; pre-selection can add the product to the mini cart right away; hide-after-selection changes what happens after acceptance.

Quick takeaway: your first order bump is not truly set up after clicking Add, but after you can see it on a test checkout page, accept the offer, remove it from the cart, and find the outcome in the order or analytics.

Post-Install Setup: Copy, Skin, Placement, and Block Behavior

The most useful part of FunnelKit Order Bumps is in the design and behavior settings. This is where the customer decides whether the bump feels like a relevant add-on or an annoying interruption. FunnelKit documentation for order bumps highlights the Content, Skin, and Style tabs, desktop and mobile placement, default pre-selection, hide after selection, image controls, exclusive offer text, and social proof tooltip. You do not need to enable everything at once. The goal is to build a clear minimal block first, then improve it based on real data.

Offer Copy: Short Headline, Clear Value, and an Honest Action

Use the Content tab to configure the visible copy. A good headline does not just repeat the product name. It explains why the offer fits the current order. For a camera, for example, instead of simply writing Memory card, use a short line that makes it clear the card is needed to start shooting right away. The description should answer one question: why is this worth adding now? If the description takes more than two meaningful sentences, you are probably trying to sell a product that is too complex for an order bump.

FunnelKit supports merge tags for bump descriptions. One useful example from the documentation is {{quantity_incrementor}}, which helps add quantity controls. For variable products, tags that show the description and the selected variation are especially important. But merge tags should be used only when they help the customer make a decision. If you add a technical element just for decoration, the block becomes heavier and harder to validate.

How to Write Copy Without Pressure

Avoid wording that creates fake urgency or hides the price. Instead of last-chance messaging, explain the connection: complete the kit, add protection, include a consumable with the main product, choose the right version. Price, discount, and action should appear together. The customer should understand exactly what will be added to the order after the click.

Placement on the Checkout Page

FunnelKit lets you choose bump placement separately for desktop and mobile. The documentation lists desktop areas above and below the order summary, above and below payment gateways, inside mini cart, above checkout form, above mini cart, and below mini cart. Mobile checkout has its own placement options as well. This matters because a block that looks clean in the right-side mini cart on a wide screen may appear too early or too low on a phone.

For the first test, start with a position where the connection to the cart is obvious. Inside mini cart works well for accessories and small add-ons because the customer sees the bump next to the order contents. Above payment gateways or below payment gateways is a good fit for services, warranties, packaging, and offers that naturally belong right before payment. Above checkout form can be noticeable, but it adds informational noise before the customer enters their details, so it should be used carefully.

Desktop and Mobile Do Not Need to Match

On mobile, page length and attention order matter more. If the bump appears too early, the customer may not have seen shipping costs yet and may not understand the full context. If it appears too late, they may never scroll far enough to see it. So test the mobile position separately: open checkout as a customer, add the main product, scroll at a natural pace, and make sure the bump does not disrupt the sequence of address, shipping, payment, and the place order button.

Pre-select and Hide after Selection

The Pre-select order bump by default option preselects the offer and places the product into the mini cart on the checkout page. This can be useful for a free gift, a required bundle, or a pre-agreed configuration. But for a normal paid upsell, it should only be enabled after careful testing. If the customer does not expect the total to change, trust in the checkout drops.

The Hide order bump after selection setting hides the bump after the customer selects it. This can reduce visual noise if the accepted offer is already visible in the mini cart. But before enabling it, check how the customer reverses the choice. If the block disappears and the product can only be removed through a tiny icon in the order summary, some users may get confused. For an initial launch, it is usually safer to keep the bump visible and confirm that the selected state is easy to understand.

Offer Image and Styling

The Order Bump Image and Style sections let you configure the product image, border, background, spacing, colors, description, price, call-to-action text, and other visual details. Style the block to fit the checkout, not the store homepage. The checkout page should stay calm and predictable. A bright background is fine if it highlights the offer, but it should not distract from required fields or look like an error state.

If your theme already applies heavy styling to WooCommerce, make changes gradually. First adjust the copy and placement, then choose the skin, then refine colors and spacing. After each step, check both desktop and mobile. That makes it easier to see what actually improved or damaged the behavior of the block.

Display Rules: How to Avoid Showing the Same Bump to Everyone

Display rules are one of the main reasons to use FunnelKit Order Bumps instead of a simple static block. Without rules, the bump may show on the checkout page to all eligible buyers by default. That is convenient for a first test, but it is rarely the best long-term setup. Rules help you show the offer only when the cart contents, total amount, selected products, or funnel context make it relevant.

In FunnelKit documentation, the Rules tab lets you add conditions and combine them with And and or logic. The key idea is that each condition narrows or expands the audience. If you use multiple rules, your test case has to satisfy all of them. Otherwise, the bump will not appear even if the product, skin, and placement are configured correctly.

An Example Rule Structure for Related Products

Imagine a photography store. The main product is a camera, and the bump is a memory card. The simplest rule is to show the bump when the cart contains a product from the camera category. If the store sells several kinds of cameras, a category-based rule is better than a rule tied to one specific product. If customers already add memory cards manually on a regular basis, you can add an exclusion: do not show the bump when the selected card is already in the cart. That prevents a duplicate offer and keeps the checkout page clean.

Another example is gift wrapping. You may want to show it for physical products but not for digital downloads. In that case, the rule should take product type, category, or specific exclusions into account. If shipping availability depends on the destination country, do not promise gift wrap to every user until you have confirmed the service is available for their address. For order bumps, fewer impressions with higher relevance is usually the better tradeoff.

Exclusions Matter More Than Blanket Reach

On the FunnelKit product page, the documentation describes an exclusion example using a cart item condition: if you need to remove a bump for a specific product, you set a rule that the cart must not contain that product. The principle is simple: do not show an offer where it conflicts with the current order. This is especially important for upgrades, consumables with compatibility differences, and products that are already included in a bundle.

A common beginner mistake is assuming that more impressions automatically mean more profit. In practice, an overly broad bump can hurt checkout usability and damage your data. If the same block is shown to customers across very different categories, you will not know who actually needs it. Start with a narrow rule, measure acceptance, and expand the audience only after validation.

How to Test Rules Without Guessing

1. Create a test main product or use a low-risk one. This keeps the bump validation separate from real orders.
2. Add only the product that should trigger the rule to the cart. Open checkout in a new window or a private session.
3. Confirm that the bump appears in the correct position. If it does not, review not just the design but every rule condition.
4. Add a product that should exclude the bump. Make sure the offer disappears or does not display.
5. Repeat the check on mobile. The rule may be correct, but the placement on a phone could make the block almost invisible.

Once the rule works, write the live use case into your store notes: which main product triggers the bump, which product is added, where the block appears, which exclusions are enabled, and what should be visible in the order. It is a simple habit, but it helps a lot when you troubleshoot weeks later.

Products, Variations, Quantity, and Replacing Instead of Adding

The Products tab controls exactly what gets added to the order after the bump is accepted. This is an easy place to make mistakes because visually, all offers can look similar while the underlying merchandising behavior is very different. One thing is adding an accessory alongside the main product. Another is replacing a cart item with a more expensive version. A third is letting the customer choose a variation of a variable product. FunnelKit supports these use cases, but each one needs separate validation.

A Simple Product Is the Safest Starting Point

If you are launching your first bump, start with a simple product: one SKU, clear price, clear stock, no variation selection. That reduces the number of moving parts during troubleshooting. The customer checks the box, the product appears in the mini cart, the total recalculates, and the order is created with two line items. Once that basic flow works, you can move on to variable products, quantity, discounts, and more complex rules.

For a simple product, test three states: the product is in stock, the product is already in the cart, and the product is unavailable for purchase. That last state is especially important. If the product is hidden, discontinued, or out of stock, do not assume the bump will explain the problem gracefully to the customer. It is better to suppress that offer with rules or replace the product.

Variable Products and Variation Selection

A variable product requires additional clarity. FunnelKit documentation describes the Choose an Option button, the variation selection popup, and the {{variation_attribute_html}} merge tag that helps display the selected option. This matters not only for usability but also for order accuracy. If the customer adds a shirt, coffee set, or subscription with variations, they should see the chosen size, flavor, term, or configuration before payment.

Testing a variable bump should include at least two options. Select one variant, verify that it appears correctly in the bump and in the order, then go back and choose another. If the store uses swatch plugins, custom attributes, or dynamic pricing, check visual compatibility as well. Not every polished variation selector works equally well inside an extra popup or a checkout block.

What to Do If the Selected Option Is Not Visible

First confirm that the description uses a documented merge tag for displaying variation details. Then check whether you selected the correct variable product rather than the wrong entry. After that, temporarily disable cosmetic theme styles that may be hiding the selection link or the attribute text. If the cause is still unclear, it is better to keep the bump simple until you review the documentation and support options than to launch a version the customer cannot verify.

Quantity and quantity_incrementor

FunnelKit documentation shows the {{quantity_incrementor}} merge tag and a PHP filter for displaying quantity controls in the right-side area. Quantity controls are useful for consumables such as cartridges, filters, packs, batteries, and similar replenishable items. They are unnecessary for services, warranties, and one-time digital add-ons. The customer should see exactly as much choice as they need to make a clear decision.

If you use quantity selection, validate the final total and inventory behavior. For a product with limited stock, the bump should not let the customer choose more than the store can fulfill. For a shippable product, make sure the shipping cost updates correctly when the quantity increases. If shipping recalculates too late, the customer may see an unexpected amount at the end of checkout.

FunnelKit documentation includes a small snippet for showing the quantity incrementor in the right-side area. Add it only through a child theme or Code Snippets, not by editing plugin files or the parent theme.

add_filter('wfacp_display_quantity_increment', '__return_true', 999);

After adding it, open a test checkout page, accept the bump, change the quantity, and verify the mini cart, final total, stock level, and created order. If the quantity control breaks the layout or confuses the customer, disable the snippet and keep the quantity fixed in the product tab.

Replacing a Cart Item

The Replace Order Bump with a Cart Item use case is for situations where the bump does not add a second product, but replaces the base item with a more suitable or more expensive one. The documentation explicitly notes that this approach is often used for subscription upgrades. In a standard store, that could mean upgrading a basic bundle to an extended one, replacing a standard configuration with a premium one, or switching from a one-time purchase to a subscription.

This mode requires especially clear copy. The customer needs to understand what happens to the original item. Do not just say "add an upgraded version." Explain it directly: the base item will be replaced with the expanded bundle, the final amount will change, and the order will contain the new line item. Check the order in the admin area: the original product should disappear or change according to the selected logic, not remain alongside the new product.

How the Offer Moves from Rule to Order

FunnelKit Order Bumps has a useful mechanic that is easy to overlook: the visible checkout block is only the final part of the chain. Before that, the store already knows the cart contents, the active checkout page inside the funnel, the selected rules, the placement settings, the bump product, the discount, the quantity, and what should happen after the customer accepts the block. When the customer opens checkout, FunnelKit has to decide whether to show the offer, where to place it, and what to change after acceptance.

It helps to keep that flow in mind whenever you configure or troubleshoot a bump. The input is a checkout page load for a specific cart. FunnelKit then checks which checkout page belongs to the current funnel, which published order bumps are attached to that page, which rules pass, and whether the global limit for displayed bumps has been reached. The selected bump then receives its desktop or mobile position, skin, and content. After the customer clicks, WooCommerce recalculates the cart and the order receives the extra item, the replacement product, or the selected variation.

Input: Cart and Checkout Context

If the bump does not appear, start with the input conditions. Is the cart actually holding the product that should trigger the rule? Has a product been added that excludes the offer? Are you opening the exact checkout page to which the bump is attached? Are you testing the old default WooCommerce checkout instead of Store Checkout? These questions sound basic, but they explain a large share of cases where the admin believes everything is configured while the customer still cannot see the block.

Processing: Rules, Limits, and Placement

After the input comes condition handling. If the rule does not match, FunnelKit does not need to display the bump. If multiple bump blocks match, a global display limit may apply. If the selected position is poor, the block may end up below the visible part of the page or next to an area the theme has altered. That is why troubleshooting should start from behavior, not appearance: is the bump published, does the rule pass, is it being hidden by the limit, and is the position set correctly?

Output: Mini Cart, Recalculation, and Order

The correct outcome is visible in three places. On the checkout page, the customer sees the selected bump and the recalculated total. In the mini cart, an extra line item appears, or a new product version appears if replacement is being used. After a test order, the WooCommerce admin area should show a clear product line, quantity, price, and applied discount. If any of these levels do not match, do not publish the bump for all users yet.

Result check: for each bump, write down the expected chain in one line: main product in cart - rule passes - block appears in position - customer accepts - total recalculates - order contains the correct item.

Practical Example: Accessory Offer for a Main Product Without Unnecessary Pressure

Let us walk through a concrete use case that is easy to reproduce on a test WooCommerce store. Suppose the store sells cameras, and customers often buy a memory card with them. The goal is to offer the memory card on the checkout page only to customers who have a camera in the cart, and not show the bump if the card has already been added manually. This is a classic FunnelKit Order Bumps setup: the offer is tied to the main product, easy to accept quickly, and does not require a separate consultation.

Goal

You want a clean block in the mini cart or near the payment gateways: a short headline, a small image of the card, a clear price, an acceptance checkbox, and correct addition of the card to the order. You do not want to add the product automatically without customer consent, so default pre-selection should stay off. Later you can A/B test the placement or the copy, but the first launch should be transparent.

Preparation

Create or choose a main product called "camera" and a product called "memory card." Verify that the card is published, in stock, and available for purchase. If the card comes in different storage capacities, it is better to use a simple product or one specific variation for the first test. If you want to sell a variable product, prepare the selected variation display using the appropriate merge tag and check the selection popup.

Setup Steps

1. Open Funnel Builder and the correct checkout page. For global checkout, use Store Checkout if it has already been created and assigned to the store.
2. Click Add Order Bump next to the checkout page. Give it an internal name, for example Memory card for camera checkout.
3. Import a calm skin. For the first test, a version with a clear checkbox and a small image is a good fit.
4. In the Products tab, choose the memory card. If you want a discount, set it here, but do not hide the final price in the copy.
5. In the Content tab, write a short headline. For example: add a memory card to your camera and start shooting as soon as it arrives.
6. In the Style tab, choose the position. On desktop, start with Inside Mini Cart; on mobile, test a position near payment or the mini cart.
7. Leave Pre-select order bump by default turned off. The customer should actively accept a paid offer.
8. In the Rules tab, add a condition for the camera product or category. Then add an exclusion if the memory card is already in the cart.
9. Save the changes and open checkout as a customer. Do not validate it only on the admin page; check the public-facing storefront.

Validation

Add the camera to the cart and go to checkout. The bump should appear in the selected position. Accept the offer, make sure the memory card is added to the mini cart, and confirm that the total changes as expected. Complete a test order using an appropriate safe payment method, then open the order in the WooCommerce admin area. The order should include both the camera and the memory card with the correct quantity and price.

Now test the reverse case: add the memory card to the cart manually before opening checkout. If you configured the exclusion, the bump should not appear. Then test mobile: the block should not overlap fields, break scrolling, or distract from the place order button.

A Common Pitfall

If the bump does not appear, do not change the skin immediately. Check the category or product rule. The test product may be in the wrong category, the wrong product ID may be selected, the memory card may already be in the cart, or you may be opening the wrong checkout funnel. If the bump appears but does not get added to the order, check product availability, stock status, and JavaScript errors from the theme on checkout. If the total updates only after a reload, look at caching, the mini cart, and WooCommerce dynamic fragments.

Multiple Bump Offers, Display Limits, and Single-Choice Selection

FunnelKit can do more than display a single order bump. The documentation covers multiple bump offers, a limit on the number of displayed blocks, and a setup where the customer can choose only one bump out of several. This is useful when the store wants to present alternative add-ons without overloading checkout.

Multiple bumps do not mean you should show customers everything at once. On the checkout page, every extra block competes with the main goal: completing the purchase. So start by deciding which offers genuinely belong together. An accessory, packaging option, and warranty may make sense side by side, but three similar upgrades for the same product are usually better turned into a single-choice decision.

Global Limit on the Number of Blocks

In the global Order Bump settings, the documentation points to a setting under FunnelKit Settings - Order Bump - Advance where you define the maximum number of bump blocks on checkout. This is not a per-product setting. It is a system-level safeguard against overload. If you have created five bump offers but only want to show two, the limit helps keep the checkout readable.

Use the limit together with priorities. First decide which bump is most valuable to both the customer and the store, then confirm the display order. Do not rely on the limit alone if the offers use different conditions. It is better to configure the rules so each customer sees a relevant set, while the limit serves as an extra safeguard.

The "Only One Bump" Setup

FunnelKit's official documentation describes a method where the customer can choose only one order bump offer: once one is selected, the others become unavailable, while the user can still change their mind and switch. This is appropriate for mutually exclusive choices such as standard warranty vs. extended warranty, standard packaging vs. gift wrap, or a basic bundle vs. a premium one.

If you use this setup, validate the order behavior carefully. Only one selected product should be added, not several. The customer should understand that the other choices became unavailable because of the selection, not because of an error. If the copy or the visual state is unclear, reduce the number of choices or move the decision back to the product page.

When a Multi-Product Slider Works Better Than a Simple List

If the offers are similar and easy to browse, a multi-product slider order bump may be worth considering. This can work for sets of consumables, accessories, or small add-on products. But a slider at checkout requires restraint. It should not turn checkout into a catalog. Show only items that are genuinely related to the current cart, keep the number limited, check mobile scrolling, and avoid placing products in the slider that require detailed comparison.

Analytics and A/B Validation Without Guesswork

You should not evaluate an order bump by feel alone. FunnelKit's official site and documentation describe Funnel Builder analytics such as views, revenue, order bump revenue, conversion rate, charts, filters, conversion data, and period comparison. For A/B experiments, the documentation confirms testing different funnel components, including order bumps, splitting traffic between variants, viewing statistics, and declaring a winner.

That does not mean every small store should immediately run a complex experiment. But even without A/B testing, you should track the baseline numbers: how many times the bump was shown, how many times it was accepted, how much revenue it added, whether overall checkout conversion dropped, and whether cancellations or support contacts increased. If the bump raises average order value but hurts order completion, the outcome may be worse than the revenue for that single offer suggests.

What Hypotheses Are Worth Testing

• Placement on the page. For example, inside mini cart versus the area above payment gateways.
• The product in the offer. Accessory versus warranty, consumable versus gift wrap.
• The headline copy. Bundle value versus savings or delivery convenience.
• The size of the discount. Test carefully: a large discount can destroy margin and attract the wrong motivation.
• Skin and visual emphasis. Compare not for beauty, but for clarity of action and effect on checkout completion.
• Default pre-selection. Test this only in ethically safe cases, such as a free gift or a clearly understood preset bundle.

How to Read the Data Without Fooling Yourself

Do not look at bump acceptance in isolation. Read it in context. If one version gets more clicks but lowers overall checkout conversion, that is a warning sign. If a heavily discounted bump adds revenue but nearly wipes out the margin, the experiment did not meet the business goal. If the outcome depends on one unusually large order, do not declare a winner too early.

For a smaller store, it is best to test one variable at a time. Do not change the product, placement, skin, discount, and copy all at once. Otherwise you will not know what actually worked. FunnelKit gives you the ability to experiment inside Funnel Builder, but test discipline is still your job. A/B testing is useful only when the variants differ by one meaningful hypothesis.

How This Connects to Ad Analytics

In the Settings tab for a specific order bump, FunnelKit documents override tracking IDs such as Facebook Pixel ID, Google Analytics ID, Google Ads Conversion ID, TikTok Pixel ID, Pinterest Tag ID, Snapchat Pixel ID, and others. Use this only if you know why you need to override your global settings. For most stores, the built-in FunnelKit analytics and WooCommerce orders are enough to start with.

If you do change a tracking ID, validate the events in the ad platform's test mode and avoid conflicting duplicates. Bad analytics are worse than no analytics because they push you to make decisions based on corrupted data. If there is any doubt, keep the global settings and track bump acceptance through the built-in analytics.

Translation, Styling, and Safe Improvements Without Editing Core Files

The order bump appears at the most sensitive point in the buying process, so any improvement should be reversible. Do not edit the core of WordPress, WooCommerce, FunnelKit, or the parent theme. For appearance, use the Style and Global Custom CSS settings; for small PHP additions, use a child theme or Code Snippets; for translation, use standard WordPress translation tools and compatible multilingual solutions if they are already part of the site.

Custom CSS: When to Use the Global Field

FunnelKit documentation confirms the Global Custom CSS field in the global Order Bump settings. It applies across all pages, so you should not drop experimental rules into it carelessly. First configure as much as possible through the built-in skin and style controls. CSS is for cases where the native settings are not enough: aligning the bump with the theme, adding spacing, refining the border, adjusting typography, or making a small contrast fix.

Before writing CSS, open checkout in the browser, inspect the actual class of the element you need, and test the rule on a copy of the site. Do not use selectors that broadly affect every WooCommerce element. If you are not sure, stay within FunnelKit's native settings. The task notes for this guide explicitly record that no universal CSS snippet was added here: the public documentation confirms where CSS goes, but does not provide a stable general-purpose selector that is equally safe across all skins.

Quantity Incrementor Through a Documented Filter

The only code snippet in this guide comes directly from FunnelKit documentation: the wfacp_display_quantity_increment filter. It is not needed in every store. Use it only if the bump truly requires quantity selection and you have already confirmed that the product, inventory, and shipping recalculate correctly.

add_filter('wfacp_display_quantity_increment', '__return_true', 999);

Add it through a child theme or the Code Snippets plugin. After enabling it, open checkout, accept the bump, change the quantity, and check the mini cart, final total, and order. To roll it back, disable the snippet and clear the checkout page cache if one is being used. Do not add extra JavaScript to checkout unless absolutely necessary: checkout is already sensitive to conflicts.

Multilingual Store

FunnelKit's official page mentions support for multilingual setups with WPML, Polylang, and TranslatePress. In practice, that means you need to review the bump text in every checkout language: the headline, description, variation selection link, acceptance text, price, variation attributes, and the message shown after selection. Do not assume that translating the product page automatically makes the bump clear.

If the store runs in multiple languages, create a separate test order for each one. Check not only the visible copy but also price formatting, currency, shipping, tax display, and WooCommerce emails. If part of a string does not translate, do not edit plugin files. Use the string translation interface, the multilingual plugin documentation, or FunnelKit support.

Compatibility with Checkout, Cache, Theme, and Payment Methods

FunnelKit Order Bumps sits between the WooCommerce cart, checkout page, theme, payment methods, cache, JavaScript fragments, and analytics. That means compatibility cannot be checked with a single page load. You need a test order under conditions close to real usage: guest and logged-in customer, desktop and mobile, different shipping methods, the main payment method, a variable product, a coupon if used, and a bump product that has already been added.

FunnelKit's official checkout compatibility documentation includes separate sections for caching plugins, hosting cache, and CDN. The main practical rule is simple: checkout, cart, and dynamic API requests must not be served as static pages. For FunnelKit A/B testing pages, the documentation also reminds you to exclude those pages from the caching plugin. If you use WP Rocket, LiteSpeed Cache, WP Super Cache, W3 Total Cache, Cloudflare, or server-side hosting cache, confirm the exclusions before sending ad traffic to a new bump.

Themes and Page Builders

FunnelKit can work with popular builders for checkout pages, but your specific theme still affects fields, spacing, buttons, the mini cart, and responsive behavior. If the theme heavily alters WooCommerce templates, do not judge based on a single desktop view. Check mobile, multiple shipping addresses, form errors, payment method changes, and the return from the payment page.

If the bump looks broken, separate a styling issue from a behavior issue. The behavior is working if the product is added, the total recalculates, and the order is created. The styling is broken if the block exists but is misaligned, the text is unreadable, the image is stretched, or the checkbox sits in the wrong place. For behavior, inspect rules, product setup, cache, and JavaScript. For styling, review the skin, Style, theme CSS, and FunnelKit global CSS.

Payment Methods and Total Recalculation

FunnelKit's official page states that order bumps work with WooCommerce-supported payment gateways. But that does not remove the need to test your actual payment method. Some gateway plugins update the total amount, fees, or method availability after the cart changes. If the bump is added during checkout, the final total must recalculate before payment is confirmed.

Check your primary payment method, a backup method, and cash on delivery if it is enabled. Accept the bump, remove it, accept it again, change shipping, and apply a coupon if coupons are allowed. If the gateway shows the old total or the pay button does not update, temporarily disable JavaScript optimization, exclude checkout from cache, and investigate a theme or payment plugin conflict.

Integration with CRM and Emails

If the store sends orders to a CRM, email marketing system, or inventory platform, the order bump should arrive there as a normal order line item. This is especially important for bundles, packaging, services, and digital add-ons. FunnelKit can display analytics, but fulfillment often happens in external systems. After a test order, check not only the WooCommerce order, but also the admin email, customer email, CRM record, inventory export, and printed documents if those are part of your process.

Validating the Result Before Launching Ads and Traffic

Once the setup is done, do not jump straight into advertising campaigns. The order bump has been inserted into the most sensitive part of the store, so validation needs to go beyond "I can see the block." You need a small test matrix: when the bump should appear, when it should stay hidden, what happens after selection, how the order looks, how removal works, what analytics show, and whether the block interferes with the main checkout fields.

Validation Matrix for a Single Bump

What to check before publishing the offer for all customers

Scenario	What should happen	What to do if it fails
The cart contains a product that matches the rule	The bump appears in the selected position and does not overlap the checkout	Check the checkout page assignment, bump publication, and every Rules condition
The cart contains an exclusion product	The bump does not appear or is replaced by another relevant offer	Review the exclusion rule and operator logic
The customer accepts the offer	The product is added to the mini cart and the total recalculates before payment	Check product availability, checkout JavaScript, and cache
The customer removes the selection	The product is removed or the selection is cleared without breaking the form	Check skin behavior, hide-after-selection, and theme CSS
A test order is created	The order shows the correct item, quantity, price, and discount	Check the Products tab, discount, and product replacement mode
The mobile checkout version is opened	The bump is visible, readable, and does not interfere with payment	Select a separate mobile position or simplify the styling

This table is not just paperwork. If even one scenario fails, it is too early to send the bump to primary traffic. A checkout error costs more than a one-day delay. Be especially careful with stores that use caching, complex shipping rules, multiple currencies, non-standard payment gateways, and custom checkout fields.

What Counts as a Successful Launch

A successful launch is not just about added sales. At a minimum, five conditions should be true: the right audience sees the bump, the offer is clear without a separate page, the total recalculates immediately, the order contains the correct data, and the analytics can distinguish an accepted bump from a normal purchase. Once those conditions are met, you can expand the rules or test the next variant.

If you plan to run an A/B experiment, define the starting hypothesis before you begin. For example: inside mini cart for an accessory will produce higher acceptance than a position below payment gateways, without reducing overall checkout conversion. Then change only the placement. Otherwise, any outcome will be hard to interpret.

Practical Offer Ideas for Different WooCommerce Stores

The ideas below are not a universal formula. They show how to think about FunnelKit Order Bumps through the relationship between the main order and the extra value being added. For each case, first check the product, margin, shipping, compatibility, and customer expectations. Then configure the rule, position, and result validation.

Physical Products: Accessories and Purchase Protection

For electronics, tools, home goods, and sports products, accessories, consumables, and protection offers are often the strongest fit. For a device, that might be a case, cable, batteries, or extended warranty. For a filter, a replacement cartridge. For a kit, packaging or a spare part. A position inside the mini cart helps the customer see the completeness of the order. The rule should suppress the offer if the accessory has already been added.

Digital Products: Template, Guide, or Expanded Package

For digital products, the bump needs to be especially honest. If the customer is buying a template, you can offer an extra set of layouts, a setup guide, or a package of ready-made elements. Do not offer a service that requires coordination if checkout does not explain the timing and terms. After a test order, confirm file delivery and the customer email: the bump should be delivered as reliably as the main digital product.

Services and Bookings Through WooCommerce

If WooCommerce is being used for services, an order bump can offer expedited handling, expanded consultation, additional material, or an upgraded package. The wording matters a lot here: the customer needs to understand exactly what changes in the service. If the service depends on scheduling, a manager, or manual review, the bump must flow into the order and internal notifications in a way that ensures the team does not miss the extra option.

Subscriptions and Upgrades

For subscription flows, product replacement or upgrade mode can work well if your WooCommerce setup supports it and it is configured correctly. For example, a one-time purchase can be replaced by a subscription, or a basic plan can be upgraded to an expanded one. This setup requires separate validation for the copy, gateway, emails, subscription status, and future charges. Do not launch an upgrade flow without a test order on a copy of the site.

In every case, remember that a bump is a small decision. If the offer requires a long comparison, it belongs on the product page, a separate page, or a post-purchase upsell instead. FunnelKit Order Bumps is strongest when the customer can decide in a few seconds and immediately see a clear outcome.

Copy, Discount, and Margin: How to Make the Offer Clear Without Losing Money

Many order bump mistakes do not start in the FunnelKit interface, but in the offer strategy itself. A store picks a product, applies a polished skin, adds a discount, and assumes the offer is ready. But the customer sees the block differently: they are trying to understand quickly what will be added to the order, why it relates to the current purchase, how much extra they will pay, whether shipping changes, and whether they can continue checkout without friction. If those answers are not obvious, even a technically correct bump will perform worse.

For FunnelKit Order Bumps, the connection between content - product - discount - result matters especially. The Content tab controls the visible meaning, the Products tab controls the product, quantity, and discount, and the Style tab determines how easily that meaning is read on the page. These settings cannot be evaluated separately. A discount without clear copy looks like a random promotion. Good copy cannot save an irrelevant product. Strong styling without a margin check may increase clicks while making the economics of the order worse.

How to Choose the Price and Discount Without Guessing Blindly

Start with the math, not with the urge to make the offer more visible. For a physical product, account for wholesale cost, packaging, payment processor fees, shipping changes, return probability, and warehouse work. For a digital product or service, account for support cost, file delivery, manual handling, and possible customer questions. If the bump adds revenue but destroys margin, it is not solving the store's problem.

A discount is not always necessary. Sometimes convenience is the stronger angle: add a compatible consumable, avoid searching for the accessory separately, include packaging, or choose an upgraded configuration. If the product is already an obvious fit, too much discounting may teach customers to wait for deals only at checkout. For a first test, it is safer to offer a moderate benefit or keep the regular price while making the connection to the main order very clear.

Mini Formula for Checking the Economics

Before publishing, write down three numbers: the net margin of the main product, the net margin of the bump product, and the minimum acceptable order margin after the discount. Then place a test order and compare not just the final amount, but the actual profit. If shipping becomes more expensive because of extra weight, the discount may look harmless at checkout while producing a worse outcome after fulfillment.

For digital offers, check a different risk: the bump may increase support volume. A mini-course, template, or consultation needs clear delivery and expectations. If the customer does not receive the material automatically or does not understand where to find it, ad savings turn into manual support work. That is why a successful bump is not only about acceptance, but also about smooth fulfillment.

How to Write the Offer for Different Product Types

For an accessory, the wording should connect it directly to the use of the main product: a memory card for a camera, a filter for a coffee machine, a screen protector for a device. For a service, explain the change in the flow: priority handling, gift wrapping, expanded review. For a digital product, explain what the customer gets after payment: an extra file set, guide, template, or access to a resource. Do not reuse the same copy across all categories.

A strong short-form bump structure looks like this: action, specific benefit, price or savings, and no hidden obligation. For example: add a protective case to your device so you do not have to look for a compatible accessory later. If there is a discount, it should sit next to the price, not be buried in a long description. If the product is variable, there should also be a clear way to choose the option and see the selected attribute.

Do not overload the offer with social proof unless it is backed by real data. FunnelKit supports a social proof tooltip, but you should not fill it with random claims. It is better used for a concise hint: why this accessory is compatible, what is included in the bundle, or which option to choose. If you cannot verify a testimonial or customer count, do not turn the tooltip into artificial social advertising.

How to Match the Copy to the Checkout Position

The same copy behaves differently in different locations. Inside mini cart, the customer sees the order contents, so the text can be shorter and more concrete: complete the kit, add a consumable, choose packaging. Above payment gateways, the wording should be calmer because the customer is already preparing to pay. Above checkout form requires even more caution: a long offer too early in the flow can distract from entering details.

On mobile, the text should be shorter than on desktop. Not because mobile shoppers are less attentive, but because the screen is already occupied by fields, shipping, payment, and the total. If the bump requires a long explanation, the mobile version quickly becomes overloaded. For a mobile test, keep one headline, one short line of value, the price, and a clear action. The details belong on the product page, not at checkout.

What to Do After the First Data Comes In

Once the bump is live, do not change it every day. First wait until your store has collected a meaningful number of impressions. Then look not only at the acceptance rate, but also at cancellations, support contacts, changes in overall checkout conversion, and the average order margin. If the bump is rarely accepted, check the connection between the product and the copy. If it is accepted often but returns or questions go up, check customer expectations. If acceptance is high only because of a deep discount, recalculate the economics.

Then you can prepare an A/B test. One variant changes only the copy, another only the placement, a third only the product. Do not mix everything into a single experiment. FunnelKit makes this especially convenient because order bumps can be tested inside the broader funnel, and the built-in analytics help you see views, clicks, conversions, and revenue. But the store owner still has to make the decision: the numbers need to connect to profit and checkout quality, not just a pretty chart.

If the Bump Does Not Show, Does Not Add, or Breaks Checkout

Troubleshooting FunnelKit Order Bumps should move from simple to complex. Do not start by reinstalling the plugin, and do not change several settings at once. First identify the symptom: the block is missing, the block appears in the wrong place, the product is not added, the total does not recalculate, the FunnelKit admin panel does not load, analytics show no events, or checkout behaves differently for guests and logged-in users.

The Bump Does Not Appear on the Checkout Page

Symptom: the bump is created and saved in the admin area, but the customer cannot see it on the public checkout page. Possible causes include opening the wrong checkout funnel, the bump not being published, the product not matching the rule, an exclusion rule firing, the global limit being reached, the position being outside the visible area, the bump product being unavailable for purchase, or checkout being served from cache.

What to check: add only the product that should trigger the rule to the cart, open the correct checkout page, and temporarily simplify the rule to the smallest possible condition. Confirm that the bump is published, that no hiding setup is active, that the offer product is available, and that no exclusion product is in the cart. If the block appears after simplifying the rules, the problem is not FunnelKit itself but the rule setup.

How to fix it: refine the rule, switch from category to a specific product or the other way around, add exclusions only after the basic setup works, reduce the number of active bump blocks, and choose a more visible position. If you suspect caching, exclude the checkout page from cache and clear the matching layer. Roll back the last change, not the entire plugin.

The Offer Is Visible, but the Product Is Not Added to the Cart

Symptom: the customer selects the bump, but the mini cart does not change, the total does not recalculate, or the product is missing from the order. The usual causes are product availability, checkout JavaScript, a theme conflict, a payment plugin conflict, dynamic fragment caching, or a misconfigured variable product.

What to check: open the bump product as a normal customer and confirm that it can be purchased. Check stock, price, variations, and required fields. Then temporarily disable JavaScript minification on checkout and test again. If the product is variable, select a specific option and make sure it appears correctly in the block.

How to fix it: make the first bump a simple product, then bring variations back later. Exclude checkout from cache, inspect the browser console for script errors, and test with a default theme on a copy of the site. If the failure happens only with one gateway, review total recalculation and gateway plugin compatibility.

The Block Appears in the Wrong Area or Interferes with Payment

Symptom: the bump is present, but the customer sees it too early or too low; inside the mini cart it crowds the summary; on mobile it breaks the form. The cause may be the chosen position, skin, spacing, theme CSS, or overly long copy.

What to check: open desktop and mobile separately, go through checkout as a normal customer, and test the areas above and below payment gateways, inside mini cart, above checkout form, and the other available positions. Reduce the copy to one idea, temporarily remove the image, or switch the skin.

How to fix it: assign a separate mobile position, reduce the visual emphasis, review Style, limit the image width, and remove unnecessary badges. If the issue exists only in the theme, add a careful CSS adjustment through Global Custom CSS after validating the selector on a copy of the site.

The FunnelKit Admin Panel Shows a Loading Error

Symptom: instead of data in the FunnelKit dashboard, you see a communication failure message. FunnelKit's official documentation ties this class of issue to cases where the browser cannot fetch data through the /wp-json/funnelkit-app/ REST API namespace. Causes include a security plugin, firewall, broken permalinks, an expired session, a server-side error, or outdated plugin files.

What to check: refresh the page, resave permalinks through Settings - Permalinks - Save Changes, and make sure FunnelKit is active and updated. Then inspect the security plugin or Cloudflare logs for blocked requests to the FunnelKit API.

How to fix it: add a targeted exception for the required REST API path in the firewall or security plugin without disabling protection permanently. If the server returns an error, inspect the PHP log and hosting limits. If the dashboard works after disabling the security plugin, turn it back on and configure an allow rule for the exact path.

Analytics Are Empty or the A/B Test Does Not Produce Clear Data

Symptom: the bump works on checkout, but the report does not help you make a decision: there is too little data, events look incomplete, variants were changed at the same time, or A/B test pages were cached. In many cases, the problem is not the report itself but a poorly designed experiment.

What to check: make sure you are testing one hypothesis, experiment pages are excluded from cache, variants are getting the expected traffic, and the observation period is long enough for your store. Compare FunnelKit data against WooCommerce orders and actual margin.

How to fix it: stop the messy experiment, create two clear variants, and do not change other settings before it finishes. If traffic is low, do not declare a winner too early. Sometimes one well-validated bump is better than an experiment with no statistical value.

Limitations and Cases Where FunnelKit Order Bumps May Not Be the Best Fit

FunnelKit Order Bumps covers a strong but very specific part of the sales process: an extra offer on the checkout page inside a WooCommerce funnel. If your goal is broader, the plugin may be only one part of the solution. For example, more complex recommendations based on user behavior may require a separate personalization system. Large kits are often handled better with product bundles. Post-purchase offers need after-payment logic and payment method support. Complex pricing comparisons usually belong on a separate page.

It is also important to understand the difference between technical capability and good user experience. The plugin lets you place bumps in different areas, preselect them, hide them after selection, use multiple offers, and test variants. But you do not need every feature on day one. The more automation and visual emphasis you turn on at the same time, the harder it becomes to prove that the checkout experience actually improved.

When It Makes Sense to Delay the Launch

• Checkout is already unstable. Fix payment, shipping, fields, and emails first.
• You do not have a good quick-decision product. A random product at checkout reduces trust.
• The margin cannot support the discount. The bump should improve total order economics, not just revenue.
• The product needs consultation. Move it to a separate upsell, consultation form, or product page.
• The team is not ready to fulfill the extra option. This matters especially for services, packaging, and manually assembled bundles.

A Useful Pairing with Native WooCommerce Features

One practical setup that does not depend on unverified integration promises is to use FunnelKit Order Bumps alongside native WooCommerce products, categories, inventory, coupons, and orders. WooCommerce handles the products, prices, stock, shipping, and final order. FunnelKit handles the relevant checkout offer, conditions, selection interface, and transfer of the accepted choice into the order. The caching plugin speeds up the site, but should not cache the dynamic checkout experience.

The setup order is straightforward: first configure WooCommerce product data, then create the FunnelKit bump, then the rules, then checkout cache exclusions, then a test order, then analytics. Potential conflicts include coupons changing the final price, shipping recalculating after the bump is added, cache returning a stale cart, or a CRM failing to recognize the extra line item. Validation means accepting the bump, completing the order, and checking the WooCommerce order, email, CRM, and FunnelKit report. Rollback means disabling the bump or experiment, clearing checkout cache, and leaving products and orders untouched.

Questions to Answer Before Launching Bump Offers

Can FunnelKit Order Bumps Be Used Without a Separate Funnel Page?

The practical FunnelKit flow is tied to a checkout page inside Funnel Builder or Store Checkout. If you want to show a bump on a standard checkout experience, check which checkout is active in your installation and where the order bump is actually added. Do not rely only on the default WooCommerce checkout page if the store is already using FunnelKit Store Checkout.

Should Default Pre-Selection Be Enabled?

For paid offers, it is usually safer to start without pre-selection. The Pre-select order bump by default option may be appropriate for a free gift or a clearly understood preset bundle, but it needs especially careful validation. The customer should clearly see what was added to the order and have an easy way to decline it.

Why Does the Bump Look Fine on Desktop but Feel Awkward on Mobile?

Desktop and mobile use different placements and different attention flow. A block inside the mini cart may work well on a wide screen, while on a phone a position near payment or after the main fields may be better. Test mobile checkout with a real order, not just by shrinking the browser window.

Can Variable Products Be Sold Through an Order Bump?

Yes. FunnelKit documentation describes variable product setup, the option selection button, and displaying the selected variation through merge tags. But a variable product needs deeper testing than a simple one: option selection, price changes, stock, attribute display, and whether the selected variation is passed into the order correctly.

What Should I Do If a Security Plugin Blocks the FunnelKit Panel?

First confirm the symptom. FunnelKit documents dashboard errors that occur when the browser cannot reach the /wp-json/funnelkit-app/ REST API path. Check your firewall or security plugin logs and add a targeted allow rule for that path. Do not leave the security plugin disabled as a permanent solution.

Can Several Bump Offers Be Shown at the Same Time?

Yes, but that is not always useful. FunnelKit supports multiple bumps, a limit on the number of visible offers, and a single-choice setup. Use multiple offers only where they do not compete with each other and do not turn checkout into a display shelf.

Does an Order Bump Affect SEO?

Usually not directly, because a checkout bump appears on a checkout page, not a search-facing content landing page. Usability and speed matter more: do not break checkout with heavy scripts, exclude the page from cache correctly, and confirm that the customer can complete the order without delays.

When Is It Better Not to Use This Plugin?

If the store does not have a good related product, checkout is unstable, the offer requires a long explanation, or the team is not ready to handle the extra option, it is better to wait. First fix the base purchase flow and prepare a relevant product, then you can download the ZIP archive and test the workflow on a copy of the site.

When FunnelKit Order Bumps Is the Right Choice

FunnelKit Order Bumps is worth using when the store already has a stable WooCommerce checkout and clear add-on products that naturally connect to the main order. The plugin is especially useful when you need more than just a visible checkout block, including control over rules, desktop and mobile placement, skins, copy, variable products, product replacement, the number of displayed offers, analytics, and A/B validation.

Do not try to launch everything at once. The best first setup is one relevant product, one narrow rule, one simple position, clear copy, pre-selection turned off, a test order, and an analytics check. After that, you can expand carefully: add exclusions, test placement, compare products, enable the quantity incrementor for consumables, validate a variable product, or launch an A/B experiment.

If after reading this you can describe your bump in one sentence - which product it attaches to, which add-on it offers, where it appears, what changes in the order, and how you will validate it - then the setup is ready for a safe test. If that sentence turns into something long and confusing, simplify the workflow first. A good order bump helps the customer complete a more complete order, not lose focus before payment.