---
title: Holiday Return Policy for Online Stores — Set One Extended Window Across Site, Merchant Center and Markup
description: Set an extended holiday return policy before Black Friday — one return window on your site, emails, Merchant Center and schema markup, plus a test plan.
source: https://pingvera.com/blog/holiday-return-policy-online-store.html
---
# Holiday Return Policy for Online Stores: Set One Extended Window Across Site, Merchant Center and Markup

A holiday return policy gives gift buyers more time to return items bought in November and December, usually with a single "return by" date in January. The policy itself is a sentence. Most of the work is publishing that same sentence everywhere a shopper or Google reads it: the returns page, product pages, checkout, order confirmation emails, Google Merchant Center or Search Console, and your structured data.

The review time is the reason to start this week. As of October 2026, Google's Search Console help says return policies are checked by hand and "can take about 10-13 days" to verify. Black Friday falls on 27 November 2026, so a policy submitted in mid-November may still show as pending during the busiest week. Decide the window this week, publish it on your site, then submit it to Google.

## At a glance

- Pick two dates first: the first order date the extended window covers, and the last day a return will be accepted.
- Publish the policy on a returns page that anyone can open without logging in, and link it from the footer, product pages and checkout.
- In Merchant Center, add an extension to your existing return policy. Search Console's shipping and returns settings have no seasonal option.
- If you use `MerchantReturnPolicy` markup, add a `returnPolicySeasonalOverride` block, and remember that Merchant Center and Search Console settings take precedence over markup.
- On Shopify, changes to return rules apply only to future orders, so set the holiday window before the first order it should cover.
- Put the revert date in a calendar so the site, Google settings and email templates go back to normal on the same day.

## Why it matters now

Holiday return windows are a seasonal change, and seasonal changes leave a mismatch behind if one channel is forgotten. Google's Merchant Center help asks you to confirm that "return policies are consistent in Merchant Center and across your website", for example in the footer, the returns page and any banner. Google also verifies return policies before using them. In Merchant Center a policy shows as Verified, Pending or Rejected, and Google states that "any return policy that doesn't meet Google's policies may not be used."

Three platform facts shape the timing as of October 2026:

1. Merchant Center lets you extend the return window "during certain times of the year like holidays". You select Add an extension, choose a date range, then enter the number of days and a "no later than" date.
2. Since November 2025 Google has offered the Shipping and returns settings in Search Console to sites it identifies as online merchants. That form covers country, return policy URL, return window and return cost. Google's help page does not mention seasonal options there, and points you to Merchant Center for further options.
3. For structured data, Google's documentation applies settings in this order, strongest first: Content API for Shopping return settings, Merchant Center or Search Console settings, product-level markup, then organisation-level markup. A correct seasonal override in your markup is ignored if a Merchant Center policy says something different.

If your feed tooling still uses the Content API for Shopping, read our note on the [Content API for Shopping sunset](https://pingvera.com/blog/content-api-for-shopping-shutdown.html) before you change return settings through it.

## Step-by-step: set the holiday window today

1. Write the rule in one sentence. Example (illustrative): "Items bought between 1 November and 24 December 2026 can be returned until 31 January 2027." Agree it with whoever handles returns and refunds, because they will apply it in January.
2. Decide exclusions. Final-sale items, personalised goods and opened hygiene products are common exceptions. List them by product, collection or category so they can be labelled in your catalogue and in Merchant Center.
3. Check the local rules for each country you sell to. Some markets set a statutory withdrawal or return period. A holiday window can extend it but should not replace it. Get local advice if you are unsure; this article covers operations only.
4. Update the returns page. State the window, the return method, who pays for return shipping, any restocking fee and how long refunds take. Google lists time frame, method and fees as information your site should show. Keep the page public with no login.
5. Update the places shoppers see before they pay: a line on product pages, the cart or checkout, and a site banner if you run one. Use the same dates and wording.
6. Update transactional emails. Order confirmation and shipping emails often carry a returns line. Edit the template text and send yourself a test order to see the rendered result.
7. Update Merchant Center. Go to Shipping and returns, open the Return policies tab, select your policy, then Add an extension. Enter the date range, the extra days and the "no later than" date. For exclusions, create an exception policy and assign it with the `return_policy_label` attribute in your product data.
8. Update Search Console if you manage returns there instead of Merchant Center. Because there is no seasonal setting, decide whether to leave the base window or change it for the season and change it back later. Policies created or edited in Merchant Center are not available in Search Console, so keep each policy in one place.
9. Update structured data if your theme or plugin outputs `MerchantReturnPolicy`. Add the seasonal override (snippet below) and validate it with Google's Rich Results Test.
10. Brief support. Give the team the exact wording, the exclusions and the revert date. A shopper who quotes the banner in February deserves a consistent answer.
11. Schedule the revert. Put one calendar event, owned by one person, that lists every place you changed in steps 4 to 9.

Shopify stores have a specific constraint. Return rules live under Settings > Policies, in the Return and cancellation rules section, and Shopify states that "changes to your return rules apply only to future orders." Shopify's help page does not describe date-based seasonal rules. If you lengthen the default window for the season, make the change before the first order it should cover. If you use the automated return policy page, Shopify updates it when your rules change, so the published text will move with the rule. Check that Merchant Center moves with it too.

WooCommerce and Magento have no built-in seasonal return window. The policy is usually a page plus whatever your returns plugin or extension enforces. Check both: the page text and the plugin's eligibility setting.

## Where the window must match

## Copyable artefact: markup snippet and test plan

Organisation-level markup, illustrative values. Google requires either `applicableCountry` plus `returnPolicyCategory` (and `merchantReturnDays` for a finite window) or a `merchantReturnLink`. Replace the country, URL and dates with your own.

{
 "@context": "https://schema.org",
 "@type": "OnlineStore",
 "name": "Example Store",
 "url": "https://www.example.com",
 "hasMerchantReturnPolicy": {
 "@type": "MerchantReturnPolicy",
 "applicableCountry": "GB",
 "returnPolicyCountry": "GB",
 "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
 "merchantReturnDays": 30,
 "merchantReturnLink": "https://www.example.com/returns",
 "returnMethod": "https://schema.org/ReturnByMail",
 "returnFees": "https://schema.org/FreeReturn",
 "returnPolicySeasonalOverride": {
 "@type": "MerchantReturnPolicySeasonalOverride",
 "startDate": "2026-11-01",
 "endDate": "2026-12-24",
 "merchantReturnDays": 60,
 "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow"
 }
 }
}

Schema.org counts `merchantReturnDays` from delivery, while shoppers think in "return by" dates. Pick a number of days that reaches your January date for the last eligible order (60 here is illustrative), and keep the page text as the source of truth. Google's own example also lists one override with an end date before its start date, so check your dates by eye before you copy anything.

Test plan, to run once after launch and once after any deploy before 31 December:

`HOLIDAY RETURN POLICY TEST PLAN (fill in)
Policy sentence: ______________________________________
Covered order dates: ________ to ________ Return by: ________
Revert date: ________ Owner: ________

[ ] Returns page opens logged out, desktop and mobile, HTTP 200
[ ] Returns page shows the covered dates and the return-by date
[ ] Footer link to returns page works on home, product and checkout
[ ] Product page and checkout line uses the same dates
[ ] Test order confirmation email shows the holiday line
[ ] Returns plugin / platform rule accepts a return for the test order
[ ] Excluded product cannot be returned, and the page says so
[ ] Merchant Center: extension saved, status = Verified (date checked: ____)
[ ] Search Console: no conflicting return window
[ ] Rich Results Test: MerchantReturnPolicy valid, override dates correct
[ ] Support team has the wording, exclusions and revert date
[ ] Revert event in calendar lists every item above
`
Worked scenario (illustrative)
A WooCommerce store selling homeware normally offers 30-day returns. The owner decides that orders placed from 1 November to 24 December 2026 can be returned until 31 January 2027, with custom-printed items excluded.

On 28 October the agency updates the returns page, the theme's product-page snippet and the order email template. On 29 October the marketing lead adds the Merchant Center extension and an exception label, `final-sale`, which the agency adds to 40 custom-print products in the feed. The developer adds the seasonal override to the theme's JSON-LD.

On 3 November a plugin update restores the theme's default product template, and the "30-day returns" line comes back on product pages. The weekly check in the table above catches it on 4 November. Without that check, the site would have shown two different windows during Black Friday week while Google was still reviewing the policy. The same week the team confirms the [holiday shipping cutoff](https://pingvera.com/blog/holiday-shipping-cutoff-online-store.html) dates, since the returns page quotes them.

On 1 February 2027 one person follows the revert event: page, banner, email template, Merchant Center extension (now expired), markup.

## Common mistakes

- Changing Merchant Center before the website. Google checks the policy against your site, so publish the page first.
- Leaving a hard-coded "30-day returns" string in a theme file, a product description template or a trust badge image.
- Adding the extension in Merchant Center and also changing the base window in Search Console. You end up with two sources describing one policy.
- Forgetting the returns plugin. The page promises January returns while the plugin rejects requests after 30 days.
- On Shopify, changing return rules after orders were placed and expecting those orders to pick up the new window.
- Copying markup examples without checking the dates.
- No revert plan, so a December promise is still live in March.

Return terms are one of several promises Google compares against your site; our guide to [Merchant Center misrepresentation suspensions](https://pingvera.com/blog/merchant-center-misrepresentation-suspension.html) covers the wider audit. Once January's returns arrive, [measure what they cost](https://pingvera.com/blog/ecommerce-returns-economics.html) before you set next year's window.

Limitations: Google does not publish how long Merchant Center review takes, and the Search Console figure of 10-13 days is a guide. A Verified status confirms Google accepted the policy. It does not tell you that every page, email and plugin setting on your site agrees with it, and that part stays your job.

## FAQ

### How long should a holiday return policy be?

There is no standard length. Many stores pick a fixed "return by" date in January that covers orders from November or early December. Choose a window your returns process and cash flow can handle, and make sure it is at least as generous as any legal minimum where you sell.

### Can I set a holiday return window in Google Search Console?

As of October 2026, Google's Search Console help describes country, URL, return window and return cost, with no seasonal option. Use a Merchant Center extension, or change the base window in Search Console and change it back after the season.

### Do I need return policy structured data if I use Merchant Center?

Not for Google: Merchant Center and Search Console settings take precedence over markup. Markup can still help other systems that read your pages, and if you keep it, it must match the page.

## Sources

- [Google Merchant Center Help: Set up your return policies for Shopping ads and free listings](https://support.google.com/merchants/answer/14011730)
- [Google Merchant Center Help: Return policy requirements and setup](https://support.google.com/merchants/answer/10220642)
- [Google Search Console Help: Shipping and return settings](https://support.google.com/webmasters/answer/14907594?hl=en)
- [Google Search Central: Merchant return policy structured data](https://developers.google.com/search/docs/appearance/structured-data/return-policy)
- [Google Search Central Blog: More ways to share your shipping and returns policies with Google (November 2025)](https://developers.google.com/search/blog/2025/11/more-ways-to-share-shipping)
- [Schema.org: MerchantReturnPolicySeasonalOverride](https://schema.org/MerchantReturnPolicySeasonalOverride)
- [Shopify Help Center: Return rules](https://help.shopify.com/en/manual/fulfillment/managing-orders/returns/return-rules)

Last reviewed: 2026-10-28

Step 4 depends on one URL staying reachable all season. Pingvera can run a one-minute HTTP check on the returns page you submitted to Google and include it in its broken-link scans, so a 404 or an unexpected redirect after a December deploy reaches you as an alert.