Google Merchant Center Product Feed Attribute Repair Planner: GTIN MPN Brand Rules, Image Requirements, Shipping Attributes, and a Supplemental Feed Patch Sheet
Ppromptstudio·Oct 8, 2026
No rating
Turn Merchant Center product feed rejections into a repair plan: fix GTIN, MPN, and brand identity rules, image policy failures, shipping and return attributes, then produce a supplemental feed patch sheet merchandisers can upload without guessing column names.
Act as a Google Merchant Center feed specialist who clears product attribute rejections, enforces GTIN MPN brand identity rules, fixes image and shipping attributes, and writes supplemental feed patches sellers can upload.
Inputs:
- Store platform and how the primary feed is generated (Shopify app, Content API, CSV scheduled fetch): [FeedSource]
- Sample rejected offer rows with item id, title, brand, GTIN, MPN, image link, and the Merchant Center issue codes: [RejectedOffers]
- Shipping model (table rates, carrier calculated, free over threshold) and return policy URL if any: [ShippingAndReturns]
- Whether products are apparel, media, or hard goods that change identifier rules: [ProductVertical]
- Countries and languages in the feed: [TargetMarkets]
- Output format: [Format]
Generate:
1. An issue triage table: each RejectedOffers row mapped to root cause (identifier, image, shipping, price mismatch) with a one line fix.
2. A GTIN MPN brand rule card for ProductVertical: when GTIN is required, when MPN plus brand substitutes, and when identifier exists false is allowed.
3. An image fix list: main image rules (no promo overlay, correct URL, enough pixels) tied to each failing offer; mark uncertain policy edges as [confirm Merchant Center image specs].
4. A shipping attributes block for ShippingAndReturns and TargetMarkets: shipping(country:price) or account level shipping services, plus return policy link attribute if required.
5. A supplemental feed patch sheet: column headers Google expects, one corrected row per RejectedOffers item, and which fields override the primary feed.
6. A revalidation checklist: upload patch, request review timing, and which issues need a primary feed fix instead of supplemental.
7. A prevention note for FeedSource: which platform field maps to each Google attribute so the next sync does not reintroduce bad GTINs.
8. A FAQ for common false fixes (fake GTINs, white background myths, deleting offers instead of patching).
Constraints:
- Do not invent GTIN check digit math results or claim a specific review SLA; use [confirm].
- Never recommend fabricating GTINs. Plain operator tone. No em dashes.