Admin / New feature

Return window overrides
Override the return window for individual products

Change the return window for specific collections, products, or variants on a per-market basis. Example: 90 days by default, but just 14 days for seasonal items.

On this page
  1. What's changing (in 30 seconds)
  2. Decision flow diagram: which return window applies
  3. 4 rules for how it applies
  4. Example: Holiday 2026 collection
  5. Before vs. with overrides
  6. Where to set it (steps)
  7. 5 key points for developers
  8. 3 business use cases
  9. One-line summary for proposals

1What's changing

Until now, return windows were set either as a store-wide default or as market-specific rules.
Now,for each market, you can give specific collections, products, or variantstheir own return window.

By collection

Apply a separate return window to a group of products at once, such as "Holiday 2026".

By product

Change the return window for specific products only.

S L

By variant

Go as granular as individual variants, such as size or color.

2Decision flow diagram: which return window applies

Item being returned Final sale? (final sale) YES Non-returnable and non-cancellable Takes priority over overrides NO Override matches? YES Override window If multiple match, the shortest applies NO Market-specific rule exists? YES Market-specific windows NO Default return window Priority: Final sale > Override (shortest) > Market-specific > Default
It's easiest to think of the decision as being evaluated left to right, settled by the first rule that matches . Final sale always wins; the default is the last fallback.

34 rules that apply

01

Overrides replace the default

When a product matches an override, the override's window applies instead of the default or market-specific window.

02

If several match, the shortest wins

If a product matches multiple overrides, the shortest return window among them applies.

30 days 14 days ← applied 21 days
03

Final sale always takes priority

Final sale items can't be returned (or canceled), even if they match an override.

04

Otherwise, existing rules apply

If an item is neither final sale nor covered by an override, the market-specific return window applies. If there's no market-specific rule either, the default return window applies.

4Example: Holiday 2026 collection

Return window (days from purchase) 0 14 45 90 days Regular products Store default 90 days Holiday 2026 Collection override 14 days ← Shorter for just these products

Example from the article: keep the store-wide default at 90 days and set only the "Holiday 2026" collection to 14 days.

5Before vs. with overrides

ItemBeforeReturn window overrides
Granularity Coarse Default / market-specific Fine-grained Market × collection / product / variant
Shorten only seasonal items Had to change the store-wide window Override just the relevant collection
Handling overlaps — Shortest return window applies
Interaction with Final sale No returns or cancellations Still not allowed (takes precedence over overrides)
Pricing & eligible plans — Not specified

6Where to configure (steps)

1

Settings > Policies

In the admin, open Settings > Policies.

2

Return and cancellation rules

Go to Return and cancellation rules.

3

Choose a market

Select the market-specific rule you want to change.

4

Set targets and window

Choose collections, products, or variants and override the return window.

The article doesn't specify eligible plans, available regions, or a limit on the number of overrides. Before rolling this out, confirm the settings actually appear in your admin.

75 key points for developers

1. Precedence is fixed at four levels

Final sale > override > market-specific > default. Write return-eligibility FAQs and customer support materials in this order to avoid contradictions.

2. Overlaps resolve to the "shortest"

When settings overlap (e.g., set on both a product and its collection), the shortest window applies. Note that an override meant to extend the window will lose to a separate, shorter rule.

3. Final sale means no returns or cancellations

Even if an override sets a window, the Final sale designation wins. Before going live, audit whether any products you want to accept returns for are marked Final sale.

4. Settings are tied to markets

Overrides are configured within market-specific rules. If you operate multiple markets, check whether each market needs the same settings.

API ?

5. No mention of APIs or webhooks

The article only covers configuration in the admin. It doesn't say whether these can be set or read via the Admin GraphQL API, or how return apps can access them. If you integrate with an external returns management system, verify beforehand.

83 practical use cases

14 days
USE CASE 1

Shorten the return window for seasonal and holiday items only

Challenge
Holiday items are hard to resell once the season ends, but shortening the store-wide return window hurts the buying experience for regular products.
Approach
Group holiday items into a collection and override the return window for that collection only (e.g., 14 days). Keep the default at 90 days.
Impact
Keep a generous return policy for regular products while reducing post-season return risk.
Technical note
Because this is set per collection, well-designed automated collection conditions make it easy to add eligible products. When rules overlap, the shortest window applies.
JP US
USE CASE 2

Adjust return terms per market × product for cross-border commerce

Challenge
Some products have very different return shipping costs domestically vs. internationally, but market-specific rules couldn't be split by product.
Approach
Within international market rules, override the return window only for products or variants with high return costs.
Impact
Optimize terms for just the high-cost products without changing the policy for the entire market.
Tech note
Overrides are configured per market. Keep a list of your settings so nothing is missed when you add a new market.
VARIANT
USE CASE 3

Replace app-based and manual processes with a built-in feature

Challenge
Differences in return windows by product are handled through manual CS judgment or third-party return apps, which leads to inconsistent decisions and operational overhead.
Approach
Inventory your return window exceptions and move them into the admin as collection, product, or variant overrides.
Impact
Return eligibility decisions are centralized in Shopify's rules, reducing CS errors and the time spent handling inquiries.
Tech note
It isn't stated whether third-party return apps read this setting. If you use one alongside it, verify the app's behavior before migrating.

9One-line summary for proposals

"A new feature that lets you override return windows per market at the collection, product, or variant level .
Keep a generous default while shortening the window for select items, like seasonal products.
When rules overlap, the shortest window applies, and Final sale items are never returnable."