Understanding and Managing Return Logics in WeSupply

WeSupply’s Return Logic feature gives you full control over how returns are handled for different product types and scenarios. By setting conditions, return windows, and priority levels, you can create a flexible, rules-based returns experience that matches your store’s policies.

Why This Feature is Useful

Return Logics allow you to create customized return rules based on product attributes like product type, tags, or price. This means you can allow or restrict returns on a case-by-case basis — such as making gift cards non-returnable, requiring return authorizations for some products, or allowing “keep item” refunds. By setting priorities, you can determine which rules are evaluated first, ensuring your return policy behaves exactly as intended.

How Return Logics Work in Your Account

Here’s a breakdown of how return logics typically appear and function in your WeSupply account:

1. Non-Returnable Logic
   • Used to block specific items from being returned (e.g. gift cards).
   • Any item that matches the conditions (such as a product type = gift card) will not be eligible for return.
2. Default Return Logic
   • Applies to all items that don’t meet the criteria of any other return logic.
   • Example configuration:
     • Return window: 30 days
     • Requires return authorization
     • Exchanges and replacements: disabled
     • Instant credit: disabled
     • No image or comment required
     • Customer keeps item (no physical return needed)
3. Cloned Return Logic
   • You can clone any existing return logic to create a new one with similar settings.
   • Helpful if you want to make small adjustments without starting from scratch.
   • Note: Only active return logics are evaluated—cloned ones must be activated to take effect.
4. Setting Priorities
   • Lower priority numbers are checked first.
   • For example, if the Non-Returnable logic is set to priority 1, it’s evaluated before any others.
   • It’s recommended to assign your Default return logic the highest number (e.g. 100) so it only applies if no other return logic conditions are met.
   • If you're creating a specialized return logic (e.g. for exchanges only), assign it a lower priority number to ensure it’s checked before the default.

By organizing your return logics with clear conditions and priorities, you ensure that each return request follows the correct flow — improving efficiency and customer satisfaction.

Need help setting up or reviewing your return logic setup? Contact our support team and we’ll be happy to assist!