How It Works

1. Select Return Policies to Override

   • Choose which return policies the override should apply to.

   • This allows you to target exceptions without affecting all returns.
     
     

2. Set Conditions for the Override

   • By product: Apply overrides to specific SKUs, collections, or product tags.

   • By order: Trigger overrides based on order tags or order dates.
     
     

With Eligibility Overrides, you get precise control over exceptions—ensuring your customers and your team get exactly the flexibility they need.

Why Use Eligibility Overrides?

• Handle special cases: Give exceptions to certain products, collections, or orders.

• Maintain standard rules: Keep your general return policies intact while managing exceptions.

• Save time: Automate overrides rather than manually adjusting returns.

• Improve customer experience: Allow exceptions without creating confusion.

Tips & Best Practices

• Use overrides sparingly: Only for cases that truly need an exception.

• Combine with return policies and workflows: Overrides work seamlessly with your existing setup.

• Document your rules: Keep a clear record so your team knows why an override exists.

• Review regularly: Ensure overrides still match your business goals and seasonal changes.

FAQs

Q: Can I apply an override to multiple return policies at once?
A: Yes! Select one or more return policies for the override to apply to.

Q: Can I override rules for specific products only?
A: Absolutely. Use SKUs, collections, or product tags to target the override.

Q: Can overrides depend on order details?
A: Yes. You can trigger overrides based on order tags or order dates.