How to submit WooCommerce variable products to Google Merchant Center

How to submit WooCommerce variable products to Google Merchant Center

Variable products are essential for WooCommerce stores that sell the same product in multiple sizes, colours, materials, patterns or other options. A T-shirt may be available in five sizes and four colours. A laptop may have different memory, storage and processor configurations. A pair of shoes may be sold in several sizes and widths.

Although these options belong to one parent product in WooCommerce, Google Merchant Center needs to understand each purchasable variation as a specific product offer. Every variation may have its own price, availability, image, SKU and landing-page selection. At the same time, related variations must be grouped correctly so Google recognises that they represent different versions of the same product.

To submit WooCommerce variable products successfully, each purchasable variation should be transmitted as an individual item with a unique product ID. Related variations should share the same item group ID, while attributes such as colour, size, material or pattern distinguish one variation from another.

The most important rule is simple:

One purchasable WooCommerce variation should be represented as one distinct Merchant Center item.

Sending only the parent product can prevent Google from receiving accurate information about the options customers can actually select. Sending every variation without grouping information can create disconnected listings that Google may not recognise as members of the same product family.

What is a WooCommerce variable product?

A variable product is a WooCommerce product with selectable options. These options are created using product attributes and variations.

For example, a merchant may create a product named “Classic Cotton T-Shirt” with the following attributes:

• Colour: Black, white and blue
• Size: Small, medium and large

This product can contain nine purchasable variations because every colour may be available in all three sizes. Each variation can have its own:

• SKU
• Regular price
• Sale price
• Stock quantity
• Stock status
• Product image
• Weight
• Dimensions
• Description
• Shipping class

The parent product organises the product page, but the individual variation represents the exact item purchased by the customer. Google needs this variation-level information whenever price, availability or another commercial attribute differs between the options.

How does Google Merchant Center understand product variants?

Google defines variants as similar products that differ through specific product details, such as colour, size, material, pattern, age group or technical configuration.

Each variation should have a unique id value. All variations belonging to the same valid product group should then use a shared item_group_id.

For example:

WooCommerce variation	Product ID	Item group ID	Colour	Size
Black, small	tshirt-101-black-s	tshirt-101	Black	S
Black, medium	tshirt-101-black-m	tshirt-101	Black	M
White, small	tshirt-101-white-s	tshirt-101	White	S
White, medium	tshirt-101-white-m	tshirt-101	White	M

The unique product ID tells Google which precise variation is being submitted. The shared item group ID tells Google that these items are variants of the same core product.

Google’s product data rules also support the variant_option attribute. This attribute can explicitly describe the properties that identify a variation. When it is used, products in the same group should provide a consistent set of option names, and each variation should have a unique combination of option values.

For example, a black medium T-shirt could contain:

• Variant option name: Colour
• Variant option value: Black
• Variant option name: Size
• Variant option value: M

The dedicated attributes, such as color and size, should also be used when those properties identify the variation. The precise attributes transmitted will depend on the integration or plugin being used.

Prepare the variable product correctly in WooCommerce

Successful submission begins with accurate WooCommerce data. An integration cannot reliably send information that is missing or incorrectly configured in the store.

Open the product in WooCommerce and confirm that its product type is set to “Variable product.” The required attributes should be added under the product data section and marked for use with variations.

Attribute names should be clear and meaningful. Use names such as:

• Colour
• Size
• Material
• Pattern
• Shoe width
• Storage capacity

Avoid unclear labels such as “Option 1,” “Type A” or “Selection.” Google and potential customers should be able to understand what each value represents.

After defining the attributes, create the individual variations and inspect them separately. Every active variation should have enough data to function as a real purchasable item.

At minimum, verify that:

• The variation is enabled.
• A valid price is assigned.
• Its stock status is accurate.
• The attribute combination is complete.
• The variation can be selected on the product page.
• Its landing page can be accessed without an error.
• The final price shown on the page matches the submitted price.

If WooCommerce displays “Any colour” or “Any size” for a variation, check whether that broad configuration can be translated correctly by your Merchant Center integration. Explicit variation combinations are generally easier to validate and submit reliably.

Give every variation a stable and unique ID

Google uses the submitted product ID to recognise an item across updates. The ID should remain stable when the product’s price, stock, title or description changes.

A suitable integration may create the product ID from a WooCommerce variation ID, SKU or another persistent internal identifier. Whichever method is used, two principles are essential:

• Every variation must have a unique ID.
• The ID of an existing variation should not change unnecessarily.

Do not use the same product ID for every variation. If all sizes and colours are submitted under one ID, later operations can overwrite previous variations instead of creating distinct items.

Repeatedly changing IDs can also cause Google to treat updated variations as new items. This may interrupt product history, delay processing and leave outdated items in Merchant Center until they expire or are removed.

SKUs are helpful for store management, but they should also be unique when used as part of the submitted identifier. Duplicate or blank variation SKUs can cause problems in integrations that depend on SKU values.

Use the correct item group ID

The item_group_id connects genuine variants of the same product. All variations in one group should share the same value.

A WooCommerce parent product ID can provide a stable source for this field. For example, variation IDs may form the unique product IDs while the parent product ID forms the shared group ID.

Do not use one universal item group ID for unrelated products. A red T-shirt and a red handbag are not variants simply because they share a colour. Products should be grouped only when they represent versions of the same core item.

Google also advises against grouping merely related products. A matching shirt and pair of trousers sold separately do not form a valid variant group. Similarly, short-sleeve and long-sleeve products may need separate groups when they are distinct product styles rather than selectable versions of one item.

The item group ID should remain stable. Changing it unnecessarily can break the relationship between existing variants.

Map variation attributes accurately

WooCommerce attributes do not automatically have the same meaning as Google product attributes. A store may use a custom attribute called “Shade,” while Google expects the colour information in color.

The integration should map WooCommerce attributes to the correct Google fields.

WooCommerce attribute	Google product attribute
Colour or shade	color
Size	size
Material	material
Pattern	pattern
Gender	gender
Age group	age_group

Values should describe the actual product and match what customers see on the landing page. If WooCommerce calls a colour “Midnight Blue,” submitting “Red” to Google creates inaccurate product data.

All products using the same item group ID should provide a consistent set of variant-defining attributes. If colour and size distinguish one T-shirt, each variation in that group should provide the relevant colour and size values.

Google may report missing or inconsistent variant attributes when one member of a group contains colour and size but another member contains only size. Consistent attribute structures make the group easier to understand.

Send the correct price for each variation

A variable product may display a price range on its main WooCommerce page, but Google needs the exact price of the submitted variation.

Suppose a product has these options:

• 64 GB: $499
• 128 GB: $549
• 256 GB: $649

Submitting $499–$649 is not appropriate as the price of an individual variation. Each Merchant Center item should contain its own exact price.

The same principle applies to sale prices. If only one colour or size is discounted, the sale price should be sent only for that affected variation. Google’s price should match the price shown after the same variation is selected on the landing page.

Taxes, currency conversion, discounts and WooCommerce pricing extensions can affect the visible value. After submission, test the actual landing page rather than checking only the WordPress administration screen.

Synchronise availability at variation level

Stock should also be evaluated separately for every variation.

A parent product may be shown as available because at least one option is in stock. This does not mean every variation is available.

Variation	WooCommerce stock	Submitted availability
Black, small	8	In stock
Black, medium	0	Out of stock
White, small	3	In stock
White, medium	0	Out of stock

If the integration sends the parent product’s general stock status to every variation, unavailable combinations may appear as available on Google. This creates a poor shopping experience and can lead to availability mismatch warnings.

WooCommerce inventory settings, backorders and stock-management extensions should be checked carefully. When backorders are enabled, the submitted availability must reflect the purchasing experience on the product page and comply with Google’s applicable availability definitions.

Use variation-specific images when available

Customers expect the product image to match the selected option. If a shopper clicks a blue variation on Google but lands on a page displaying a red product, the experience becomes confusing.

Assign a dedicated image to every important visual variation, particularly colour and pattern variations. The image should clearly show the submitted product without promotional overlays, misleading placeholders or unrelated accessories.

If size is the only difference, the same main image may be appropriate for several variations. If colour changes, variation-specific images are strongly recommended.

Also confirm that Google can crawl the image URL. Security systems, hotlink protection, temporary URLs or restrictive server rules can prevent Merchant Center from retrieving an otherwise valid WooCommerce image.

Make the landing page open the correct variation

Each submitted item should lead customers to a page where they can identify and purchase that exact variation.

WooCommerce can use variation parameters in product URLs to preselect attributes. A correctly formed landing-page URL might open the product with “Black” and “Medium” already selected.

This is especially important when:

• Prices differ between variations.
• Some variations are out of stock.
• Images change by colour.
• A product has many combinations.
• The default WooCommerce selection is not the submitted variation.

Test the URL in a private browser window. Confirm that the selected attributes, price, availability, image and currency agree with the information sent to Merchant Center.

Do not assume the URL works simply because it opens the parent product page. The page should make the advertised variation clear to the customer and Google’s automated systems.

Submit identifiers for each variation

Product identifiers may include:

• Brand
• GTIN
• MPN

When a manufacturer assigns a different GTIN to each colour or size, submit the GTIN belonging to the exact variation. Do not reuse one variation’s barcode across an entire product group unless the manufacturer has genuinely assigned the same identifier.

The brand generally remains the same across the group. An MPN may be shared or variation-specific depending on the manufacturer’s data.

For products that do not have assigned identifiers, do not invent a GTIN. The correct configuration depends on the nature of the product and Google’s identifier requirements.

Submit only real and purchasable variations

WooCommerce stores sometimes contain incomplete, disabled or placeholder variations. These should not automatically become Google products.

Before synchronisation, exclude variations that:

• Are disabled
• Have no valid price
• Cannot be purchased
• Have an incomplete attribute combination
• Lead to an invalid landing page
• Represent an internal placeholder
• Are not intended for the target country

Out-of-stock variations do not always need to be deleted. They may remain submitted with accurate availability if the integration and sales strategy support this approach. This preserves a stable product identity and allows the item to return to an available state when stock is replenished.

Common mistakes when submitting WooCommerce variations

One common mistake is submitting only the parent product. This can hide individual prices, stock levels and option-specific information.

Another is sending each variation as a completely unrelated item without an item group ID. Google may then fail to associate the variants.

Additional problems include:

• Reusing the same product ID for several variations
• Assigning different item group IDs to members of one group
• Grouping unrelated products
• Sending a parent price instead of a variation price
• Sending the parent stock status to every variation
• Omitting colour or size from part of a group
• Reusing an incorrect GTIN
• Linking every item to an unselected generic product page
• Sending disabled or incomplete combinations
• Changing product IDs during routine updates
• Keeping deleted variations active in Merchant Center
• Using inconsistent attribute names and values

These issues are easier to prevent when WooCommerce product data is cleaned before the first submission.

How to verify the results in Google Merchant Center

After synchronisation, allow Merchant Center time to process the submitted operations. Then open the Products section and inspect several variations individually.

Check:

• Product ID
• Item group ID
• Title
• Variation attributes
• Price
• Sale price
• Availability
• Image
• Landing-page URL
• Brand and product identifiers
• Target country
• Processing status

Select products from different groups and test both available and unavailable options. Do not validate only one variation from one product.

The “Needs attention” area can reveal missing attributes, inconsistent groups, invalid identifiers, landing-page problems and other product data issues. Correct the source data in WooCommerce or the integration’s attribute mapping whenever possible. Manual changes made only in Merchant Center can be overwritten by the next synchronisation.

Can Merchant API submit WooCommerce product variations?

Yes. Merchant API can transmit each WooCommerce variation as an individual product while preserving its relationship with the other variations through shared grouping data.

The effectiveness of the process depends on the integration. A suitable WooCommerce Merchant API solution should be able to:

• Detect valid product variations
• Generate stable, unique product IDs
• Assign a consistent item group ID
• Read variation-level price and availability
• Map WooCommerce attributes to Google attributes
• Send variation-specific images and links
• Update changed variations
• Remove obsolete variation records safely
• Report failed operations clearly

PW Merchant is designed to help create a manageable connection between WooCommerce product data and Google Merchant Center. The quality of the final listing still depends on the accuracy of the product information stored in WooCommerce.

Frequently asked questions

Should every WooCommerce variation have a separate Merchant Center item?

Generally, yes. If a variation represents a specific purchasable option with its own attribute combination, price, availability, identifier or image, it should be submitted as a separate item.

Should the parent variable product also be submitted?

The parent normally acts as the organisational source for the group rather than an additional purchasable variation. Submitting both the parent and all child variations can create a duplicate or incomplete item unless the integration has a specific reason and valid data model for doing so.

Do all variations use the same item group ID?

All genuine variations of the same core product should use the same item group ID. Each variation must still have its own unique product ID.

Can colour and size variations share the same image?

They can when the image accurately represents each submitted option. However, colour and pattern variations should ideally use images showing the correct visual option.

What happens when one variation is out of stock?

Its availability should be updated independently. Other variations can remain available if they still have stock.

Do variations need separate SKUs?

Unique SKUs are strongly recommended for inventory and integration reliability. They are especially important when the selected submission method uses SKU values to build product IDs.

Can a variable product have different prices in Google Merchant Center?

Yes. Each variation can carry its own price, provided that the same price is visible when customers open or select that variation on the WooCommerce landing page.

Why are my WooCommerce variations missing from Google?

Possible causes include missing prices, disabled variations, invalid attribute combinations, duplicate IDs, mapping errors, failed API operations or Merchant Center processing issues. Inspect both the WooCommerce variation data and the item status in Merchant Center.

Final checklist

Before submitting WooCommerce variable products, confirm that:

• Every active variation is purchasable.
• Every variation has a stable and unique ID.
• Related variations share a valid item group ID.
• Variation attributes are complete and consistent.
• Exact variation prices are submitted.
• Stock is evaluated at the variation level.
• Colour and size values match the landing page.
• Variation-specific images are used where appropriate.
• Landing pages identify the advertised option.
• GTIN, MPN and brand values belong to the correct item.
• Disabled or incomplete variations are excluded.
• Obsolete variations can be removed or updated safely.
• Merchant Center results are reviewed after submission.

A correctly structured variation system helps Google understand exactly what a WooCommerce store sells. It also gives customers more accurate information before they visit the store.

By treating each purchasable option as an individual item while preserving the relationship between related options, merchants can create clearer listings, reduce data inconsistencies and manage changing prices and stock more reliably.