Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Google Ads & PPC › Shopping & Performance Max

Setting Up Product Variants for Shopping

How to submit colour, size and other variants in a Merchant Center feed: an id per variant, a shared item group, variant attributes, titles, links and checks.
Tutorialintermediate9 min readUpdated

Why variants need their own setup

A shopper searching for a navy wool jumper in a medium wants to see a navy jumper, at the price of the medium, in stock, and to land on a page where it is selected. The feed can only deliver that if each variant is described as itself. Google's product data specification provides the pieces: a unique id per item, an item_group_id shared by the variants of one product, and variant attributes such as color, size, material and pattern, with gender and age_group for apparel. The product feeds guide summarises them in its attribute table and notes that requirements differ by country and category, so the current specification is the reference for the markets a feed serves. Because a product campaign has no keywords, the Shopping and Performance Max hub explains, the feed does the matching, and variant data is part of what it matches on.

The common failures are predictable. A store exports one row per product and ignores sizes, so the price or stock shown is wrong for most shoppers. Or it exports every variant without a group id and with identical titles, so the catalogue looks like dozens of unrelated, near-duplicate products. Or every variant links to the default colour, so the page disagrees with the ad. Each failure costs relevance, clicks or approval, and each is fixed by the same sequence.

AttributeRole for variantsRule of thumb
idIdentifies each variant as its own itemUnique and stable; never reused or regenerated
item_group_idTies the variants of one product togetherSame value on every variant of the product, different from any item's id
color, size, material, patternSay how variants differFill the ones that vary, with the same wording across the group
gender, age_groupDescribe who apparel is forRequired for apparel in some countries; check the specification
titleMatching and display textIncludes the variant value, using the attribute's own wording
linkLanding pageOpens the page with that variant shown or selected
price, availabilityThe offer for that variantMatches the page for that variant
image_linkThe variant's main imageShows that variant, not the default
gtinThe variant's own product codeEach variant has its own; never one code across sizes

Before you start

  • The product catalogue export with every variant as a row, including the fields the store uses for colour, size and any other option.
  • Access to Merchant Center for the feed and its diagnostics, and to whoever maintains the store's export or feed app.
  • A sample of product pages showing how the site selects a variant: by URL, by parameter or by script.
  • The current product data specification for each country the feed serves, open alongside the work, because apparel and some other categories carry country-specific requirements.
  • Barcodes for each variant, where the products have them; the missing identifiers diagnosis covers what to do when they are absent or reused.
  • The campaigns' listing or product groups, so you know which attributes they subdivide on before ids or labels change.
  • A feed that has passed the Merchant Center feed setup checklist, so account, shipping and required-attribute problems are not mistaken for variant problems.

The steps

  1. List each product's variant dimensions

    For each product, write down the dimensions on which its variants differ: colour, size, material, pattern, or a combination. Use the store's real options, not every attribute the specification offers. A jumper offered in several colours and sizes has two dimensions and one variant for every combination of them; a mug offered only in colours has one dimension. Note which dimensions people search on, because those belong in titles later, and which are filters only. This list is the plan the export will be checked against.

  2. Give every variant its own id

    Assign each variant a unique id that will not change. A pattern built from the parent code and the variant values, such as the product code followed by colour and size codes, is easy to read and to regenerate the same way. Never reuse an id for a different variant, and never let the platform regenerate ids on export, because the feed guide notes that changing an id resets the item's history. If the store already exports stable variant SKUs, use them. Where products carry barcodes, each variant has its own; a code repeated across sizes is flagged as invalid, as the missing identifiers diagnosis explains.

  3. Set a shared item group id

    Give every variant of one product the same item_group_id, usually the parent product's code. This is what tells Merchant Center that the navy medium and the grey large are the same product in different versions. The group id should be stable too, and it should differ from any variant's own id. Products with no variants do not need one. Check that two different products never share a group id, which happens when an export uses a category code instead of the parent code.

  4. Fill the variant attributes

    Fill the attributes listed in step one on every variant in the group: color for colour, size for size, and so on, with the same wording throughout. "Navy" on one variant and "Dark blue" on its sibling makes the group look inconsistent and confuses filters. For apparel, add gender and age_group where the specification requires them for the target country, and use the size wording shoppers expect in that market. Leave attributes that do not vary filled the same way across the group rather than blank on some rows.

  5. Write titles that carry the variant

    Add the distinguishing value to each title, using the attribute's own wording, as the feed guide recommends: if the colour attribute says "navy", the title says "navy". Follow the category pattern the feed guide sets out, usually brand, product type, the defining attribute, then colour and size for apparel, so that the words people search for come first and the variant value is still visible. Keep promotional text out of titles. A supplemental feed keyed on id can override titles without changing the store's own product names.

  6. Link each variant to a page showing it

    Set each variant's link to a URL that opens the product page with that variant shown or selected, typically the parent page with a parameter the platform supports. The test is simple: open the link and check that the colour, size, price, stock status and main image are the variant's, without clicking anything. If the platform can only open the default variant, fix that before going further, because the page is what Merchant Center compares the feed against. Where links carry tracking parameters, the optional canonical_link attribute holds the clean URL. Whether variants also get their own indexable pages is a separate organic decision; the product structured data tutorial keeps the page's markup describing the variant the URL shows.

  7. Match price and availability per variant

    Give each variant its own price and availability, taken from the same source the page uses. Sizes often differ in stock and sometimes in price, and the feed guide is explicit that price and availability must match the landing page; a mismatch leads to disapproval. Sale prices go in sale_price with effective dates on the variants actually on sale, not into price. If the platform exports stock per product rather than per variant, fix the export: one sold-out size reported as available is a mismatch waiting to happen.

  8. Assign an image to each variant

    Set image_link on each variant to an image of that variant: the navy jumper shows navy, the grey shows grey. Sizes of the same colour can share an image. An image of the default colour on every variant tells the shopper the wrong thing and undoes the work of the attributes and titles. Keep images to the specification's requirements on quality, overlays and watermarks, which the feed guide summarises.

  9. Check diagnostics after the next fetch

    After the next fetch, open Merchant Center diagnostics and filter to the products you changed. Look for item issues naming variant attributes, item groups, price or availability mismatches and identifiers; the feed guide lists incomplete variant data among the issues that limit items. Spot-check a few variants of each product: the item details should show the group id, the attributes and a link that opens the right variant. The Merchant Center help centre explains each issue message. If an item still shows old values, the shopping products not showing diagnosis separates feed, listing group and auction causes.

  10. Decide how campaigns group variants

    Finally, decide whether campaigns treat a product's variants as one unit or bid on them separately. Listing groups and product groups subdivide on feed attributes, including item ID, as the Performance Max structure guide lists. Check whether the subdivision options in your account include the item group; where they do not, a custom label carrying the parent code groups a product's variants just as well. Bid on individual variants only where one colour or size behaves very differently from its siblings, and remember that new ids land in the everything-else group until a listing group includes them.

The order matters because each step depends on the one before. Titles carry the attribute wording from step four, links are checked against the price and image set in steps seven and eight, and the campaign grouping in the last step relies on ids and group ids that no longer change.

A knitwear range set up as variants (illustrative)

Illustrative example — not a real result

Ravelthorn Knitwear rebuilds its jumper variants

Ravelthorn Knitwear, an invented knitwear brand, sells 24 jumpers, each in three or four colours and five sizes, about 420 variants in all. Its platform exported every variant with the parent's title, no item group id, the default colour's image and a link to the parent page. Shopping search terms showed several near-identical cards for the same jumper in one results page, 61 items disapproved for price or availability mismatch, and colour searches such as "navy cable knit jumper" matching grey items.

The rebuilt feed for one jumper looks like this (four of its variants shown):

iditem_group_idtitlecolorsizelink opens
RK-CBL-NVY-SRK-CBLRavelthorn Cable-Knit Wool Jumper – Women's – Navy – SNavySCable-knit jumper, navy, size S selected
RK-CBL-NVY-MRK-CBLRavelthorn Cable-Knit Wool Jumper – Women's – Navy – MNavyMCable-knit jumper, navy, size M selected
RK-CBL-GRY-MRK-CBLRavelthorn Cable-Knit Wool Jumper – Women's – Grey – MGreyMCable-knit jumper, grey, size M selected
RK-CBL-OAT-LRK-CBLRavelthorn Cable-Knit Wool Jumper – Women's – Oatmeal – LOatmealLCable-knit jumper, oatmeal, size L selected

Each variant also carries gender and age_group, its own price and stock, an image of its colour and its own barcode. After the next fetch, the mismatch issues fall from 61 items to 3, all sizes the warehouse had sold out during the fetch. Over the following four weeks the duplicate cards disappear from the search terms checks, colour searches match the right colour, and the jumpers' click-through rate rises from 0.8% to 1.2% in the Standard Shopping campaign, whose product groups now subdivide on a custom label carrying the parent code.

Common mistakes

  • One row per product. Sizes and colours disappear, and the price or stock shown is wrong for most shoppers.
  • Variants without a shared item group id. The feed guide's warning: they compete with themselves as unrelated products.
  • Ids regenerated on every export. Each variant's history resets, and campaign groups built on ids break.
  • Inconsistent attribute wording. "Navy" beside "Dark blue" in one group confuses matching and filters.
  • Titles identical across variants. The shopper cannot see which version the ad shows.
  • Every variant linking to the default colour. The page disagrees with the ad, and mismatches follow.
  • Stock exported per product, not per variant. A sold-out size reported as available.
  • One barcode across all sizes. Flagged as invalid, and the catalogue match is lost.

Frequently asked questions

Do variants that share one product page still need their own id?

Yes. In the product data specification every variant is its own item, so a jumper in three colours and four sizes is a set of separate items, each with a unique id that stays the same over time. The product feeds guide notes that changing an id resets the item's history. What ties the variants together is the item group id they share, not a shared id, and the variant attributes say how each one differs.

Which variant attributes are required?

The specification is the reference, and requirements differ by country and category. The product feeds guide summarises them: colour, size, material and pattern are required for apparel in some countries, as are gender and age group, and the item group id is required for variants. Outside those cases, fill the attributes that actually distinguish the variants, consistently across the group, because they are used for matching and for the filters shoppers apply.

Should each variant link to a different URL?

Each variant's link should open a page that shows that variant, so the price, availability and image the shopper lands on match the item they clicked. A URL that opens the shared product page with the variant already selected does that. Whether variants also deserve their own indexable pages is an organic search decision, which the category and product pages guide covers; the feed only needs each link to land on the right variant.

Terms used on this page

Also related

Sources

  1. Product data specification — Google Merchant Center Help
  2. Google Merchant Center Help — Google

Related