Stock & fulfilment

Component stock

When a bundle sells, the stock of every component variation inside it is reduced by the exact quantity ordered (a size run of ten reduces those variations by ten, not by one), and restored if the order is cancelled or refunded. There is no double counting and no overselling through the components’ own product pages.

Stock is checked at three points:

• While configuring: low-stock badges (like “Only 3 left”) appear per unit, and out-of-stock options are blocked.
• At add to cart.
• On the cart: if a component runs low while the bundle is sitting in the cart, the shopper is warned right there (classic and block cart), not only stopped later.
• Again at checkout, in case stock changed in the meantime.

The shop owner is told, too: when bundle sales drain a component past its low-stock threshold (or to zero), WooCommerce sends its normal low-stock or out-of-stock email, exactly as if the product had sold on its own product page. And every order lists its component stock movements in the order notes, so the change is visible on the order even where email is switched off.

Cross-unit stock conflicts

If the same variation is picked in more than one unit and the combined demand is more than the stock available, the configurator says so and keeps Add to Cart disabled until the customer changes a selection. Two units cannot quietly claim the same last item.

How many can be built

A stock feed tells you the navy 3XL has forty left. What you actually want to know is how many bundles that is, and which line to reorder to make the next one. BundleBoss works it out: it walks the bundle’s components, divides what each has in stock by what one bundle uses, and the tightest answer is how many can be built right now.

Both sides of the shop read it:

• The editor tells you plainly: “Navy 3XL runs out first: 40 in stock, 4 used per bundle.” That is your reorder line. A bundle whose components do not manage stock says so instead, and a bundle capped by its own stock says the limit is the cap, not the components.
• The product page shows scarcity, and only scarcity: once ten or fewer can be built, the shopper sees it; when nothing can be built, the page says some items have sold out. Above ten the page says nothing, deliberately, because “enough stock for 900” is not urgency, it is your stock depth published to anyone who loads the page. The page never names which component is short, either; that is your business, not the customer’s. (Developers can move the threshold with the bundle_boss_buildable_notice_threshold filter.)

Bundle stock cap

Separately from component stock, you can cap how many of the bundle itself can sell, on the Inventory tab. That uses WooCommerce’s native stock counter, including its low-stock email threshold. See Pricing & discounts for the cap and the other selling options.

Shipping weight

On the Shipping tab, choose a weight mode:

• Automatic: the shipping weight is the sum of the components the customer actually chose.
• Manual: always uses the weight you set on the bundle.

Downloadable and virtual components

• Downloadable components work fully: file permissions are granted on payment (the right number of times for the quantity, with the product’s own expiry), links appear in the customer’s emails, the thank-you page, the order view and My Account, and a refund or cancellation cuts access. The pick list tags download rows.
• Virtual components add no weight or shipping. A bundle made entirely of virtual items is itself virtual.