Return Policy Disapprovals in Merchant Center: A Decision Tree From Label to Return Window

Google generally gives a merchant who breaks a Shopping ads policy "7 or 28 calendar days to fix your issue", and for violations it classes as egregious it may suspend an account without a warning (Merchant Center Help, Shopping ads policies). Return policy problems sit on both sides of that line. A bad label in one column can quietly disapprove a batch of products, while a policy that contradicts your checkout can threaten the whole account.

This guide is for feed managers and e-commerce leads who have seen "Invalid return policy label" or "Invalid return window" in the Needs attention page. By the end you will be able to name which of four causes you have, fix it at the right layer (feed, Merchant Center, or website), and verify the fix before the next review cycle.

How Google decides which return policy a product gets

Return handling has three layers, and most diagnostic mistakes come from editing the wrong one.

1. The feed layer. One optional attribute, return_policy_label. Leave it blank or set it to default and the product uses your default policy. Enter a label and the product uses the exception policy with that name (Merchant Center Help, return policies).
2. The Merchant Center layer. The policies themselves: return URL, countries, whether you accept returns, return window, return method, restocking fee, refund processing time. Each country can belong to only one policy, and a standard policy can have several exception policies.
3. The website layer. Your return page and any MerchantReturnPolicy markup. Google's precedence order, strongest first, is Content API return settings, Merchant Center or Search Console settings, product-level markup, then organization-level markup (Google Search Central, return policy structured data). If you set both markup and Merchant Center, Google uses the Merchant Center settings.

A feed tool can only touch layer one. That matters, because two of the four causes below cannot be fixed in the feed at all.

Step 1: Read the exact issue name

Open Needs attention, filter by the affected products, and write down the issue title as printed. Three situations matter here:

Sources: invalid label and invalid return window in Merchant Center Help. Google's help page for the return window issue does not publish the minimum numbers; it says only that the window must meet the minimum for the product's target country. Do not trust a blog post that gives you a single global number. Read the number Merchant Center shows for your country.

Step 2: Run the decision tree

Branch A: the label does not exist

Export the distinct values of return_policy_label from your feed and compare them with the labels listed under Shipping and returns, then Return policies. The usual causes are a typo, a case difference, a trailing space, or a label that was renamed in Merchant Center after the feed rule was written.

A feed with the problem looks like this (tab-separated, abbreviated):

id        title                         return_policy_label
SKU-1001  Wool coat, navy, M            default
SKU-2044  Clearance sneakers, white 42  final-sale
SKU-2045  Clearance sneakers, black 42  Final Sale
SKU-3310  Gift card 100 TRY             no-return 

If Merchant Center has a label named final-sale and nothing else, then SKU-2045 and SKU-3310 both reference labels that do not exist. SKU-2045 differs from the real label by case and a hyphen, and we would not assume Merchant Center forgives that; this is how the problem appears when two teams edit the column. The fix is to normalise the label in the feed (lowercase, hyphenated, trimmed) or to create the missing policy. Google offers both options: create the label in Merchant Center, or remove it from the product so the default applies.

Note what the fallback does. A product with an invalid label does not fail closed. It silently takes the default policy. If your default is a 30-day return policy and the product is a final-sale item, you are now advertising a promise you do not intend to keep. That is a Branch C problem waiting to happen, so fix labels even when the product is still approved.

Branch B: the label exists but the window is below the minimum

Here the feed is fine. Open the policy the product maps to and check the return window for the country in the disapproval. Google's own fix is to edit the default policy or add a new one with a compliant window and assign it to the disapproved products. Two cautions:

• Editing a policy changes every product that uses it. Before you shorten or lengthen anything, count the rows per label in the feed.
• Each country belongs to one policy. If you want a different window for one country, move that country, do not duplicate it.

If you manage policies through the Merchant API, the onlineReturnPolicies resource carries a label, a list of countries, and a policy whose type is NO_RETURNS or NUMBER_OF_DAYS_AFTER_DELIVERY with a days value. Google states that a new policy can take up to 10 business days to be reviewed and become available, whether you create it in the interface or by API (Merchant API guide). Plan peak-season changes around that delay, not around the day you notice the problem.

Branch C: the policy is valid, but it does not match your site

This branch produces no feed error, which is why it is dangerous. Google's guide says return policies should be reachable on your site without sign-in or personal information and should match the policy in Merchant Center. The Shopping ads policy page lists specific mismatches it treats as violations:

• Concealing that the customer pays cross-border freight to return a product.
• Restocking fees that are not disclosed clearly before checkout.
• International return windows that start on the purchase date instead of the delivery date.
• Denying a refund despite a clear policy that allows it, which the page lists as scamming.

The test is simple. Take three SKUs, one per policy label, and walk from the product page to checkout as a customer would. Write down the window, the fee, and who pays shipping at each step. Compare that with the Merchant Center policy row by row. If any field differs, the website wins the argument, because the violation is judged on what the customer sees. If you are already facing a suspension, continue with our misrepresentation recovery guide.

Branch D: the product should not be returnable

Some items legitimately have no returns: custom-made goods, sealed hygiene items, perishable goods. In Merchant Center this is a policy with "No, I don't accept returns" (or NO_RETURNS in the API) assigned through a label. Create it deliberately and map those SKUs to it. Do not rely on a blank label, because blank means default.

Step 3: Handle country law before you set the window

Consumer law sets its own floors, separate from Google's minimums. For a Turkish store, a consumer can withdraw from a distance contract within 14 days without giving a reason, counted from receipt of the goods, under Article 48/4 of Law No. 6502 and Article 9 of the Regulation on Distance Contracts. Since 1 January 2026, if the consumer returns goods with the carrier the seller named, the consumer cannot be charged the return cost, and the same applies when no carrier was named (Ongur & Partners, Distance Sales Contracts Under Turkish Law 2026, Mondaq, 23 September 2026). The same article notes that where the seller did not properly inform the consumer, the 14-day period does not apply and a longer statutory period, capped at one year, runs instead.

For feed work this has two consequences. A Turkey-targeted policy with a "customer pays return shipping" field set to a fee needs a legal check before it ships, and a window shorter than 14 days for ordinary goods is a legal problem before it is a Google problem. We are not lawyers, and the statute has exceptions for custom, perishable and sealed goods, so take the final wording from counsel. If you sell into other regions, check the equivalent rule for each country that appears in the policy's country list.

Step 4: Scoring your setup

Use this rubric before any seasonal change. One point per yes.

Seven or eight is healthy. Five or six means you will see sporadic disapprovals. Four or fewer means fix the website layer first, because feed fixes will not hold.

Step 5: Verify the fix

1. Re-export the feed and confirm the label set is a subset of your policy labels.
2. Wait for the next processing cycle, then check Needs attention. Google notes that updates can take time to appear there.
3. Spot-check one product per label in Shopping results for the return information Google displays.
4. Log the date of every policy edit, because an edit affects every product on that policy.

Where this method breaks down

This guide cannot tell you the minimum return window for your country, because Google does not publish it on the help pages we reviewed. It also does not cover Meta or TikTok Shop return fields, which differ. Google's help page does not state which return policy fields are mandatory, so treat the field list as what the form offers, not as a validation spec. We have not tested how fast each fix clears on a live account, and review timing varies.

On tooling: nothing here needs a feed management platform. The policies live in Merchant Center, and any tool that can write a static or conditional column, Feedance included, can populate the label. Where you edit shipping at product level, our shipping override guide shows the same layering problem. If a product is missing from results with no return-related issue, check the attribute switches in pause versus excluded destination before blaming the policy.

FAQ

Is return_policy_label required?

No. With a single policy you do not need to change your data source, though you can set the value to default for every product. The column becomes necessary only when some products need an exception policy.

What happens if my label is misspelled?

Merchant Center cannot find it, raises "Invalid return policy label", and applies the default policy to the product. The product may stay approved while advertising the wrong terms.

Why was a product disapproved even though the label is correct?

The likely cause is the return window. If the assigned policy falls below the minimum for the product's target country, the product is disapproved until you edit that policy or assign a compliant one.

Does editing a return policy affect other products?

Yes. Google states that editing a policy changes every product that uses it. Count the rows per label before changing a window.

Which wins if my website markup and Merchant Center disagree?

Merchant Center settings rank above product-level and organization-level markup, and Google will use the Merchant Center information. The mismatch can still be judged against what shoppers see on your site.

How long does a new policy take to become active?

Google's Merchant API guide says a new policy can take up to 10 business days to be reviewed and become available. Create seasonal policies well before a campaign.

Can one policy cover several countries?

Yes, a policy can list several countries, but each country can belong to only one policy. Use exception policies for products that differ.

Can I mark a product as not returnable?

Yes. Create a policy that does not accept returns and map those products to it with a label. Do not leave the column blank, because blank resolves to the default policy.

Check your own feed

Run your catalog through our free product feed audit tool to see which attributes are missing or inconsistent before Google does.