Executive summary
- What: return window overrides can now be set by market against a specific collection, product or variant, replacing your default or market level window for matching items.
- Why: seasonal, clearance and perishable ranges no longer force you to choose between one generous storewide window and a policy you cannot enforce.
- Who: merchandising, customer experience and ecommerce operations teams, particularly on stores selling into several markets.
What changed
You set overrides under Settings, Policies, Return and cancellation rules, select the market rules you want to modify, then target a collection, product or variant. A common example is a 14 day window on a holiday collection while the storewide default stays at 90 days.
The precedence logic is worth committing to memory, because it decides what your customers see at request time. An override replaces the default or market specific window for any item it matches. Where an item matches more than one override, the shortest matching window applies. Items flagged as final sale cannot be returned or cancelled at all, even when they also match an override. Anything that is neither final sale nor matched by an override falls through to the market specific window, and then to the store default if no market rule exists.
Two constraints carry over from the existing rule set. Self serve returns and cancellations remain a store level switch that applies across all markets, and return rules apply to every order including B2B, with no ability to scope rules by order type.
Why it matters
Return policy is one of the few levers touching conversion, margin and support load at once, and the granularity was coarse until now. Merchants with mixed catalogues set one permissive window, absorbed the cost on categories that should never have carried it, and handled exceptions manually. Overrides move that handling into the rule engine where it is consistent and auditable.
The market dimension is what enterprise teams should plan around first. Statutory minimums differ by jurisdiction, so a single global window is usually either over generous or non compliant somewhere. Layering collection level overrides on top of market rules lets you hold a compliant baseline per market and still tighten specific ranges. Teams running several markets should read this alongside our guidance on using Shopify Markets for global expansion before restructuring policy.
Role-specific impact
- Marketers: promotional planning gains a real control. A clearance drop can carry a short window without weakening the storewide promise, but the shortened terms belong on the product page and in campaign copy, not at the returns portal.
- Developers: if your storefront or headless build renders return terms, read them from the configured rules rather than hardcoding per template. The correct window is now item and market dependent, and a stale hardcoded value becomes a support dispute.
- Store admins: collection membership is now policy enforcement. Adding a product to a collection that carries an override silently changes that product's return terms, so collection hygiene needs the same review discipline as pricing.
Use-case example
Real-world scenario
A home goods brand selling into the UK, EU and US runs a 90 day default window it never intended for seasonal decor. Post holiday returns on that range reach roughly 18 percent of units, much of it arriving in February against product that cannot be resold at full price. A 14 day override on the Holiday 2026 collection in each market, statutory minimums respected, targets that behaviour rather than the whole catalogue. The likely outcome is seasonal return rate compressing toward single digits while the advertised storewide 90 day promise stays intact.
Implementation checklist
- Inventory the SKU classes that genuinely need a different window: seasonal, clearance, perishable, made to order, hygiene sensitive.
- Confirm the statutory minimum return period for each market before setting any override below your default.
- Target collections rather than individual variants wherever possible, so the rule survives catalogue churn.
- Model overlaps deliberately, remembering that the shortest matching override wins.
- Audit final sale flags, the correct tool for non returnable items, since final sale overrides everything.
- Update the written policy page and product page messaging to match the configured rules.
- Test a request per market and override class in the returns flow, then brief support on the precedence order.
FAQ
Q: What happens when an item matches two different overrides?
A: The shortest matching return window applies. Overlapping overrides do not error, so model the intended outcome before configuring rather than relying on order of creation.
Q: Can we apply different return windows to B2B orders?
A: Not by order type. Return rules apply to all orders, including B2B, and company location staff can submit requests. Where wholesale ranges need different terms, isolate them in dedicated collections and apply overrides there.
Resources
Setting up return and cancellation rules
Need guidance? Talk to Makro.