How to Send Configurable Products to Google Shopping from Magento 2

Send every child product of a configurable product to Google Shopping as its own item, and group the children with item_group_id. Do not send the configurable parent itself. Google's variant rules say exactly this: use the parent SKU as the item group ID for all variants, and don't submit the parent SKU as a separate product (Google Merchant Center Help). Each child then carries its own price, stock status, image and landing URL, which is what Merchant Center checks.

Why the configurable parent alone fails

A configurable product in Magento has no price or stock of its own. Its price is the lowest price among its in-stock children, and it shows as in stock while at least one child can be bought. If the feed sends only the parent, a shopper who clicks a "$29 in stock" ad can land on a size that costs $35 or is sold out. Merchant Center compares the feed with the landing page, and that mismatch is what gets items disapproved.

Google requires item_group_id for variants in free listings, and in Shopping ads that target Brazil, France, Germany, Japan, the United Kingdom or the United States.

What to take from the child and what from the parent

Google attribute Take it from Why
id child each variant is a separate item
item_group_id parent (SKU or ID) the same value groups all variants of one product
title child, or parent name plus the variant option Google shows it per variant
price child, guest price the price a shopper who is not logged in pays
availability child, salable status a size can sell out while the product stays in stock
color, size, material, pattern child these are the attributes that make variants differ
gtin, mpn child identifiers belong to the physical item
image_link child, fall back to parent the image should show the chosen color
link parent URL that opens this variant Google asks for a different landing URL per variant
product_type parent's category children are usually not assigned to categories

Children of a configurable product are usually set to Not Visible Individually, so they have no page of their own. That is why the link points to the parent page, with the variant's options in the URL so each variant gets a distinct address. After you generate the feed, open a few of those links and check that the page shows the same color and size as the feed row: Google asks that the product details on the landing page match the variant you submit.

Five feed mistakes that break variants

Each of these shows up in our support tickets about product feeds, and each is now handled or documented in Mirasvit Advanced Product Feeds.

  1. Filtering by visibility drops the children. A filter such as Visibility is Catalog, Search keeps the parent and removes every child, because children are Not Visible Individually. The feed then has no variants at all.
  2. A child belongs to two parents. A simple product can be a variant of a configurable product and also a member of a grouped or bundle product. If the feed picks the wrong parent, variants of one product are split across several item groups or mixed with unrelated products. The parent used for item_group_id has to be the configurable one.
  3. Every variant sold out, price becomes 0. Magento prices a configurable product from its in-stock children only, so when the last size sells out, the computed price drops to 0. Merchant Center suspends items with a zero price, and other tools that read the feed can treat the product as free. The feed should keep the real price and send out of stock.
  4. The source says "in stock", the quantity is 0. With Multi-Source Inventory, a source can be flagged In Stock while its quantity is 0 and backorders are off. Exporting the source flag sends unsellable variants to Google. Use Magento's salable check for the feed's website instead.
  5. The feed exports a customer group price. If the feed is generated while a customer is logged in, or the price comes from the wrong context, tier prices or catalog rule prices for one group can leak into a public feed. Shopping channels must get the guest (NOT LOGGED IN) price.

How to set it up with Mirasvit Advanced Product Feeds

Advanced Product Feeds ships a Google Shopping (configurable products) template that already follows the child-and-group pattern:

  • one item per child, g:id from the child and g:item_group_id from the parent's ID;
  • g:price from the final guest price, and g:availability from the salable stock status;
  • g:product_type from the parent's category path, and color, size, GTIN and MPN from the child.

Two settings to check before you submit the feed:

  1. Link. The template links every variant to the parent page with {{ product.parent.url }}. To give each variant its own landing URL, replace it with {{ product.url_with_options }}, which adds the variant's option values to the parent URL. Then open a few links and confirm that your theme shows the selected variant.
  2. Filter. Do not filter by visibility, or the children disappear (mistake 1). To keep only products that can be bought, use the Is Salable condition.

Versions 1.15.14 to 1.17.5 fixed the price of sold-out configurable products, the MSI stock status, the guest price and the parent choice for children that also belong to a grouped or bundle product. If your feed shows any of the five mistakes above, update the extension first. The full list of attributes, including product.parent.* values, is in the attribute reference.

Checklist before you submit

  • Each child is a separate item, and the parent is not in the feed.
  • All children of one product share the same item_group_id.
  • Price and availability come from the child, not from the parent.
  • Each variant has its own landing URL, and that page shows the same variant.
  • Color and size are filled on every child that differs by them.
  • No visibility filter removes Not Visible Individually products.
Loading...