WooCommerce product bundles can turn several eligible products into one configurable package, but a reliable setup requires more than adding products to a new offer. In the WooCommerce Product Bundles extension, bundle structure, quantity limits, pricing, shipping behavior, inventory and compatibility are separate configuration decisions. Treating them independently makes it easier to predict what customers can select, what they pay, how orders are fulfilled and which stock levels change.
This guide focuses specifically on WooCommerce Product Bundles. It explains how to create a bundle, configure quantities and prices, match shipping settings to fulfillment, manage component and bundle-level inventory, and investigate conflicts with plugins, themes or checkout implementations. Test the complete setup on a staging site before changing a live store.
Choose the Right WooCommerce Bundling Model
Start by defining what the package should contain and how much choice customers need. Product Bundles supports configurable packages, optional items and adjustable quantities. That makes it suitable for both fixed packages and structures in which shoppers choose components or quantities within limits.
Before configuration, confirm that every planned component fits the extension’s supported product types. Product Bundles supports simple products, variable products and simple or variable subscription products. Grouped and external products are not supported, and a product bundle cannot be nested inside another product bundle. Each selected bundled product should also have a valid price before you test purchase behavior.
Check Component Eligibility Before Configuration
Make a component checklist before creating the parent product. Review whether each item is simple, variable, or an eligible subscription product. Remove grouped or external products from the plan, and avoid using one product bundle as a component of another. This early check prevents a failed configuration from being mistaken for a pricing, stock or theme problem.
Keep the planned customer experience clear as well. A fixed package has different testing needs from a pick-and-mix bundle with optional products and adjustable quantities. Test the intended combination on staging before applying it to the live store.
Create the Product Bundle Step by Step
Using WooCommerce Product Bundles, go to Products > Add New and create the parent product. In the Product Data panel, select Product Bundle as the product type. Next, open Bundled Products and add the eligible products that belong in the package.
Configure each bundled item according to the role it has in the offer. Depending on the planned structure, review quantity, pricing, shipping and visibility options. Decide which items are fixed, which are optional and which allow customer-selected quantities. Once the product structure and item settings are complete, publish the product after reviewing the full configuration.
Build the Bundle Structure
Separate product-level decisions from bundled-item decisions. The parent product defines the bundle customers view and purchase, while the products added under Bundled Products define its contents. This distinction is useful when the same component is sold normally and also appears inside a package.
Before publishing, inspect the product page as a customer would. Confirm that the available choices, required items and quantity controls reflect the intended offer. Then place a test order and review the cart, checkout and resulting order lines. Confirm again that all selected bundled products have prices assigned.
Configure Quantities and Bundle Size
Quantity rules determine how flexible the package is. Bundle items can have minimum and maximum quantities. Set the minimum to define the smallest permitted quantity and set a maximum when customers should not be able to add more than a defined amount. A blank maximum means that no upper limit is set in that field.
For configurable or pick-and-mix structures, use optional items or bundle-size limits where the planned customer experience requires them. The extension does not support decimal quantities, so quantity-based configurations must use whole units. Also check whether an item is marked Sold individually: an item with that setting cannot have a quantity range above one.
Test Customer Selection Rules
Test the lowest permitted quantity for every adjustable component, then test the highest permitted quantity when a maximum is configured. Try optional items both selected and unselected, and test configurable items separately from fixed contents. These tests should cover realistic combinations rather than only the default product-page state.
Review the same combinations in the cart and checkout. Confirm that invalid quantities cannot be submitted and that valid quantities remain consistent as the customer moves through the purchase flow. Do not configure decimal quantities or a quantity range above one for an item marked Sold individually.
Set Bundle Pricing Without Confusing Customers
Product Bundles provides more than one pricing model. You can set a base price for the entire bundle, or enable individual pricing for bundled products. When Priced Individually is enabled, an optional percentage discount can also be applied to the component prices.
A base bundle price treats the package as one priced offer. Individual component pricing is relevant when selections or quantities can change the total. The correct choice depends on how the store wants the offer represented, not on a universal rule. Whichever model you choose, compare the displayed total on the product page with the cart, checkout and final order.
Compare Fixed and Component-Based Pricing
Use a base price when the package is intended to have one price as a whole. Use individual pricing when the contents or quantities need to affect the calculation. If the percentage discount is enabled, test how it changes both the visible component amounts and the final bundle total.
Run tests with minimum and maximum permitted quantities and with optional products included or excluded. Validate taxes, checkout totals and order-line displays on staging before applying pricing changes to a live store. The available documentation does not establish that one pricing model always produces better commercial results.
Configure Shipping and Fulfillment
Shipping settings should reflect how the package is actually handled. First classify the bundle as physical or virtual. For a physical bundle, choose whether it is assembled or unassembled. An assembled bundle can use a static or calculated weight. In a partially assembled bundle, selected items can be marked Shipped Individually when they remain in separate packaging.
Review container weight, dimensions and shipping class where the configuration requires them, then test the resulting rates and package behavior. The distinction between assembled and unassembled affects how the order should be understood by the fulfillment process, so the setting should match the store’s operational workflow rather than only the product-page description.
Match Settings to the Fulfillment Process
Use assembled behavior when the components are handled as one assembled package. Use unassembled behavior when the contents are fulfilled separately, and mark selected components as shipped individually when that reflects the packaging process. After configuring the bundle, verify the order representation with the shipping and fulfillment workflow.
External fulfillment, shipping or inventory systems may not import an assembled bundle as one item. Additional integration work may be required, so test synchronization after testing both assembled and unassembled configurations. Do not assume that a third-party system will interpret the bundle exactly as the cart does.
Manage Component and Bundle-Level Inventory
When a bundle is sold, inventory-managed bundled products are reduced. Product Bundles creates separate cart and order line items for purchased bundle contents, so the stock effect is primarily visible at the component level. Bundle availability can therefore be affected by insufficient stock in its contents.
A bundle can also have its own SKU and independently managed stock quantity. This is useful when the limiting resource is not a component but the assembled product, packaging or fulfillment capacity. Component inventory and bundle-level inventory are separate controls and should be selected according to the actual constraint.
Choose the Stock Control That Matches the Constraint
Use component inventory when availability depends on the products included in the package. Consider independently managed bundle stock when the package itself is limited by assembly, packaging or fulfillment capacity. Document how normal product sales and bundle sales share the same component stock.
The extension does not reserve part of a product’s stock specifically for bundles. Shared inventory must therefore be planned across ordinary product sales and bundle sales. Place test orders and verify component deductions, bundle availability and any independent bundle stock changes. If an external inventory system is involved, verify synchronization because order data may represent bundle contents separately.
Troubleshoot Plugin, Theme and Checkout Conflicts
Compatibility with third-party extensions should not be assumed. A plugin or theme that works with standard WooCommerce products may still interact differently with Product Bundles. Begin by updating WooCommerce, Product Bundles, other extensions and the theme, then check WooCommerce > System Status.
For a controlled test, create a backup and preferably reproduce the issue on staging. Temporarily disable all plugins except WooCommerce and Product Bundles, then reproduce the problem. If it disappears, reactivate plugins one at a time and test after each activation. This can identify a possible trigger, although it cannot prove that every issue has the same cause.
Use a Controlled Conflict-Isolation Sequence
Follow the sequence consistently: update the relevant software, record the symptom, test with only WooCommerce and Product Bundles active, and reactivate plugins individually. Then switch temporarily to Storefront or a default WordPress theme to isolate a theme conflict. Compare the result with the original setup and document which change affects the problem.
Temporary deactivation can affect checkout, payments, shipping, caching and other store functions. Do not perform these changes on production without preparation. If the issue remains, consider custom code, server configuration, caching, database synchronization or an external integration as possible areas requiring further investigation.
Check Checkout and Integration Context
Review the official compatibility information and distinguish tested integrations from unlisted combinations. The documented lists are not exhaustive, so an unlisted plugin requires testing in the target store. Also identify whether the site uses Cart and Checkout Blocks or shortcode-based Cart and Checkout. Some documented integration behavior differs between these checkout implementations.
After basic isolation, test caching and optimization plugins, payment and shipping integrations, and external inventory or fulfillment services. Optimization tools can interfere with bundle scripts and price updates, while tools that bypass WooCommerce APIs can contribute to stock-status issues. Verify product-page calculations, cart contents, checkout totals, order lines and stock updates together.
Setting up WooCommerce product bundles works best as a sequence: verify eligible components, create the Product Bundle, define quantity rules, choose a pricing model, match shipping to fulfillment, and decide whether component or bundle-level stock is the real constraint. Finish with staging tests covering selections, totals, stock deductions, shipping and checkout.
The documented behavior described here applies to the WooCommerce Product Bundles extension and does not establish identical behavior for every third-party bundling, shipping, inventory or optimization tool. Test integrations in the store’s actual checkout and fulfillment environment before launch. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.