Funnel Builder PRO 3.15.0.13 Free Download — Rules Tests & Nulled FAQ

Funnel Builder PRO: test the offer conditions before trusting the funnel

FunnelKit Funnel Builder is a WordPress and WooCommerce tool for building purchase journeys, checkout pages and related offers. Our exercise focuses on its Pro order-bump module: the distinction between a cart subtotal greater than $100 and at least $100, how target-product quantities are counted, and what happens at a price boundary.

The source product is labelled Funnel Builder PRO 3.15.0.3 on GPLHub, but the supplied ZIP’s own plugin header and installed plugin screen identify version 3.15.0.13. We use the file’s actual version in this page and download button. The main ZIP is preserved; we did not rewrite the plugin to match a catalogue label.

We exercised the installed native rule and pricing methods against a synthetic WooCommerce cart, then inspected the saved product and rule configuration in the real administrator screens. This is a component-level functional exercise. It does not claim a payment, post-purchase upsell, accepted checkout offer or conversion increase.

• Official FunnelKit order-bump overview

A real version mismatch changed the dependency we provide

Installing the latest free base was not a valid shortcut for this particular Pro package. Funnel Builder base 3.17.0 displayed an explicit warning that it pairs with Pro 3.16.0 or newer, while our installed Pro was 3.15.0.13. The older standalone order-bump administrator route was also unavailable in that pairing.

We selected official WordPress.org base 3.15.0.9 from the plugin’s version archive, installed it without changing the supplied Pro ZIP and reran the native checks. The saved offer and rule screens then rendered. The final required-components archive includes this tested base version and WooCommerce 11.2.1, with hashes in its inventory.

• Official FunnelKit installation order

Greater than and greater or equal differ at exactly $100

The two-product cart is the important boundary: greater than 100 is false at exactly $100, whereas greater or equal is true. A rule that looks nearly identical in the editor can therefore exclude the exact cart value you intended to include. We tested both native operators against the same three cart states instead of relying on the wording alone.

The target-product condition separately checked whether at least two Studio setup packs were present. One failed and two or three passed. It counted the named product’s quantity; it was not simply counting distinct cart lines or every object in the cart.

• Official FunnelKit rule-engine guide

An already-marked bump item did not inflate the base subtotal rule

We made a cart containing one $50 setup pack and four $20 checklist items carrying the module’s native bump-item marker and complete zero-discount option metadata. The whole cart subtotal was $130, yet the ordinary Cart Total (Subtotal) rule for at least $100 returned false. That rule evaluated the non-bump base amount rather than allowing the already-added bump line to make itself eligible.

This is a native rule-engine check using a deliberately marked cart line. It is not evidence that a shopper accepted a rendered bump widget. We did not simulate an order confirmation or claim that every other rule type excludes bump lines the same way. If an offer depends on shipping, taxes, discounts or another rule type, test that precise combination.

The distinction is useful when designing thresholds: a total that includes an optional offer may differ from the base purchase amount you meant to qualify. In this run we specifically inspected the subtotal rule. We did not test the separate full-cart-total rule with shipping and taxes.

The installed price method handled percentages and a zero floor

A 25% regular-price discount produced $15. A fixed discount larger than the $20 regular price was clamped to zero rather than returning a negative price. A positive flat-price option returned the selected $9. These are direct observations of the native installed calculation method, not a claim that a gateway accepted a zero-value order.

A percentage can be based on the regular price or the sale price; those are different choices in the real editor. Our calculation and saved offer use the regular-price option, with no separate sale price. Tax-inclusive pricing, subscription signup fees, variable products and quantity changes inside the widget were not part of this exercise.

Repeat the boundaries with a staging cart

• Use a disposable store and record the complete main/base/WooCommerce version pair. Do not assume that a newer base supports an older Pro package.
• Install WooCommerce, then the compatible free Funnel Builder base, then the separate Pro ZIP. Complete ordinary native setup before using its APIs.
• Create a $50 virtual base product and a $20 virtual offer product. Save the offer as one item with 25% off regular price.
• Create a subtotal rule at least $100. Compare it with a strictly greater-than rule at $50, $100 and $150.
• Repeat with an already-marked bump item and compare whole-cart subtotal with the rule’s actual result. Keep this component-level test separate from any later complete checkout test.

The reproduction fixture creates synthetic products, saves the offer and rule through the plugin’s native helpers, and calls the installed rule and price methods. Because this is a CLI context, it explicitly loads the plugin’s native rule base/cart class files when those classes are not already loaded. It does not replace their logic with a reimplementation.

The public results retain the calculated cart states and checks. They contain no customer account, payment token or real transaction. Before using a developer fixture in your own staging environment, review and adjust its explicit laboratory guard. The fixture is not a funnel-template import file.

• Official order-bump setup steps

• Download the synthetic reproduction fixture
• Read the recorded functional results

What the second download contains, and where the test stops

The GPLHub record for this exact product listed one Pro ZIP and no separate add-on archives on 17 October 2026. The second download is therefore labelled Required Components. It contains the official free base 3.15.0.9 and WooCommerce 11.2.1 used here, not FunnelKit Automations Pro, a payment-gateway bundle or a collection of unrelated paid modules. Extract the outer ZIP before installing its individual plugins.

Verified: the actual supplied Pro version; the incompatible current-base warning; a working saved product/rule administrator screen with the selected older base; strict/inclusive subtotal boundaries; target-product quantity; native marked-bump exclusion; and three native price calculations.

Untested: complete checkout offer acceptance, revenue or conversion impact, payment processing, post-purchase upsells, subscription renewals, thank-you routing, analytics delivery, A/B tests, external templates and broad add-on compatibility. The native component results do not validate those full workflows.

If you only need a regular WooCommerce checkout, the simpler native flow may be sufficient. Use an offer builder when you have a concrete additional offer or checkout requirement and can test it end to end in your own store. This page provides a reproducible starting point for its conditions, not a promise of commercial results.

Funnel Builder PRO Nulled FAQ

“Nulled” usually describes software whose activation or licence checks have been removed or altered; the word alone does not determine whether a particular use is lawful. GPL-covered code can be studied, modified and redistributed subject to its licence conditions, but this does not grant access to a developer’s account, hosted services, updates or support. We discuss the term here to answer a common search question; the download details separately identify the package source and tested version. Any plugin or theme obtained through an unverified third party can contain unwanted changes or malicious code, whether or not it is labelled “nulled”. Before installing it, you can ask ChatGPT or Claude Code to inspect the extracted source for suspicious behaviour without executing it or sharing credentials. Treat that review as an additional check: AI can miss harmful code or flag harmless code, and a clean result is not a security guarantee.

Which version is actually downloaded? The supplied main ZIP declares 3.15.0.13, despite the source listing’s 3.15.0.3 label. Its hash below identifies the exact archive.

Why not bundle the newest free base? Base 3.17.0 explicitly requested Pro 3.16.0 or newer. We retained official base 3.15.0.9 for the documented final test with supplied Pro 3.15.0.13.

Does this include FunnelKit Automations? No. It is a different product. This page provides the selected Funnel Builder Pro ZIP and the explicitly inventoried free prerequisites.

Was an entire sales funnel or payment tested? No. These are native rule/pricing checks and genuine saved administrator configurations. Do not treat them as a checkout acceptance, gateway or conversion test.

• GNU GPL FAQ
• GNU GPL version 2 licence text