Eligible order statuses
Last updated November 20, 2026
Two simple rules decide whether a given WooCommerce order can file a return through Gorilla Returns:
- The order’s status must be in your eligible statuses list
- The order’s date must be within your return window
Both are configurable at Returns → Settings → Portal. This article covers how each one works and what the customer sees when their lookup fails.
Eligible order statuses
By default, four statuses are eligible: completed, processing, shipped, delivered. The reason all four are on by default (rather than just completed) is that most stores running real shipping integrations use statuses beyond WooCommerce core — shipping plugins commonly transition orders through shipped and delivered as the package moves. If your eligible list only includes completed, customers with a shipped-but-not-marked-complete order get an error they shouldn’t get.
Configuring which statuses are eligible
Go to Returns → Settings → Portal → Eligible order statuses. You’ll see a checkbox for every registered order status on your WooCommerce install, including custom statuses added by shipping plugins like AST, WooCommerce Shipment Tracking, Trackship, etc. Check the ones you want, save.
If you use a shipping plugin that adds custom statuses (Delivered, Shipped, In Transit, etc.), check those statuses in Pro’s eligibility list too. Otherwise customers whose orders are stuck in your shipping plugin’s “Delivered” status won’t be able to file returns, which they obviously should be able to.
Why NOT include every status
Some statuses should stay off:
- on-hold — payment hasn’t cleared; return requests make no sense
- pending — awaiting payment
- failed — payment failed
- cancelled — order was cancelled before fulfillment
- refunded — order was already fully refunded
These are off by default. Keep them off unless you have an unusual use case.
The return window
The return window is how many days after the order was created a customer has to file a return. Default is 30 days. Set it at Portal settings → Return window (days).
Pro calculates the window from the order’s date_created (when the customer placed it), not from date_completed. This matches what customers intuitively expect (“I bought it 20 days ago”) and avoids edge cases where slow-fulfilled orders start their return clock from the wrong date.
If you want to be more generous with a specific customer or handle an edge case, you can approve returns outside the window by looking up the order in the WooCommerce admin and manually creating an RMA from there (bypasses the portal’s window check).
What customers see when they fail eligibility
Gorilla Returns deliberately shows plain-English, status-specific error messages on the portal lookup screen — not a generic “Sorry, try again.”
Examples:
- “Your order #1032212 is still awaiting payment. Returns can be filed once the order is processed and shipped. If you believe this is an error, please contact us.”
- “Your order #1032212 is currently on hold. Please contact us to resolve this before filing a return.”
- “Your order #1032212 was placed on April 5, 2026 — outside our 30-day return window (which ended on May 5, 2026). Please contact us if there’s a special circumstance.”
- “Your order #1032212 is in status shipped, which isn’t currently set as a return-eligible status. Please contact us for assistance.”
The error gives the customer actionable information — they can see the real reason, which tells them whether to wait, to contact support, or to adjust their expectations.
The lookup log
Every portal lookup attempt (success or failure) is recorded in the Lookup log at Returns → Lookup log. For each attempt you see:
- Timestamp
- Order number the customer entered
- Email the customer entered
- Result (success, eligibility issue, bad request, other)
- A plain-English explanation of what happened
Successful lookups link to the created RMA. Failed lookups show the specific reason they failed. This is incredibly useful for diagnosing why customers aren’t completing the portal flow — you can watch the log in real time during initial rollout to catch misconfigurations (wrong eligible statuses, too-tight return window, etc.).
Filter the log by All / Errors only / Successes only. The most recent 200 lookups are retained; older ones are auto-pruned. Clear the whole log with one click if you want to start fresh.
Common mistakes
Only completed is checked and you use a shipping plugin. Customers whose orders are marked shipped or delivered can’t file returns. Fix: check those statuses too.
Return window is too short. Default 30 is standard for many stores, but if you sell items customers might not inspect for weeks (holiday gifts, bulk orders), consider extending to 60 or 90.
Return window is too long. If you set it at 365 days for marketing reasons, you’ll get requests on orders from a year ago where the item is no longer in your catalog. Consider 60–90 days as the sweet spot.
Confused customer feedback. If customers tell you “the portal doesn’t work for my order,” check the lookup log first. It’ll tell you exactly what happened.