WooCommerce 11.3 bundle in cart count: what changes and how to test it

What changes in WooCommerce 11.3

The Product Button block shows a small label such as 1 in cart when a shopper already has that product in their basket. The same button appears inside the Add to Cart with Options block. From WooCommerce 11.3, items that an extension declares as children of another cart item no longer count towards that label.

Until now, a product that sat in the cart only because it was part of a bundle made its own button say 1 in cart, even though the shopper never chose it separately. WooCommerce core cannot tell those items apart from products added on their own, so the extension that added them has to say which item they belong to. A new filter, woocommerce_store_api_cart_item_parent_item_key, lets the extension do exactly that, and Store API cart items gain a read-only field called parent_item_key.

A second, smaller adjustment arrives alongside it. When the same product appears on several cart lines, the button now adds every line together. Previously it showed only the first line's quantity.

Which stores the bundle count change affects

Your store is in scope when two conditions meet: you display the Product Button block or Add to Cart with Options, and an extension adds cart items on behalf of another cart item. WooCommerce gives these extension types as examples:

Free gift and upsell plugins sit in a grey area. They add a real product tied to another item, and for them a 1 in cart label can be correct, so a vendor can reasonably keep the old count.

WooCommerce never marks an item as a child by itself. If your extension does nothing, those items keep counting exactly as they do today.

• Product bundles
• Composite products
• Mix and match products
• Force sells
• Chained products
• Frequently bought together

Test the WooCommerce 11.3 in cart count on staging

The check needs no code and belongs on a staging copy of the shop, so no live customer's basket or order is touched. Run it once 11.3 is available and installed on staging alongside the extension versions you plan to run live.

Read the results with care. A missing count at step five is an observation, not proof that the extension supports the new filter, because a page layout without the Product Button looks the same. Confirm support through the vendor's changelog or support team.

Step six matters as well. Once the parent leaves the cart, any child left behind counts as a standalone item again and shows a count. WooCommerce does not remove those children, so if they should never be sold without their parent, removing them is the extension's job.

1. Update staging to WooCommerce 11.3 with your bundle, composite or similar extension active.
2. Open a private browser window so you start with an empty cart.
3. Add the parent product, such as a bundle, to the cart.
4. Visit a page showing the Product Button for one of the items the parent added.
5. Read the button. A 1 in cart label means the extension has not declared that item as a child.
6. Remove the parent from the cart, then check whether the child items remain and what their buttons show.

What to ask your extension vendor

If your test shows 1 in cart against a bundled item, send the vendor a short, specific question rather than a bug report. Ask whether their extension supports the woocommerce_store_api_cart_item_parent_item_key filter in WooCommerce 11.3 and, if not, whether support is planned. Useful follow-up questions:

Developers maintaining custom code that adds items to the cart follow the same rules. The parent key is the cart item key that the cart's add_to_cart() method returns when the parent goes in, not a product ID, stored in the child's cart item data. Once the parent leaves the cart, WooCommerce returns null for the child's parent_item_key, so the stored key needs no tidying.

• Does the extension return the parent's cart item key from the filter, rather than a product ID?
• For items it did not add, does it pass the existing value through unchanged, so it never erases a parent declared by another extension?
• What happens to child items when the shopper removes the parent?
• Which version adds support, so you can confirm it in the changelog?

What the change does not do

Keep the scope in proportion. WooCommerce describes the 11.3 change as a Product Button count adjustment plus a new Store API field, and for now that count is the only place the field is used. The release is not a security fix, and an extension that ignores the filter carries on working.

WooCommerce has also said blocks can rely on the parent link in future, giving the Cart and Mini-Cart blocks showing child items indented under their parent as an example. Treat that as a stated direction rather than a scheduled feature. Even so, it gives you a fair reason to ask vendors to declare parents when the count itself does not bother you.

Before updating your live shop, read the 11.3 release notes and repeat your usual checks on staging, including a complete test order.

When the cart count is wrong for other reasons

A bundled item still showing 1 in cart is expected until the extension adopts the filter. Counts that refuse to change at all after adding or removing products point elsewhere, such as caching, cookies or a theme conflict, and our guide to a WooCommerce cart not updating walks through those checks safely.

If you would rather hand the problem over, our cart fix service covers AJAX, caching and theme conflicts, with pricing confirmed before you pay.