Why an item can't be returned

A customer emails saying your returns page won’t let them send something back. They’re annoyed, and you can’t immediately see why.

There are six things that can cause it, and they’re checked in a fixed order. Work down the list and you’ll find it.

The six checks, in order

flowchart TD
    A[An item on the order] --> B{Any left to return?}
    B -- No --> X[Greyed out]
    B -- Yes --> C[Is the product or order blocked?]
    C --> D[Does a return policy cover it?]
    C --> E[Does a warranty cover it?]
    D --> F[Is the customer allowed or blocked?]
    E --> F
    F --> G[Do your workflows allow it?]
    G --> H{Covered by either?}
    H -- No --> X
    H -- Yes --> I[They can pick it]

1. Is there anything left to return?

If they bought three and already sent one back, only two are available. An item already sitting in another open request can’t be claimed twice.

2. Have you blocked it?

Some things never come back, and you may have said so already. Items can be blocked by their SKU, their tags, the tags on the order, or answers to custom questions. Warranties can be blocked at the order level too — an order tag saying “no more warranty claims on this one”.

If a final-sale product is refusing to return, this is almost always why.

3. Does a return policy cover it?

Richpanel looks for a policy matching where the customer is returning from — their country, sometimes their state. That policy decides how long they have, whether the clock starts when the order shipped or when it arrived, which options they’re offered, and what fees apply.

If they’re past the window, normal returns stop here. Nothing further down the list will bring them back, unless a workflow has extended the window for them.

4. Does a warranty cover it?

Warranties are checked separately, and they don’t care about your return window. A warranty can apply based on when the order was placed, when it arrived, where it’s going, or what the product is.

So an item can be months past its return window and still be claimable — if a warranty covers it. This surprises people in both directions.

5. Is this customer allowed or blocked?

You can allow or block specific people by email or order number. A block stops them using both normal returns and warranties. An allow entry lets a specific person do something they’d otherwise be refused.

If someone has both, the allow entry wins for whatever it covers. Try not to create that situation unless you mean to.

6. Do your workflows allow it?

Finally, your own rules run. A workflow can shorten or extend the window, remove options, insist on a human looking at it, approve it outright, demand a photo, change the fees, or send it to a different address. When several apply, the higher one in your list goes first.

See Workflows.

When the item’s fine but an option is missing

Sometimes the item is selectable and it’s a specific choice that’s absent. That’s usually one of these:

• Your policy or warranty doesn’t offer that option.
• A workflow has taken it away.
• Swaps are switched off, or the more advanced swap options are.
• They’ve already hit the limit on swaps.
• The item is swap-only, so money back was never available.
• Nothing suitable is in stock to swap to.

That last one catches people constantly. If the only size left is the one they’re returning, there’s nothing to offer.

What wins when rules disagree

At the moment of submission, things are applied in this order — later steps can’t undo earlier ones:

1. Your workflows
2. The warranty policy
3. The return policy
4. Your swap settings
5. What the customer chose
6. Default behaviour

What this means: a workflow beats a policy, and for warranty claims, the warranty policy beats your normal return policy. If a policy change isn’t taking effect, check whether a workflow is overriding it.

Questions people ask

A customer is past the window but I want to let them return anyway. How?

Add them to your allow list by email or order number, or write a workflow that extends the window for whatever describes their situation. The allow list is quicker for one person; a workflow is better if you’ll keep doing it.

I changed my return policy but nothing happened. Why?

Check your workflows first. A workflow beats a policy, so if one is setting the window or restricting options, your policy change is being overridden.

Why can a customer claim on something months out of date?

A warranty is covering it. Warranties are checked separately from your return window and don’t expire with it.

Can I see which rule blocked a particular return?

Not as a single answer, no. Work down the six checks above in order — the first one that fails is your cause, and it’s usually the window or a blocked tag.

A customer bought 3 and returned 1. Why can they only pick 2?

That’s correct — one is already accounted for. Quantities already returned or sitting in an open request aren’t available again.