An item group ID is the feed attribute that ties multiple variants of the same base product — different sizes, colors, or configurations — together under one shared value, so a shopping platform recognizes them as options of a single product rather than as unrelated listings. Every variant keeps its own unique identifier for price, stock, and shipping purposes, but the item group ID is what lets the platform group those separate rows into one merchandised listing with a size or color selector. Without it, a shopper searching for a jacket might see the same product ten times over, once per color, instead of one listing with options.

Why Item Group ID Matters for Variant-Heavy Catalogs

Retailers selling apparel, footwear, or anything else that comes in multiple options depend on the item group ID to avoid flooding a shopping feed with duplicate-looking listings that compete against each other for the same search query. Get it wrong — inconsistent values, or the field missing on some variants but not others — and a platform may either merge products that shouldn't be merged or, more commonly, fail to group variants that should appear together, fragmenting what should be one strong listing into several weak ones. This is a common enough failure mode that entire audits are built around checking whether item group ID values line up cleanly with the sku and variant structure underneath them.

How Item Group ID Works

Every variant row in a product feed keeps its own unique id, usually matching its sku, but all variants sharing the same base product carry an identical item_group_id value. A shopping platform reads this field, clusters every row sharing that value, and renders them as one listing with a picker for the differentiating attribute — typically size or color, which the feed also has to declare via separate attributes. The item group ID itself carries no meaning beyond "these rows belong together"; it's an internal grouping key, not a customer-facing value, so retailers are free to base it on an existing product code as long as it stays consistent across every variant of that product.

Example: Item Group ID Linking Two Variants

<item>
  <g:id>SKU-71042-BLK-M</g:id>
  <title>Waxed Canvas Field Jacket - Black, M</title>
  <g:item_group_id>FIELD-JACKET-2024</g:item_group_id>
  <g:color>Black</g:color>
  <g:size>M</g:size>
  <g:price>158.00 USD</g:price>
</item>
<item>
  <g:id>SKU-71042-OLV-M</g:id>
  <title>Waxed Canvas Field Jacket - Olive, M</title>
  <g:item_group_id>FIELD-JACKET-2024</g:item_group_id>
  <g:color>Olive</g:color>
  <g:size>M</g:size>
  <g:price>158.00 USD</g:price>
</item>

Both rows share g:item_group_id, so Google or Meta will present them as one listing with a color selector, even though each carries its own unique g:id and can go out of stock independently.

Related Concepts

The item group ID only works because each row underneath it is a distinct variant with its own sku, and the whole mechanism exists to make a product feed represent real merchandising structure instead of a flat list of disconnected SKUs. For a deeper walkthrough of setting this up correctly across a full catalog, see The Complete Guide to Product Variant Feeds.