Multipack is a feed attribute, written as multipack in a spreadsheet feed or as the tag g colon multipack in an XML feed, that tells Google Shopping how many identical units are bundled together and sold as a single listing, such as a six-pack of the same socks sold under one SKU. The value is a whole number of two or greater, it's submitted only when a listing genuinely represents that kind of bundle, and it's left off entirely for single-unit products. It exists so Google can reconcile a bundled listing's price and identifiers against its catalog data for the individual unit inside the pack, rather than evaluating the pack as some unrelated product on its own.

Why Multipack Matters

Google's catalog already has GTIN-level data for a huge share of individual products, and it uses that data to sanity-check prices and flag mismatches. A six-pack listing that submits the single unit's GTIN without declaring multipack looks, to that matching logic, like the same single product suddenly priced six times higher — which is exactly the kind of anomaly that gets a listing suppressed for a price or identifier mismatch. Declaring multipack tells Google the price difference is expected and shouldn't be flagged. It also matters for keeping a catalog's structure honest: a multipack isn't a size or color option, so folding it into an item group ID as if it were just another variant misrepresents the product, even though the two mechanisms often sit right next to each other in the same feed.

How Multipack Works

The value must be an integer, two or higher — there's no attribute value for "not a multipack," the field is simply omitted for standalone products. Google recommends still submitting the GTIN of the single unit contained in the pack rather than inventing an identifier, since that's what lets its matching engine connect the multipack listing back to real catalog data for that product; if the multipack itself has its own distinct barcode, that GTIN should be used instead. Multipack should not be confused with a bundle of different products sold together, which is a separate concept entirely, since it's specifically for identical units of the same item. It's also worth pairing correctly with google product category: categories that commonly sell in bulk, like grocery, health, and household goods, are exactly where multipack mislabeling causes the most price-mismatch disapprovals, simply because bulk pricing patterns are so common there.

Example

<item>
  <g:id>SKU-30567-6PK</g:id>
  <title>Athletic Crew Socks - Black, 6-Pack</title>
  <link>https://example-shop.com/products/athletic-crew-socks-black-6pack</link>
  <g:price>21.00 USD</g:price>
  <g:availability>in stock</g:availability>
  <g:gtin>00196565998211</g:gtin>
  <g:multipack>6</g:multipack>
  <g:item_group_id>ATHLETIC-SOCKS-BLACK</g:item_group_id>
</item>

The g:gtin value here still identifies a single pair of socks; g:multipack is what tells Google this particular listing sells six of them together, so the higher price doesn't read as an error against that same GTIN.

Related Concepts

Multipack sits alongside a catalog's other structural attributes rather than replacing any of them: the item group ID still ties this six-pack to whichever other sizes or colors of the same sock line exist as separate listings, and it's still a variant of that broader product line in every sense except pack quantity. Correct google product category classification remains just as important on multipack listings as on single-unit ones, since the category still determines which other attributes Google expects to see. Treating multipack as an isolated flag rather than one more piece of a consistent product structure is the most common source of avoidable disapprovals on bundled listings.