Skip to content

Merchant Center duplicate GTIN errors across variants

Trace duplicate GTIN errors to product variants or repeated feed records, correct the catalog mapping, and verify the selected product on its landing page.

By Crawlito · 5 min read

In short

  • Different product variants should use their actual assigned product identifiers.
  • A shared group identifier is different from a variant's GTIN.
  • Correct the source catalog and feed mapping instead of inventing replacement identifiers.
On this page

If Merchant Center reports duplicate GTINs across variants, determine whether the feed repeats the same product or assigns one variant's identifier to several different items. Correct the catalog mapping using the actual assigned identifiers, and use the appropriate group identifier for related variants. Do not invent GTINs to make the warning disappear.

The landing page matters too. A feed entry can identify one size while its URL opens another. Verify the full chain from the source product record to the item a visitor actually sees.

Read the affected item records

Open the specific issue and export the affected records where available. Keep the item ID, GTIN, variant attributes, condition, multipack value, and data source together.

Google's duplicate GTIN guidance explains that repeated combinations can indicate duplicate products or an identifier reused for different products. It also describes using unique variant identifiers alongside item_group_id for related variants.

Do not group solely by product title. The title may omit size, color, or pack details. Compare the actual sellable units.

A hypothetical inventory might contain three sizes of the same shirt. They belong to a related family, but each item must be matched to its own actual identifier where assigned. Copying the parent's value into every child record can create the reported issue.

Also inspect duplicate data sources targeting the same market and language. The problem may be repeated submissions of one item rather than a bad identifier in the source catalog.

Separate item identity from variant grouping

Google's unique product identifier guidance distinguishes identifiers for the products sold and explains variant considerations. Use the assigned identifier for the exact item rather than treating the family as one indistinguishable product.

A group ID connects related variants in the feed. It does not replace the identity of the individual item.

Create a mapping table:

FieldIntended role
Item IDYour stable feed record identity
GTINActual assigned identifier for the sellable item
Item group IDRelationship among supported variants
Size and colorAttributes describing the selected variant
Landing URLPage that presents that item accurately

Avoid storing all these meanings in one generic “product code” field. A database can contain a parent SKU, supplier code, barcode, and internal record ID that look similar but serve different purposes.

The product variant guide helps connect those identities to the public page experience.

Verify identifiers against the authoritative source

Use the manufacturer's or your own authoritative product records to confirm the correct identifier for each item. Packaging and supplier data can help, but record which source the catalog team trusts.

Check whether the product is a single item, a multipack, or a bundle. Do not assume that the identifier for one component describes the entire offer.

Preserve leading zeros and treat identifiers as strings through imports and spreadsheets. A numeric conversion can change a valid stored value before the feed is generated.

Do not borrow an identifier from a similar item. A matching brand name or picture does not establish that two records represent the same sellable product.

For products that genuinely have no assigned GTIN, follow Google's documented identifier guidance for that case. Do not manufacture a number to satisfy a field. The repair should improve product identity, not merely silence a validation message.

Keep a small evidence note linking each corrected record to its source. This makes future supplier imports easier to review.

Repair the catalog-to-feed transformation

Trace the value through the source catalog, export mapping, feed rule, and final submitted record. Determine where the wrong value first appears.

A common hypothetical failure is a feed template reading the parent product's barcode for every variant. Another is a CSV join using a non-unique title instead of a stable item identifier.

Fix the earliest incorrect transformation. Manual edits in a downstream dashboard may be overwritten at the next scheduled feed refresh.

Test a representative family before applying the change across the catalog. Include an item without variants and a pack configuration if those use different mapping rules.

Keep the item IDs stable where appropriate to the existing feed contract. Changing every identifier at once can make the repair harder to reconcile and may introduce unrelated tracking issues.

The product schema guide is relevant if the same catalog data feeds the page's structured data. Correct both outputs from the shared source rather than leaving the feed and page in disagreement.

Verify the selected landing-page product

Open the URL from each corrected feed record as a logged-out visitor. Confirm the selected variant, visible attributes, availability, and price correspond to the record.

A URL that always opens the default size can mislead readers even if the feed's GTIN is now correct. Test the selection after a fresh load, not only after manually clicking the variant in an existing session.

Inspect structured data for the selected item and related variants according to the site's implementation. Do not assume that a visible selector updates all machine-readable fields correctly.

Use a simple acceptance record:

Feed item: the intended size and color.
Assigned identifier: confirmed by the catalog source.
Landing URL: opens that item directly.
Visible offer: agrees with the submitted item.
Structured data: describes the same product state.

The price mismatch guide covers a separate offer problem that can remain after identity is repaired. Keep those findings distinct.

Confirm the refreshed data and issue status

Submit or refresh the corrected data through the normal source workflow. Verify the processed item values in Merchant Center, not just the local export file.

Record when the update was submitted and when the platform reflects it. Do not treat a pending processing state as proof that the correction failed.

If the duplicate issue persists, compare the active sources and repeated records again. An old supplemental rule or another feed may still overwrite the corrected value.

Avoid repeatedly generating new product IDs to force a new evaluation. Preserve a clear timeline of the actual catalog correction and processed result.

For an agency report, distinguish “source mapping fixed,” “updated data processed,” and “issue resolved.” Each state has its own evidence. A successful upload alone does not establish the final state.

Prevent variant identity errors in future imports

Validate the relationship between parent records and child items when new products enter the catalog. The import should preserve the actual assigned identifiers instead of filling missing values with a parent fallback.

Add a review for duplicate identifier combinations, but do not automatically delete every repeated row. Some apparent duplicates may reflect legitimate data-source or market contexts that require careful evaluation.

Keep the catalog owner's decision in the workflow. Technical checks can flag a conflict, while product specialists confirm whether the records describe the same sellable unit.

Test spreadsheet exports for leading-zero preservation and column mappings. A correct database can still produce a damaged feed if a manual file conversion changes the identifiers.

When changing ecommerce platforms, migrate the identity relationships alongside titles, images, and prices. A visually correct catalog can hide a broken product mapping that only surfaces after submission.

Frequently asked questions

That is the purpose of a supported grouping field. It does not mean every variant should reuse the same actual GTIN.

Should I make up a GTIN for a handmade item?

No. Follow the documented guidance for products without assigned identifiers and use accurate source information.

Does resolving the feed warning prove the page is correct?

No. Open the submitted landing URL and verify that it presents the intended item and offer.

Run a representative product URL through the free Crawlito check after reconciling its catalog identity.

Filed under Structure and schema. Topics: ecommerce, structured-data, product-schema