Invalid return window: return policy label [return_policy_label]

What Google requires

A window in days that parses and agrees

The return window is expressed in days on the return policy, and it has to be a whole number in the format Google expects. A window submitted without its window_days sub-attribute, or one that contradicts another part of the policy, is invalid. Google reports it as Invalid return window: return policy label [return_policy_label] or Missing window_days sub-attribute.

What Google does

The policy cannot be applied, and can hold up approval

A malformed or missing window means the policy cannot be applied as written, and Google may fall back to your default policy, which can set different costs. Google's own guidance ties a valid return policy to approval, so a broken window is not only a data-quality gap but can hold the product back.

How to fix it by hand

State the window cleanly

• Give the return window as a whole number of days in the expected format.
• Include the window_days sub-attribute wherever a window is declared.
• Make the window consistent with the rest of the policy rather than contradicting it.

What FeedMender checks today

Two checks apply, read from the scanner's registry

The scan checks the return window's format and catches the missing window_days sub-attribute.

• returns_window_days_formatblocks
• returns_window_days_missingblocks

What the scan does not check today: the return policy configured in your Merchant Center account, and whether the feed's window matches your live returns page; it reads the feed's return fields only.

The quicker way

Let the scan check the window

Run the free scan and it flags every return window that is missing or malformed. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed