Some SKUs genuinely sit at the intersection of two packaging types: they group distinct products together (a bundle) and include more than one unit of a component item (a multipack). Knowing which attribute controls which signal — and that both can appear on the same item — prevents unnecessary disapprovals and keeps your feed accurate.
What Each Attribute Actually Does
is_bundle and multipack are separate attributes that solve different classification problems. Conflating them is a common feed mistake.
is_bundle [is_bundle] tells Google that you, the retailer, have grouped a main product with other, different products into a single package sold at one price. Google documentation is explicit: use this attribute "to indicate that you've grouped a main product with other, different products, sold together as one package for a single price." The attribute is a Boolean (yes/no). If you do not submit it, Google documentation states "the default is no." Crucially, you must not set is_bundle=yes for a manufacturer-defined bundle — only for packages you have assembled.
multipack (a separate attribute covered in the product data specification) captures the number of identical units of a single product you have packaged together. It is a numeric value representing count — for example, 6 if you are selling six identical protein bars as one SKU.
The two attributes serve different purposes and are not mutually exclusive. Google documentation describes the product data specification as containing both "Basic product data" and "Detailed product description" sections — multipack falls under detailed product description, while is_bundle is its own distinct attribute.
When a Single SKU Qualifies for Both
A product can legitimately require both attributes when it combines distinct items (triggering is_bundle) and multiple units of one of those items (triggering multipack).
Consider a hypothetical example (this is an illustrative scenario, not a real customer result):
A sporting goods retailer creates a "Starter Cycling Kit" that contains:
- 1 cycling helmet (the main product)
- 2 identical water bottles (a multipack component)
- 1 puncture repair kit
In this hypothetical case, the correct submission would be:
| Attribute | Value | Reason |
|---|---|---|
is_bundle | yes | Retailer-assembled kit with a main product (helmet) and accessories |
multipack | 2 | Two identical water bottles are included |
title | Cycling Starter Kit — Helmet + 2 Water Bottles + Repair Kit | Reflects the whole bundle |
condition | new | All components are new |
Note that the multipack value reflects only the count of the repeated identical unit within the package, not the total number of items. The helmet and repair kit are distinct products, not additional units of the same item, so they do not factor into the multipack count.
Submission Rules and Requirements by Country
The requirements for is_bundle vary by destination and listing type.
is_bundle is required for free listings if you have created a bundle containing a main product. For Shopping ads, Google documentation states it is "Required for Shopping ads if you've created a bundle containing a main product and you're targeting any of the following countries: Australia, Brazil, Czechia, France, Germany, Italy, Japan, Netherlands, Spain, Switzerland, United Kingdom, United States." If you sell into any of those markets and your product qualifies as a retailer-assembled bundle, omitting is_bundle=yes will cause a disapproval.
For multipack, submit the integer count of identical units. Do not use multipack to represent the total item count across different product types in a kit — that is what is_bundle handles.
Format reminders for is_bundle:
- TSV/CSV: submit
yesorno - XML:
<g:is_bundle>yes</g:is_bundle> - The field is not a repeated field; submit it once per item
What to do if the bundle was created by the manufacturer: Do not submit is_bundle=yes. Google documentation states: "Don't submit the bundle attribute for a manufacturer-defined bundle." If a supplier pre-packs the combination at the factory, is_bundle does not apply, regardless of whether you also need multipack.
Content Requirements That Apply to Both Configurations
When a product carries both attributes, your title, image, and description must reflect the complete package — not just the main item.
Google documentation advises: "Describe the entire bundle. For example, submit content for the image link [image_link], title [title], and description [description] attributes that take into account the entire bundle."
For condition, the same source notes: "if any product in the bundle is used, then set the value to used for the condition [condition] attribute." This applies even when one component among several is a used item.
Accurate product data is a foundation requirement across the board. Google documentation is clear that "Incorrect, inaccurate, or missing product information can cause disapprovals, limited eligibility, incorrect displays for your products, or other Issues in Merchant Center." A misclassified bundle — one submitted without is_bundle=yes when it should have it — falls squarely into this category.
A Quick Pre-Submission Checklist
Before submitting a SKU that may qualify for both attributes, run through these questions:
- Did you assemble this combination? If yes, and it contains a main product plus different accessories, set
is_bundle=yes. If the manufacturer packaged it, do not. - Does the package contain more than one identical unit of any single item? If yes, set
multipackto that count. - Is your title covering the whole kit? If a buyer would not know what all the items are from the title alone, expand it.
- Is your image showing the complete contents? A product image showing only the hero item understates the bundle.
- Is condition set to the least-new item? If anything in the kit is refurbished or used, the condition attribute must reflect that.
Managing these attribute combinations at scale — especially when your catalog has dozens of kit SKUs with varying component counts — is exactly the kind of feed operation where a structured approach pays off. Magicfeedpro is built to help catalog operators maintain accurate attribute mappings across product types including bundles and multipacks, so each SKU reaches its destination feed correctly classified.
Related articles
availability_date in Shopping Feeds: Format, Conditions and Errors
Learn when availability_date is required, how to format it correctly, and what happens when it is missing or malformed in your product feed.
size_type in Google Shopping Feeds: Values, Format and Rules
Learn when size_type is required, what values it accepts, and how it works with the size attribute to prevent apparel disapprovals.
age_group in Google Shopping Feeds: Values, Rules and Variants
Learn which age_group values Google accepts, when submission is required, and how it works with item_group_id for apparel variants.