Feed case: GTIN cleanup restored Shopping eligibility
A Merchant Center issue was caused by mismatched product identifiers across variants.
Direct answer
The fix was to remove invented identifiers, use real GTINs where available, and align brand and MPN fields across the feed.
Sources and review
Last checked: 2026-05-28- Ecomwith authored answer recordEcomwith · first_party_case · 2026-05-28
- The direct answer and decision frame shown on this page.
Applies to: Use this answer as a concept and decision frame. Verify current platform, market, account, and business facts before acting.
Limitations: The page does not prove a ranking, approval, revenue, profit, or conversion outcome. Platform rules and store data can change.
Reviewed by: Ranfeng · Next review: 2026-08-26
- Direct answer and operating decision frame → Ecomwith authored answer record
Context
Several products were disapproved or limited because identifiers did not match manufacturer data.
Actions taken
The useful part of this case is the operating sequence, not a generic success claim.
- Audited feed identifier fields by product and variant.
- Set identifier_exists correctly for products without valid GTINs.
- Re-submitted the feed after aligning visible product facts.
Result and lesson
Shopping eligibility recovered for corrected products, and future feed QA gained a clear identifier rule.
FAQ
Why not leave identifier fields blank?
If valid identifiers exist, platforms expect them. If they do not exist, the feed must say so correctly.
Can wrong GTINs hurt catalog performance?
Yes. They can cause disapprovals, wrong matching, and weaker product understanding.
Should feed data match page data?
Yes. Price, availability, brand, title meaning, and product identity should align with visible page facts.