WPC Frequently Bought Together for WooCommerce - WordPress Plugin

How to Set Up WPC Frequently Bought Together for WooCommerce for Product Recommendations

WPC Frequently Bought Together for WooCommerce is not meant for a generic "related products" block. Its real purpose is much more specific: showing a set of additional items on the product page that the customer can add alongside the main product. In this guide, we will look at how to turn that recommendation into a controlled sales flow: prepare the store, enable the plugin, configure the global settings, build an offer at the product level, test the cart behavior, and identify where problems are most likely to appear.

This guide is intended for WooCommerce store owners, webmasters, and content managers who already work with products, categories, linked products, and the basic WordPress settings. We are not going to rehash the product listing. Instead, we will walk through the full process from the initial setup to a practical "main product + accessories" bundle, and separately cover discounts, quantities, block placement, cart behavior, the limitations of the free and paid versions, and the cases where a different type of product bundle may be the better fit.

The core idea is simple: a frequently bought together block should help the customer make a decision, not just make the page longer. That means the actual products matter, but so do the display position, pricing, quantities, labels, variation behavior, stock status, and the post-add-to-cart result.

Practical baseline: start with one test product and one small set of two or three additional items. Only after you verify the cart, checkout, and theme behavior should you roll the setup out across the full catalog or enable bulk rules.

What Problem the "Frequently Bought Together" Block Solves

WooCommerce already includes linked products, upsells, and cross-sells. But they do not always work well as a short commercial offer on the product page. Related products may appear below the description, cross-sells are usually seen in the cart, and upsells suggest a more expensive or alternative item. WPC Frequently Bought Together for WooCommerce adds a different layer: the customer views the main product and immediately sees additional products that can be selected along with it.

This approach is especially useful for accessories, consumables, components, collections, care sets, variable products, and items where customers may forget an important add-on. For example, it makes sense to offer a mouse, sleeve, and adapter with a laptop; a memory card and strap with a camera; another product from the same line with a cosmetic item; or a matching belt or pair of shoes with apparel. The point of the block is not to show everything possible, but to save the customer from having to search for compatible add-ons themselves.

The plugin lets you define these offers manually for a specific product, pull products from existing related, upsell, or cross-sell settings, and in the paid version apply Smart Rules for bulk assignment based on conditions. That distinction matters: one store may manually build precise pairings for bestsellers, another may use rules for categories and tags, and a third may completely disable the block on products where recommendations get in the way.

How This Differs from a Standard Bundle

The customer is not required to take every additional item. WPClever's documentation specifically states that Bought Together items are optional extra items. If you need required products that cannot be removed from the set, that is a different scenario altogether - forced sales or a full bundle. With WPC Frequently Bought Together, voluntary selection is essential: the customer can keep only the main product, choose one add-on, or add several.

That makes the plugin a good fit for soft cross-selling. But for the same reason, it should not be used where the business logic depends on a mandatory dependency. If the product cannot be sold without a service, warranty package, required license, or physical component, you are better off looking at forced bundle products or creating a dedicated bundled product.

Where the Block Delivers the Most Value

• On product pages with obvious accessories, where the customer can quickly understand the value of the additional item.
• In catalogs where related products are already set up carefully and can serve as a source for default products.
• In stores with variable products, if the selected plugin version supports the required product type or exact variation.
• In categories where an extra discount on an accessory helps customers decide faster without damaging margin.
• On products with a repeatable purchase pattern: a core product, consumables, spare parts, care items, or compatible add-ons.

If the product is complex, expensive, or consultation-heavy, the block can still be useful as a navigation aid, but it will not replace a solid description, a compatibility table, or clear answers to common questions. On pages like that, it is better to keep the add-on set short and focused rather than overload the layout.

Who the Plugin Fits, and Who Should Choose Another Tool

WPC Frequently Bought Together for WooCommerce is a strong fit for stores that want to manage product recommendations directly inside WooCommerce without relying on a separate external recommendation system. It is a practical option for sites where the owner or manager already knows which products are genuinely bought together and is willing to maintain those links as the catalog changes.

The plugin is especially convenient if you already use the WPClever ecosystem. The documentation describes integrations with WPC Product Bundles, WPC Composite Products, WPC Grouped Products, WPC Variations Radio Buttons, WPC Smart Quick View, and other WPClever products. That does not mean every store needs all of them. But if the project already includes WPC plugins, Bought Together is easier to fit into an already familiar settings workflow.

When It Is a Good Choice

Choose this plugin if you need a controlled recommendation on the product page where the customer can select or remove the extra items. What matters here is that WPC Frequently Bought Together can assign a new price to each add-on as either a percentage or a fixed value, change the quantity, enable default selection, display products in different layouts, and control how the offer is added to the cart.

The plugin also makes sense for stores that do not want to turn every set into a separate bundle product. Sometimes a bundled product is the better option, but it creates a separate product entity, separate SEO footprint, separate product page, and separate analytics. Bought Together works more gently: the main product stays central, and the add-ons are built around it.

When the Plugin May Not Be the Best Fit

There are several situations where it makes sense to choose another tool upfront, or at least run a test on a site copy first.

• If the add-on products must be mandatory and the customer should not be able to remove them from the set.
• If you need a full bundle builder where the customer selects components from several groups and sees dependent options.
• If the store relies heavily on a custom product page template, a page builder for product layouts, or custom AJAX add-to-cart behavior.
• If discounts depend on complex cumulative logic, coupons, user roles, subscriptions, or multi-layer pricing rules.
• If you need precise automated recommendations based on actual order history rather than manual links, related products, upsells, cross-sells, or rules.

It is also worth paying attention to reviews and support threads on WordPress.org. You can find complaints there about broken layouts, problems after updates, and block behavior inside nonstandard templates. That does not mean the plugin will necessarily perform poorly, but after WooCommerce, theme, and plugin updates, the block should always be tested on a live product page, in the cart, and during checkout.

What to Check Before Installing It on a WooCommerce Site

Pre-installation prep matters more than it might seem. WPC Frequently Bought Together affects not only how the product page looks, but also how add-to-cart behavior works. If the store already uses a product page builder, quick view, floating cart, HTML caching, or script minification, you first need to understand exactly where the new block will appear and which scripts are responsible for recalculating the price.

It is best to test on a staging copy or at least on a low-traffic product with limited visibility. Do not start with the main product in a key category unless you are sure the theme displays the block correctly, the price recalculates properly, and the additional products do not disappear when added to the cart.

Basic Requirements

• WooCommerce must be installed and working: products open correctly, the cart accepts regular products, and checkout completes without errors.
• Each additional product must have correct pricing, publication status, stock availability, and variations if needed.
• The products you plan to offer as add-ons should ideally have clear images and short, understandable names.
• If you use cross-sells, upsells, or related products, check them in advance: WPC Frequently Bought Together can use those links as default products.
• If the store uses a product page builder, confirm that the selected template supports the standard WooCommerce hooks in the product area.

Theme and Cache Compatibility

The official description states compatibility with WooCommerce themes and WPC plugins, but every real store may include its own custom work. So do not rely on the generic compatibility claim - look for actual symptoms instead: does the block appear in the right place, have the buttons shifted, are quantity fields duplicated, does the price update after selection, and is script minification breaking the interface?

As for caching, the rule is simple: product pages can be cached, but dynamic cart elements, WooCommerce fragments, and price recalculation scripts must not break. If the price stops changing after optimization is enabled, first disable JavaScript combining for the product page or exclude the plugin scripts from aggressive minification. Do not do that blindly across the entire site - compare one product page before and after the change.

Validate the Business Logic Before Setup

Before installation, build a short table of three to five test products. For each one, decide in advance which add-ons actually make sense, what discount is acceptable, whether the customer should be able to change the quantity, and whether the products should be added separately. That prep saves time because you will not be choosing add-ons randomly inside the admin panel.

Mini Checklist Before the First Setup

What to Check	Why It Matters	Example Decision
Connection between the main product and the add-on	The customer should immediately understand why these specific items are being recommended.	Offer a memory card and strap with a camera, not a random product from the same category.
Discount and margin	The new price should not accidentally wipe out profit or conflict with the sale price.	For a sale item, calculate the discount from the regular price if you need to avoid a double markdown.
Quantity	Some accessories make sense in multiples, while others only make sense once.	Set quantity 2 for screen protectors, but keep a sleeve at quantity 1.
Inventory	There is no point recommending a product that cannot actually be purchased.	Enable the unavailable items exclusion or manually replace the item.

Installation and the First Safe Test

The installation process is standard for WordPress: open Plugins, add a new plugin, find WPC Frequently Bought Together, install it, and activate it. WordPress.org also notes that WooCommerce must already be installed, and that when editing a product, a Bought Together tab appears inside the Product Data block. After activation, you do not need to start filling in every product immediately. It is much safer to begin with one test scenario.

After installation, the admin panel shows the path WPClever - Bought Together. That is where the global settings live: pricing method, default products, positions, details, variation selector interface, link behavior, change image, change price, counter, cart and checkout settings, and search settings. At the individual product level, you will choose the specific Bought Together items, set the price, quantity, selection mode, and labels.

First Post-Activation Check

1. Open a test simple product in the admin panel.
2. In the Product Data block, find the Bought Together tab.
3. Add one simple product through search and save the product.
4. Open the product on the front end of the site in a regular browser window.
5. Check whether the recommendation block appears in the expected area of the page.
6. Add the main product and the selected add-on to the cart.
7. Make sure both products appear in the cart and that the total matches the configuration.

If the block does not appear at this stage, do not move on to bulk configuration. First check the output position, the product page template, whether the product itself is enabled, whether the add-on product is published, whether the theme hides the block with CSS, and whether there are conflicts with the page builder.

Settings You Should Not Touch on Day One

Do not enable Smart Rules, complex variation logic, a custom selector for pricing, quick view, bulk import, or nonstandard block positions right away until you have validated the simple scenario. These features are useful, but each one adds another layer of testing. At the beginning, what matters most is confirming that the core flow - "product page - add-on selection - cart - checkout" - works reliably.

Quick takeaway: the first test should be boring and predictable. One simple main product, one simple add-on product, clear pricing, a standard block position, and a normal WooCommerce cart.

Key Settings After Installation: Price, Product Source, and Display Position

The WPClever - Bought Together section controls the plugin at the store level. The goal here is not to switch on everything available, but to choose the modes that match your sales logic. Below are the settings worth reviewing first.

Pricing methods: which price the discount is based on

The documentation describes two ways to calculate the price of Bought Together items: from Sale price and from Regular price. By default, the plugin calculates from the product's current price, which means a product already on sale may use its reduced sale price as the base. If you then apply an additional percentage discount, the final price may end up lower than expected.

The from Regular price mode helps prevent a double discount for products that are already on sale. It is not the "best" setting for every site, but for most stores running active sale campaigns, it is worth testing. If you sell accessories without sale pricing, the default mode may be perfectly fine. If sales, coupons, and Bought Together discounts frequently overlap, always verify the final cart total on a real product.

Default products: the automatic source of recommendations

Default products are used when no manual list has been set in the Bought Together tab for a specific product. The settings offer options tied to upsells, related products, or combinations of the two. That is convenient if the catalog is already organized carefully. But if related products are generated too broadly, the automatic block may display items that do not actually help the customer.

A good strategy is to assign manual sets for bestsellers and promoted products, and use default products as a fallback layer for the rest of the catalog. The documentation states that a manual list at the product level takes priority over default products. That makes gradual cleanup easier: enable a general mode first, then improve your key products manually over time.

Positions: where to display the block

The block position affects both conversion and the visual order of the product page. WPClever settings include options such as Above add to cart, Under Add to cart, Under title, Under price, Under excerpt, Under meta, and None. For most stores, starting near the purchase button makes sense because the user is already evaluating the product and its price.

But the right position depends on the theme. If the block appears too high, it can distract from selecting the main product variation. If it appears too low, the customer may never see it before clicking Add to cart. After choosing a position, check the product page on both desktop and mobile, especially if the theme rearranges the summary area.

Details: what to show inside the list

In the details group, you can control thumbnails, pricing, and the short description. It is not always a good idea to show everything. A thumbnail is useful for accessories where visual recognition speeds up the choice. Pricing is essential if you offer a discount or if the quantity differs from one. The short description is best enabled only when it is genuinely short and helps explain compatibility.

If the product page is already crowded, start with the thumbnail and price, and leave the short description off. Then review whether the customer has enough information. For compatible parts, consumables, and products with similar names, a brief description can be helpful, but long text inside the block often hurts readability.

Change image and Change price

The Change image option can switch the main product image when a Bought Together item is selected. That is not always beneficial. For accessories, changing the main image can pull attention away from the primary product, especially while the customer is still choosing a variation. Use it only where the visual response genuinely clarifies the selection.

Change price controls automatic price updates when an item is selected or its quantity changes. The documentation lists Yes, Yes, custom selector, and No. On a standard theme, Yes is usually enough. A custom selector is meant for nonstandard page structures, and it is best treated as a diagnostic setting only after you have confirmed that the price is failing to update because of custom theme markup.

Search settings: how the manager finds products for the set

Search settings affect how products are found in the admin area when creating a Bought Together list. The documentation mentions searching by SKU, ID, exact title, phrase matching, the ability to allow the same products, and filtering by product types. These settings matter in large catalogs. If a manager cannot quickly find the right item, they will either choose less accurate products or avoid manual setup entirely.

For a catalog with clear SKUs, enable SKU search. For stores with many similar product names, exact search can be useful, but it requires consistent naming discipline. Only enable Accept same products when the exact same product genuinely needs to appear more than once in the offer, for example for different pattern choices or a special variation-based scenario. In most other cases, it only creates confusion for both the manager and the customer.

Configuring the Offer at the Product Level Through the Bought Together Tab

The most important work happens on the product page itself. Global settings define the overall rules, while the Bought Together tab is where you build the actual offer. The official instructions outline the process clearly: find the tab, add products via search, set a new price, quantity, custom quantity, min/max, discount for the main product, check all by default, add separately, and add text above or below the block.

It is easy to make mistakes here if you treat every field as mandatory. In practice, it is better to start from the commercial goal: what exactly should the customer buy in addition to the main product, and why? Then choose the price, quantity, removability, and cart behavior to support that goal.

Selecting Products Through Search

Start with two or three items. The longer the list, the higher the cognitive load on the customer and the harder it becomes to verify pricing. Search may distinguish between simple products, variable products, and variations if your installed plugin version and settings allow those item types. The feature set may differ between the free and paid versions, so do not promise variation support to your managers until you have confirmed it in the version you actually use.

Once the products are added, drag them into a logical order. Show the most obvious accessory first, then the secondary add-ons. If the product depends on exact compatibility by size, color, or model, do not rely on the title alone. Add a clear note on the main product page or use the exact variation if that is supported.

New Price: Percentage or Fixed Value

WPClever's instructions include several examples: a number can define a fixed new price, 100% means the current price, 90% applies a discount relative to the selected calculation base, and 0 or 0% turns the product into a free gift. That is a powerful setting, but it requires care.

Do not use gift pricing for products with a high cost basis unless you have checked it separately. If the product is added as a separate line item, review how it appears in orders, taxes, reports, and emails. If the discount is meant to be temporary, make sure the manager remembers exactly where it was configured. Otherwise, a hidden discount may still be active weeks later without anyone accounting for it in the promo plan.

Quantity, custom quantity, and min/max

Default quantity sets how many units of the add-on product are included in the offer. That is useful when one accessory is typically needed in multiples. Custom quantity allows the customer to adjust the quantity of the Bought Together item. Min/max limits the range, but the documentation makes one detail clear: min/max only works when Custom quantity is enabled, and different maximum values cannot be set for each product individually.

If custom quantity is disabled, you can use sync quantity so the quantities of the additional products follow the quantity of the main product. That protects scenarios where a customer might try to get a cheap or free accessory in a larger quantity than the main product. For consumables, synchronization often makes sense; for independent accessories, separate quantity control is usually better.

When to Enable Custom quantity

Enable custom quantity if the customer has a legitimate reason to choose more or fewer add-on items. For example, a printer could reasonably be offered with several packs of paper. But a laptop rarely needs three identical adapters. If quantity choice does not add value, the extra field only makes the block harder to use.

When to Use Check all by default

Check all by default helps present a "ready-to-buy set" that is preselected from the start. But for expensive products, that mode can create distrust: the customer clicks the button and ends up with more items in the cart than expected. Use default selection only when the list is short, the discount is obvious, and the customer can easily see what is being added.

Add Separately: When Products Should Become Independent

The Add Separately mode is important to understand. The documentation states that when this mode is enabled, discounts on Bought Together items are removed, prices revert to their original values, and the additional products stay in the cart even if the main product is removed. In other words, this is no longer a promo combo with linked pricing, but simply a convenient way to add several separate products at once.

Use Add Separately when convenience matters more than discounting. For example, a customer might be looking at a group of products from the same collection and want to add them quickly in one step. But if your commercial goal is specifically "buy together for less," this mode may quietly remove the discount. That is why the final price should always be checked after enabling it.

How to Design the Block So It Does Not Get in the Way of the Purchase

WPC Frequently Bought Together offers several presentation modes: default layout, separate image layout, grid layouts, responsive mode, an additional Add to cart button for long lists, and detail display settings. The goal here is not to choose the prettiest layout, but the one that helps the customer understand the offer quickly.

For a short list of accessories, a compact default layout usually works well: product title, checkbox, price, and possibly a thumbnail. For more visual products where image comparison matters, a separate image layout may work better. For longer lists, it makes sense to add a second purchase button near the block so the customer does not need to scroll back up the page.

Default layout, separate image layout, and grid

The default layout is usually easier to read on narrow screens and in themes with dense product pages. A separate image layout does a better job of showing visual differences, but it may take up more space. A multi-column grid can work well for accessories with images, but it must be checked on mobile: if the cards become too small, users stop seeing the prices and checkboxes clearly.

Do not choose a layout based on a screenshot from the documentation. Open your theme, your product, and your images. The same layout may look polished in a demo and fall apart in a real catalog with long product titles.

Above/Under text labels and localization

The Above/Under text fields help explain the offer next to the block. Do not write ad copy like "best offer." It is better to state the purpose briefly: "Add compatible accessories to your order" or "Choose consumables that fit this product." If the store runs in Russian, review all strings in the localization tab and the associated text settings for cart and checkout.

The plugin supports custom phrases for the additional price and associated text. In cart and checkout, the associated text may contain the %s placeholder, which is used to output the name of the main product. Do not remove it accidentally if you want to preserve the link between the add-on item and the main product inside the cart.

A Small CSS Adjustment for a Cleaner Block

If the theme displays the block too tightly, you can add a small CSS adjustment through Appearance - Customize - Additional CSS or via a child theme. The example below is based on publicly seen plugin markup classes. Before applying it, open the product page, use the browser inspector, and confirm that the classes match what your site actually uses.

.single-product .woobt-products {
  margin-top: 18px;
  padding: 16px;
  border: 1px solid rgba(0, 0, 0, 0.08);
  border-radius: 8px;
  background: #fff;
}

.single-product .woobt-product-item {
  padding-top: 10px;
  padding-bottom: 10px;
}

.single-product .woobt-add-to-cart {
  margin-top: 12px;
}

The check is simple: refresh the product page without cache, make sure the block no longer blends into the description, confirm the button has not shifted outside the container, and check that the mobile version has not ended up with oversized spacing. Rolling it back is safe too: remove the CSS and clear the page cache.

Variations, Selection Methods, and the Logic of "One or Several Products"

WooCommerce stores often sell products with variations: size, color, material, volume, configuration. For Bought Together, this is an especially sensitive area. The customer needs to understand which exact variation of the add-on product is being added, and the store must calculate price and stock correctly. In this section, it is important to separate three things: which product types are available in your version of the plugin, how the customer selects the add-on product, and whether multiple items can be selected at the same time.

WPClever's official sources state that the Premium version adds support for variable products or exact variations as Bought Together items. WordPress.org also highlights that as a Premium feature. That means before promising this workflow to a catalog manager, you need to open your installed version and confirm that search actually allows you to add the required product type. Do not transfer variable product logic from a demo or review into a production store without testing it on the exact version you use.

Default selector and WPC Variations Radio Buttons

In the general settings, the documentation describes two interfaces for variation selection: the standard selector and the option that uses WPC Variations Radio Buttons. Standard mode shows dropdown selectors for the attributes of a variable product. That is familiar in WooCommerce, but not always convenient inside a compact recommendation block. Radio buttons can make the choice more visible, but they require a separate WPC Variations Radio Buttons plugin and interface settings on the corresponding product tab.

If you have one add-on variable product with two options, the standard selector is usually clear enough. If the product has many sizes or colors and the customer needs to choose the right variation directly inside the Bought Together block, a radio-based interface may be more practical. But in that case, test whether the theme markup breaks the buttons, whether the text becomes too small, and whether switching variations recalculates the price correctly.

Single selection and multiple selection

In the selection methods section, WPClever describes two modes: single selection and multiple selection. Multiple selection is used by default and allows the customer to choose one or several Bought Together items. That makes sense for accessories: they may want the mouse and the sleeve, but not the adapter. Single selection limits the choice to one product from the list. That mode is helpful when the items are alternatives rather than complementary add-ons.

For example, the main product might be paired with one of three protective case options. The customer does not need all three - they need one suitable choice. In that scenario, single selection reduces the risk of an incorrect cart. But for consumables, an accessory set, or products from the same collection, multiple selection is usually the better choice, otherwise the block loses its meaning as a grouped recommendation.

How Not to Confuse the Customer with a Complex Combination

If the main product itself has variations and the additional products also have variations, the page becomes complicated very quickly. The customer first chooses the size or color of the main product, then sees several Bought Together items, then chooses their variations and quantities. On a page like that, you cannot rely on UI alone. Add a short Above text, keep only the most relevant items in the block, and check the keyboard focus order if the theme heavily customizes the product form.

For complex products, it is better to create two levels of workflow. The first is a short Bought Together block with simple, obvious accessories. The second is a full bundle or composite product for customers who need more advanced configuration. That way, you avoid turning every product page into an overloaded builder while keeping the purchase flow clear.

Practical Scenario: An Accessory Set for a Main Product

Let us look at a concrete example. Suppose the store sells a laptop. The goal is to offer the customer a mouse, a sleeve, and a USB-C adapter directly on the laptop product page. The customer can remove any unnecessary items, while the store offers a moderate discount on the accessories to lift average order value without creating a separate bundle product.

Goal and Preparation

The goal of the scenario is simple: the main product remains the laptop, and the accessories are added as optional items. To prepare, you need published products for the "mouse," "sleeve," and "USB-C adapter" with prices, images, and stock availability. If an accessory has variations, check in advance whether your plugin version supports adding either a variable product or a specific variation to the Bought Together list.

Setup Steps

1. Open the laptop product in the WooCommerce admin panel.
2. In the Product Data block, go to the Bought Together tab.
3. Add the mouse, sleeve, and USB-C adapter through search.
4. Set the mouse price to 90% if you want a discount based on the selected pricing method.
5. Leave the sleeve at 100% if no discount is needed but it should still appear in the offer.
6. Set a fixed value for the adapter only if you specifically want a new fixed price rather than a percentage.
7. Keep the default quantity at 1 for each accessory.
8. Do not enable custom quantity if the customer does not need to change accessory quantities.
9. Enable Check all by default only if the offer is short and the discount is obvious.
10. Add Above text such as "Add compatible accessories to your order" and save the product.

Checking the Result on the Site

Open the laptop product page in a private browser window. Make sure the block is visible near the purchase area, the items appear in the correct order, the prices do not look broken, the checkboxes work, the selected items are added to the cart, and the final total matches your expectations. Then remove the main product from the cart and see what happens to the add-on items. The behavior depends on the selected mode, especially if Add Separately is enabled.

The Detail That Often Breaks the Scenario

If the price does not change after selecting an accessory, do not start with CSS. First check Change price, look for JavaScript errors in the browser console, review caching, and inspect any nonstandard price template in the theme. If a custom selector is configured, temporarily switch back to the standard mode and test the product on a default theme or in a minimal environment. That will tell you whether the issue comes from the plugin, the theme, or optimization.

Bulk Recommendations, default products, and Smart Rules

Once the first scenario works, it is tempting to enable recommendations across the entire catalog. You can do that, but carefully. WPC Frequently Bought Together has several layers: a manual product-level list, default products based on related products, upsells, and cross-sells, and Smart Rules in the Premium version. These layers solve different problems.

Default products as a Quick Start

Default products work well if the store already has disciplined linked product data. Related products based on categories and tags can provide a decent set for simple catalogs, upsells can promote an upgraded version, and cross-sells can suggest complementary items. But an automatic rule does not understand context as well as a human manager. That is why expensive products and bestsellers are usually better handled with a manual list.

If default products are showing strange items, do not blame the plugin alone. Often the real problem is that the categories, tags, linked products, and cross-sells themselves are configured too broadly. Clean up the catalog structure first, otherwise the automatic block will simply repeat that same chaos.

Smart Rules for Large Catalogs

Smart Rules in the Premium version let you assign Bought Together products by condition: all products, selected products, source combinations, categories, tags, brands via WPC Brands, collections via WPC Smart Product Collections, product types, visibility, shipping classes, and attributes. That is useful for large catalogs where manually maintaining hundreds of product relationships is too expensive.

But Smart Rules require strict validation. If a rule applies too broadly, the block may appear on products where it does not belong. If a rule overlaps with manual settings, you need to understand the priority order. The documentation notes that rules can be managed on a single page, dragged, collapsed, duplicated, and deleted. Use that as an actual system, not as a storage area for random conditions.

When Automation Is the Wrong Choice

Do not automate recommendations for products with legal restrictions, model-specific compatibility, seasonal sets, expensive accessories, or complex variations unless the manager is ready to validate every relationship. A bulk rule works well for standardized consumables, but poorly for products where a compatibility mistake leads to returns.

Cart, Checkout, and Verifying the Final Total

Testing does not end on the product page. WPC Frequently Bought Together affects how products are added to the cart, how they are tied to the main product, whether the customer can change the quantity, and what associated text appears in cart and checkout. If you test only the front-end block, you can miss a serious issue in the actual order flow.

Change quantity in the cart

The cart and checkout settings include Change quantity. If enabled, the customer can change the quantity of Bought Together items in the cart without increasing the quantity of the main product. If disabled, the quantities of the additional products stay synchronized with the main product. The right choice depends on the product. For an accessory that is commonly purchased independently, changing quantity may be perfectly fine. For a gift or a heavily discounted item, it is usually better to keep the quantities synchronized so the discount does not work separately from the main product.

Associated text

Associated text shows in the cart and at checkout which main product an add-on item belongs to. That is especially important when the cart contains several main products and similar accessories. Keep %s in place if you want to output the main product name. Without that connection, it becomes harder for both the manager and the customer to understand why the item appears in the order.

Test Order

For final verification, place a test order with a minimal amount or use a safe test payment method if one is configured. Check the thank-you page, the customer email, the admin email, the order contents in the admin panel, taxes, discounts, and inventory. If the additional product is supposed to reduce stock, make sure it is deducted like a normal product. If you use ecommerce analytics, verify that the added items do not break data tracking.

Result check: a configuration should only be considered complete after the full test flow "product page - cart - checkout - email - order in the admin panel." A nice-looking block on the product page alone does not prove that the scenario actually works.

How to Tell Whether the Block Is Really Helping Sales

After the technical check, it is worth evaluating how customers actually behave. Do not promise yourself a guaranteed increase in average order value: pricing, traffic, assortment, seasonality, trust in the store, and the quality of the recommendation itself all affect the outcome. But you can still collect a few practical signals. Compare the number of orders with add-on products before and after enabling the block, see which accessories are chosen most often, and check whether abandoned carts increased on product pages where the block became too aggressive.

If analytics is configured, tag the test products in your reporting or use a separate accessory category. It is important to look not only at total revenue, but also at the quality of the added items: are customers buying compatible products, are they returning them more often, and are they asking your team questions about incorrect compatibility? A good Bought Together block should reduce uncertainty, not create a new support burden.

Mini Test for One Category

Choose one category where the relationships are obvious: electronics and accessories, cosmetics and care products, sports goods and consumables. Configure 5 to 10 product pages, place the block somewhere visible but not aggressive, and compare the share of orders with accessories a few weeks later. If the result is neutral or poor, improve the product selection and wording first rather than increasing the discount. Often the problem is not price, but the fact that the recommended products feel random.

Common WPC Frequently Bought Together for WooCommerce Issues and Diagnostics

It is best to troubleshoot from symptom to cause. Do not change ten settings at once - that makes it hard to tell what actually fixed the problem. Below are the typical situations you may run into with the plugin and a WooCommerce bought together setup.

The block does not appear on the product page

Symptom: the product is saved, the add-on items are selected, but the block is missing on the public page. Possible causes include: the output position is set to None, the product template does not render the required hook, the manual list is disabled at the product level, default products did not find suitable items, or the add-on products are unavailable or hidden.

Check the position in WPClever - Bought Together, confirm the items are present in the Bought Together tab, verify the publication status of the add-on products and their stock status. If a builder is in use, temporarily test the product on a standard template or insert the block through an available shortcode/widget only if that is confirmed by your version and documentation.

The price does not update when a product or quantity is selected

Symptom: the checkbox works, but the final price on the product page does not change. Start with the Change price setting. If No is selected, the price is not supposed to update. If Yes is selected, check the browser console, look for JavaScript minification conflicts, review WooCommerce AJAX fragments, and inspect the theme's custom price markup.

If the theme outputs the price in a nonstandard location, you may need Yes, custom selector. But that is a targeted adjustment, not a universal fix. First confirm that recalculation works correctly in a standard WooCommerce structure.

The discount disappears in the cart

Symptom: the product page shows a discounted price, but the add-on items appear at their normal price in the cart. Check whether Add Separately is enabled. WPClever's documentation states that in this mode, discounts on Bought Together items are removed and prices revert to their original values.

If you need a true promo pairing, disable Add Separately and rerun the test. If you only want convenient joint purchasing without a discount, keep the mode enabled, but explain that clearly to your managers so they do not expect promotional pricing.

Quantity buttons are duplicated

Symptom: the block shows two plus/minus pairs, or the quantity field looks broken. The cause is often an overlap between the Show plus/minus buttons option and a theme or plugin that already replaces the quantity input. Disable plus/minus in the Bought Together settings and see whether the duplicate disappears.

If the theme already adds buttons to all quantity fields, it is usually better to let the theme handle it. If you specifically need the plugin's styling, disable the theme's duplicate script only in a targeted way and only after testing other WooCommerce pages.

Out-of-stock products appear in the list

Symptom: the customer sees an out-of-stock item in the Bought Together list. The general settings include Exclude unpurchasable. If set to Yes, unavailable products are removed automatically. If set to No, they may remain visible with a strikethrough and still not be added to the cart.

For most stores, it is better to hide unavailable items to avoid frustration. But if the product is coming back into stock soon and you want to preserve the pairing as a reference, you can leave it visible and add a clear message on the page.

Recommendations appear where they are not needed

Symptom: the block appears on the wrong products or is displayed too broadly across the catalog. Check default products and Smart Rules. If the automatic source based on related products, upsells, or cross-sells is enabled, the block will follow those relationships. If the Premium version contains a broad rule by category or tag, it may capture more products than intended.

Fix it by narrowing the source, limiting the category, disabling the rule, manually setting the list for key products, or using a product-level disable option if your version supports it.

Questions About Setup and Limitations

Can WPC Frequently Bought Together for WooCommerce be used for free?

On WordPress.org, the plugin is presented as free with commercial upgrades or support. Some features - such as adding variable products or exact variations as additional items, and Smart Rules for bulk conditions - are listed as Premium. Before configuring a complex workflow, confirm that the feature you need exists in your version.

Why are the additional products optional instead of required?

The Bought Together logic is built around voluntary selection. The customer can remove products from the list. If you need required items, this is not the best plugin scenario. Look at force sells, bundles, or composite products, where the dependency can be enforced more strictly.

What should I choose: manual products or default products?

For important products, a manual list is better. Default products are useful as an automated layer for a catalog where related products, upsells, or cross-sells are already configured. If those relationships are messy, default products will show messy recommendations too.

Should I enable Add Separately?

Enable Add Separately if the additional products should go into the cart as independent standard products without promo linkage and without preserving Bought Together discounts. If you are promising the customer a discount for buying together, this mode is usually the wrong choice.

How do I verify that the discount is calculated correctly?

Compare the product page price, the price of each selected add-on, the cart total, the checkout total, and the order in the admin panel. Also test products that already have a sale price, because the pricing method may calculate the discount from either the sale price or the regular price.

Will the block affect site speed?

Any WooCommerce block that includes products, images, and JavaScript can add some load. Usually, what matters more than the installation itself is the number of products in the block, image quality, caching, minification, and theme complexity. Keep the list short, avoid showing dozens of products, and test the product page with speed tools after enabling it.

Can the block be displayed in a custom product template?

That depends on the theme, the builder, and the insertion methods supported by your version. If the standard position does not work, first check whether the template outputs the standard WooCommerce hooks. If you need a shortcode or a separate widget, use only a method confirmed by the documentation or a support response for your version.

What should I do after updating the plugin?

Check several products with different scenarios: a simple product, a product with variations, a product using default products, a product with a manual list, plus the cart and checkout. The WordPress.org changelog includes fixes related to CSS/JS, cart/checkout blocks, variation issues, and WooCommerce compatibility, so both visual and functional checks after an update are mandatory.

When WPC Frequently Bought Together for WooCommerce Is the Right Choice

This plugin is worth using if you need a clear block of additional products on the product page rather than a full bundle builder. Its strong point is controlled optional recommendations: a manual list at the product level, default products from linked products, percentage-based or fixed-value discounts, quantity settings, multiple layouts, cart behavior settings, and Premium Smart Rules for large catalogs.

Before rolling it out to a live catalog, configure one product and test the price, quantity, cart, checkout, emails, inventory, and theme behavior. Then expand carefully: first the key products, then categories, then bulk rules. If the logic matches your actual sales workflow after testing, you can download WPC Frequently Bought Together for WooCommerce and introduce it carefully into the production store.

If instead you need a required set, complex component-based assembly, deeper bundle inventory handling, or automated recommendations based on order history, it is better to compare WPC Frequently Bought Together with bundle, composite, and recommendation tools right away. The right choice here is not the one with the longest feature list, but the one that most accurately supports your real sales scenario.