Google Shopping bundles and multipacks: is_bundle and multipack
How to list Google Shopping bundles correctly, when to use is_bundle vs multipack, what happens to GTINs on bundled products, and the disapprovals each mistake causes.
Google has two attributes for products sold in groups. multipack is several identical items sold together, a 6-pack of socks. is_bundle is a merchant-created group of different products sold as one, a camera with a bag and memory card. They are not interchangeable, and using the single item's GTIN on either is one of the most common identifier disapprovals.
Two attributes, two different situations
| Attribute | What it marks | Value | Example |
|---|---|---|---|
multipack |
Several identical items sold as one offer | The item count | 6 for a 6-pack of socks |
is_bundle |
Different products combined by you into one offer, with one main item | true |
Camera + bag + SD card |
The distinction matters because it changes what Google expects from every other attribute: especially the GTIN. Get the classification wrong and the identifier, price and landing-page checks all start failing in confusing ways.
multipack: identical items, sold together
Use multipack when you've grouped multiples of the same product into a pack the manufacturer doesn't sell as a unit:
- Set
multipackto the number of items:4,6,24. - Keep the single item's GTIN: the attribute is what tells Google the quantity differs from the catalogue entry.
- Set
priceto the total pack price. - The landing page must sell that pack quantity, not the single unit.
If the manufacturer sells that pack size as its own retail unit (a shrink-wrapped 6-pack with its own barcode) it isn't a merchant multipack at all. List it as a normal product with the pack's own GTIN and no multipack attribute.
is_bundle: different products, one offer
Use is_bundle: true when you've combined distinct products into a single offer around one main item: a console with an extra controller, a razor with a pack of blades, a camera kit.
- Identify the bundle by the main product's
brandandmpn(or the bundle's own GTIN if the manufacturer created it). - Do not submit the main item's standalone GTIN for a bundle you assembled: that claims your offer is the bare product, and Google's crawl of your landing page will disagree.
priceis the full bundle price; the title and image should make the bundle contents obvious.- Bundles need a main product. A pick-and-mix of unrelated items with no anchor product ("mystery box") isn't supported.
Deep dive The GTIN logic behind bundles and multipacks
Both attributes exist to solve the same problem: Google matches offers to catalogue entries by GTIN, and a GTIN describes an exact retail unit: one specific product, in one specific quantity, as the manufacturer sells it. The moment your offer differs from that unit, the bare GTIN becomes a lie, and these attributes are how you tell the truth without losing the match:
- Merchant multipack: the GTIN is right about what but wrong about how many. Keep the GTIN, add
multipackwith the count. Google keeps the catalogue match (reviews, spec data) and adjusts the quantity expectation for its landing-page checks. - Merchant bundle: the main item's GTIN would be right about the anchor product but wrong about the offer. Drop the standalone GTIN, set
is_bundle: true, identify viabrand+mpnof the main product. You trade away some catalogue-match strength in exchange for not being disapproved. - Manufacturer multipack or bundle: the outer pack has its own GTIN, so it's just a product. No attribute needed, full catalogue match available.
The predictable failure at feed scale comes from platform exports: bundle and pack SKUs inherit the base product's barcode field, so hundreds of pack offers reach Google claiming to be single units. Google cross-checks price against the catalogue entry (a "single" item priced at 6x the market price for that GTIN is an easy automated flag) and the account collects "incorrect product identifier" or price-mismatch disapprovals in batches. The fix is structural, not per-product: pack and bundle SKUs need their own identifier logic in the feed layer, applied before submission.
Common bundle and multipack disapprovals
| Symptom in Diagnostics | Root cause | Fix |
|---|---|---|
| Incorrect product identifier | Single item's GTIN on a bundle | Remove GTIN, set is_bundle: true, submit main item's brand + MPN |
| Price mismatch | Pack price vs single-unit catalogue price under a bare GTIN | Add multipack with the correct count |
| Mismatched value (page crawl) | Landing page sells a different quantity than the offer implies | Align pack quantity across feed, title and page |
| Invalid value for multipack | Text like 6-pack in the field |
Numeric count only: 6 |
Titles do the shopper-facing half of the work here: "Gym Socks: 6 Pack" or "Canon EOS R50 + Bag + 64GB Card Bundle" sets the expectation the attributes formalise. See product titles for how to structure them.
How this works in /tools
Feed validation flags the classic patterns: pack-quantity language in a title with no multipack attribute, bundle SKUs carrying a GTIN that belongs to a single unit, non-numeric multipack values: before they reach Merchant Center. Corrections are written to the supplemental layer, never back to your store data, and identifier consistency across pack variants feeds your Feed Health Score. If pack offers are already disapproved, work through fixing disapproved products: bundle identifier fixes typically clear whole groups at once.
Frequently asked questions
What is the difference between multipack and is_bundle?
multipack is a quantity of the same product sold together, set it to the count, e.g. 6 for a 6-pack. is_bundle marks a group of different products you've combined into one offer, with one main product, set it to true. A 4-pack of the same batteries is a multipack; a torch sold with batteries included is a bundle.
Do bundles need a GTIN?
Only if the bundle itself has one. Manufacturer-created bundles often have their own GTIN on the outer packaging, submit that. A bundle you assembled yourself has no GTIN, so submit is_bundle true with brand and MPN of the main product, and never reuse the single item's GTIN.
Why was my multipack disapproved for identifiers?
Almost always because the feed carries the single unit's GTIN on the multipack offer. If the manufacturer sells that pack size with its own barcode, use that GTIN. If you created the pack yourself, set multipack to the quantity and use the single item's GTIN, the multipack attribute tells Google it's your pack, not the manufacturer's.
Should the price be the bundle price or the per-item price?
The total price a shopper pays for the whole pack or bundle, exactly as shown on the landing page. Per-unit maths belongs in unit_pricing_measure where required, not in price.