Days After Purchase Date as a Condition for Return Rules

1) Overview

You can now build return rules that trigger based on the number of days since the purchase date (not delivery date). This lets you enforce time-based eligibility, fees, or methods—e.g., “Free returns within 14 days of purchase; 15–30 days incur a fee; after 30 days not eligible.”

2) Before You Begin

• You have Admin access to WeSupply.
• Your Return Logics & Policies are already created (or you’re ready to create one).
• You know the time windows you want to enforce (e.g., 0–14 days, 15–30 days, >30 days).

3) Step-by-Step Instructions

Step 1 — Open Return Logics & Policies

1. Go to Settings → Return and Warranty Methods → Return Logics and Policies.
2. Click an existing Return Logic to edit, or choose Create Return Logic.
    

Step 2 — Add the “Days after Purchase Date” Condition

1. In Conditions, click Add Condition.
2. From the condition drop-down, select Days after Purchase Date.
3. Choose an operator (e.g., is less than, is between, is greater than or equal to).
4. Enter the day value(s) to define the window (e.g., 0–14).
5. (Optional) Combine with other conditions (SKU, category, price, address, etc.) as needed.
   

Step 4 — Save & Test

1. Click Save on the return logic.

4) Example Configurations

• Free within 14 days, fee after 15–30 days
  • Rule A: Days after Purchase Date is between 0–14 → Allow, $0 fee
  • Rule B: Days after Purchase Date is between 15–30 → Allow, $10 fee
  • Rule C: Days after Purchase Date ≥ 31 → Disallow (policy message)

5) Best Practices

• Name clearly: Use rule names that match your policy language (e.g., “0–14 days (Free)”).
• Avoid overlaps: Make windows mutually exclusive to prevent collisions.
• Communicate policy: Reflect the same windows on your Returns Policy page to reduce confusion.
• Test edge days: Validate days exactly on the boundary (e.g., day 14, day 15, day 31).
• Combine wisely: Pair with item/category conditions for nuanced policies (e.g., electronics vs. apparel).

6) Troubleshooting / FAQ

The wrong rule is triggering.

• Check for overlapping ranges or rule priority/order. Ensure only one rule matches a given day count.

Customers see “Not Eligible” too early.

• Re-check your operator and values (e.g., between 0–14 includes day 14; less than 15 also works).
• Verify the system’s purchase date source (order date vs. other timestamp) is what you expect.

We need a different policy by region.

• Add additional conditions (shipping country/region/ZIP) alongside Days after Purchase Date.

Fees look incorrect.

• Confirm the fee type (fixed vs. percentage), tax settings, and any per-method overrides.

7) Summary

Create or edit a Return Logic, add a rule with the Days after Purchase Date condition, set the operator and day range, and define the actions (allow/disallow, methods, fees). Repeat for each window, save, and test with sample orders on boundary days to ensure your policy behaves exactly as intended.