Bundler Pro - WordPress Plugin

Guide to Configuring Bundler Pro for WooCommerce Offers

Bundler Pro is best approached not as a cosmetic add-on for a product page, but as a tool for managing ready-made WooCommerce offers: quantity discounts, product bundles, buy-one-get-another deals, gifts, and widgets that encourage customers to choose a more valuable package. In this guide, we will walk through how to prepare your site, which settings to check after installation, how to build a working offer, and how to confirm that it actually performs well throughout the buyer journey.

This article does not repeat the short product description usually shown higher on the page. The focus here is practical: where errors tend to happen, how a single product offer differs from an offer built around different products, why stock levels and variation pricing matter, when you need a shortcode, and how to avoid conflicts with your theme, cache, and other discount plugins.

According to the official sources, Bundler works with WooCommerce and supports several offer types: quantity breaks, standard bundles, frequently bought together, BOGO, free gift, discounted upsell, mix and match, and discounted products. In this guide, those features are covered not as a feature list, but as working scenarios: what to choose, what to configure, and what to verify on the product page and in the cart.

What Problem the Plugin Solves for an Online Store

The main purpose of Bundler is to give store owners a way to build a commercial offer around a product without manually recalculating prices or creating dozens of replacement products. On a standard WooCommerce product page, the customer sees the product, selects a quantity or variation, and adds it to the cart. Bundler adds an offer layer: buy more, choose a bundle, add a complementary item, receive a gift, or apply a discount to a related purchase scenario.

This layer is especially useful when a store sells repeat-purchase items, sets, consumables, accessories, digital products, cosmetics, apparel, care kits, training materials, or any products where it is easier for the customer to choose a ready-made option than to piece together several items on their own. The plugin becomes valuable when the offer explains the benefit directly on the product page, rather than hiding it inside a coupon or a separate promo page.

Which Use Cases Are Confirmed by Official Sources

The official site and WordPress.org listing describe several ways the plugin can be used. It helps to group them by store logic:

• Quantity breaks. The customer sees multiple quantity tiers, such as a single item at full price, several units at a better rate, or a pack option.
• Product bundles. The offer combines several products into one clear package so the customer does not need to add them separately.
• Frequently bought together. Related items appear next to the main product as logical add-ons.
• BOGO and free gift. The store can display a gift or a promotion such as "get an extra item with purchase."
• Discounted upsell and mix and match. The shopper chooses an upgraded package or combines suitable products within the offer.

What matters to the reader is not the list of labels, but choosing the right scenario. If you want to encourage customers to buy multiple units of the same product, start with quantity breaks. If you need to sell a kit made up of different items, look at bundle or frequently bought together. If the goal is a promotional campaign where the extra item should feel like a bonus, choose BOGO or gift scenarios only after confirming that your version and your offer rules support them.

Where Bundler Pro May Be Unnecessary

The plugin is not needed for every store. If you sell a single simple product, do not rely on repeat purchases, do not offer packages, and do not need to change product page behavior, an extra offer layer may only make administration more complicated. It also does not replace a full storewide discount management system if you need advanced rules based on customer segments, coupons, categories, roles, subscriptions, or loyalty programs.

Another limiting factor is catalog discipline. Bundler depends on WooCommerce products, pricing, stock, variations, and product page output. If your catalog is inconsistent, some products have no price, variations are unpublished, or the theme heavily alters the standard purchase form, you should first get the base product page working properly. Otherwise, the offer will look like a plugin problem even though the real cause is the store's underlying product data.

Quick pre-launch check: open a product without Bundler, choose a variation, add it to the cart, and make sure the price, stock, and purchase button all work normally. If the base product page is broken, any offer layered on top of it will also be unstable.

Who Bundler Pro Is a Good Fit For and When Another Approach Makes More Sense

Bundler Pro is especially useful for store owners and site managers who need a fast way to control offers at the product level. It is not a broad marketing campaign builder, but a practical tool for the product page and the scenarios connected to it. Its strength is showing ready-made options to the customer right where the add-to-cart decision is made.

Good Store Types for This Plugin

The plugin works best in catalogs where customers compare packages. For example, a skincare store can offer a set with a core product and an accessory, a consumables store can offer a discount for multiple packs, an apparel store can offer a complete outfit, and a digital seller can pair a core product with bonus material. In every case, the offer should not feel random. It should answer the shopper's question: "What should I get with this product, and why is this option more convenient?"

Bundler is also a good fit for agencies and administrators who manage multiple WooCommerce sites and want a repeatable way to present offers. The official documentation includes separate guidance for creating an offer, choosing a type, configuring the widget, customizing fonts, using a shortcode, and troubleshooting specific issues. That suggests the plugin is designed not just for one-time activation, but for ongoing offer management.

Scenarios Where You Should Be More Careful

If the store already uses a powerful discount plugin, a dynamic pricing system, a third-party checkout builder, or a custom theme with a modified purchase form, Bundler should be tested on a site copy or at least on a dedicated test product. The WordPress.org changelog includes fixes related to add-to-cart behavior, shortcode handling, tax, multicurrency support, and compatibility with other discount scenarios. That does not mean a conflict is guaranteed, but it does show the areas where testing is mandatory.

Stores with complex stock logic have another nuance to consider. In the official knowledge base for different products and variations, it is specifically noted that regular variations must already exist and be configured in WooCommerce, and they must have both a price and stock. If the store sells products with frequent inventory changes, offers should be retested after bulk catalog updates, stock imports, or changes to inventory management rules.

What to Check Before Installation and Before Creating Your First Offer

Preparation is not just a formality. A Bundler offer runs on top of a WooCommerce product, which means any catalog error immediately becomes an offer error: the button does not add the item, the price does not calculate, the option is unavailable, the gift does not appear, or the bundle cannot be purchased. Before installation, it is better to verify a few specific elements that will be used in your first scenario rather than audit the entire store.

Core WooCommerce Dependencies

First, make sure WooCommerce is installed, activated, and handling add-to-cart actions correctly. For testing, use one simple product and one variable product if you plan to work with variations. The product must have a price, published status, correct stock status, and be purchasable without theme-related errors. If variations are involved, each variation the customer can select must have a price and be available based on stock.

For offers built around different products, the official Bundler documentation emphasizes the difference between custom variations inside the offer and regular WooCommerce variations on connected products. That is an important point: Bundler may provide its own option logic inside an offer, but if the related product is itself a variable product, its variations must still be configured in WooCommerce rather than magically created by Bundler.

Theme and Page Builder Compatibility

Your theme should output the standard WooCommerce purchase area correctly. If the theme or page builder completely replaces the product template, the offer may appear in the wrong place or the add-to-cart button may behave differently. The official documentation includes separate guidance for shortcode usage and Elementor compatibility, so it is better to plan nonstandard placement in advance rather than after the offer has already been created.

The check itself is simple: open a test product page on the live frontend, make sure the purchase form is visible, the button works, there are no JavaScript errors in the console, and page caching can be temporarily disabled. Then install Bundler and work with a single test product instead of enabling offers across the whole catalog right away.

Cache, Discounts, and Multicurrency

If the site uses page cache, fragment cache, JavaScript optimization, or a third-party discount plugin, run your first tests without aggressive optimization enabled. This matters even more on a commercial site: the offer must change the price or the cart composition at the exact moment the customer makes a selection. If the cache serves an outdated product page, the user may see one version of the offer while a different result is sent to the cart.

Multicurrency and taxes should also be checked separately. The changelog mentions fixes related to taxes and multicurrency, so you should not assume that every currency add-on will immediately handle discounted offers correctly. The safest path is one product, one currency, one scenario, then a test of the same product page in another currency if your site uses one.

Installation and an Initial Check Without Risking Your Catalog

Installing the WordPress plugin is standard: upload the ZIP through Plugins, activate it with Activate, and confirm that the Bundler interface appears in the admin area. There is no need to create dozens of offers right away. Your first run should confirm that the plugin can see WooCommerce products, save an offer, and display the block correctly on the selected product page.

The First Safe Launch

1. Create or choose a test product that is not critical to current sales.
2. Check its price, stock, publication status, and add-to-cart behavior without any offers.
3. Activate Bundler and go to create a new offer.
4. Choose a simple scenario, such as quantity breaks for one product.
5. Save the offer and open the product page as a regular shopper.
6. Select one of the offered options, add the product to the cart, and compare the price with what you expected.

If the offer does not save or does not appear in the interface after saving, do not continue creating new variations. The official knowledge base includes a separate article about offers not being saved. In practical terms, that means you should first check browser console errors, server limits, plugin conflicts, or a problem with the specific save form.

How to Tell the Installation Went Smoothly

A normal result after the first run looks like this: the offer is created, appears in the list, is linked to the correct product, the widget shows up on the product page, the selected option is added to the cart, and the cart total matches the selected offer. You need to verify not only the widget on the page but also the final cart result, because a visible block by itself does not prove that the pricing rule actually applied.

After the initial check, it is useful to document the test offer settings: type, selected product, quantity tiers, discount, display location, and cache state. If an error appears later, you will have a baseline configuration to return to.

Configuring an Offer: Type, Products, Discount, and Widget Appearance

Detailed setup begins with choosing the offer type. Bundler documentation includes a separate article on the offer creation process, along with materials on fonts, custom CSS, background widget, shortcode, Elementor, single product offers, and different products. That shows the setup is not a one-click task, but a multi-layer process: offer logic, related products, design, placement, and result verification.

Choosing the Offer Type

The offer type determines how the plugin interprets the shopper's action. Quantity breaks revolve around the quantity of one product. Bundle and frequently bought together revolve around multiple items. BOGO and free gift add promotional logic where the customer gets an extra benefit when a condition is met. A common beginner mistake is choosing the type by the most appealing name rather than by the real business scenario.

For your first working offer, it is better to choose the scenario that is easiest to verify. A good example is quantity breaks for one product: the shopper selects 1, 2, or 3 units, and you can immediately see whether the price updates correctly in the widget and in the cart. Once that works, you can move on to bundles made of different products, where there are more dependencies: related products, variations, stock, availability, and button behavior.

Products and Variations

If the offer uses a single product, check its base price, purchase status, and stock. If the offer uses different products, verify each related product individually. For a variable product, keep one point in mind: standard variations are created in WooCommerce. Bundler can use custom variations inside the offer, but that does not remove the need to configure the products and their options correctly.

A practical test looks like this: open each product in the bundle separately, choose the needed variation, add it to the cart, and make sure WooCommerce does not show a "product unavailable" error. Only then should you connect that product to the offer. That makes it much easier to separate a Bundler issue from a base product issue.

What to Do If a Price or Stock Value Is Missing

If the offer does not appear or cannot be added to the cart, do not start by reinstalling the plugin. First check the product price, variation prices, and inventory settings. The official article on different products explicitly states that regular variations must have both price and stock defined. Without that, correct offer behavior becomes impossible or unpredictable.

Widget Appearance

Once the offer logic is in place, move on to the widget. Bundler documentation includes separate guidance for background widget, fonts, and custom CSS. That means the appearance can be adapted to your theme, but this should happen only after the logic is verified. First make sure the offer works, then adjust colors, background, fonts, spacing, and small interface details without interfering with price calculation.

For a typical site, light customization is enough: a clear heading, readable price, an obvious active offer card, and a visually noticeable button or selection area. The widget should not turn into a separate promotional banner that competes with the product page. It should help the shopper decide, not distract from the purchase.

A Small CSS Tweak for Better Readability

If the built-in design settings are not enough, you can add a small CSS adjustment through Appearance -> Customize -> Additional CSS or through a child theme. It is best to inspect the exact classes in your own HTML, because your theme and plugin version may change the wrappers. The example below shows a safe principle: improve offer container readability without touching price calculation or cart behavior.

.bundler-offer,
.wcbundler-offer {
  border-radius: 10px;
  line-height: 1.45;
}

.bundler-offer .price,
.wcbundler-offer .price {
  font-weight: 700;
}

After adding the CSS tweak, open the product page, check the widget on both wide and narrow screen widths, then add the offer to the cart. Rolling back is simple: remove the added CSS and clear the site cache. If your actual classes differ, do not guess based on the example. Open the browser inspector and use the classes from your specific widget.

Quantity Breaks and Bundles: How to Choose the Right Offer Mechanic

Quantity breaks are one of the clearest Bundler scenarios: the shopper sees that buying more gives them a better price or a more attractive option. But even this scenario needs careful logic. If the quantity tiers are too close together or the discount is not obvious, the customer will not understand why they should choose the second or third option. If the discount is too aggressive, the store may lose margin.

Single Product Offer

For a single product offer, the logic is straightforward: one product, several quantity options, different value conditions. This works especially well for consumables, packs, digital licenses, training materials, care products, and any item where repeat purchase is natural. The key is that the offer should not look like a random set of prices. The title and labels should explain why the option is useful: family supply, one-month pack, team bundle, backup pack.

Testing a single product offer happens in two stages. First, select each tier on the product page and make sure the active widget state is visually clear. Then add each option to the cart and compare the final price. If the page shows a discount but the cart does not, the issue may be related to add-to-cart behavior, caching, a script conflict, or another discount plugin.

Different Products Offer

An offer with different products is more complex because it depends not only on the main product but also on the state of each related item. One product may be simple, another variable, and a third temporarily out of stock. If the customer selects a bundle and one bundle item is unavailable, the business value of the offer breaks down.

For different products, follow a simple rule: first test each product on its own, then build the offer, then test the full bundle. Do not combine products with unpredictable stock levels in one offer unless you are ready to monitor availability regularly. For seasonal bundles, it is helpful to create a dedicated test scenario before the promotion starts and repeat the check after stock updates.

Shortcode, Elementor, and Nonstandard Display Locations

Not every WooCommerce site uses the standard product page layout. Themes, Elementor templates, custom sections, and landing pages often change the order of blocks: gallery, price, purchase form, description, related products. The official Bundler documentation includes articles on shortcode and Elementor, so this scenario is worth covering separately.

When You Need a Shortcode

A shortcode is useful if the default widget placement does not fit your layout or if the product page is built with a page builder. In that case, you can output the offer in the part of the page you want, but the responsibility for testing increases. The widget should stay close to the purchase context, not be pushed into some random section below the description where the shopper has already lost focus.

Before using a shortcode, check three things: the block is visible only on the intended page, it is not duplicated by the default output, and the button or selection logic correctly sends the chosen offer to the cart. If the shortcode is added inside an Elementor template, test not only the editor preview but also the public-facing page as a regular visitor.

What to Check in Elementor

With Elementor, container behavior, responsiveness, and script load order matter. If the Bundler block is placed inside tabs, popups, or hidden sections, the option-selection script may not behave the same way it does on a standard product page. It is safer to output the offer in a simple static section first, verify the cart, and only then move it into a more complex layout.

Practical rule: if the offer works on a standard product page but fails inside an Elementor template, first look for the issue in the output location, hidden containers, script caching, or a duplicated purchase form.

Practical Example: A Bundle for a Product with an Accessory

Let us look at a concrete scenario: the store sells a main product and wants to offer a bundle with an accessory. The goal is to increase average order value without using a coupon or a separate promo page. The shopper should see the offer directly on the main product page, choose the bundle, and get both items in the cart at the expected price.

Goal and Preparation

The goal of this scenario is to show a clear bundle next to the main product: the main item plus a compatible accessory. Before setting it up, prepare both the main product and the accessory in WooCommerce. Both products must be published, priced, and available for purchase. If the accessory has variations, test each variation separately.

For testing, use neutral product names and do not enable the offer across the entire catalog. That lets you verify the mechanics without risking real sales.

Setup Steps

1. Open the Bundler interface and create a new offer.
2. Select the offer type that fits a bundle made from different products.
3. Choose the main product the widget will be attached to.
4. Add the accessory as a related product or bundle item.
5. Configure the discount or overall value if your scenario includes one.
6. Check the widget heading and labels so the customer understands what is included.
7. Save the offer and open the product page as a regular visitor.

Verifying the Result

The offer widget should appear on the product page. The customer should be able to see what the bundle includes, the price or benefit, and a clear way to choose the offer. After adding it to the cart, make sure both items are present, the quantity is correct, the final total matches the offer settings, and checkout does not show a discount conflict.

If the accessory was not added, check its stock, publication status, and price. If only the main product was added, check whether the theme's old purchase form is appearing instead of the Bundler form. If the price looks correct on the product page but changes in the cart, temporarily disable other discount plugins and caching, then rerun the test.

A Detail People Often Miss

The customer does not need to understand the internal offer logic. They only see the offer itself. That is why tier names and labels should explain the value in plain language: "Product + Accessory," "Starter Bundle," "Gift Set." Do not use internal labels such as "Bundle 1" or "Offer A" on the public site.

Practical Ways to Use It in Different Types of Stores

The plugin is most useful when offers are built around real buying tasks. Below are several scenarios based on confirmed offer types and standard WooCommerce logic. You do not need to copy them word for word. Use them as a way to decide which offer type best fits your catalog.

Consumables and Repeat Purchases

For products people buy regularly, start with quantity breaks. It is easier for the customer to choose a one-month supply or several packs when the benefit is visible right next to the purchase button. Check not only the discount, but also how clear the tier labels are: "2 packs," "3 packs," and "family pack" read better than abstract percentages.

Main Product and Accessories

For electronics, cosmetics, apparel, sporting goods, and digital products, bundle or frequently bought together often works well. The point of the offer is to remove the burden of searching for compatible accessories. In this scenario, however, the availability of every related product is critical. One out-of-stock accessory can make the entire bundle useless.

Gift and Promotional Campaign

BOGO and free gift are good fits for short-term campaigns, but they need more careful testing. Check how the gift appears in the cart, whether it can be removed, whether it conflicts with coupons, and what happens when the quantity changes. Do not use a gift as a way to hide an unclear discount. The customer should understand both the condition and the outcome right away.

Upselling Without Pressure

Discounted upsell works best when the upgraded option genuinely helps the customer. For example, a main product plus a consumable, a basic digital product plus a template, or a single item plus a care kit. Do not turn every product page into an aggressive list of add-ons. One logical offer that clearly relates to the product and is easy to verify in the cart is usually more effective.

How to Verify the Result After Setup

Result verification is a separate stage, not just a quick glance at the product page. Bundler changes the commercial flow, so testing should cover the entire customer journey: product page, offer selection, cart, and checkout up to final confirmation without real payment if the site has a payment test mode.

Post-Save Checklist for an Offer

• Open the product page on the public site without being logged in as an administrator.
• Make sure the widget appears only once and does not break the theme layout.
• Select each offer option and confirm that the active state changes correctly.
• Add the offer to the cart and compare the products, quantities, and final total.
• Update the quantity in the cart, if allowed, and check whether the discount disappears.
• Test the same scenario with cache enabled if the site uses caching.
• Repeat the test for variations if the offer works with a variable product.

What Counts as a Successful Result

A successful offer is not just visually appealing. It must be understandable to the customer, technically correct, and predictable in the cart. If the customer chooses a bundle, the correct items should appear in the cart. If they choose a quantity break, the quantity and price should match the selected tier. If they receive a gift, the gift should be visible in a way that does not raise doubts or break checkout.

Also test behavior after clearing the cache and in a private browser window. An administrator may see a fresh page while a regular visitor sees a cached version. For offers that affect pricing, that difference is especially risky.

Compatibility, Limitations, and Safe Improvements

Bundler runs inside a WooCommerce environment where the final result is affected by the theme, discount plugins, currency handling, taxes, caching, page builders, and the state of the catalog. That is why safe configuration is built not around enabling every possible feature, but around gradual rollout and verification.

Other Discount Plugins

If the site already uses an extension for dynamic discounts, coupons, or price rules, do not enable a complex offer across the entire catalog without testing. A scenario is possible where the Bundler discount and another discount apply at the same time, or one overrides the other. The official changelog includes references to fixes related to compatibility and discount logic, so this risk should not be ignored.

A safe test path looks like this: create a test product, disable all coupons for it, configure the offer, and check the cart. Then enable the second discount mechanism and repeat the same path. If the final total changes in an unexpected way, keep only one discount mechanism for that product or confirm the rule priority in the documentation for the relevant extensions.

Cache and JavaScript Optimization

Page caching can preserve an outdated version of the widget, and script optimizers can change the load order of required JavaScript. If the offer stops switching options correctly or the button becomes unstable after caching is enabled, exclude the product page from aggressive optimization, temporarily disable script merging, and rerun the test. Do not start by reinstalling the plugin until caching has been ruled out.

SEO and Analytics

By itself, the Bundler widget does not guarantee ranking growth and should not be treated as an SEO plugin. Its SEO value is indirect: the product page may become clearer if the offer helps the user choose a bundle without overloading the page. Do not hide important offer conditions only inside an image or script. The product page text should explain the bundle contents and the benefit in regular HTML content if that matters to the customer, not only through a dynamic block.

When It Is Better Not to Add Code

If you need more than a cosmetic CSS tweak and want to change pricing logic, gift behavior, variations, or cart handling, do not write your own snippet without a confirmed API. The available public sources for Bundler do not provide enough reliable public documentation on hooks and filters to recommend PHP changes to core logic. For those cases, it is safer to use the plugin settings, consult the developer's documentation, or test customization on a staging site.

Why the Offer Is Not Working and How to Find the Cause

Troubleshooting is best done from simple to complex. There is no need to change every offer setting at once. First identify the symptom: the offer is not saving, the widget is not displaying, the product is not being added, the price is wrong, the variation is unavailable, or the block breaks inside Elementor. Each symptom has its own verification path.

The Offer Is Not Saving

Symptom: after creating or editing an offer, the data does not remain in the admin area. A possible cause is a script conflict, request limitation, save-form error, or conflict with another extension. The official knowledge base includes a separate article called "Why I cannot save my offers?", which means the developer recognizes this as a distinct troubleshooting area.

Check the browser console in the admin area, temporarily disable unnecessary extensions on a test copy, make sure the user has administrator permissions, and try saving the simplest possible offer without extra products. If a simple offer saves correctly, add elements one by one until you find the specific setting that breaks the save process.

The Widget Does Not Appear on the Product Page

Symptom: the offer is saved, but the customer does not see the block on the product page. Start by checking that the offer is attached to the correct product and that the product is published. Then verify that the theme is not hiding the block, that the product template has not been replaced by Elementor, and that you are not outputting the offer only through a shortcode somewhere else on the page.

If the default output does not work, try temporarily using the shortcode in a simple page section. If the shortcode is visible, the problem is most likely the output position or the theme template. If the shortcode also fails to display the offer, go back to the offer settings and the connected product.

The Product or Variation Is Not Added to the Cart

Symptom: the customer selects the offer, but the cart stays empty or shows an availability error. Check the stock status, price, and publication state of each product. For a variable product, open the WooCommerce variation settings and make sure the required variation has both a price and stock. This is especially important for a different products offer, where one missing item can break the entire bundle.

The Cart Price Does Not Match the Widget

Symptom: the offer looks correct on the product page, but the cart calculates a different total. Possible causes include a second discount plugin, a coupon, tax settings, a multicurrency extension, caching, or quantity changes in the cart. Test one factor at a time: first without coupons, then without the other discount plugin, then without cache, then in the site's primary currency.

Elementor or the Theme Breaks the Appearance

Symptom: the widget is there, but buttons are misaligned, the selected option is not highlighted, or the block looks different in the editor and on the site. First check the standard product template. If everything works there, the issue is in the builder's containers, styles, or scripts. Only adjust CSS after confirming that the offer logic itself works.

Quick Bundler Troubleshooting Path

Symptom	What to Check First	When to Roll Back a Setting
Offer is not saving	The simplest possible offer, browser console, extension conflicts	If the error appeared after adding a specific product or parameter
Block is not displaying	Product assignment, theme template, shortcode, page cache	If the block appears after disabling a custom template
Incorrect price	Coupons, another discount plugin, taxes, currency, cart	If the discount is applied twice or does not match the offer
Variation unavailable	The variation's price and stock in WooCommerce	If the related product cannot be purchased on its own without Bundler

Bundler Video: When It Is Worth Watching

The Bundler page on WordPress.org includes an official step-by-step video tutorial. That format is useful if you want to see the general quantity breaks setup process and compare it with the written instructions above. The video covers the "how to use Bundler" intent and helps you understand more quickly where the offer is created in the interface and what the path to result verification looks like.

While watching, pay attention not to promotional wording, but to the sequence of actions: selecting the product, creating the offer, setting up the tiers, saving, and checking the product page. If the interface looks different in your version, follow the logic and cross-check the exact labels against the developer's current documentation.

When Bundler Pro Is the Right Choice

Bundler Pro makes sense if you want to make the product page more practical: show better quantity options, build a bundle, suggest a related product, add a gift, or create an upsell without manually handling coupons for every customer. It is especially useful when the customer makes the decision directly on the product page and needs to immediately see the offer contents, the benefit, and the outcome.

Before rolling it out in production, follow a short path: one test product, one offer, and a check of the public page, cart, variations, cache, and discount conflicts. If that path works without errors, you can scale offers to similar products. If problems appear, do not expand the setup until you have identified both the symptom and the cause.

When you are ready to test the plugin on your WooCommerce site, you can download the Bundler Pro archive near the download section, install it on a test product, and verify the first offer step by step using this guide. That approach is safer than enabling several complex offers at once on a live catalog.