How to fix item group ID and variant attribute errors in Google Merchant Center
How to fix item group ID and variant attribute errors in Google Merchant Center
A variable product can work correctly in WooCommerce and still be grouped incorrectly in Google Merchant Center.
Customers may be able to choose a colour and size on the product page, while Google sees several unrelated products. The opposite can also happen: completely different products may be placed in the same variant group because they were submitted with one shared item group ID.
Other products may receive errors because one variation includes a colour, another includes only a size and a third contains neither. Two WooCommerce variations may even become indistinguishable when their identifying attributes are lost during product synchronisation.
These problems can result in:
Missing attribute value for grouped variants
Duplicate variant
Too many variant values
Incorrectly grouped products
Missing item group ID
Inconsistent variant attributes
Incorrect colour, size, material or pattern
Products displayed as separate offers instead of one family
Unavailable or inaccurate variation landing pages
Product limitations or disapprovals
Fixing these errors requires a complete comparison between the WooCommerce parent product, its individual variations, the submitted Merchant API data, the public landing-page behaviour and the final processed products in Merchant Center.
The objective is straightforward:
Every purchasable variation should have its own stable product ID, all genuine variations of the same parent should share one stable item group ID, and each variation should contain the attributes that distinguish it from the other products in that group.
The short answer
To fix Google Merchant Center item group ID and variant attribute errors:
Identify the exact affected offer IDs.
Find the corresponding WooCommerce parent product and variations.
Confirm that the products are genuine variations of one parent product.
Give every submitted variation its own stable product ID.
Use one shared item group ID for all variations of the same parent.
Do not use the item group ID as the individual product ID.
Do not reuse one item group ID across unrelated products.
Keep the item group ID stable during later updates.
Submit each purchasable variation as a separate product.
Use the same set of identifying attributes across the group.
Give every variation a unique combination of attribute values.
Map WooCommerce colour, size, pattern and material attributes correctly.
Include applicable apparel attributes such as age group and gender.
Review item_group_title and variant_option where supported.
Confirm that each variation URL opens or preselects the correct option.
Match each variation’s title, price, availability and image to the landing page.
Remove accidental duplicate offers.
Review structured product variant data.
Eliminate competing data sources that overwrite corrected values.
Resynchronise the affected variation group.
Inspect the processed products after Google evaluates the update.
Check that a later scheduled operation does not restore the error.
Changing only one product inside Merchant Center may not provide a permanent correction. If WooCommerce or another active product source remains authoritative, its next operation can overwrite the manual edit.
What is an item group ID?
The item group ID identifies a family of product variants.
Suppose a WooCommerce T-shirt is available in:
Red, small
Red, medium
Blue, small
Blue, medium
These are four separate purchasable offers, but they belong to one parent product.
A correct conceptual structure could be:
Parent product: Classic T-shirt
Shared item group ID: TSHIRT-100
Red small product ID: TSHIRT-100-RED-S
Red medium product ID: TSHIRT-100-RED-M
Blue small product ID: TSHIRT-100-BLUE-S
Blue medium product ID: TSHIRT-100-BLUE-M
Every individual product ID is unique. The item group ID is identical because all four offers are variations of the same product.
Google’s current item group ID specification explains that the attribute is used to group products that differ by characteristics such as colour, size, material, pattern or a technical configuration.
Google currently defines the item group ID as a single value with a limit of 1–50 characters. It recommends using alphanumeric characters, underscores or dashes and advises merchants to keep the value stable.
The item group ID does not replace the individual product ID.
Product ID and item group ID are different
The individual product ID answers:
Which exact purchasable offer is this?
The item group ID answers:
Which parent product family does this offer belong to?
For example:
Product ID: SHOE-BLACK-42
Item group ID: SHOE-2026
Another variation could use:
Product ID: SHOE-WHITE-42
Item group ID: SHOE-2026
The product IDs differ because the two shoes are different purchasable variations. Their item group IDs match because they belong to the same model.
Do not submit this:
Product ID: SHOE-2026
Item group ID: SHOE-2026
for every variation.
That would make several distinct variations use the same individual identity. Google could interpret them as repeated updates to one offer or as conflicting duplicate products.
Do not reverse the fields either:
Product ID: Parent SKU
Item group ID: Variation SKU
That separates the variants instead of grouping them.
When should an item group ID be used?
Use an item group ID when several submitted products are true variants of one product.
Common examples include:
One T-shirt in different colours and sizes
One shoe model in different colours, sizes and widths
One sofa in different materials or colours
One phone in different colours and storage capacities
One laptop in different memory and processor configurations
One cosmetic product in different shades
One bag in different materials and sizes
The products should represent the same basic design or model and differ through specific variant-defining characteristics.
Do not use an item group ID merely because products:
Belong to the same category
Have the same brand
Look similar
Appear in the same WooCommerce collection
Share a promotional campaign
Have the same price
Are frequently purchased together
Are accessories for one another
Form a multipack or bundle
Use the same supplier
Were imported in the same operation
A black T-shirt and a black jacket are not variants simply because they share a colour and brand.
A phone and its protective case are not variants.
A dining table and four matching chairs are not variants.
A product bundle is not automatically a variation of each product inside it.
If a product has no genuine purchasable variations, it generally should not receive an item group ID.
How WooCommerce variable products are structured
WooCommerce uses a parent-and-child structure for variable products.
The parent product can contain:
Product title
Main description
Shared categories
Shared attributes
Main image
Parent SKU
Default selections
General product information
Individual variations can contain:
Variation ID
Variation SKU
Attribute combination
Regular price
Sale price
Stock status
Stock quantity
Variation image
Weight
Dimensions
Shipping class
Download or virtual settings
Tax class
WooCommerce’s official variable product documentation confirms that variations can have their own price, inventory, image and other product information.
This structure must be translated into Google product offers accurately.
The WooCommerce parent can provide the shared group identity. Each purchasable child variation should provide its own offer identity and commercial details.
A typical mapping could be:
WooCommerce parent ID or stable parent SKU → Item group ID
WooCommerce variation ID or variation SKU → Individual product ID
Parent title → Item group title
Variation attributes → Colour, size, material, pattern or other variant options
Variation price → Product price
Variation stock → Availability
Variation image → Image link
Variation-specific URL → Product link
The exact mapping depends on the integration and store configuration, but the identity relationship should remain stable.
What are variant attributes?
Variant attributes describe how one product in a group differs from another.
Common standard attributes include:
color
size
material
pattern
age_group
gender
Other products may vary through technical or commercial properties such as:
Memory capacity
Screen size
Processor
Graphics configuration
Shoe width
Finish
Flavour
Pack size
Google’s current product-data specification also documents item_group_title and variant_option for describing product groups and their variant-identifying properties. Review the current Google product data specification before implementing or changing these fields.
The item group ID establishes the relationship. The variant attributes explain the difference.
An item group containing five products but no meaningful variant differences does not provide Google with enough information to understand why the five offers exist.
Item group title and variant option
Google currently documents two related attributes:
item_group_title
variant_option
The item group title provides a shared name for the product group.
For example:
Item group ID: LAPTOP-500
Item group title: Performance Laptop 15
Variant option: memory:16 GB,color:black
Another variation could use:
Item group ID: LAPTOP-500
Item group title: Performance Laptop 15
Variant option: memory:32 GB,color:black
The group title should remain the same across the related variations. The variant option should describe the properties that distinguish each offer.
Google’s variant option documentation states that products sharing an item group ID should use the same set of variant-option names. Their values then distinguish the individual products.
If the first variation uses:
color:blue
size:medium
other members of that group should not arbitrarily switch to:
colour:blue
dimension:medium
The names should be consistent.
Standard variant attributes should still be supplied when applicable. A value inside variant_option does not mean an applicable colour, size, material or pattern field can always be omitted.
A correct variant group example
Consider a WooCommerce shoe with two colours and two sizes.
Variation one:
Product ID: RUN-RED-41
Item group ID: RUN-100
Item group title: Run 100 Shoe
Colour: Red
Size: 41
Variant option: color:red,size:41
Price: 100.00 EUR
Availability: in_stock
URL: Red, size 41 preselected
Variation two:
Product ID: RUN-RED-42
Item group ID: RUN-100
Item group title: Run 100 Shoe
Colour: Red
Size: 42
Variant option: color:red,size:42
Price: 100.00 EUR
Availability: out_of_stock
URL: Red, size 42 preselected
Variation three:
Product ID: RUN-BLUE-41
Item group ID: RUN-100
Item group title: Run 100 Shoe
Colour: Blue
Size: 41
Variant option: color:blue,size:41
Price: 105.00 EUR
Availability: in_stock
URL: Blue, size 41 preselected
Variation four:
Product ID: RUN-BLUE-42
Item group ID: RUN-100
Item group title: Run 100 Shoe
Colour: Blue
Size: 42
Variant option: color:blue,size:42
Price: 105.00 EUR
Availability: in_stock
URL: Blue, size 42 preselected
The prices do not have to be identical. The stock status can differ. The images can differ. What matters is that every submitted offer accurately describes its exact variation and uses the shared group identity correctly.
Common item group ID errors
The item group ID is missing
If WooCommerce variations are submitted as individual products without an item group ID, Google may not understand that they belong to one product family.
Possible causes include:
The integration submits variations but ignores their parent relationship.
The parent product ID is unavailable during processing.
A product import separated variations from the parent.
A custom product type is not recognised as variable.
Another data source removed the group field.
The parent product was deleted and recreated.
Variation records contain damaged parent references.
A mapping rule applies only to certain categories.
Confirm that each submitted child variation can be traced to one active WooCommerce parent product.
Unrelated products share one item group ID
This error creates an oversized or illogical product group.
Examples include:
Every T-shirt in the store uses TSHIRT.
Every product from one brand uses the brand name as its group ID.
All imported products use the supplier ID.
Every variation in the catalogue receives 1.
One category slug is used as the group ID.
A missing parent value is replaced with the same fallback value.
The item group ID must identify one specific variant family, not a brand, product category or catalogue.
Google also warns that casing alone does not make group identifiers unique. Values such as abc123 and ABC123 should not be treated as separate groups.
Every variation has a different item group ID
If each variation receives its own group value, the relationship is lost.
Incorrect:
Red small → TSHIRT-RED-S
Red medium → TSHIRT-RED-M
Blue small → TSHIRT-BLUE-S
Those values are suitable candidates for individual product IDs, not the shared group ID.
Correct:
Every variation → TSHIRT-100
The item group ID changes during every update
A generated timestamp, random token or changing database value should not be used as the group ID.
Changing it can:
Break variant grouping
Create apparently new product families
Separate current products from historical data
Make diagnostics difficult to follow
Cause old and new groups to coexist temporarily
Complicate Merchant Center reporting
Choose a stable source, such as a persistent parent SKU or parent product ID, and keep it unchanged.
One item group ID is recycled for a different product
A discontinued product’s group ID should not be reassigned to an unrelated new product.
For example, if MODEL-100 represented a shoe family, do not later use MODEL-100 for a bag.
Stable identifiers should preserve the same commercial identity over time.
The parent product is submitted as another offer
A common integration error is submitting:
The variable parent
Every child variation
The parent may contain a price range, lowest price, shared image or no exact stock status. It is usually not the distinct selected variation that the customer purchases.
This can create:
One apparent duplicate
An extra product with no unique attributes
A price that matches only the cheapest variation
A generic image instead of the selected variation image
An incomplete product URL
Incorrect stock information
When child variations are submitted individually, do not automatically submit the non-purchasable parent as another member of the group.
The item group ID is used on simple products
A catalogue-wide rule may assign an item group ID to every product, including simple products with no variants.
This can place unrelated simple products into groups or create unnecessary group metadata.
Apply the group field only when the product is part of a genuine variation family.
Common variant attribute errors
Missing attribute value for grouped variants
Google reports this issue when members of the same group do not consistently include the attributes that distinguish the products.
For example:
Red small → Colour and size included
Red medium → Colour and size included
Blue small → Colour included, size missing
Blue medium → Size included, colour missing
Google’s missing attribute value guidance says that products sharing an item group ID should provide a consistent set of variant attributes or should not be grouped through that ID.
To correct the problem:
Identify every product sharing the affected item group ID.
Determine the attributes that define the group.
Supply the same attribute structure for every variation.
Give every variation its actual values.
Remove incomplete or accidental variations.
Resynchronise the complete group.
Duplicate variant
A duplicate variant occurs when two or more products in one group cannot be distinguished through their submitted variant values.
For example:
Product A: Black, medium
Product B: Black, medium
If both have the same group ID and no other distinguishing property, Google may see two copies of the same variant.
Google’s duplicate variant guidance recommends submitting unique variant values, removing duplicate offers or removing the item group ID when the products are not true variants.
In WooCommerce, duplicate combinations can be caused by:
Duplicate variation records
An old disabled variation still being exported
Custom attributes failing to map
Two attribute labels becoming the same normalised value
Supplier imports creating repeated children
Variation IDs being copied incorrectly
Attribute values being omitted from the submitted data
A parent product being submitted alongside a child
Two product sources submitting the same variation
Compare WooCommerce variation IDs, SKUs and attributes before deleting anything. The offers may look identical in Merchant Center because one distinguishing attribute failed to reach Google.
Too many variant values
A single product variation should not receive multiple conflicting values for an attribute that expects one variation-specific value.
For example, one submitted shoe variation should not be described as:
Size: 40, 41, 42
That represents several purchasable options, not the exact selected offer.
Google’s too many variant values guidance explains that each combination of variant values should occur only once within its item group.
Submit separate offers:
Shoe, size 40
Shoe, size 41
Shoe, size 42
A multicoloured product is different from several colour variants. A shoe intentionally designed with red, green and black components can use an allowed multi-colour format, while three separate red, green and black variations should be submitted individually.
Review Google’s current colour specification before formatting multi-colour products.
Different attributes are used across the group
Suppose one variation uses:
Colour
Size
Another uses:
Colour
Material
A third uses:
Size
Material
Google cannot determine one consistent basis for the variation family.
Choose the complete set that genuinely differentiates the group and use it consistently.
If the product varies by colour, size and material, each submitted variation should be evaluated for all three attributes.
A custom WooCommerce attribute is not mapped
WooCommerce stores may use labels such as:
Colour
Color
Renk
Shade
Finish
Fabric
Memory
Capacity
The commercial meaning may be clear to the merchant, but an integration still needs to map the attribute to the applicable Google field or variant option.
A colour stored as pa_renk does not automatically become Google’s color attribute unless the integration recognises or maps it.
Review:
Attribute name
Attribute slug
Global or product-specific status
Variation checkbox
Visible-on-product-page setting
Term values
Translation behaviour
Import mapping
Merchant attribute mapping
Do not rename production attributes across the entire store without first evaluating their effect on product variations, URLs, filters and historical data.
An “Any” attribute creates an incomplete variation
WooCommerce can allow a variation to match any term of an attribute.
For example:
Size: Medium
Colour: Any colour
This can be convenient inside the store, but it may not represent one exact Google offer if the colour changes the purchasable item.
Determine whether:
The “Any” value represents identical stock, price and imagery.
The customer receives a specific selectable product.
The integration expands the wildcard correctly.
Separate colour offers are required.
The landing page clearly communicates the exact selection.
Do not submit an unspecified value as if it were a precise variant.
Attribute values change between languages
A multilingual WooCommerce store may contain:
Black
Schwarz
Siyah
Noir
These can represent the same colour but should not accidentally create four commercial variants if they are language versions of one offer.
Review whether translation plugins:
Duplicate variation records
Translate attribute labels only
Translate term slugs
Change product IDs
Change item group IDs
Create language-specific product URLs
Submit multiple language sources
Language-specific product data may be appropriate, but product identity and variant grouping must remain intentional.
The variation SKU is missing or duplicated
Google product IDs can be based on stable variation IDs even when a SKU is unavailable, but missing or duplicate WooCommerce SKUs make diagnosis more difficult.
A duplicated SKU can also cause another integration or ERP system to treat two variations as the same product.
For each variation, confirm:
Variation ID
SKU
Parent ID
Attribute combination
Product URL
Stock record
Submitted product ID
Do not generate new SKUs solely to hide an item group error. First determine the source of the identity conflict.
The variation title does not identify the offer
A generic title such as Classic T-shirt may be used for every variation.
Although dedicated attributes carry structured information, a clear title can help customers and systems understand the exact offer.
A variation title could include relevant distinguishing information naturally:
Classic T-shirt – Red – Medium
Classic T-shirt – Blue – Large
Avoid keyword stuffing or adding every internal WooCommerce value to the title.
The variation image is wrong
A red variation that displays the blue product image creates an inconsistent offer even if its item group ID and colour field are correct.
Check:
Variation image
Parent fallback image
Main image link
Additional images
Selected swatch
Mobile image
Cached image
Image URL accessibility
The submitted image should accurately represent the variation whenever the difference is visually significant.
The price belongs to another variation
A parent product may display a price range or lowest available price.
If every variation receives the lowest parent price, Google can process the variants but later detect landing-page price mismatches.
Every offer should use its own:
Regular price
Active sale price
Currency
Availability
Stock state
Do not infer one price for an entire group unless that price genuinely applies to every variation.
How to diagnose item group and variant errors
1. Record the exact Merchant Center issue
Open the affected product in Merchant Center and record:
Issue name
Offer ID
Product title
Item group ID
Product source
Feed label
Language
Target country
Destination
Detection time
Processing status
Submitted variant attributes
Landing-page URL
Do not begin with a catalogue-wide edit. First establish the exact error and affected group.
2. List every offer sharing the item group ID
The problem may not be located in the product that first displays the warning.
Create one row for every offer sharing the group ID and include:
Product ID
Item group ID
Title
Colour
Size
Material
Pattern
Age group
Gender
Variant options
Price
Availability
Image
Link
This group-level view usually reveals missing, repeated or conflicting combinations.
3. Match offers to WooCommerce records
For every submitted product, find:
Parent product ID
Parent SKU
Variation ID
Variation SKU
Attribute combination
Product status
Variation status
Stock status
Product URL
Do not rely on titles alone. Several variations can share an almost identical title.
4. Confirm that the products are genuine variants
Ask:
Do they share one parent product?
Are they the same model or design?
Do they differ only through defined variant properties?
Can customers select between them on the landing page?
Would customers reasonably understand them as versions of one product?
If the answer is no, remove the shared group relationship.
5. Identify the authoritative data source
Determine whether the group is controlled through:
PW Merchant API
Another Merchant API connection
An XML source
A CSV upload
Google Sheets
An automated website source
A supplier system
An ERP
A supplemental source
Manual Merchant Center editing
Another WooCommerce Google integration
A correct WooCommerce mapping can still be overwritten by another source.
6. Verify the individual product IDs
Every submitted variation should have its own stable ID.
Check for:
Duplicate IDs
Empty IDs
Parent IDs used for every child
Random IDs that change
IDs truncated by an import
IDs altered by language
IDs altered by currency
Recycled IDs
Case-only differences
The product ID should remain stable when the same offer is updated.
7. Verify the shared item group ID
All genuine variations of the same parent should use one stable group ID.
Check for:
Missing group values
Different group IDs within one family
Category-wide group values
Brand-wide group values
Fallback values such as 0 or unknown
Changing timestamps
Variation SKUs incorrectly used as group IDs
One group ID reused for unrelated products
Google recommends using a parent SKU where possible. A persistent WooCommerce parent ID can also provide stable group identity when no suitable parent SKU exists.
8. Compare the attribute set
Determine which attributes define the variation family.
For example:
Colour and size
Material and colour
Storage and colour
Size and width
Finish
Flavour and pack size
Then confirm that every variation uses the same defining structure.
9. Check that every combination is unique
Within one group, each submitted combination should represent one exact offer.
A table might reveal:
Black / Small
Black / Medium
Black / Medium
Blue / Small
The second Black / Medium record is duplicated unless another meaningful variant property distinguishes it.
10. Inspect the exact landing page
Open every affected link while logged out.
Confirm that:
The page loads without an account.
The correct variation is preselected or readily selectable.
The submitted colour is visible.
The submitted size is available.
The price matches.
The currency matches.
The stock status matches.
The variation image matches.
The add-to-cart action purchases the intended variation.
The URL does not silently return to the default variation.
Google recommends distinct variation URLs using path segments or query parameters when appropriate. The URL should allow Google and customers to reach the submitted offer.
11. Test cart and checkout identity
Add the exact variation to the cart.
Verify:
Variation name
Selected attributes
SKU
Price
Currency
Quantity
Stock status
Image
Checkout line item
If selecting a red medium shirt places a blue large shirt in the cart, the problem extends beyond Merchant Center.
The visible page and Merchant data may be correct while an SEO plugin, theme or schema plugin generates conflicting variant markup.
Do not assume that Merchant Center’s item group ID and schema markup are interchangeable in implementation. They should describe the same commercial relationships using the requirements of their respective systems.
13. Review cached variation data
Clear and test:
WordPress page cache
WooCommerce transients
Object cache
Server cache
CDN cache
Browser cache
Structured-data cache
Variation lookup tables where relevant
A variation can be corrected in WooCommerce while an old cached response continues to show the previous attributes or default selection.
14. Correct the source of truth
Possible corrections include:
Restoring the correct parent-child relationship
Assigning unique variation identities
Selecting one stable parent group ID
Mapping WooCommerce attributes correctly
Completing missing variation values
Removing duplicate variations
Removing the non-purchasable parent offer
Fixing variation URLs
Fixing variation images
Correcting prices or availability
Removing item group IDs from non-variants
Disabling a duplicate product source
Correcting structured data
Repairing import or ERP rules
15. Resynchronise and verify
Send the corrected group through the authoritative integration.
Then inspect:
Operation result
Submitted product input
Processed product
Product ID
Item group ID
Item group title
Variant options
Standard variant attributes
Link
Price
Availability
Product issues
Destination status
Allow Google time to process the changes before repeatedly altering the same group.
Apparel products
Apparel commonly requires closer attention to standard attributes.
Depending on the product and target requirements, relevant attributes may include:
Colour
Size
Gender
Age group
Material
Pattern
Size system
Size type
Do not use internal shorthand that customers cannot understand.
Examples requiring review include:
BLK instead of Black
M1 instead of Medium
01 instead of a meaningful age group
Combined values without clear separators
Promotional descriptions inside the colour field
Brand names included as materials
The product page, submitted data and customer-facing selectors should communicate compatible values.
Non-apparel products
Variant grouping also applies outside apparel.
A phone may vary by:
Colour
Memory
Storage
Network configuration
A sofa may vary by:
Material
Colour
Finish
Size
A cosmetic product may vary by:
Shade
Finish
Volume
Use standard Google attributes where applicable and use supported variant-option structures for other genuine variant-identifying characteristics.
Do not force an electronics configuration into an unrelated apparel field merely because a field already exists.
Variation URLs and default selections
A shared product page can support several variations, but each submitted link must lead to an accurate offer experience.
Possible URL models include:
Query parameters
Path segments
Preselected variation values
Separate variation pages
Test what happens when:
Cookies are cleared.
The user is logged out.
The URL is opened on mobile.
The default variation is changed.
One variation is out of stock.
A URL parameter contains a translated slug.
A caching system removes query parameters.
A CDN normalises the URL.
A swatch plugin modifies the selection through JavaScript.
A blue variation link should not consistently open a red default variation without a clear and reliable way for Google to identify the intended blue offer.
Merchant API representation
Merchant API product attributes include fields such as itemGroupId, color, size, material and pattern. Review the current Merchant API ProductAttributes reference before implementing a mapping.
A reliable WooCommerce integration should preserve:
One stable identity for every variation
One stable shared identity for the parent group
The correct variation attribute values
The variation’s price and currency
The variation’s availability
The correct image
The correct landing-page URL
Common implementation mistakes include:
Using the parent ID for every variation product ID
Using the variation ID as the item group ID
Generating a random item group ID
Submitting every product under one group
Submitting the parent and all children
Reading only the first variation
Using the lowest parent price for every child
Using the parent stock status
Omitting custom variation attributes
Converting empty values into generic placeholders
Creating several values for a single variation field
Changing identifiers after synchronisation
Using translated slugs as unstable identities
Sending disabled or incomplete variations
Keeping deleted variations active in Google
Mapping colour and size from formatted HTML
Failing to update the entire group after an attribute change
An accepted API operation means the request was accepted for processing. It does not prove that Google has grouped the products correctly or removed every issue.
Inspect the processed products.
Competing product sources
Variant corrections can fail when several sources control the same products.
For example:
PW Merchant API submits the correct group.
An old XML source submits the same products without group IDs.
A supplemental source applies a shared category value.
An ERP later changes variation IDs.
An automated website source rediscovers the parent product.
Review every active source for:
Individual product ID
Item group ID
Variant attributes
Item group title
Variant options
Product link
Image
Price
Availability
There should be one clear source of truth for each field.
Correcting a large WooCommerce catalogue
For a large store, create an audit table containing:
Parent product ID
Parent SKU
Variation ID
Variation SKU
Submitted product ID
Item group ID
Item group title
Variant attributes
Variant-option names
Variant-option values
Price
Currency
Availability
Image
Landing-page URL
Data source
Merchant Center issue
Root cause
Correction
Operation result
Final status
Verification time
Group errors by cause:
Missing item group ID
Unstable item group ID
Shared catalogue-wide group ID
Unrelated products grouped together
Different group IDs for one family
Duplicate product ID
Duplicate variant combination
Missing attribute
Inconsistent attribute set
Too many values
Unmapped custom attribute
“Any” attribute problem
Parent product submitted
Disabled variation submitted
Incorrect URL
Incorrect image
Parent price used for children
Parent stock used for children
Structured-data conflict
Duplicate product source
Import overwrite
Merchant API mapping error
Test a representative product family before applying a bulk correction.
A single mapping correction may resolve thousands of affected offers. Editing products manually one by one can conceal the shared cause and create further inconsistencies.
How PW Merchant API fits into variant management
PW Merchant API is designed to support controlled WooCommerce and Google Merchant API product operations.
Depending on the installed version and supported configuration, it can help users:
Read supported WooCommerce product information.
Work with supported simple and variable products.
Prepare supported product and variation data.
Send new products.
Update previously submitted products.
Organise scheduled catalogue operations.
Review successful and unsuccessful operations.
Identify products that require attention.
Maintain a more controlled product-management workflow.
As a WooCommerce Google Merchant Center plugin, PW Merchant API can support communication between WooCommerce product variations and Google Merchant Center.
However, it cannot independently decide the merchant’s complete product structure.
Determine a commercially correct value from an ambiguous “Any” attribute.
Control another active product source.
Prevent a supplier import from recreating duplicate variations.
Correct unrelated theme or SEO schema output automatically.
Guarantee that Google will group or display products in a particular way.
Guarantee product approval.
Guarantee Shopping visibility, clicks or sales.
Override Google’s independent processing and policy decisions.
WooCommerce remains the commercial source, PW Merchant API manages supported communication, and Google independently processes and evaluates submitted products.
The error may originate from another member of the same group. Review the complete group.
Changing item group IDs repeatedly
This breaks continuity and can create several temporary product families.
Using one group ID for the whole category
An item group is one variant family, not a category.
Removing every item group ID
This may hide a grouping error but also prevents genuine variants from being represented correctly.
Submitting the parent as a purchasable variation
The parent may contain a price range, fallback image or incomplete attributes.
Using the same individual ID for every variation
Google cannot preserve the identity of separate offers.
Testing only the default variation
The default option may be correct while another variation has missing attributes, an incorrect price or a broken URL.
Ignoring disabled variations
An old source may continue submitting variations that are no longer purchasable in WooCommerce.
Using product titles as the only comparison
Titles may be identical or translated. Use IDs, SKUs, parent relationships and exact attributes.
Treating a swatch label as structured data
A visual colour button does not prove that the underlying colour value reaches Merchant Center.
Ignoring structured data
Conflicting ProductGroup or Product markup can describe a different variation relationship.
Changing the full catalogue before testing
A faulty group-ID rule can place thousands of unrelated products into the same group.
Frequently asked questions
What is an item group ID in Google Merchant Center?
It is a stable identifier used to group separate product offers that are genuine variations of the same parent product.
Is item group ID the same as product ID?
No. The product ID uniquely identifies one exact offer. The item group ID is shared by all variations of the same parent.
Can every WooCommerce variation use the same product ID?
No. Each submitted variation should have its own stable product identity.
Should all variations use the same item group ID?
All genuine variations of one parent should use the same group ID. Unrelated product families should use different values.
Can I use the WooCommerce parent SKU as the item group ID?
Google recommends using a parent SKU where possible. The value must remain stable and unique to that product family.
What if the parent product has no SKU?
A stable parent product identifier can be used by the integration, provided it consistently identifies that family and does not change during updates.
Should I submit the WooCommerce parent product?
When individual child variations are submitted as separate purchasable offers, the non-purchasable parent should not automatically become another duplicate offer.
Why does Google report a missing attribute value for grouped variants?
Products sharing one item group ID do not consistently include the attributes needed to distinguish them. Review every offer in the group.
What causes a duplicate variant error?
Two or more products in one group have the same submitted variant combination or have lost the attributes that would distinguish them.
Can two variants have the same colour?
Yes, if another attribute such as size, material or width distinguishes them. Their complete variant combinations must remain unique.
Can one variation contain several sizes?
An exact purchasable variation should normally contain the one size that identifies it. Separate selectable sizes should be submitted as separate products.
Should simple products have an item group ID?
Not merely because they belong to the same category or brand. Use the field for genuine variant groups.
Do custom WooCommerce attributes work with Google?
They can, but they must be recognised and mapped accurately. An internal attribute slug does not automatically become a standard Google attribute.
What is item_group_title?
It is the shared title used to describe the parent product group. Google currently documents it for use with item group ID.
What is variant_option?
It describes the properties that identify each variant. Products in the same group should use a consistent set of option names with values appropriate to each offer.
Does variant_option replace colour and size?
Not automatically. Google’s current specification says applicable standard variant attributes should still be provided.
Do variations need separate URLs?
Each submitted link should lead to or reliably preselect the exact variation. Google recommends distinct variant URLs using appropriate paths or query parameters.
Can structured data cause a variant conflict?
Yes. Incorrect or duplicated ProductGroup and Product markup can describe relationships that conflict with the visible page or submitted product data.
Why did the error return after I fixed it manually?
The next WooCommerce synchronisation, XML import, ERP update or supplemental source may have restored the original value.
Does an accepted Merchant API operation prove the group is correct?
No. Google still needs to process the product and evaluate its relationships and attributes.
How long does a correction take?
Processing time varies. Verify the operation, processed products and Needs attention area instead of repeatedly changing a confirmed correction.
Does fixing the group guarantee approval or visibility?
No. Google evaluates other product-data, landing-page, destination and policy requirements independently.
Final checklist
Before considering item group ID and variant attribute errors resolved, confirm that:
The exact Merchant Center issue was recorded.
Every affected offer ID was identified.
Every item group ID was recorded.
All members of each affected group were listed.
Each offer was matched to a WooCommerce product.
Each offer was matched to the correct variation.
The WooCommerce parent product was identified.
The parent-child relationship is valid.
The products are genuine variants.
Unrelated products are not grouped together.
Every variation has a unique product ID.
Product IDs are stable.
Product IDs are not empty.
Product IDs are not duplicated.
Case-only differences were reviewed.
Every genuine variant shares the correct item group ID.
Each different product family has a unique group ID.
The group ID is not category-wide.
The group ID is not brand-wide.
The group ID is not a changing timestamp.
The group ID is not a random value.
The group ID is not recycled for unrelated products.
The parent SKU was reviewed as a possible stable group value.
The parent product ID was reviewed when no parent SKU exists.
Individual product IDs were not confused with group IDs.
The non-purchasable parent was not submitted as a duplicate.
Simple products were not grouped unnecessarily.
Every group has a defined attribute structure.
The same identifying attributes are used across the group.
Every variation contains its required attribute values.
Every attribute combination is unique.
Duplicate variation records were removed or corrected.
Disabled variations were reviewed.
Deleted variations are no longer submitted.
“Any” attribute values were reviewed.
Custom WooCommerce attributes were mapped.
Global and product-level attributes were reviewed.
Attribute names were checked.
Attribute slugs were checked.
Attribute term values were checked.
Translation behaviour was reviewed.
Colour values are accurate.
Size values are accurate.
Material values are accurate.
Pattern values are accurate.
Age-group values are accurate where applicable.
Gender values are accurate where applicable.
Size system was reviewed where applicable.
Size type was reviewed where applicable.
Multi-colour values use the correct format.
Multiple purchasable sizes were not combined into one offer.
Item group titles are consistent where used.
Variant-option names are consistent where used.
Variant-option values distinguish the products.
Applicable standard attributes were not omitted.
Every variation title describes the correct offer.
Every variation price is correct.
Every sale price is correct.
Every variation uses the correct currency.
Every availability value is correct.
Every variation image is correct.
Parent fallback images were reviewed.
Each submitted URL was opened.
Each URL loads without login.
Each URL selects or identifies the intended variation.
Query parameters survive caching and redirects.
Desktop variation behaviour was checked.
Mobile variation behaviour was checked.
The intended product is added to the cart.
Cart attributes match the submitted variation.
Checkout attributes match the submitted variation.
Structured Product data was inspected.
Structured ProductGroup data was inspected.
productGroupID was checked.
variesBy was checked.
hasVariant was checked.
Duplicate schema output was reviewed.
Theme schema was reviewed.
SEO-plugin schema was reviewed.
Schema-plugin output was reviewed.
Page caches were purged.
Object caches were purged.
CDN caches were purged.
WooCommerce transients were reviewed.
The authoritative product source was identified.
Competing Merchant API integrations were reviewed.
XML sources were reviewed.
Supplemental sources were reviewed.
Automated sources were reviewed.
ERP updates were reviewed.
Supplier imports were reviewed.
Variation ID mapping was checked.
Parent ID mapping was checked.
Item group ID mapping was checked.
Standard attribute mapping was checked.
Empty values were not converted into generic placeholders.
The entire affected group was corrected.
A representative group was tested before bulk changes.
Corrected products were resynchronised.
Operation results were inspected.
Submitted product inputs were inspected.
Processed products were inspected.
Google was allowed time to process the correction.
The Needs attention area was checked again.
A later scheduled operation did not restore the error.
The final group and attribute structure was documented.
An item group ID error is not merely a missing-field problem. It is an identity and relationship problem.
Google must be able to determine which submitted record represents each exact purchasable offer, which offers belong to the same product family and which attributes distinguish one variation from another.
The most reliable correction begins with the complete affected group. It verifies the WooCommerce parent-child structure, assigns stable individual and group identities, supplies consistent variant attributes and confirms that each landing page represents the submitted selection accurately.
When WooCommerce, the landing page, structured data, PW Merchant API and Google Merchant Center describe the same variation relationships, product groups become easier to process, customer choices become clearer and recurring variant errors become less likely.
