Missing Item Group ID
item_group_id links variant products together — all sizes and colors of the same base product should share the same item_group_id. When Google sees multiple products with the same item_group_id, it groups them into a single Shopping listing with color/size swatches that shoppers can filter without leaving the search results. Without item_group_id, your 5 color × 6 size = 30 variants appear as 30 separate unrelated products, each competing with each other and confusing shoppers.
Missing value [item_group_id]Impact: Missing item_group_id is a Warning, but it has a significant impact on how your variant products display in Google Shopping. Without it, Google can't group your size/color variants together — each appears as a separate, unrelated product instead of a grouped listing with swatches. This hurts CTR and wastes impression budget on the same product across multiple unrelated listings.
Root Causes
- 1Your feed submits one row per product (not per variant) and doesn't include an item_group_id column at all — common when feed templates were built before variants were added.
- 2Your feed submits per-variant rows but doesn't include the parent product ID as the item_group_id — each variant has a unique ID but no shared group identifier.
- 3Variant products were added to your catalog without the original parent product, so there's no base product ID to use as the group identifier.
- 4A feed platform migration reset or dropped the item_group_id column during import.
- 5Your feed app is configured to include item_group_id only for products with more than one variant — products with exactly 2 variants sometimes fall through this logic.
Fix by Platform
- 1In Shopify, the parent product's ID is the correct item_group_id for all its variants. In your feed app, map item_group_id to the Shopify product ID (not variant ID).
- 2For Simprosys: go to Feed Settings → Column Mapping → item_group_id → map to 'Product ID' (not 'Variant ID').
- 3For AdNabu and DataFeedWatch: the field is usually called 'Item Group ID' or 'Parent ID' in the template. Map it to the Shopify product ID.
- 4Verify your feed app is generating one row per variant (not one per product). If it's one row per product, item_group_id is meaningless — each product has only one entry so grouping does nothing.
- 5If using Shopify's native Google & YouTube channel: this is handled automatically — the channel generates the correct item_group_id from the parent product ID.
{% comment %} item_group_id = parent product ID, not variant ID {% endcomment %}
{{ product.id }}
{% comment %} Each variant row uses the same product.id as item_group_id {% endcomment %}When This Doesn't Apply
Check your store now
Free compliance scan — 47 rules checked in minutes.
Frequently Asked Questions
What value should I use for item_group_id?+
Use the parent product's unique identifier — typically its ID in your platform (Shopify product ID, WooCommerce post ID, BigCommerce product ID). It can be any string up to 50 characters. The key requirement is that all variants of the same base product share the exact same item_group_id, and different products never share an item_group_id.
How many variants can share an item_group_id?+
There's no hard limit, but practical limits apply. If you have 6 sizes × 8 colors = 48 variants, all 48 share the same item_group_id. Google will display up to ~20 swatches in its Shopping interface before truncating. For very large variant sets (100+), consider whether all variants are genuinely the same base product or should be split into multiple product families.
My products don't have variants. Do I need item_group_id?+
No. item_group_id only applies to products that come in multiple variants (sizes, colors, materials, etc.). Single-SKU products don't need it. If your product catalog has both variant and non-variant products, only the variant products need item_group_id.
Can I use my SKU prefix as the item_group_id?+
Yes, as long as all variants of the same product share the same prefix and the prefix is consistently used. For example, if your SKUs are 'SHIRT-BLUE-S', 'SHIRT-BLUE-M', 'SHIRT-RED-S', using 'SHIRT' as the item_group_id works. The most reliable approach is using the platform's native parent product ID.