Google Merchant Center Refund Policy Requirements: What Actually Gets You Suspended

Refund and return policies are the number one cause of misrepresentation suspensions in Google Merchant Center. This isn't because merchants are trying to deceive customers — it's because Google's requirements are stricter than most merchants realize, and policy conflicts between pages are remarkably easy to create without noticing. This guide explains exactly what Google requires, the most common mistakes, and what a compliant policy actually looks like.

Why Refund Policies Are the #1 Misrepresentation Trigger

Google's crawler doesn't just read your return policy page. It cross-references your return policy against every product page and against your feed. When it finds a claim on a product page — 'free returns,' '30-day guarantee,' 'no questions asked' — it checks whether your policy page says the same thing. If there's any discrepancy, that's flagged as misrepresentation. This cross-referencing is automated, comprehensive, and consistent.

The reason this catches so many merchants off-guard is that return claims on product pages often come from places the merchant didn't write: third-party trust badge apps, theme templates with built-in return language, imported product descriptions from suppliers, or seasonal promotions that updated product pages but not the policy page. Google doesn't distinguish between intentional misrepresentation and accidental inconsistency — either way, the claim and the policy don't match.

What Google Requires from Your Return Policy

Google's Shopping Ads policies don't publish a line-by-line checklist, but based on the patterns in approved and rejected accounts, here is what a compliant return policy must include:

• A specific return window stated in days — not 'a reasonable time,' not 'contact us,' not 'we'll review on a case-by-case basis.' It must be a number: '30 days from delivery date' or '14 days from the date of purchase.'
• What the refund is to — original payment method, store credit, or exchange. If it varies, state clearly which option applies in which circumstances.
• Who pays return shipping — you or the customer. If it depends on the reason for return, state that explicitly.
• The condition the item must be in — 'unused and in original packaging,' 'unopened,' 'in resaleable condition,' etc.
• Any category exceptions — final sale items, custom orders, digital products, hazardous materials, perishables.
• How to initiate a return — email address, form link, or phone number.
• How long the refund takes to process once the return is received.

The Most Common Policy Mistakes

1. 'Free returns' on product pages, restocking fee in policy

This is the single most common mismatch. A trust badge app or theme element says 'Free returns' on every product page. The actual return policy says '15% restocking fee applies.' Even if your policy is technically more prominent, Google flags the product page claim as misrepresentation because it contradicts the policy.

2. '30-day returns' on product pages, 14-day window in policy

Often caused by using a theme template or app that has a generic '30-day returns' badge while the merchant's actual policy is shorter. Or a supplier-provided product description says '30-day satisfaction guarantee' and the merchant published it without checking.

3. Policy page buried in footer and not linked from checkout

Google expects the return policy to be linked from the checkout process as well as from product pages. If your checkout doesn't show or link to the return policy, this is a transparency issue. Many platform checkouts include this by default, but customized checkouts often remove it.

4. Using a template that mentions products you do not sell

Boilerplate return policy templates often include language like 'Items must be unworn, with original tags attached' or 'Software licenses are non-refundable.' If you sell software and your policy says software is non-refundable, but your product pages don't mention this exception, the policy contradicts the product page. Always customize templates to match your actual product catalog.

5. Different return windows for different categories without labeling

If electronics have a 14-day return window and apparel has 30 days, your policy must clearly label which category gets which window. A policy that says '30 days' in one section and '14 days' in another without distinguishing which products each applies to will be read as contradictory.

6. Vague language like 'we'll try to help'

Phrases like 'we take returns on a case-by-case basis,' 'contact us and we'll do our best,' or 'we aim to keep customers happy' are not policies. Google requires a defined, unambiguous commitment. If your policy doesn't state a clear window, Google treats the absence of a clear commitment as a misrepresentation risk.

The Conflict Detection Pattern

Here's how Google's crawler identifies the conflict: it visits a product page and extracts any text related to returns, refunds, guarantees, or shipping. It then visits your return policy page and extracts the equivalent information. It compares the two. If the product page says '30 days' and the policy says '14 days,' that's a flag. If the product page says 'free returns' and the policy says 'customer pays return shipping,' that's a flag. The comparison is automated and does not give benefit of the doubt.

This is why you cannot fix the policy page alone — you must audit and fix every product page too. And because product pages can be modified by apps that run after the page loads (injecting JavaScript-generated content), you need to check what Google's crawler actually sees, not just what you see. The Rich Results Test and Search Console's URL Inspection tool show you what the crawler retrieved.

What a Compliant Return Policy Section Looks Like

This example covers every required element: window (30 days from delivery), condition, how to initiate, shipping responsibility (split by reason), refund method, processing time, and exceptions. Note that the exceptions are clearly labeled, so any 'final sale' product page claim is consistent with the policy.

Shipping Policy Requirements

The same cross-referencing logic applies to shipping policies. Your shipping policy must state: the dispatch timeframe (how long after order before it ships), the transit timeframe for each shipping method you offer, the countries you ship to, and any exceptions (hazardous items, oversized items, remote locations). Every shipping claim on every product page must match what your shipping policy says.

How to Audit Your Own Pages for Conflicts

1. Go to your return policy page and write down: the exact return window, the exact refund method, who pays return shipping, and any exceptions. These are your 'policy commitments.'
2. Visit 15-20 product pages — your best sellers, any recently added products, and any products that were individually disapproved in GMC.
3. On each product page, look for any text that mentions returns, refunds, guarantees, or satisfaction — in the product description, in trust badges, in app-injected widgets, in the page template header or footer.
4. Compare every claim you find against your policy commitments. Any difference is a flag.
5. Check in an incognito browser and on mobile as well as desktop — some apps render different content in different contexts.
6. Use Google's Rich Results Test to see the structured data Google extracts from the page — this tells you what Google actually sees, not just what you see.